Dear Nvidia representative, I was trying for several days to flash the jetson Orin I just bought. The linux machine I am working with sees usb 3.0 drives for example, and lsusb finds them under bus controler for USB3.0 but when attaching the Orin it assigns it to the usb 2.0 controler. I do not know what to do , please help, thanks
Just to clarify. It is normal that recovery mode only runs in usb2.0 mode by default…That won’t affect the result of flash.
Dear Nvidia Representative, I am trying for a couple of days now to successfully re-flash the Jetson Orin 32 DevKit with the Jetpack 6.0 rev 2.
The flashing process goes all the way, mentioning flashing was successful done, but nothing appears after Jetson reset on Display. Here are the only errors the flashing process returns, even if flashing succesfully done was mentioned in the SDK manager terminal:
…
13:19:18 ERROR: Flash Jetson Linux - flash: [ 0.0274 ] ERROR: failed to read rcm_state
…
3:21:34 INFO: Flash Jetson Linux - flash: [ 8.5748 ] tegrabct_v2 --chip 0x23 0 --mb2bct mb2_bct.cfg --recov --mb2bctcfg tegra234-mb2-bct-misc-p3701-0000_cpp.dtb --scr tegra234-mb2-bct-scr-p3701-0000_cpp.dtb
13:21:34 ERROR: Flash Jetson Linux - flash: [ 8.5752 ] ERROR: value 0x31 is out of range
13:21:34 ERROR: Flash Jetson Linux - flash: [ 8.5762 ] ERROR: value 0x31 is out of range
13:21:34 ERROR: Flash Jetson Linux - flash: [ 8.5763 ] ERROR: value 0x31 is out of range
13:21:34 ERROR: Flash Jetson Linux - flash: [ 8.5764 ] ERROR: value 0x31 is out of range
…
I try to boot both using sdk and also using the terminal commads such as sudo ./flash.sh jetson-agx-orin-devkit internal. Same errors. I try to connect through a serial connection to the Jetson to see some log during boot, but, when not in Recovery Mode, dmesg grep | tty does not show any device such as ttyusb or ttyacm0 that can be identified as the Jetson. Please advise me what to do,
Thank you very much,
Looking forward for your response,
Bogdan
SDKM_logs_JetPack_6.0_(rev._2)_Linux_for_Jetson_AGX_Orin_32GB_2025-06-16_13-18-04.zip (1.2 MB)
If the device is able to get flash, then the original topic “unable to flash” is no longer correct.
This is a boot problem but not flash problem. None of the error you captured there matters.
If this is a NV devkit, please follow this page to dump serial log from micro usb port.
Thank you for your answer.
I have connected all Jetson Usb ports, one by one, to the Ubuntu PC (on different ports, front and back) , but no ttyACM device showed up on /dev/. Moreover I put the device on recovery mode and try to look for the ttyACM but none was found. Do you now what I am missing ?
Please be aware of that all my comment based on one assumption: if you are using a NV devkit.
You need to make sure this first.
If you don’t even know what I mean, if you are not using NV developer kit, then it is not NV devkit.
The only debug port to check here is that “micro USB port” on the board. Not type A nor the type C port.
Please make sure you know what is micro usb port there.
Also, make sure the OTG cable you are using there has data line but not some cheap cables which only have power line.
Here is my actual Jetson
I tried with all USB ports typeC and TypeA, and it is not seeing the /dev/ttyACM connection…
This is not NV developer kit. Our device does not have HDMI port by default but a DP port.
Please contact the board vendor for the BSP for this board.
Sdkmanager cannot flash a custom board unless your board vendor told you their board supports it.
Thank you! Sorry for misunderstanding…
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.