Home › Forums › MultiConnect OCG › Flashing new Image unsuccessfully
Jeff Hatch.
Samuel ChenHi,
As I am flashing the MTCDP-H5 with the uImage/rootfs and touch do_flash_upgrade, the following message occurs one out of every four times. I am forced to power cycle the machine in order for the machine to reboot. After power cycling, the MTCDP-H5 would boot successfully. Is there a file system corruption or something I need to be aware of ?
Thanks,
Samuel
Writing data to block 290 at offset 0x2440000
Writing data to block 291 at offset 0x2460000
Writing data to block 292 at offset 0x2480000
Writing data to block 293 at offset 0x24a0000
Rebooting…
Node CRC 0d504577 != calculated CRC 84d5e85e for node at 005c6a48
Node CRC f42ce857 != calculated CRC 3b4787ef for node at 005c74cc
Node CRC cde27217 != calculated CRC e07cdae1 for node at 005c7f60
Node CRC be0d68d1 != calculated CRC 16de5df7 for node at 005c89e8
Node CRC cde27217 != calculated CRC e07cdae1 for node at 005c7f60
Kernel panic – not syncing: Attempted to kill init!
[<c002d190>] (unwind_backtrace+0x0/0xe0) from [<c02b6f48>] (panic+0x58/0xdc)
[<c02b6f48>] (panic+0x58/0xdc) from [<c003d660>] (do_exit+0x5c/0x664)
[<c003d660>] (do_exit+0x5c/0x664) from [<c003dfb0>] (do_group_exit+0xb8/0xec)
[<c003dfb0>] (do_group_exit+0xb8/0xec) from [<c00483e0>] (get_signal_to_deliver+0x3b0/0x40c)
[<c00483e0>] (get_signal_to_deliver+0x3b0/0x40c) from [<c002af04>] (do_signal+0x68/0x5a4)
[<c002af04>] (do_signal+0x68/0x5a4) from [<c002b978>] (do_notify_resume+0x18/0x4c)
[<c002b978>] (do_notify_resume+0x18/0x4c) from [<c0028ecc>] (work_RomBOOT
Jeff HatchSamuel,
Are you using the same images to write to flash each time? Is this one out of every four times failure happening on the same device each time? This is a kernel panic and it appears to be happening on the reboot when it is trying to run the ROM boot code.
If I can get some time to look into this I might be able to give you more information. If this is causing serious issues for you, file a support portal case at:
Jeff