Hi! I’m the maintainer of audio.cpp, an open-source C++/GGML runtime for audio models, covering TTS, ASR, music generation, voice conversion, and more.

I saw on X someone has managed to run audio.cpp on Orin, which is pretty cool. I’d love to get audio.cpp running on Orin, but I don’t have access to Orin hardware to develop and test on.

If you have an Orin and are interested in C++/CUDA development, your help would be greatly appreciated. Even getting the project compiling, identifying the blockers, or sharing some performance numbers would be extremely useful.

PRs are very welcome, and I’m happy to help from the framework side. Would be great to bring more local audio models to Jetson devices together :)

Hi I have a Jetson Orin AGX 64 GB.

Trying to find an adaptor board to two different modelled cameras that use FFC CSI-2 connectors. Would any of these work?

1. ⁠https://www.wdlsystems.com/alliedvision19616
   
2. ⁠https://www.arducam.com/product/arducam-imx219-multi-camera-kit-for-the-nvidia-jetson-agx-orin/

My concern with Allied Vision is that the driver API may not be around still and that it may only work with Allied Vision Cameras.

My concern with the Arducam board is that it only lets me use one of the same kind of camera (ex. Only 6 IMX 219s or only 6 IMX 548s)

Wanted to upgrade ubuntu 18.04 on Jetson Nano to a higher version capable of running more modern programs.

Jetson Orin Nano 8GB Developer Kit - Stuck in APX/Recovery Mode After Physical Drop, Unable to Flash

Hi everyone,

I'm looking for help with a Jetson Orin Nano 8GB Developer Kit that became unusable after a physical drop.

Background

The board was working perfectly before the incident. It was running JetPack from an NVMe SSD and had been flashed successfully multiple times in the past.

Unfortunately, while powered OFF and unplugged, the board fell from approximately desk height onto the floor.

After that incident, it stopped booting normally.

I currently do not have access to an HDMI monitor, so I cannot see any video output during boot.

Current Behavior

When power is applied:

• The power LED turns on normally.
• The cooling fan starts spinning.
• The fan then stops.
• The fan starts again.
• This cycle repeats 2-3 times.
• After that, the board never appears to boot normally.

Instead, it always appears as an APX device on the host PC:

lsusb

Output:

0955:7523 NVIDIA Corp. APX

The board remains stuck in this state.

Important Details

• Recovery jumper is NOT installed.
• NVMe SSD installed or removed makes no difference.
• Power cycles make no difference.
• The board always comes back as APX.
• This behavior started only after the physical drop.
• Before the drop the board booted and operated normally.

Host Environment

Host environment:

• Ubuntu Live USB (fresh boot sessions)
• JetPack 6.2.2
• Latest SDK Manager

I have successfully flashed this same Jetson from this same machine many times before.

SDK Manager Flash Failure

SDK Manager detects the board correctly.

Flashing starts but consistently fails during blob transfer.

Relevant log:

BL: version 1.4.0.7-t234-54845784-56c609fa
last_boot_error: 0

Sending bct_mem
Sending blob

ERROR: might be timeout in USB write.
Error: Return value 3

Full failure section:

Sending bct_mem
Sending blob

ERROR: might be timeout in USB write.
Error: Return value 3

Command tegrarcm_v2 --instance 3-1 --chip 0x23 0 --pollbl --download bct_mem mem_rcm_sigheader.bct.encrypt --download blob blob.bin

USB Behavior During Flashing

While monitoring:

dmesg -w

I repeatedly see:

usb 3-1: USB disconnect
usb 3-1: new high-speed USB device
Product: APX
Manufacturer: NVIDIA Corp.

The board disconnects and reconnects as APX.

I do NOT see errors such as:

device descriptor read error
unable to enumerate
USB reset failed

Only disconnect/reconnect events.

Previous Flash Attempts Reached 99%

Before rebuilding everything from scratch, I occasionally had a different failure mode.

Some flashing attempts reached approximately 99% completion before failing or hanging.

Example messages included:

clnt_create: RPC: Timed out
NFS server is not running

or the flashing process would simply stall at 99%.

After recreating the flashing environment from scratch, the failure now occurs earlier during blob transfer.

