If it helps, I am using Ubuntu 18.04 LTS on a virtualbox VM, with close to 60GB of disk allocated, 5.2GB RAM.
I do understand that using a VM to flash is not supported by Nvidia, but I do not have any other choice as this is the only available terminal I can have access to back homeā¦
Thank you and looking forward to receiving some help on thisā¦
Could check to reconect the usb port to your virtalbox VM? you can check with lsusb within the ubuntu, ā** NVIDIA corpā will be appeared on one of the usb port indicating the target jetson device is in the right recover mode be ready to receive the flash command.
khoongweihao@khoongweihao-VirtualBox:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0955:7019 NVidia Corp.
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
@alanz I have just tried flashing the AGX with Jetpack 4.3, and an error occured at 99.8% (second time on 4.3) and exported the logs. Is there a particular name for the log file? When I clicked on export logs and export debug logs, I got 2 zip folders instead, each containing multiple ālogā files. Iām attaching the ones from āSDKM_logs_2020-04-06_23-32-10ā here:
JetPack/SDK Manager will download content before running or installing components. Missing a basic file has me wondering if it is actually an internet access issue from before flash ever starting. Does your VM have full internet access without any special proxy setup?
@linuxdev Yes, I believe so. Is there a way I can check on this further in my terminal? Also, if all else fails, shall I remove all the downloaded files by the SDK Manager, then use SDK Manager to re-download all the files required when flashing JetPack 4.3? Thank you for the continued assistance on this matter.
@alanz Yes I am flashing with the AGX developer kit, not the module. The VMās current total size is 50GB (had to down-size it due to space limitations on my host PC), with actual size 45.59GB. I can increase the disk size, but my host PC may have issues.
Do let me know I I understood your questions right.
@WayneWWW Thanks for the feedback and suggestions. Iāll take a look at the wiki page as you have suggested.
Just to clarify, by native Ubuntu host, do you mean something like Ubuntu 18.04 LTS downloaded (can be from Windows app store) and installed in Windows? I actually do have something like that, which looks like the following:
@WayneWWW Iāve extracted the two possible zipped logs extractable from the sdkmanager. As I cannot upload .zip files here (donāt see the option for me to do so), Iāve added a .log extension to them to get by this limitation. Kindly remove the .log extensions when accessing the .zip folders, which Iāve attached below. For the UART log, I canāt seem to find itā¦ is it within those two zip folders?
A simple Ubuntu terminal is probably insufficient for flash. You basically need a full install of Ubuntu 18.04, but this can be set up as dual boot with Windows. It sounds like you are short on disk space though, and Iād actually advise to install Ubuntu to a new disk and leave the original Windows alone (youād end up picking which to boot to as you start your computer).
Understand that during a flash loopback devices are employed, and that these are more than terminal programs. Loopback requires an actual Linux kernel be running, and a VM will have this, but any standalone terminal which otherwise looks like Linux probably wonāt have that ability.
Note that flashing can probably consume 40GB of space on the host PC without much effort. Actually installing Linux would take a lot of space, and so once youāve installed SDK Manager your VM must be close to being full. In a case where your VM is running out of space, then it is possible some of the content is truncatedā¦including that previously missing file, āicon_retry.svgā. Regardless, a VM tends to be a source of pain.
For the UART log, I canāt seem to find itā¦ is it within those two zip folders?
No, sdkmanager does not provide the uart log.
The UART log is the serial console log from your device. You must use some tools like minicom on your host to read it.
I put the info in the link of general debug page. Please do read it.
To make it more simple to understand, just forget about sdkmanager at this moment. I notice many users new to jetson platform would get confused by it.
Please use flash.sh script on your host directly. As for the info of this script, the wiki page also tells where to find it.
@linuxdev@WayneWWW Thank you for the continued support, feedback and suggestions once again. Do give me some time to digest all the information you have given, so that I do not make some deeper blunder on my end which may make debugging harder. In summary, Iāll address @WayneWWWās points first, then try performing a dual-boot some time later as @linuxdev has suggested.
Thanks again and Iāll be in touch soon once I get the UART log extracted, or when I encounter any hitches (hopefully not).
