I was doing a project with their AD-3DSMARTCAM1-PRZ, which uses an NVIDIA Jetson Nano SoM with eMMC, product number P3448-0002. There is a custom image at ADI and I was flashing the camera with that one, until one fateful afternoon, when the camera decided not to boot anymore. I suspect that it is in recovery mode, because in dmesg I see “APX” instead of “Linux Tegra” for Product.
I determined, that the problem is with the SoM (when I used a SoM in the camera, about which I knew for sure, that it worked, everything was fine).
I tried flashing the device again with ./flash.sh (this is used by ADI) and I noticed that immediately after the flash I can connect to the SoM with picocom, because a ttyACM0 appears in /dev. I tryed flashing the device with sdkmanager from the docker image provided here for ubuntu 18, using the following command:
The result was similar, I could connect to the SoM via SSH. However, in both cases, after I disconnected the power and I connected it back again, the original error occurred.
I suspect, there might have happened something during the times when I flashed the camera, because I flashed it several times. I am not entirely sure though, that it is a hardware problem or something that I can solve by meddling with some files or registers in Linux, right after flash. If it is a hardware problem, do you know whether it can be repaired or is it just better to buy a new SoM?
I used the ADI carrier with the exposed UART pins. Since the device was in a kind of recovery state, I did not have to force it to flash the image. After the flash, because there were no hardware connections forcing the SoM into recovery, the module booted up. I could connect to it via /dev/ttyACM0. Then, I removed the power supply, and connected it back, but the device was no longer responding.
In the text file below you can see the debug messages corresponding to the flashing of camera and the booting. When I removed the power supply and connected it back, there were no more debug messages jetson_log.txt (124.2 KB)