JetPack 4.6.3/L4T 32.7.3 released

JetPack 4.6.3 with L4T 32.7.3 is released. JetPack 4.6.3 is the same as JetPack 4.6.2 but includes Jetson Linux 32.7.3 which brings in security fixes. It also adds support for Jetson TX2 modules with new Hynix memory.

This release supports Jetson AGX Xavier series, Jetson Xavier NX series, Jetson TX2 series, Jetson TX1, and Jetson Nano.

Please can you provide a link to the “Driver Package (BSP) Sources” for the Jetson Nano for this release?

There is only a link to “Driver Package (BSP) Sources” for “Jetson AGX Xavier series, Xavier NX series, and TX2 Series” and nothing for Jetson Nano.



I was able to pull the sources with ./ against the tegra-l4t-r32.7.3 tag.

I ran -k tegra-l4t-r32.7.3

but there are no DTS files for the Nano.

@jetsonnvidia thanks for reporting this. We are taking a look.


The Jetson Nano Developer Kit SD Card Image is still 4.6.1 which can be downloaded from jetson_nano_sd_image_download.
Is it possible to provide a sd card image with the latest jetpack 4.6.3 as well?
Please also provide a document to upgrade the Jetpack from 4.6.1 to 4.6.3.

1 Like

New Image will be needed for prevent in some config/Board version by OTA.

Will re-test soon seems are update the kernel 4.9.299 What changes seen here? .

I Can confirm the problem for nvidia-l4t-bootloader still script subprocess returned error in A02 4GB board.
The problem is returned IndexError String index out of range.
It’s solved it with the link I put or by creating a new image with everything updated.
I think it’s related with the _check_ver in int(ver_list[4][2] in line 977 l4_payload_updater cause some conflict

Other issue Detected the latest image is based older kernel 4.9.253 instead 4.9.299 so will cause conflicts depmod ERROR could not open directory /lib/modules/4.9.253-tegra when first update OTA update-initramfs generatin exists boot is 4.9.253

Hello All,
I have used the latest image and I am getiing i2c read probe error. Also, the startup is very slow and it gets hanged everytime. I need to restart the jetson nano to proceed still it is very slow.

Can anyone please help me in resolving these issues?

Thanks in advance !!

The Jetson Nanon Carrier board RTSO 6002E SD card SLot and 128GB emmc not showing in jetson nano EMMC module . Pls help !!!

Hi, Suhash
i am continously getting this error message while booting up. I have Jetson nano module with 16gb emmc inbuilt. I am stuck with this stuff. Looking forward for your help soon. Thanks in advance.

1.1527641 tegrade tegradc.1: tegra_dc_parse_panel_ops: panel: 1.162473) tegrade tegradc.1: err:-19 parsing panel ops /hostix/sor/dp-dis 1.3020631 imx219 7-0010: inx219_board setup: error during i2c read inx219 7-0010: board setup failed [ 1.3259651 Imx219 8-0010: imx219_board_setup: probe (-121) error during 12c read probe (-121) 1.382130] 1.3268221 inx219 8-0010: board setup failed cp: not writing through dangling symlink 'etc/resolv.conf" /sbin/init: error while loading shared libraries: cannot open shared ob [ 1.5820691 1.582069) Kernel panic- not syncing: Attempted to kill initf exitcode=0x00007f00 I 1.5912431 CPU: 2 PID: 1 Comm: init Not tainted 4.9.253-tegra #2 1.5973581 Harduare nane: MISTRAL Neuron Basic Board-REV.A (DT) t 1.6833861 Call trace: 1.605847] [] dump_backtrace+0x0/0x198 1.611268] [] shou_stack+0x24/0x30 1.616340] [] dump_stack+0xa6/0xc1 1.621410] [] panic+0x12c/0x2a8 [] complete_and_exit+0x0/0x30 1.626219] 1.631812] [] do_group_exit+0x40/0xa6 1.637142] [] wake_up_parent+0x9/0x40 1.642647] [] ele_suc_naked+0x34/0x38 1.647980] 1.651970] 1.6554711 Memory Linit: none [ [ [ [ [ 1.663529) Rebooting in 5 seconds…

Is this the latest JetPack that supports Jetson Nano devkit? Does it support both board revisions?

Is there any way to use the Jetson Nano with modern Ubuntu (like 22.04)? 18.04 is antiquated, and I can’t build the Swift compiler with the available tools, forcing me to do a ton of infrastructure work just to get started.

It seems negligent to give Jetson Nano an EoL in 2027 but keep it stuck on JetPack 4/Ubuntu 18.

1 Like

Nano reached “new feature” end of life quite some time back (Nano is just a different form factor of a TX1), and is officially supported only up to Ubuntu 18.04. The newer platforms, Xavier and Orin, support up to Ubuntu 20.04 (that’s with JetPack 5.x; it is unlikely Xavier will support a future JetPack 6.x, but Orin will, and this would be when Ubunt 22.04 is introduced). The EOL of 2027 would simply be for Nano module availability and not for new features.

That seems like a cop-out. These devices represent a significant investment (we have several), and they’re becoming obsolete because of their lack of support for current Ubuntu. I don’t think it’s unreasonable to ask for that support to carry forward.

It might be acceptable if one could even purchase an Orin Nano, but where to get one? I certainly can’t find any.

1 Like

I don’t even see where to get JetPack 4.6.3. This page has a link to, which doesn’t look like 4.6.3 (looks like 4.6.1). Is that the right link? Also, the modification date on the unzipped file is 2022-Feb-02, but the date of the 4.6.3 announcement is Dec 2022.

1 Like

hi is there any issue why jetson nano is not capable of reading the inputs from the logitech g29 steering wheel i have been trying each and everything from past couple of weeks

You really should start a new thread on this, but here is some starting information…

I know nothing about that controller. In many cases it is just a case of adding a driver. When you start your new thread, add the output from the following:

  • head -n 1 /etc/nv_tegra_release
  • uname -r
  • Copy “/proc/config.gz” somewhere, and then attach it to the forum (this isn’t a real file, it is the kernel naming its features in RAM and pretending to be a file, so I suggest copy somewhere else before trying to attach it to the forum).

Note that all operating systems need drivers for whatever hardware is attached; it is a case of the Linux kernel supporting this, and the Nano itself is somewhat irrelevant to that talk. However, adding drivers is different on a Nano.