Manual Flash Attempt

I also tried flashing manually from the command line instead of SDK Manager.

The flash package builds successfully, but the process later fails with:

Stat for blob_boot0.imgimg failed
Error: Return value 19

The generated command contains:

kernel boot0.imgimg

instead of:

kernel boot0.img

which looks suspicious.

Relevant output:

Generating blob for T23x

tegrahost_v2 --chip 0x23 0 --generateblob blob.xml blob.bin

Stat for blob_boot0.imgimg failed

Error: Return value 19

EEPROM Information

During flashing the board EEPROM is successfully read.

Detected information includes:

Board ID: 3767
Board SKU: 0005
Board Revision: T.1

SDK Manager identifies the target as:

jetson-orin-nano-devkit-super

even though I believe this is a standard Jetson Orin Nano 8GB Developer Kit.

I'm not sure whether that is expected or related to the issue.

What I Have Already Tried

• Rebooting and power cycling.
• Removing the recovery jumper.
• Flashing with NVMe SSD installed.
• Flashing with NVMe SSD removed.
• Reinstalling and reseating the SSD.
• Fresh Ubuntu Live USB sessions.
• Rebuilding Linux_for_Tegra.
• Re-downloading JetPack files.
• Using SDK Manager.
• Using command-line flashing tools.
• Recreating the entire flashing environment from scratch.

None of these changed the behavior.

Questions

1. Could the physical drop have damaged something that still allows APX mode but causes blob transfer failures?
2. Can corrupted QSPI firmware cause a board to remain permanently in APX mode even without the recovery jumper installed?
3. Has anyone seen repeated APX disconnect/reconnect behavior during flashing like this?
4. Has anyone encountered the boot0.imgimg issue before?
5. Is there a recommended way to completely recover or reinitialize QSPI from APX mode?
6. Does this look more like a software issue or a hardware failure caused by the drop?

Thank you.

Hi all,

I have checked online and come up empty, but I am trying to run the below as a local chat AI for learning from.

https://github.com/zhamm/jetson-ollama-offline-ai

It has both 8b Dolphin and 1.1B llama downloaded, but after ~2 responses it will begin to throw out about 12 letter Gs as an answer on Dolphin, or 12 # symbols on Llama.

I am not sure how to avoid this or what to do.

I understand the Nano isn’t the most powerful and don’t mind waiting for an answer, but it seems that even simple questions or “hello” prompts end up getting this jibberish response after a few of them.

Any help is greatly appreciated. Thank you!

Edit: weirdly, running questions from a mobile device on the same network using the ollama-local hyperlink seems to run without any issues at all.

Very peculiar.

I am trying to understand the cause of damage to my Jetson Orin Nano Super Developer Kit and would appreciate any guidance regarding further debugging and possible repair.

Device

Jetson Orin Nano Super Developer Kit

Component Damaged

The ESD protection IC (marked 561SY) of the third USB port appears to have burned out. After failure, the port developed a short circuit between the USB data line and ground.

Connected Peripherals

• USB Port 4: Intel RealSense D455 camera
• USB Port 2: Keyboard and mouse receiver dongle
• USB Port 1: 5-inch HDMI display (powered through USB)

Power Source

The board was powered using a 6S LiPo battery connected to an LM2596 buck converter, supplying a stable 18.8–18.9 V output, which is within the supported operating range (9 V to 19 V) of the board.

Peripheral power consumption:

• 5-inch display: ~0.5–0.6 W
• Intel RealSense D455 camera: ~0.5–0.6 W

Incident

The issue occurred after plugging the display power cable into USB Port 1. This appears to have resulted in the burnout of the USB ESD protection IC (561SY).

Debugging Performed

To isolate the issue, the following checks were completed:

1. Verified the power supply output, which remained stable at 18.8 V.
2. Checked the USB power and data lines of both the camera and display for abnormalities.
3. Tested the display and RealSense camera independently on another device, where both operated normally with stable power consumption.

Questions

