Eric Cooper wrote on 20101212: > On Sun, Dec 12, 2010 at 08:16:26PM +0100, H wrote: >> Uploading a new zImage and ramdisk.gz with 'fis load' will erase the >> existing entries. Is there a way to save these first somewhere ? > Does the bootloader have a "flash_dump" command? If so, you can use > this to dump the contents in hex, and then convert that back to binary.
Interesting idea. RedBoot has this : Display (hex dump) a range of memory x -b <location> [-l <length>] [-s] [-1|2|4] Reading http://ecos.sourceware.org/docs-latest/redboot/dump-command.html I assume I don't need the [-s] [-1|2|4] options. RedBoot> fis list Name FLASH addr Mem addr Length Entry point RedBoot 0xF0000000 0xF0000000 0x00040000 0x00000000 RedBoot config 0xF1FC0000 0xF1FC0000 0x00001000 0x00000000 FIS directory 0xF1FE0000 0xF1FE0000 0x00020000 0x00000000 rammode 0xF0060000 0x00200000 0x00040000 0x00200000 log 0xF0040000 0xF0040000 0x00020000 0x00000000 naskey 0xF00A0000 0xF00A0000 0x00020000 0x01008000 zImage 0xF00C0000 0x01008000 0x00200000 0x01008000 ramdisk.gz 0xF02C0000 0x01800000 0x00400000 0x01800000 vendor 0xF06C0000 0xF06C0000 0x01880000 0x01800000 wmdata 0xF1F40000 0xF1F40000 0x00080000 0x01800000 The fis list mentions a 'FLASH addr' and a 'Mem addr' ... which one would be the one to use as start for my hex dumps ? Fis list also mentions an 'Entry point'. No idea what that is, my google searches did not help either. Anyone ? I've tried the 'FLASH addr' starting point of the ramdisk.gz entry : RedBoot> x -b 0xF02C0000 -l 0x00400000 F02C0000: 1F 8B 08 08 F3 D9 E7 45 02 03 72 61 6D 64 69 73 |.......E..ramdis| F02C0010: 6B 00 EC 7C 0D 60 54 D5 B5 F5 99 64 12 02 06 0C |k..|.`T....d....| ... I'll try to clean this up and feed it so a hex->binary converter (hints anyone ?) and see if gunzip likes the result, if so it should be OK I hope :) -- Hans Lambermont -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
