Other Parts Discussed in Thread: OMAPL138
We recently added some of the secure boot L138 processors to our SOMs. This week I noticed that our automated test tool kept failing in u-boot when we were trying to run various setup commands like setting bootcmd or boot args. And configuring our factory config.
After some investigation it appears to be limited to the new secure boot modules. They appear to be dropping characters sent to them from our automated tool. I assume that we are somehow overflowing their uart buffers though I'm not sure why this would be the case as this same code has worked for thousands of L138 modules for 10 years. And continues to do so in my testing this week. I am using the same u-boot binary for both but the ubl is different.
Is there any known issues with the secure boot version of the L138 modules?
Is there a tool to dump the clocks, etc so I can compare a working non-secure boot modules with a secure boot module to make sure the ubl is setting them up the same?
