We are pleased to announce JetPack 4.5, a production release supporting Jetson AGX Xavier series, Jetson Xavier NX, Jetson TX2 series, Jetson TX1, and Jetson Nano.
JetPack 4.5 includes VPI 1.0, Security features including enhanced secure boot and support for full disk encryption, enhanced bootloader functionality, and a new way of flashing Jetson devices using NFS.
We will be hosting a webinar on Feb 9th for an in-depth overview of JetPack 4.5 features where we will also demo select features and answer any questions you may have. Please register here.
Learn how to implement computer vision and image processing pipelines using VPI by registering to the webinar we will be hosting on Feb 11th
Highlights of JetPack 4.5 are:
First Production release of Vision Programming Interface (VPI).
Support for loading kernel, device tree and initrd from the root file system on USB drive or NVMe. Refer to release notes for more details.
UBoot version updated to v2020.04.
Boot firmware for all Jetson Nano developer kits updated to relocate boot firmware to integrated QSPI-NOR. Developer kits will use microSD Cardsolely or OS/app storage after this change
All Jetson Nano Developer Kits will now show a warning screen if no microSD Card is inserted. It will attempt to boot from other supported media after showing this warning screen.
Does this apply to all existing Jetson Nano Developer Kits once Jetpack 4.5 has been installed using the SDK Manager or is this applied in the factory and only available in newly purchased Jetson Nano Developer Kits.
Boot firmware for all Jetson Nano developer kits updated to relocate boot firmware to integrated QSPI-NOR. Developer kits will use microSD Cardsolely or OS/app storage after this change
All Jetson Nano Developer Kits will now show a warning screen if no microSD Card is inserted. It will attempt to boot from other supported media after showing this warning screen.
@tuna.akyol i assume you are reffering to SPI driver for the external controller. We see that the MCP251X is enabled in the kernel and was so in previous release as well.
After pulling the source code (with tag “tegra-l4t-r32.5”) in process of preparation for U-Boot bootloader rebuild, I noticed that there is no “p3450-porg_defconfig” as well as board/nvidia/p3450-porg/ directory which was present in R32.4.4 source.
I would be helpful if there was a more clear instruction how to move from SD card to a USB Drive. I have tried the steps in the instruction, but it became unclear at the point where the target device had to be put in recovery mode. The instructions which follow that step are supposed to be carried out at the host system, right? I think there’s also a error in the instructions where the raw image is being copied to the USB Drive:
sudo rsync -axHAWX --numeric-ids --info=progress2 --exclude=/proc ./tmp_system /mnt
I think it missed a ‘/’ behind ‘tmp_system’ otherwise the roots will be in folder /tmp_system on the USB device?!