Hi ian, the 4 MB scrambled file is fine. I had that too.
the discriminator parameter to scramble.exe to specify the device is simply "-iriver". I think all irivers (with rockbox up to now) have the same scrambeling. To be drop-dead-sure, you should compare the md5 checksum. That's what it's made for. openssl can do md5 for example And finally, I think things like these should go over to the user list instead of the developers list. Hope that helps, lImbus On 12/9/05, ian douglas <[EMAIL PROTECTED]> wrote: > Don't mind my little conversation with myself ... I'm really not > schizophrenic or anything. Just making notes on what I'm trying, > hopefully someone can spot my mistake. > > $ tools/mkboot -h300 H300-104.bin bootloader-h300.bin H300-104-rockbox.bin > Wrote 0x3fcfd7 bytes in H300-104-rockbox.bin > $ ls -l H300* > -rwxr-xr-x 1 id users 4181975 Dec 8 18:18 H300-104-rockbox.bin > -rwxr-xr-x 1 id users 2909222 Dec 8 17:45 H300-104.hex > -rwxr-xr-x 1 id users 2909222 Dec 7 15:09 H300.hex > $ tools/scramble -iriver H300-104-rockbox.bin H300-104-rockbox.hex > Model H300 series > File encoded successfully and checksum table built! > [EMAIL PROTECTED] /usb $ ls -l H300* > -rwxr-xr-x 1 id users 4181975 Dec 8 18:18 H300-104-rockbox.bin > -rwxr-xr-x 1 id users 4181975 Dec 8 18:20 H300-104-rockbox.hex > -rwxr-xr-x 1 id users 2909222 Dec 8 17:45 H300-104.hex > -rwxr-xr-x 1 id users 2909222 Dec 7 15:09 H300.hex > > I noticed the scramble utility has a -add=H300 option that could be > passed, but when I tried that: > > $ /tools/scramble -add=h300 -iriver H300-104-rockbox.bin \ > H300-104-rockbox.hex > -iriver: No such file or directory > $ > > ... even after grabbing the latest cvs source. > > I just don't want to try flashing a 4MB firmware file if it's going to > kill my H320, I've got a 90 minute commute ahead of me... :o) > > -id >
