[Avila] (2347) redboot gone

[David Acker]

Sangsu Baek wrote:
> hellow 
> 
> Below are some parts of  boot log ( last scream of my Gateworks-2347 )
> After 'reboot', the board never wake up !
> I'm guessing that i've blown redboot away !
> Am I right ? 
> 
> 
> regards
> 
> Sangsu Baek
> 
> 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> ...
> ...
> cfi_cmdset_0001: Erase suspend on write enabled
> cmdlinepart partition parsing not available
> Searching for RedBoot partition table in phys_mapped_flash at offset 0x7e0000
> 23 RedBoot partitions found on MTD device phys_mapped_flash
> Creating 23 MTD partitions on "phys_mapped_flash":
> 0x00000000-0x00800000 : ""
> 0x00000000-0x00800000 : ""
> 0x00000000-0x00800000 : ""
> 0x00000000-0x00800000 : ""
> 0x00000000-0x00800000 : ""
> 0x00000000-0x00800000 : ""
> 0x00000000-0x00800000 : ""
> 0x00000000-0x00800000 : ""
> 0x00000000-0x00800000 : ""
> 0x00000000-0x00800000 : ""
> 0x00000000-0x00800000 : ""
> 0x00000000-0x00800000 : ""
> 0x00000000-0x00800000 : ""
> 0x00000000-0x00800000 : ""
> 0x00000000-0x00080000 : "RedBoot"
> 0x00011301-0x6f607670 : "       "
> mtd: partition "        " extends beyond the end of device "phys_mapped_flash" -- size truncated to 0x7eecff
> mtd: partition "        " doesn't start on an erase block boundary -- force read-only
> 0x00080000-0x001c0000 : "zimage"
> 0x001c0000-0x004e0000 : "ramdisk"
> 0x004e0000-0x00736372 : "unallocated"
> mtd: partition "unallocated" doesn't end on an erase block -- force read-only
> 0x00736372-0x00736373 : ""
> mtd: partition "" doesn't start on an erase block boundary -- force read-only
> 0x00736373-0x007e0000 : "unallocated"
> mtd: partition "unallocated" doesn't start on an erase block boundary -- force read-only
> 0x007e0000-0x007ff000 : "FIS directory"
> 0x007ff000-0x00800000 : "RedBoot config"
> i2c /dev entries driver
> TCP bic registered
> 
> ...
> ...
> 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Minimally, it looks like your FIS directory information got corrupted. 
RedBoot writes to this when you create partitions.  The FIS directory 
stores information about all the partitions including start address, 
length, and checksums.
That said, redboot should be able to handle a FIS directory corruption 
due to the use of checksums and other validation checks.  Do you get any 
console output at all on a power cycle at this point?  If not, I would 
erase all of the flash and jtag the redboot partition.
-Ack