Dear Nvidia Technology, we have an AGX ORIN 64GB module that cannot be started, has a stained screen, and is stuck and restarted when swiping l4t36.4. We replaced other modules of the same model and swiped the same system version, but this phenomenon did not occur. We suspect that this module is broken. I have attached the log to the attachment and look forward to your reply
AGX.log (246.7 KB)
Hi,
Based on your log, seems like uuid cannot find.
Could you provide how to flash your device (commands or sdk manager) ?
Thanks
Brush the machine with the command,"sudo ./ flash.sh *** mmcblk0p1 " After the flash prompt is successful, the system may not be able to start, the screen may appear after starting, or it may keep restarting. However, the system was normal after replacing the same model module and brushing the machine in the same environment. The fault will follow the module, so it is determined that it is a module problem
Hi,
Could you provide the log with the successful flash?
We need to compare and find the reason.
Thanks
How do I get the flash log and in which folder is it?
If you use a command to flash, then the log wont’ be saved to any folder.
You need to check the terminal where you run the flash command.
If you use sdkmanager to flash, then there is a “export logs” button on the GUI which can dump out the log.
Also, if you want to check the log on device side, then please use the micro usb port on the NV devkit. Below is the guidance.
Dear NVIDIA technicians, I have attached the flash log. Thank you for your guidance and look forward to your reply.
flash.txt (98.9 KB)
Dear NVIDIA technicians, I have
1111.txt (151.0 KB)
p
ut it in the boot log after I re-refreshed this module. I look forward to your reply.
Dear Nvidia technician, I have provided the log information of this module. When replacing other modules, there is no fault. We can confirm that there is a problem with this module and whether we can go through MRP.
Hi,
But your log indicates it is waiting for you to configure the account.
[ 12.036196] tegra194-pcie 14180000.pcie: supply vddio-pex-ctl not found, using dummy regulator
[ 12.663726] using random self ethernet address
[ 12.663735] using random host ethernet address
[ 12.905954] using random self ethernet address
[ 12.905962] using random host ethernet address
[ 16.822309] tegra194-pcie 141e0000.pcie: supply vddio-pex-ctl not found, using dummy regulator
[ 16.985060] rt5640 8-001c: Device with ID register 0xffff0000 is not rt5640/39
[ 17.010421] nvme nvme0: missing or invalid SUBNQN field.
[ 21.468667] [drm:nv_drm_atomic_commit [nvidia_drm]] ERROR [nvidia-drm] [GPU ID 0x00020000] Flip event timeout on head 0
[ 22.585084] Please complete system configuration setup on desktop to proceed…
Could you run l4t_create_default_users.sh before doing flash and flash again? Also, could you try rel-35 release too?
The log is to initialize, and I have also operated the steps you mentioned, but this module will be stuck, restart, screen display and other phenomena, and I have also tried to brush l4t 35.*** failure will still occur, and there is no problem in replacing other modules, so I judge that this module is the problem and RMA is required
ok then please RMA.
Okay, thank you