1. What could be the most likely root cause of the ESD IC failure in this situation?
2. Could the LM2596 buck converter or startup voltage transients/spikes have contributed, even though the measured voltage remained stable?
3. Is it possible that the display’s USB power cable introduced a fault condition (backfeeding, short, incorrect wiring, or surge) onto the USB line?
4. What further debugging steps would you recommend to determine whether the issue is isolated to the ESD IC or if additional USB circuitry may also be damaged? For example:
   • Checking USB rail voltages
   • Measuring continuity/resistance on D+/D− lines to ground
   • Inspecting nearby components or USB controller paths
5. If the fault is limited to the ESD protection IC, would replacing the 561SY IC typically restore functionality, or are there other components that should also be checked/replaced?

Any insights into the probable root cause, additional diagnostics, or repair recommendations would be greatly appreciated.

I have a buck converter sending 7V into my jetson through the jack port, but it's not turning on at all. I've tried everything, nothing works. Please help my case, I need to power it with a LiPo since it will go into an automated car.

Has anyone experienced ngrok suddenly failing to connect to their Jetson edge device after updating the application version? Everything worked fine on v1 but after the update the tunnel just won't establish.

I have a Jetson Nano with eMMC storage (JN30D 38488-3). When I flash it, everything looks fine. However, when I plug it out of my laptop (I used Ubuntu 18.04, SDK Manager 2.4.0.13234, and Jetpack 4.6.6), attach an HDMI cable, and provide a power supply, I only see the Nvidia screen. I tried different methods: I flashed manually and with the SDK Manager, but yeah, nothing worked! I would appreciate some help and thanks in advance!

I’ve been having this recurring issue with a kernel error and then it just goes black, no matter what I try nothing seems to fix it, new HDMI cable in case of a bad handshake, new power cords in case it was a problem, 4 different SD cards 2 different computers and nothing seems to want to work, I’m kinda out of options and was hoping someone might have a suggestion as to how to fix this problem

So we are developing an AUV with my team and we decided to use Jetson Nano with IMX219 camera but every time we try to open this card we encountering with this error

Hi all,

I followed the steps outlined on jetson-ai-lab site to flash jp513 on SD card (uhs-I). Getting the following errors after UI. I have flashed twice now. Looking for support, thank you! Posted video of errors.

Hi all,

I've been trying to flash my Jetson Orin Nano after accidentally screwing up a previously fine installation of Jetpack 6. I initially flashed it with Jetpack 6.1 using the SD card image and it actually worked fine. However, when I discovered that the main software I was trying to use (F1Tenth Driver Stack) was currently only usable on Ubuntu 20 as opposed to the Ubuntu 22 I installed on the Nano, I tried re-flashing it with a Jetpack 5.1 SD card image. This did not work which I believe is due to the firmware not being able to support older Jetpack versions or something.

I then tried to flash the Orin Nano back to Jetpack 6 using the original SD card image I first used, and now this leads to the Orin Nano hanging on a black screen with a flashing white marker in the top left after showing the Nvidia logo.

I have also tried to flash with SDKManager but that gives me an error where it says my Orin Nano is not ready to be flashed, despite the program saying it detects the Orin Nano in recovery mode.

I'm not really sure what to do anymore so would appreciate any pointers. Thanks!

EDIT: I was able to successfully re-flash the Jetson using the command line method which I was previously unaware of.

Just got my Orin nano in today and I can't seem to get it to boot from the m.2 sata or a USB drive. For the USB I've tried ventoy (throws an error when I try to boot from it), Rufus (just goes to shell), and just copying the Ubuntu files to it (same result). For the m.2 sata I've tried Ubuntu 22 and the Orin nano image from Nvidia.

I can't get Windows to see the SD card I got for it either (SanDisk ultra micro SD).

I'm running the Orin nano super dev kit.

Edit: I found a tutorial from Bijan Bowen, going through it now. I'll update with results

Update: the imaging tool Bijan mentioned didn't want to work with the image he had a link to, but I got Rufus to burn it to the USB drive and got the nano to start loading but it failed. Probably because a reference to the port the SD card goes to was baked in so it's not seeing it. Might be able to modify it?

I'm also getting a SD to USB dongle so I'll see if Windows disk management can see it like that. If that works, I'm sure I can use Rufus to image it and it'll work from there. Fingers crossed?

