Has anyone come across a power-on-self-test, and if so, how to read the results (assuming enough of the system is operational that Linux can boot)?
Thanks,
John
hello john.obendorfer,
each JetPack have being test before release.
may i have more details about your use-case?
thanks
FYI, embedded systems don’t have the usual desktop POST or BIOS/UEFI. Much of this is migrated into the boot software.
Thank you for your prompt response.
We are integrating the TX2 into a product, and I am assisting with development of manufacturing tests for the assembly.
So this was just a general question: is anything done to validate bootloader images before jumping into them; is anything done to test DDR4; is there any systematic test of the board’s hardware features performed at any point prior to launching Linux, by any of the boot loaders?
If so, we’d like to report the results of such tests in our own testing process.
we have similar POST (Power On Self Test) requirements to report the self-test results of DDR, EEPROM, etc. upon startup before bootloading. Is this POST considered a critical path to permit bootloader to proceed with loading kernel images, device trees etc. ? Please share insight. Thanks!
Much has changed since the first question, and the answer usually depends on which particular Jetson model and which software is flashed. However, one thing remains: Jetsons don’t have a BIOS, and thus they don’t have any standard POST. All of this does occur, but it is using software which is stored either in eMMC or QSPI (it depends on the model). In most cases serial console is the method of seeing the log of those actions occurring, e.g., DDR memory training. Some of the newest releases using UEFI would require rebuilding boot software if you want to see the log messages on console during boot. So you really need to ask in the specific Jetson forum for your model with the exact software release you are flashed with.
There will be no POST possible, only logs.