X264 and TensorRT sudden reboot (MJPG encoder not affected, but not fast enough) on Jetson Orin Nano

Check it here:
https://docs.nvidia.com/jetson/archives/r35.5.0/DeveloperGuide/SD/SoftwarePackagesAndTheUpdateMechanism.html#updating-to-a-new-minor-release

Hi,

We tested on this setup for at least three more hours, and still did not hit any crash.
Based on your other posts, it looks like it’s some hardware failure, and it’s not related to software you run.

Hi @DaveYYY

I was able to upgrade successfully to Jetpack 5.1.3 via apt, however it seems that I need to reinstall the IMX477 drivers/ configure them (getting the “camera not found” errors, etc.).

When I try to do this via sudo opt/nvidia/jetson-io/jetson-io.py however, it doesn’t work unfortunately. I can see the outline of the menu show for a split second, but then it closes. This was how I used to install the drivers on all our Jetsons, so I know this worked back when I was using Jetpack 5.1.1 from a fresh SD card flash.

I’ve tried adding print statements within the jetson-io.py file for debugging, but nothings coming through:

fov@marvel-fov-test:/boot$ sudo /opt/nvidia/jetson-io/jetson-io.py
fov@marvel-fov-test:/boot$ sudo /opt/nvidia/jetson-io/jetson-io.py
fov@marvel-fov-test:/boot$ cd /opt/nvidia/jetson-io
 fov@marvel-fov-test:/opt/nvidia/jetson-io$ sudo python jetson-io.py
fov@marvel-fov-test:/opt/nvidia/jetson-io$ sudo python jetson-io.py

Running dmesg for camera errors it looks like the 219 driver might be installed by default…?

fov@marvel-fov-test:/opt/nvidia/jetson-io$ sudo dmesg | grep -E "imx477|imx219|arducam"
[   17.673718] imx219 9-0010: tegracam sensor driver:imx219_v2.0.6
[   17.684880] imx219 9-0010: imx219_board_setup: error during i2c read probe (-121)
[   17.700946] imx219 9-0010: board setup failed
[   17.705883] imx219: probe of 9-0010 failed with error -121
[   17.711965] imx219 10-0010: tegracam sensor driver:imx219_v2.0.6
[   17.723190] imx219 10-0010: imx219_board_setup: error during i2c read probe (-121)
[   17.736705] imx219 10-0010: board setup failed
[   17.741582] imx219: probe of 10-0010 failed with error -121

But anyways, I’m not able to install or configure the jetson for imx477 cameras without the jetson-io.py script working…

Do you have any idea what might be going on? Or how I might be able to bypass it?

There have been other mentions of this issue on the forum for older jetpack versions, but none of them seem to fix it.

Many thanks
Tim

If its relevant, when installing the new jetpack via apt, I pressed Y to all the prompts it asked for rewriting new files (i.e. used Nvidia’s new versions)

Another update:

Running sudo /opt/nvidia/jetson-io/jetson-io.py | less produces this error being show:

No APP_b partition found!

And here is the following too:

fov@marvel-fov-test:~$ sudo /opt/nvidia/jetson-io/config-by-hardware.py --list
Traceback (most recent call last):
  File "/opt/nvidia/jetson-io/config-by-hardware.py", line 125, in <module>
    main()
  File "/opt/nvidia/jetson-io/config-by-hardware.py", line 94, in main
    jetson = board.Board()
  File "/opt/nvidia/jetson-io/Jetson/board.py", line 229, in __init__
    self.appdir = _board_partition_mount(mountpart)
  File "/opt/nvidia/jetson-io/Jetson/board.py", line 156, in _board_partition_mount
    raise RuntimeError("No %s partition found!" % partlabel)
RuntimeError: No APP_b partition found!

Hi,
The imx477 supported through jetson-io is RPi high quality camera. Your camera looks to be from other vendor. Would need to manually port sensor driver.

Yeah that’s actually exactly the camera I have.

I have another Jetson orin nano here which I reflashed with jetpack 5.1.1 and the jetson-io configuring script worked fine. It’s what I’ve always been using

But after using apt to upgrade to 5.1.3 it’s not working, just flashes the menu momentarily.

Do you have another device that yuo can freshly flash 5.1.3 and verify the camera?