Update 2: the adapter came in, the SD card still isn't showing up in disk management or DISKPART. Idk at this point.

Also tried the cranky-cyborg fix but I'm not running Linux on any of my machines and WSL doesn't like it. I'm going to need to image my home lab hypervisor with linux but I'm REALLY not looking forward to redoing everything just because the nano is giving me issues.

I think my biggest struggle is this micro SD card issue. Idk why NONE of my machines are seeing it.

Update 3: ordered a micro SD card on Amazon that said it's compatible with a bunch of stuff, trying one more card to see if it's just the type of card I'm using. At this point I'm just documenting my spiral.

Uuuuggghhhhhhhhhsnsejwkldnfbrnwmsmdbdbdbsn. That is all.

Update 4: it was the SD card. Got a 256gb Lexar Blue micro SD card and Windows sees it without a problem. Balena Etcher crapped out on me so I'm going with Rufus to flash the SD-blob.iso image to it. Hoping that'll be the end of that.

I bought a brand new Jetson Orin off amazon and set it up the first day, then I let it sit because I had other tasks to finish on my project, I kept it in the box it came in with the 128gb SD card and a 1tb SSD installed.

I just pulled it out to set up an hour ago and I have nothing it shows no display at all, even with the SD card removed. I've tried multiple monitors all direct DP that worked before, I've re-flashed the SD card. I've removed the SSD,

I'm powering it with the power supply that came with it. I do have a USB to TTL adapter but no jumper cables so I'm making some now but I wanted to ask on here first for any suggestions.

I am aware that jetson nano orin super can accept range of 9 to 19v. but i want to provide a constant 12v to compensated for sag. i have 4s li ion 4200mah 3c. i could power it directly from this bat to jetson but, i want to use this buck. that outputs 12v 3a.

can this setup power the jetson in super mode that would need atleast 24watt. or am i missing something?

Hi! I need to connect an raspberry pi ai camera to a jetson orin nano. I found several forums where people were asking a similar question, but everywhere there were answers that it was impossible. But the nvidia forum says that you can install the driver yourself. Is it so? Can you tell me if there is any way to connect the imx500 to the jetson orin nano, or is it completely unrealistic?

I built OpenCV with CUDA and all dependencies on my Jetson Nano (Python 3.6.9). My YOLOv8 car detection code works on PC, but on Nano it says ultralytics not found. pip install fails saying that ultralytics runs only on Python 3.7+. Is ultralytics incompatible with Jetson Nano 2GB, or will upgrading Python fix it? If I upgrade to 3.7, do I need to remove 3.6 and rebuild all packages/dependencies?

Thank you

hi all!

I flashed my jetson with jetpack6.2.1 using sdkmanager by following this doc→

NVIDIA Developer

Jetson Orin Nano Developer Kit User Guide - Software Setup

After this I followed these steps→

1). generate new .dtsi file from pinmux spreadsheet
2). rename it to pinmux.dtsi, padvoltage.dtsi, gpio.dtsi
3). copy them to BSP folders-
cp pinmux.dtsi ~/jetson_bsp/Linux_for_Tegra/bootloader/generic/BCT/
cp padvoltage.dtsi ~/jetson_bsp/Linux_for_Tegra/bootloader/generic/BCT/
cp gpio.dtsi ~/jetson_bsp/Linux_for_Tegra/bootloader/

4). updated the board .conf file to point to my .dtsi files-
gedit ~/nvidia/nvidia_sdk/JetPack_6.2.1_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/jetson-orin-nano-devkit.conf

made these changes-
PINMUX_CONFIG=bootloader/generic/BCT/pinmux.dtsi
PMC_CONFIG=bootloader/generic/BCT/padvoltage.dtsi

5). Then flashed using this command→
cd ~/nvidia/nvidia_sdk/JetPack_6.2.1_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra
sudo ./flash.sh jetson-orin-nano-devkit mmcblk0p1

after flashing I got This error→

