I’m going to try Jetpack 7.2 to see if I get any luck.
I have lots of cool projects I want to do, but I can’t get this Orin nano board working at all.
Quite frustraing.
Maybe @DavidDDD @kayccc you have other ideas. I don’t have an Ubuntu machine to use. So that is not an option, I’m not about to buy a new computer for this board. I see WSL is not a path forward eiteher, so I think I need to stick with WIndows SDK manager.
Please let me know what to try, it has been 6 months and I can’t get the board working at all.
Regards,
Andrei
The ClawBox ( ClawBox.com) is a prepackaged ready to run openclaw on Jetson Orin super nano solution - they’ve even recently migrated the need for a host pc to access terminal. This will allow 99.9+ % working from iPad web access to headless ClawBox. The 0.1% was larger maybe 5% - 10% a few months back. So It work on it’s own. After running it March through April , decided to do full Jetson Orin super nano install- how difficult could this be right? I’m no longer in Windows world, have Apple & raspberry pi 5 products. Raspberry Pi 5 will support the ongoing cli work that ClawBox has now internalized. Still that’s not 100%.. that’s where the choice of PC host is yours & not necessarily mine. Ubuntu 24.04 (ARM) was my goal for the SDK manager on arm64 processors. Look at “Base SDKs Host Operating System Compatibility Matrix” & pick you existing pc or prospective new pc host. My choice of orange pi 6+ is to get Ubuntu 24.04(arm). The Jetson, orange & raspberry all share Linux so no reason to go back to windows in my situation. You’re in an entirely different position & maybe Windows is your host pc path. Now I’ve got the Ubuntu host running 24.04 and the Jetson nano in warranty return to NVIDIA, so my testing of Ubuntu 24.04 arm64 host is on hold until NVIDIA returns my Jetson nano. The raspberry is not a Ubuntu device it’s a Debian trixie OS so not the 24.04 host. My ClawBox sits at Ubuntu 22.04 / jetpack6.x thus cannot at as host for jetpack 7.x install. Both rpi5 & ClawBox are running openclaw currently but cannot support the Jetson Orin super nano install project.
So I was able to flash the latest jetpack 7.2.1 through a usb onto my microSD card but not my NVME SSD -
I see this when I list the devices
sudo lspci | grep -i nvme
sudo dmesg | grep -i pcie
[ 0.000000] Kernel command line: root=PARTUUID=98ee5e16-5ef2-490f-9e09-a9a83436bb6c rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 firmware_class.path=/etc/firmware fbcon=map:0 video=efifb:off efi_pstore.pstore_disable=1 pstore.backend=ramoops efi=runtime pci=pcie_bus_perf nvme.use_threaded_interrupts=1 bl_prof_dataptr=2031616@0x267210000 bl_prof_ro_ptr=65536@0x267200000
[ 4.268259] tegra194-pcie 14100000.pcie: Adding to iommu group 4
[ 4.269970] tegra194-pcie 14100000.pcie: host bridge /bus@0/pcie@14100000 ranges:
[ 4.270174] tegra194-pcie 14100000.pcie: MEM 0x2080000000..0x20a7ffffff → 0x2080000000
[ 4.270399] tegra194-pcie 14100000.pcie: MEM 0x20a8000000..0x20afffffff → 0x0040000000
[ 4.270622] tegra194-pcie 14100000.pcie: IO 0x0030100000..0x00301fffff → 0x0030100000
[ 4.271146] tegra194-pcie 14100000.pcie: iATU: unroll T, 8 ob, 2 ib, align 64K, limit 32G
[ 4.484255] tegra194-pcie 14100000.pcie: PCIe Gen.1 x1 link up
[ 4.596255] tegra194-pcie 14100000.pcie: PCIe Gen.1 x1 link up
[ 4.596643] tegra194-pcie 14100000.pcie: PCI host bridge to bus 0001:00
[ 4.597831] pci 0001:00:00.0: [10de:229e] type 01 class 0x060400 PCIe Root Port
[ 4.602649] pci 0001:01:00.0: [10ec:c822] type 00 class 0x028000 PCIe Endpoint
[ 4.724048] pcieport 0001:00:00.0: Adding to iommu group 4
[ 4.737766] pcieport 0001:00:00.0: PME: Signaling with IRQ 179
[ 4.751216] pcieport 0001:00:00.0: AER: enabled with IRQ 179
[ 4.761869] tegra194-pcie 14160000.pcie: Adding to iommu group 6
[ 4.772602] tegra194-pcie 14160000.pcie: host bridge /bus@0/pcie@14160000 ranges:
[ 4.781007] tegra194-pcie 14160000.pcie: MEM 0x2140000000..0x2427ffffff → 0x2140000000
[ 4.789488] tegra194-pcie 14160000.pcie: MEM 0x2428000000..0x242fffffff → 0x0040000000
[ 4.801730] tegra194-pcie 14160000.pcie: IO 0x0036100000..0x00361fffff → 0x0036100000
[ 4.814903] tegra194-pcie 14160000.pcie: iATU: unroll T, 8 ob, 2 ib, align 64K, limit 32G
[ 5.916258] tegra194-pcie 14160000.pcie: Phy link never came up
[ 6.916256] tegra194-pcie 14160000.pcie: Phy link never came up
[ 6.923159] tegra194-pcie 14160000.pcie: PCI host bridge to bus 0004:00
[ 6.961841] pci 0004:00:00.0: [10de:229c] type 01 class 0x060400 PCIe Root Port
[ 7.104978] pcieport 0004:00:00.0: Adding to iommu group 6
[ 7.123377] pcieport 0004:00:00.0: PME: Signaling with IRQ 182
[ 7.136316] pcieport 0004:00:00.0: AER: enabled with IRQ 182
[ 7.183708] tegra194-pcie 141e0000.pcie: Adding to iommu group 8
[ 7.261791] tegra194-pcie 141e0000.pcie: host bridge /bus@0/pcie@141e0000 ranges:
[ 7.269476] tegra194-pcie 141e0000.pcie: MEM 0x3000000000..0x3227ffffff → 0x3000000000
[ 7.280049] tegra194-pcie 141e0000.pcie: MEM 0x3228000000..0x322fffffff → 0x0040000000
[ 7.298330] tegra194-pcie 141e0000.pcie: IO 0x003e100000..0x003e1fffff → 0x003e100000
[ 7.298674] tegra194-pcie 141e0000.pcie: iATU: unroll T, 8 ob, 2 ib, align 64K, limit 32G
[ 8.780363] tegra194-pcie 141e0000.pcie: Phy link never came up
[ 9.780257] tegra194-pcie 141e0000.pcie: Phy link never came up
[ 9.780351] tegra194-pcie 141e0000.pcie: PCI host bridge to bus 0007:00
[ 9.780402] pci 0007:00:00.0: [10de:229a] type 01 class 0x060400 PCIe Root Port
[ 9.783117] pcieport 0007:00:00.0: Adding to iommu group 8
[ 9.783234] pcieport 0007:00:00.0: PME: Signaling with IRQ 185
[ 9.783345] pcieport 0007:00:00.0: AER: enabled with IRQ 185
[ 9.795710] tegra194-pcie 140a0000.pcie: Adding to iommu group 38
[ 9.904741] tegra194-pcie 140a0000.pcie: host bridge /bus@0/pcie@140a0000 ranges:
[ 9.904771] tegra194-pcie 140a0000.pcie: MEM 0x3240000000..0x3527ffffff → 0x3240000000
[ 9.904782] tegra194-pcie 140a0000.pcie: MEM 0x3528000000..0x352fffffff → 0x0040000000
[ 9.904787] tegra194-pcie 140a0000.pcie: IO 0x002a100000..0x002a1fffff → 0x002a100000
[ 9.905128] tegra194-pcie 140a0000.pcie: iATU: unroll T, 8 ob, 2 ib, align 64K, limit 32G
[ 10.120261] tegra194-pcie 140a0000.pcie: PCIe Gen.1 x1 link up
[ 10.228267] tegra194-pcie 140a0000.pcie: PCIe Gen.1 x1 link up
[ 10.228374] tegra194-pcie 140a0000.pcie: PCI host bridge to bus 0008:00
[ 10.228432] pci 0008:00:00.0: [10de:229c] type 01 class 0x060400 PCIe Root Port
[ 10.231310] pci 0008:01:00.0: [10ec:8168] type 00 class 0x020000 PCIe Endpoint
[ 10.245061] pcieport 0008:00:00.0: Adding to iommu group 38
[ 10.245159] pcieport 0008:00:00.0: PME: Signaling with IRQ 242
[ 10.246209] pcieport 0008:00:00.0: AER: enabled with IRQ 242
I think this means the NVME link is up but maybe my SSD is not compatible?
Hello … The installation fails on an Orin Nano Super when using the USB flash drive that is now in the documentation as fully supported and that seems to be where there are quite a few people experiencing the difficulty with subiquity failing; using the USB approach since many of us simply do not have an x86 Ubuntu computer on which to install SDK Manager.
But this Usb issue seems to have been open for about 6 weeks now that I can see but Nvidia has not yet provided a workable USB install solution, in part because once the system reaches that point one cannot reboot the machine into the working state that it was previously.
When will Nvidia actually have a workable solution ? For the documented USB flash drive installation ? From what I am seeing in the forum there are issues on more than one Orin device, this does not look good for Nvidia frankly, first that it fails and second that it is taking so long to provide a fix and have that corrected version posted at the download hyperlink.
If I was new to Nvidia and considering buying one of the Orin devices, and if someone told me about all this, then I would probably just buy something else, who needs the hassle of such broken software.