I just performed a fresh SD Card image reflash with Jetpack 5.1.3 with the device above where I tried to upgrade to Jetpack 5.1.3 previously via apt, and then once updated, when I tried to run sudo /opt/nvidia/jetson-io/jetson-io.py to install the imx477 drivers it didn’t work (the menu would flash for a split second and the disappear, and the script would exit without any errors.

I just did a full SD card reflash with jetpack 5.1.3, and this issue has managed to persist… I still can’t install the imx477 drivers. It seems like trying to upgrade to 5.1.3 via apt has actually messed up the Jetson Orin Nano at a lower level…? Why would an issue like this persist after a fresh SD card reflash?

I have attached a short video of it occurring…

Any idea what’s going on? Why would this still happen after a reflash when the device was working fine before I upgraded to jetpack 5.1.3 via apt?

Thanks
Tim

Regarding verifying the camera - yes I know it works. We have it on 9 other devices and it works fine. It was working perfectly on this device until we upgraded to jetpack 5.1.3 via apt.

Did you get any log in dmesg or syslog?
Jetson-IO runs correctly on our local devices with 5.1.3.

I just did a fresh SD card reflash of Jetpack 5.1.3 onto our our other Jetson Orin Nano which I know was recognizing the camera and working fine with IMX477 when it was on 5.1.1 beforehand, and I’m getting exactly the same error, the jetson-io.py menu only shows for a split second and then closes without any errors.

Is there any particular keywords I should search for within dmesg or syslog? From a quick look (unfortunately don’t have too much time rn) I didn’t see anything out of the ordinary

We got another Jetson Orin Nano, and flashed that with 5.1.3 too, and jetson-io is not working with that either! Reproduced across 3 devices now.

This is the jetpack zip file name we flashed it with, JP513-orin-nano-sd-card-image_b29.zip

I would attach the zip file but its massive - its just the normal one from the downloads page here under the SD card image: JetPack SDK | NVIDIA Developer

Hi,
Do you use RPi HiQ camera? We support this IMX477 in jetson-io. The IMX477 from other vendor is not supported.

As I said above, yes that’s the camera we are using; it works perfectly fine with 5.1.1 which is what I’m now reflashing our jetsons back to unfortunately

However our original issues, the sudden rebooting, still persist

Hi,
Please run the comamnds and share the prints for reference:

nvidia@tegra-ubuntu:~$ sudo i2cdump -y -f 0 0x50
No size specified (using byte-data access)
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 02 00 fe 00 00 00 00 00 00 00 00 ff 00 00 00 00    ?.?.............
10: 00 01 00 01 36 39 39 2d 31 33 37 36 37 2d 30 30    .?.?699-13767-00
20: 30 35 2d 52 43 31 20 42 2e 34 00 00 00 00 00 00    05-RC1 B.4......
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
40: b0 48 00 00 0f 8d bc 2d b0 48 31 34 31 30 36 32    ?H..???-?H141062
50: 33 30 30 30 33 30 30 00 00 00 00 00 00 00 00 00    3000300.........
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
90: 00 00 00 00 00 00 4e 56 43 42 00 ff 4d 31 00 00    ......NVCB..M1..
a0: 00 00 00 00 00 00 00 00 00 00 00 00 0f 8d bc 2d    ............???-
b0: b0 48 01 00 00 00 00 00 00 00 00 00 00 00 00 00    ?H?.............
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 82    ...............?
nvidia@tegra-ubuntu:~$ sudo i2cdump -y -f 0 0x57
No size specified (using byte-data access)
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 02 00 fe 00 00 00 00 00 00 00 00 00 00 00 00 00    ?.?.............
10: 00 00 00 0a 36 39 39 2d 31 33 37 36 38 2d 30 30    ...?699-13768-00
20: 30 30 2d 52 43 32 20 43 2e 33 00 00 00 00 00 00    00-RC2 C.3......
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
40: 00 00 00 00 71 8e 3c 2d b0 48 31 34 31 30 37 32    ....q?<-?H141072
50: 33 30 30 30 35 31 39 00 00 00 00 00 00 00 00 00    3000519.........
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
90: 00 00 00 00 00 00 4e 56 43 42 00 00 4d 31 00 00    ......NVCB..M1..
a0: 00 00 00 00 00 00 00 00 00 00 00 00 71 8e 3c 2d    ............q?<-
b0: b0 48 0a 00 00 00 00 00 00 00 00 00 00 00 00 00    ?H?.............
c0: 00 00 00 00 00 00 00 00 36 37 30 2d 31 33 37 36    ........670-1376
d0: 36 2d 30 30 30 35 2d 52 43 31 00 00 00 31 34 31    6-0005-RC1...141
e0: 30 37 32 33 30 30 30 37 37 36 00 00 00 00 00 00    0723000776......
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 dc    ...............?

We can enable RPi HiQ camera on Orin Nano developer kit 5.1.3. Would like to confirm our developer kits are identical. And when the loading is high, do you see FAN on the module being triggered?

Thanks @DaneLLL will do that once I have a Jetson that is booting up with 5.1.3.

Can I ask if you know if its safe to downgrade the Jetsons to 5.1.1 from 5.1.3 via a fresh SD card image reflash? We upgraded all three of the Jetson Orin Nano’s we have on hand to Jetpack 5.1.3 but were unable to install camera drivers on any of them via jetson-io, so I decided to try and reflash them with the 5.1.1. image → I formatted the SD cards, flashed Jetpack 5.1.1 onto them, and then put this SD card back into the Jetson device and powered on, however none of them will boot properly. They open up in the boot page, and then power off momentarily (the fan will turn off) and then turn back on to repeat. I have attached a video (and screenshot of the text that shows) of the behaviour below.

(FYI we’re working out of an airbnb on location!)

(Also note that I unfortunately don’t have a UART serial on hand for a debug log)

Right now, I am flashing 5.1.3 on to an SD card again, to see if one of the jetsons will successfully boot with that.

Flashing 5.1.3 back onto an SD card and using that we the Jetson worked in getting it to boot - but we can’t install the imx477 driver with this jetpack via jetson-io still.

Here is the output requested, thanks:

fov@marvel-fov-test-1:~$ sudo i2cdump -y -f 0 0x50
[sudo] password for fov:
No size specified (using byte-data access)
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 02 00 fe 00 00 00 00 00 00 00 00 ff 00 00 00 00    ?.?.............
10: 00 01 00 01 36 39 39 2d 31 33 37 36 37 2d 30 30    .?.?699-13767-00
20: 30 35 2d 33 30 30 20 4b 2e 32 00 00 00 00 00 00    05-300 K.2......
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
40: b0 48 00 00 c5 06 ec 2d b0 48 31 34 32 31 38 32    ?H..???-?H142182
50: 33 30 34 34 30 37 37 00 00 00 00 00 00 00 00 00    3044077.........
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
90: 00 00 00 00 00 00 4e 56 43 42 00 ff 4d 31 00 00    ......NVCB..M1..
a0: 00 00 00 00 00 00 00 00 00 00 00 00 c5 06 ec 2d    ............???-
b0: b0 48 01 00 00 00 00 00 00 00 00 00 00 00 00 00    ?H?.............
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0    ...............?
fov@marvel-fov-test-1:~$ sudo i2cdump -y -f 0 0x57
No size specified (using byte-data access)
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 02 00 fe 00 00 00 00 00 00 00 00 00 00 00 00 00    ?.?.............
10: 00 00 00 0a 36 39 39 2d 31 33 37 36 38 2d 30 30    ...?699-13768-00
20: 30 30 2d 34 30 30 20 44 2e 31 00 00 00 00 00 00    00-400 D.1......
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
40: 00 00 00 00 71 8e 3c 2d b0 48 31 34 32 31 39 32    ....q?<-?H142192
50: 33 30 30 35 32 37 33 00 00 00 00 00 00 00 00 00    3005273.........
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
90: 00 00 00 00 00 00 4e 56 43 42 00 00 4d 31 00 00    ......NVCB..M1..
a0: 00 00 00 00 00 00 00 00 00 00 00 00 71 8e 3c 2d    ............q?<-
b0: b0 48 0a 00 00 00 00 00 00 00 00 00 00 00 00 00    ?H?.............
c0: 00 00 00 00 00 00 00 00 36 37 35 2d 31 33 37 36    ........675-1376
d0: 36 2d 30 30 30 30 2d 30 30 30 00 00 00 31 34 32    6-0000-000...142
e0: 31 39 32 33 30 30 33 35 36 38 00 00 00 00 00 00    1923003568......
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c5    ...............?

Also note that the fan is constantly on or triggered… not too sure what you mean by “when the loading is high”… maybe its supposed to generally only be triggered when running intense workloads but in our case it runs from the moment it turns on until we power it off