1) As of today 9/28/17, does TI or anyone else have a DDR3 test application external to CCS similar to something that NXP has?
2) How are others testing DDR3 during bring up before u-boot when they think there might be a DDR issue but without using DDR hardware testers? Need R/W testing quickly, if not also easy to configure, to test DDR3 for possible intermittent behavior or potential noise.
Seeing random failures during booting uboot and can't tell for sure if it is a bad DDR or a uboot relocation issue. But boot fails at different sections of uboot code based on adding printfs in uboot for debugging. So, we wanted to test the DDR3 and make sure ir's functioning properly. It acts like a null pointer issue in a driver where the failure randomly changes to different sections of code at boot time as if memory is getting corrupted.
3) Has anyone seen the above behavior prior to fully coming to a uboot prompt on a custom BBB based board? See the same regardless of using CCS over JTAG or the serial console when trying to boot off a mini SD.
When using CCS and gel files to test all of the DDR, it was estimated to take more than a month for some reason. Not sure why. Just need something quick, if not necessarily easy, that runs on windows that can test the DDR using JTAG or something else. Looking at doing bare metal testing with the memtester, rawhammer, or https://github.com/auselen/down-to-the-bone but all of these are potentially time consuming to convert to bare metal applications or modify for DDR3 testing for random failures.
4) Any additional recommendations?
