We have an issue with Drive AGX kit, we noticed that Xavier A gets stuck while booting most of the time, please find attached the failure log we obtained via minicom
Please note that we flashed the kit (after receiving it) with Drive Software 10.0 (rev.2) using SDK Manager 1.5.0.7774. Flashing was successful however it took very long time (72 minutes for Xavier-B and 82 minutes for Xavier-A). I attached the flashing logs also for your reference
Dear @alaa.mahdy,
Have you done parallel flash or individual flash? Also, do you have this boot struck issue even after flashing again? If not, could you check that and confirm?
I did parallel flashing for both SoCs, The SDK manager doesn’t give an option for flashing individual SoCs
Based on the minicom trace I shared, is there any obvious reason for the failure?
Xavier A-gets stuck most of the time during booting however it did boot fine few times and I could run the prebuilt demos on it. The fact that it some times boot would indicate that the image was written successfully to the flash. I will try to reflash the kit and see if it helps
I tried to reflash both SoCs in parallel and now both of them are stuck, Xavier B is now showing the following error in minicom which indicates that image verification is failing
Dear @alaa.mahdy,
For some reason I don’t have this option
This is strange. You can confirm the version with sdkmanager --ver as I don’t see sdmanager version in GUI. I think it could be due to system resolution due to which you might not be seeing text after Flash. Please check changing resolution and see if other flashing options available.
Could you attach the latest complete logs in ~/.nvsdkm/logs/ folder and ~/.nvsdkm/sdkm*.log
Please find the logs attached, please note that i have two installations
(DRIVE Software 10.0 and DRIVE OS 5.2) I am only trying to to flash DRIVE Software 10.0
Dear @alaa.mahdy,
I notice cannot remove '/home/amahdy/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_DDPX/DRIVEOS/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/_temp_dump/_temp_dump_xxNg1qqwid/flash-images': Directory not empty error in NV_FLASH_XAVIER_PDKFLASH_PARALLEL_COMP.log. Could you check deleting those temp folder and check flashing again
XA seem to be not responding to ADB, the following is part of the attached trace TegraALog_…
Android Debug Bridge version 1.0.36 Revision -android Platform version 7.0 supports 262144 Bytes MAX_PAYLOAD This build is for NVIDIA embedded bootburn Build time : May 16 2017 01:26:13 serial number to adb : 2P1101020000001G30K0 Could not find a device online
Now when i try to boot I get the following trace on the minicom terminals (XB on the left side and XA on the right side)
I am using the cable provided with the Kit, I don’t see how this is relevant to the issue I am facing.
Currently both SoCs are not booting as shown in the screen shots in my previous post, XA seems to be stuck at a very early stage and this would explain why it is not responding to ADB
Flashing seems to be consistently failing at the same point as shown in the logs attached in the previous post
I checked again and found that I am already using a USB2.0 Type A cable (~2 meters long), this is the cable delivered with the kit. Do I need to use a shorter USB2.0 cable ? also do I need to apply the DTB patch provided in the other thread ?
and by checking other threads in the forum it seems that I may have an issue with the PMIC since it seems to be not responding with an ACK. I think this would explain why Xavier A is not responding to the bootburn via ADB because it stuck at a very early stage