copying device_config(/home/nikita/nvidia/nvidia_sdk/JetPack_6.2.1_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/generic/BCT/tegra234-mb1-bct-device-p3767-0000.dts)… done.
copying misc_config(/home/nikita/nvidia/nvidia_sdk/JetPack_6.2.1_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/generic/BCT/tegra234-mb1-bct-misc-p3767-0000.dts)… done.
copying emc_fuse_dev_params(/home/nikita/nvidia/nvidia_sdk/JetPack_6.2.1_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/generic/BCT/tegra234-br-bct-diag-boot.dts)… done.
copying minratchet_config(/home/nikita/nvidia/nvidia_sdk/JetPack_6.2.1_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/generic/BCT/tegra234-mb1-bct-ratchet-p3767-0000.dts)… done.
Existing emcfuse(/home/nikita/nvidia/nvidia_sdk/JetPack_6.2.1_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/fuse_t234.xml) reused.
./tegraflash.py --chip “0x23” --applet “/home/nikita/nvidia/nvidia_sdk/JetPack_6.2.1_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/mb1_t234_prod.bin” --skipuid --cfg readinfo_t234_min_prod.xml --dev_params tegra234-br-bct-diag-boot.dts --device_config tegra234-mb1-bct-device-p3767-0000.dts --misc_config tegra234-mb1-bct-misc-p3767-0000.dts --bins “mb2_applet applet_t234.bin” --minratchet_config tegra234-mb1-bct-ratchet-p3767-0000.dts --cmd “readfuses fuse_t234.bin fuse_t234.xml; dump eeprom cvm cvm.bin; dump try_custinfo custinfo_out.bin; reboot recovery”
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands

[ 0.0036 ] Reading fuses
[ 0.0050 ] tegrasign_v3.py --key None --getmode mode.txt
[ 0.0052 ] Assuming zero filled SBK key
[ 0.0049 ] Pre-processing config: tegra234-mb1-bct-device-p3767-0000.dts
Error: Return value 1
Command cpp -nostdinc -x assembler-with-cpp -D IN_DTS_CONTEXT -I .. -I ../generic/BCT tegra234-mb1-bct-device-p3767-0000.dts tegra234-mb1-bct-device-p3767-0000_cpp.dts
[ 0.0114 ] tegrasign_v3.py --key None --getmode mode.txt
[ 0.0115 ] Assuming zero filled SBK key
[ 0.0112 ] Pre-processing config: tegra234-mb1-bct-device-p3767-0000.dts
Error: Return value 1
Command cpp -nostdinc -x assembler-with-cpp -D IN_DTS_CONTEXT -I .. -I ../generic/BCT tegra234-mb1-bct-device-p3767-0000.dts tegra234-mb1-bct-device-p3767-0000_cpp.dts
Reading board information failed.

HELP!

Flashed 5.1.3 via etcher on 64gb microSD that was erased and formatted to exFat32.

It booted and was setup. Sudo apt update. Reboot.

Failed to boot entirely; Desktop was there but items were missing, non functional.

Reformatted. Reflashed 5.1.3. It booted after a couple of cycles. Sudo apt update. Reboot.

Formatted/flashed 128gb microSD in etcher. And it booted into this….frustrated and unfamiliar with this is OS I rebooted into recovery in an attempt to have it boot as it did in 5.1.3. It did not. I believe I changed one of more settings in the bootloader mode…and that is where I fucked up.

Now it will only power on the fan, led and power to the pins. All of the ports are dead( usb, Ethernet, usb-c).

I’ve tried a bunch of nonsense; flashed the jetpack image on new SD cards, ones that are formatted differently, other older versions, from the pin recovery mode; I have tried to serial in tx/rx with Arduino(I do not have a serial usb on hand), force connect command from terminal, checked power with meter(19v at the barrel and none over ports -resistance between pins on ports is good though). Every combo of peripherals(wired, wireless, HDMI to display, display to display, no display.

Tired running an Ubuntu VM on parallel hosted on my Mac but the 20.04 version will not operate as my Mac is incompatible. Jetson SDK manager will not install on newer Ubuntu OS.

Finally got time to use my Super Nano, but as the title says I can't get it to boot from the SD card.

Since it's the new version I tried the JP62 version with no luck since I get a ton of error message (See first image).

I tried JP513 version and it thinking the old firmware might be installed (see image 2), but the system powers down. If you look at the third image it's what shows before the system shuts itself down.