I'm attempting to resurrect a NetBotz 420 that's boot-looping in U-boot with a "Bad Data CRC".
U-Boot 1.1.4 (Jun 13 2006 - 19:04:01) CPU: MPC885ZPnn at 120 MHz: 8 kB I-Cache 8 kB D-Cache FEC present Board: NetBotz Cobra, Rev 0000 10MHz XTAL Watchdog enabled I2C: ready DRAM: 64 MB FLASH: 2 MB In: serial Out: serial Err: serial DOC: DiskOnChip Millennium Plus @ 0x7F000000, 32 MB RTC: Philips PCF8563 Net: FEC ETHERNET PCMCIA:No Card Found Hit any key to stop autoboot: 0 ## Booting image at ffe00000 ... Image Name: Created: 2006-06-14 0:05:20 UTC Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 922658 Bytes = 901 kB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... Bad Data CRC NetBotz>
My first thought is to reflash the kernel image but I can't seem to find a copy of the firmware anywhere. Can someone point me in the right direction?
Solved! Go to Solution.
Hi @jkhuon ,
If this is indeed an issue with the firmware, a TFTP flash of the system should resolve it. Instructions for that procedure are here:
Please note this mentions the newer units but it should be the same for the older ones as well.
As for the firmware, I've found a copy and put it on box where hopefully you can download it. I was able to download myself using edge but Chrome blocked it due to tftp.exe and a false warning about it. This link should be good for 2 weeks:
Hi, i was wondering if you could provide a working firmware link again? I have the same issue with bad crc.
Hit any key to stop autoboot: 0
## Booting image at ffe00000 ...
Created: 2007-10-31 23:17:43 UTC
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 922648 Bytes = 901 kB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... Bad Data CRC
Any help would be greatly appreciated.
Hi @kentwv You also sent me a direct message (which I saw first) so I sent you a link through that option ...it should be valid for 2 weeks.
If anyone else runs into this, i tried the above linked instructions and the postupg worked, but the rootupg still failed with bad data crc..
After some more searching, i found some instructions that had a "kernupg' command in between thet postupg and rootupg..
I did that and it was successful and then the rootupg worked after as well.
Thanks again to Steve for the files and help.
Discuss challenges and get support in energy and automation with 30,000+ experts and peers.
Over 10,000+ support articles are available to help you find answers to your product and business challenges.
Find peer based solutions to your questions. Provide answers for fellow community members!