Tool/software: TI C/C++ Compiler
This time I encountered a very complicated problem.
I have a batch of equipment, using am3352, software version is PDK6.0, u-boot2011.09 + kernel 3.2.0, using Nandflash for storage system, model is 29F2G08ABACA, MT.
The system I transplanted has been running on more than 1,000 products.
After the equipment has been running for one month, more than 10 systems have failed to start.
The phenomenon is as follows:
1. u-boot.img stopped when starting the kernel.
2. When troubleshooting this problem, I redone the u-boot of the SD card boot, enter the u-boot shell in the SD card u-boot, and execute bootm $ (kernel_addr). This is no problem, exclude Linux kernel problem.
3. I updated the u-boot.img of one of the devices again, and the system runs smoothly. Here, we can all think of the problem with u-boot.img.
4. In the SD card u-boot shell, execute the nand read command to read the data of the problematic u-boot.img, print it out through mw, and read it out, then proceed with the normal u-boot.img Contrast and found no problem.
5. As long as the system is re-upgraded, the phenomenon is gone.
I am very puzzled that 1 and 2 can already infer 3, but 3 is self-contradictory. How can I check this problem.