Hi kayccc，
Thank you for your prompt reply. It is custom carrier board. JetPack version is 4.5. flash conf file is 3509-0000+p3668-0001-qspi-emmc.conf. device use internal emmc to boot. I don’t know eMMC’version. how to get it?
I am not sure if you really know what yourself is talking about.
The logic here is
If the board is in “problem state”, then clarify if this is software or hardware → if you don’t know how to clarify, then flash it with sdkmanager… so that at least the software is correct… → if your board cannot even flash with sdkmanager, then it is hardware issue…
Your current situation sounds like you just plug in a module and you don’t know what was installed on that module. You hit error and you come here to ask question.
My expression is not accurate enough. Let me describe the problem phenomenon again. The board has been flashed by running flash.sh. the board could boot after flashing image.
But the board couldn’t boot yesterday.I wish you to analyze what causes the board could not boot.
In addition, the board that Cannot boot can boot after re-flash the image. it is not hardware that it is not issue. Up to now, four devices have the same problem.
Then you need to at least provide a method to reproduce issue. Also, try to reproduce issue on devkit and see if this is related to your custom board.
We are not some kind of fortunate-teller that can know what happened on your side by just reading a partial log.
From your partial log, I can only see some SMD partition got broken.
The funny thing here is I don’t even know which software release you are using. You better clarifying more detail about your issue in the beginning. But not let us ask you again. Please remember that we are not your friend or colleague. We don’t know this info.