I am having an intermittent issue while booting production SOMs.
Seemingly at random, I have a SOM failing to boot; I have attached images of the errors(sorry for the bad quality, I could not reproduce it when I was connected over the debug port). It does not matter if I am using a devkit carrier board or my custom carrier board.
Interestingly, sometimes if I leave the SOM in the state at which it gets stuck, it automatically reboots. And when it does that, it generally boots up fine.
Can you see this error with devkit + serial console log?
or are you able to use any method to dump the full log instead of showing me a picture of your screen?
I will try, but as I said, it is very unpredictable to generate the error. I am trying to get a full dump right now, on a new production SOM and SOM that originally gave me this error.
Hopefully it was just something wrong with that specific SOM, and not a general issue.
You should tell what software release you are using in the beginning
If this issue will cause hang and reboot, then it is not a general issue, at least we don’t have users reporting this here.
Sorry about that.
So, after testing on multiple SOMs, using both release 32.5.1 and 32.6.1, and rechecking the device tree, I have found the problem.
It was to do with the DisplayPort lines being left floating on the PCB, and not being disabled in the device tree.
Disabling those lines from the pinmux spreadsheet solved this issue.
It was to do with the DisplayPort lines being left floating on the PCB,
If this is due to such problem, then why you said “t does not matter if I am using a devkit carrier board or my custom carrier board.” from the beginning? You also changed the DP lines on the devkit?
