Part Number: TDA4VH-Q1
When performing powercycle, I occasionally found that the startup got stuck in U-Boot, and the data in norflash had been tampered with. Through the debugger, it was discovered that when U-Boot started, an error A occurred fi rst, and then the error handling would enter do_sync. There is a bug in do_sync This will trigger a series of nested errors. During this bunch of nesting, the SP pointer points to the mapping space of norflash, modifying the data of Norflash.
In the attachment, we have fixed do_sync, added some crash log records, and re-reproduced the scene of error A. Now, I would like to take A look at why error A occurred
we just change the chip selects/ranks from 2 to 1,and multi DDRSS interleave memory size from 32GB to 16GB