- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
Hi ,
I am facing an issue in the bootup of my AM3354 (custom) board after performing a software update which involves an MLO copy from USB to SD card.
We prepare an SD card with the MLO file in the root directory and application files are placed in a separate directory. On a normal power up the board boots up without a hitch and launches the application.
After performing an update, the following happens:
The ROM bootloader prints "CCCCC" on the debug port indicating that the MLO is not found however the SD card contains the valid MLO file in the root directory.
The copy operation from the USB to SD card goes through without any issue as we have validated the MD5 hash of both the files (in USB drive and SD card). We feel the issue might have something to do with the FAT32 filesystem on the SD card getting messed up? A software update with only the "application binaries" being copied over has no issues (board boots up with new application binary) but the moment we try to copy the MLO as well we run into this problem.
To recover from this issue, all we do is plug the SD card into Windows PC and run the built-in check disk utility, which says that "No problems were found on the device or disk. It is ready to use". After this we plug the card back into the board and it boots up fine
We suspected the MBR (Master Boot Record) might have something to do with this issue but we were able to read the 512 bytes from the SD card before and after the check disk utility ran. Both the MBR's were same except the SD card did not boot before and now after running checkdisk it booted up successfully.
Could there be anything else that we are "corrupting" in the FAT32 file system while copying the MLO that prevents the TI-ROM bootloader from detecting the MLO and booting up
