Hello all,
First of all sincerest apologies for the newbie questions …googling gives me varied answers.
I have gotten 4 devices 3 seem to be xavier nx with carrier cards and one is nano dev kit ( going by part number searches )
I have tried resetting and using ubuntu 24.04 to get sdk going but still struggling.seems i need 20.04 ( ?) Question i have is
a) whats the best way to get them reset and have very lightweigt os going on these
b) are they good for running either ollama type or frigate
dont know what else i can use these for .
First one question to confrim,
Is your device a Xavier NX or AGX Xavier?
Host PC with Ubuntu 18.04 (Recommended)
Since your device is either a Jetson Xavier NX or Jetson Nano, which are compatible with JetPack 4.x and 5.x, it is advisable to use Ubuntu 18.04. For further details, you can consult the Compatibility Matrix.
Using the Docker SDK Manager
While using the Docker SDK Manager is an option, be aware that USB passthrough issues might arise. Resolving these problems could require significant time and effort.
Since Ollama and Frigate are third-party libraries, some users have shared their experiences using them.
Additionally, the Jetson Nano lacks sufficient memory to run LLM. Use Xavier NX instead.
The one i am currently working on first is " NVIDIA Jetson Xavier NX Developer Kit" part number 945-13450-0000-000 … found a site with pin info and have tried powering on to reset …doesnt seem to take Connecting power and reset buttons to Jetson Nano - Dots and Brackets: Code Blog this is what i think might be the right pinout …when i short the 2 pins when running it resets but force recovery doesnt seem to work . i dont know if i am doing it the right way but i cannot power it on with barrel jack without shorting the two pins that say "short these to disable usb power " or something like that … so when i short them i can power on from the barrel jack and stays on nvidia logo … i have an sd card slot so i downloaded the sdcard image and it doesnt seem to do anything
once i get this going will try others thanks
Just adding that when you see L4T, this is just what you would call Ubuntu once you add the NVIDIA drivers. You can find an L4T release on a running Jetson with “head -n 1 /etc/nv_tegra_release”. From there you can go to this URL to get to the content which is specifically for that release: https://developer.nvidia.com/linux-tegra
You can also go to that URL to pick an L4T release. You’ll find that Xavier and Orin and just plain “old” Nano (not Orin, not Xavier, not TX2) all have different releases which are supported. Once you are certain of which model you have you can use that chart to find the newest L4T release it can handle.
Incidentally, these are equivalent:
L4T R32.x is Ubuntu 18.04. Uses the kernel source at the above URL.
L4T R35.x is Ubuntu 20.04. Uses the kernel source at the above URL.
L4T R36.x uses mainline kernel, and is Ubuntu 22.04.
Something to reduce confusion when looking at Jetson models and flashing requirements…
Some Jetsons have eMMC memory. If there is an SD card slot on those models, then the slot is on the carrier board, and not on the module. Many of the smaller form factor Jetsons have a “developer’s kit”, and those have an SD card slot on the module, not on the carrier board. This latter SD card model does not have eMMC memory. However, the SD card models do have QSPI memory on the module itself.
Jetsons do not have a true BIOS. They do have to go through setting up power rails and clocks and such to boot, and they still have that content in the form of software rather than being in a dedicated BIOS. This boot content must be present and compatible with the release used for the operating system itself.
That QSPI of an SD card model needs to be flashed once for a given “major” release, and then the SD card can have an image from any release of that major release. For example, an Xavier is compatible with L4T R32.x and L4T R35.x. If you have an SD card model without eMMC (probably you do), then if the module has been flashed once with R35.x, then any SD card for R35.x will work even with minor release versions changing. That same Jetson could not run an R32.x on the SD card because the major release differs. One would have to flash the module’s QSPI to R32.x for an SD card with R32.x to work. Once R32.x is on the QSPI early boot content an SD card from R35.x would fail to boot. You would then flash the QSPI with R35.x if you are switching SD card release.
Incidentally, one of the reasons why Orin is interesting is because it uses the mainline kernel, and is fully UEFI compatible (there is no BIOS, but once it reaches the “hardware abstraction” phase, the boot chain becomes more standardized; earlier models not using full UEFI are completely custom). Once you have UEFI compatibility your ability to customize boot goes up dramatically. This also includes the ability to standardize, not just customize. R36.x+ is required for this, and only Orin does this at this point in time.
Is your host PC an actual Ubuntu 18.04 or 20.04 system? Or is it a VM? VMs tend to do that a lot. If not a VM, then you can generate logs from JetPack/SDK Manager (there is a button for that). If using some other specialized script, e.g., an initrd flash, then you can also log that with a few extra keystrokes. What is your flash method? Direct from JetPack/SDKM? Command line with something like initrd flash?
alright guys thanks for the help on that one . gave up and used the 2nd one … flashed easy and have ubuntu running … now on to the main thing … this one seems to be a xavier agx ,.good for frigate ? docker or something else
You cannot flash mmcblk0p1 on a Nano dev kit. The dev kit does not have eMMC. On a commercial Nano that has eMMC, that would be correct. However, the target for a Nano dev kit is: mmcblk1p1
Also, this is the AGX Xavier forum. If this is a Nano it is quite different from an AGX. An AGX always has eMMC, and this would indeed be mmcblk0p1, but the target would no longer be jetson-nano-devkit.
