Comments for Rob Royce https://robroyce.dev Exploring frontier technology at the intersection of AI, robotics, and business. Mon, 19 Jul 2021 08:15:24 +0000 hourly 1 http://wordpress.com/ Comment on How to Convert Encrypted TLT Files to TensorRT Engine on Nvidia Jetson by Salim https://robroyce.dev/2021/02/03/how-to-convert-encrypted-tlt-to-tensorrt-engine-on-nvidia-jetson/comment-page-1/#comment-53 Mon, 19 Jul 2021 08:15:24 +0000 http://robroyce.wordpress.com/?p=1081#comment-53 Hey Rob,
Your blog was a great read. It would also be very helpful to see your viewpoint on how to deploy this .engine model file onto the jetson device using a simple python script to run the inferencing stage.

Like

]]>
Comment on How to Boot Jetson Nano From USB 3.0 (Natively) with Jetpack 4.5 by Pavel Rybar https://robroyce.dev/2021/02/11/how-to-boot-jetson-nano-from-usb-3-0-natively-with-jetpack-4-5/comment-page-1/#comment-52 Wed, 21 Apr 2021 16:33:26 +0000 http://robroyce.wordpress.com/?p=1147#comment-52 Hi, nice post. Is there any chance to use HDD bigger than 2TB. I’m trying this with 4TB and got errors:
GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
find_valid_gpt: *** ERROR: Invalid Backup GPT ***
GPT: first_usable_lba incorrect: 22 > 0
find_valid_gpt: *** ERROR: Invalid GPT ***
GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
find_valid_gpt: *** ERROR: Invalid Backup GPT ***
** Invalid partition 1 *

I thing it’s because of big drive..

Like

]]>
Comment on How to Boot Jetson Nano From USB 3.0 (Natively) with Jetpack 4.5 by Ravishankar https://robroyce.dev/2021/02/11/how-to-boot-jetson-nano-from-usb-3-0-natively-with-jetpack-4-5/comment-page-1/#comment-51 Thu, 25 Mar 2021 06:02:24 +0000 http://robroyce.wordpress.com/?p=1147#comment-51 Thanks for this tutorial. I have a a jetson-nano B01 with JP 4.5.1 latest. So QSPI firmware has been updated to boot from USB.

I just want to know how I can do it without a host Ubuntu PC because I dont have access to one.
It seems many of the steps can be done on Jetson Nano itself.

Like

]]>
Comment on How to Boot Jetson Nano From USB 3.0 (Natively) with Jetpack 4.5 by Neil Young https://robroyce.dev/2021/02/11/how-to-boot-jetson-nano-from-usb-3-0-natively-with-jetpack-4-5/comment-page-1/#comment-50 Fri, 12 Mar 2021 20:17:02 +0000 http://robroyce.wordpress.com/?p=1147#comment-50 Thanks for this blog post. I can’t wait for part 2 (regarding step 10).

I have two questions: 1) Is this reversible? I mean, will I be able to return to SD as root device? 2) The purpose of read only systems or overlay systems is to protect the SD from being damaged on sudden power loss during write cycles. Is there anything known about whether or not such a USB stick is not the same way problematic as an SD?

Like

]]>
Comment on How to Boot Jetson Nano From USB 3.0 (Natively) with Jetpack 4.5 by DanDeng https://robroyce.dev/2021/02/11/how-to-boot-jetson-nano-from-usb-3-0-natively-with-jetpack-4-5/comment-page-1/#comment-49 Thu, 11 Mar 2021 16:23:45 +0000 http://robroyce.wordpress.com/?p=1147#comment-49 Thank you very much

successfully got job done exactly follow your papaer guide.

Dan

Like

]]>
Comment on How to Boot Jetson Nano From USB 3.0 (Natively) with Jetpack 4.5 by Yaroslav Stanko https://robroyce.dev/2021/02/11/how-to-boot-jetson-nano-from-usb-3-0-natively-with-jetpack-4-5/comment-page-1/#comment-48 Sun, 07 Mar 2021 20:15:17 +0000 http://robroyce.wordpress.com/?p=1147#comment-48 Hi Rob, thanx! I have a problem on my jetson nano 2gb. Exactly that https://medium.com/@cpyang/quick-summary-on-using-usb-external-disk-for-jetson-nano-301cc70616f1
USB 2 works, but USB 3 doesn’t work with my SSD.

Like

]]>
Comment on How to Convert Encrypted TLT Files to TensorRT Engine on Nvidia Jetson by Rob Royce https://robroyce.dev/2021/02/03/how-to-convert-encrypted-tlt-to-tensorrt-engine-on-nvidia-jetson/comment-page-1/#comment-47 Fri, 26 Feb 2021 18:37:22 +0000 http://robroyce.wordpress.com/?p=1081#comment-47 In reply to AnthonyJ.

Hey Anthony, thanks for pointing this out! It appears Nvidia changes the underlying link every week or so. Unfortunately this means the process will be slightly less convenient since users will have to navigate to the website to download, but that shouldn’t be a big deal. I’ll update the article to reflect your findings. I really appreciate the feedback!

Like

]]>
Comment on How to Convert Encrypted TLT Files to TensorRT Engine on Nvidia Jetson by AnthonyJ https://robroyce.dev/2021/02/03/how-to-convert-encrypted-tlt-to-tensorrt-engine-on-nvidia-jetson/comment-page-1/#comment-46 Fri, 26 Feb 2021 13:54:22 +0000 http://robroyce.wordpress.com/?p=1081#comment-46 FYI, the link to the trt-converter.zip seems to be broken. I found a different link to it via https://docs.nvidia.com/metropolis/TLT/tlt-getting-started-guide/text/deploying_to_deepstream.html#generating-an-engine-using-tlt-converter

Like

]]>
Comment on How to Boot Jetson Nano From USB 3.0 (Natively) with Jetpack 4.5 by Rob Royce https://robroyce.dev/2021/02/11/how-to-boot-jetson-nano-from-usb-3-0-natively-with-jetpack-4-5/comment-page-1/#comment-45 Fri, 26 Feb 2021 01:07:53 +0000 http://robroyce.wordpress.com/?p=1147#comment-45 In reply to Michael Newham.

Hi Michael, happy to help! One thing I found with the Nano devices in general is that the `sudo apt-get upgrade` command tends to break things, unfortunately.

I have indeed encountered this exact same issue and the only way I was able to fix it was by purging `nvidia-l4t-bootloader`, `nvidia-l4t-xusb-firmware`, and `nvidia-l4t-initrd`. I didn’t record my steps, unfortunately, but you should try `sudo apt-get purge nvidia-l4t-bootloader`, and so on. After purging all three of the specified packages, do a `sudo apt-get autoremove` and then reboot the device.

You will also find this issue discussed briefly on the Nvidia forum here: https://forums.developer.nvidia.com/t/dist-uopgrade-fails-on-l4t-bootloader/121346, which may or may not help you find a fix!

Like

]]>
Comment on How to Boot Jetson Nano From USB 3.0 (Natively) with Jetpack 4.5 by Michael Newham https://robroyce.dev/2021/02/11/how-to-boot-jetson-nano-from-usb-3-0-natively-with-jetpack-4-5/comment-page-1/#comment-44 Fri, 26 Feb 2021 00:22:20 +0000 http://robroyce.wordpress.com/?p=1147#comment-44 Now the issue is ‘dpkg’ errors on the usual apt update / upgrade command. I’ve posted the error output below. My install is on a Jetson Nano 2Gb – with the following firmware > — NVIDIA Jetson Nano (Developer Kit Version) L4T 32.5.1 [ JetPack UNKNOWN ] Ubuntu 18.04.5 LTS Kernel Version: 4.9.201-tegra — I’ll also post this on the Nvidia forums too – but you may have already encountered this. hence my post here. Error output below… Cheers, Michael. _______ Setting up nvidia-l4t-bootloader (32.5.1-20210219084526) … 3448-300-0003–1–jetson-nano-devkit-sda1 Starting bootloader post-install procedure. ERROR. Procedure for bootloader update FAILED. Cannot install package. Exiting… dpkg: error processing package nvidia-l4t-bootloader (–configure): installed nvidia-l4t-bootloader package post-installation script subprocess returned error exit status 1 Setting up nvidia-l4t-xusb-firmware (32.5.1-20210219084526) … 3448-300-0003–1–jetson-nano-devkit-sda1 Starting xusb firmware post-install procedure. ERROR. Procedure for xusb firmware update FAILED. Cannot install package. Exiting… dpkg: error processing package nvidia-l4t-xusb-firmware (–configure): installed nvidia-l4t-xusb-firmware package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of nvidia-l4t-initrd: nvidia-l4t-initrd depends on nvidia-l4t-xusb-firmware (= 32.5.1-20210219084526); however: Package nvidia-l4t-xusb-firmware is not configured yet. dpkg: error processing package nvidia-l4t-initrd (–configure): dependency problems – leaving unconfigured Setting up nano (2.9.3-2) … No apport report written because the error message indicates its a followup error from a previous failure. update-alternatives: using /bin/nano to provide /usr/bin/editor (editor) in auto mode update-alternatives: warning: skip creation of /usr/share/man/man1/editor.1.gz because associated file /usr/share/man/man1/nano.1.gz (of link group editor) doesn’t exist update-alternatives: using /bin/nano to provide /usr/bin/pico (pico) in auto mode update-alternatives: warning: skip creation of /usr/share/man/man1/pico.1.gz because associated file /usr/share/man/man1/nano.1.gz (of link group pico) doesn’t exist Processing triggers for man-db (2.8.3-2ubuntu0.1) … Errors were encountered while processing: nvidia-l4t-bootloader nvidia-l4t-xusb-firmware nvidia-l4t-initrd E: Sub-process /usr/bin/dpkg returned an error code (1)]]> Hi Rob, thanks for your efforts..

My go was successful and your commands have allowed me to use an SSD with at least a 5x speed increase over the old SD card 🙂

Now the issue is ‘dpkg’ errors on the usual apt update / upgrade command. I’ve posted the error output below. My install is on a Jetson Nano 2Gb – with the following firmware >

—
NVIDIA Jetson Nano (Developer Kit Version)
L4T 32.5.1 [ JetPack UNKNOWN ]
Ubuntu 18.04.5 LTS
Kernel Version: 4.9.201-tegra
—

I’ll also post this on the Nvidia forums too – but you may have already encountered this. hence my post here. Error output below…

Cheers, Michael.

_______

Setting up nvidia-l4t-bootloader (32.5.1-20210219084526) …
3448-300-0003–1–jetson-nano-devkit-sda1
Starting bootloader post-install procedure.
ERROR. Procedure for bootloader update FAILED.
Cannot install package. Exiting…
dpkg: error processing package nvidia-l4t-bootloader (–configure):
installed nvidia-l4t-bootloader package post-installation script subprocess returned error exit status 1
Setting up nvidia-l4t-xusb-firmware (32.5.1-20210219084526) …
3448-300-0003–1–jetson-nano-devkit-sda1
Starting xusb firmware post-install procedure.
ERROR. Procedure for xusb firmware update FAILED.
Cannot install package. Exiting…
dpkg: error processing package nvidia-l4t-xusb-firmware (–configure):
installed nvidia-l4t-xusb-firmware package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of nvidia-l4t-initrd:
nvidia-l4t-initrd depends on nvidia-l4t-xusb-firmware (= 32.5.1-20210219084526); however:
Package nvidia-l4t-xusb-firmware is not configured yet.

dpkg: error processing package nvidia-l4t-initrd (–configure):
dependency problems – leaving unconfigured
Setting up nano (2.9.3-2) …
No apport report written because the error message indicates its a followup error from a previous failure.
update-alternatives: using /bin/nano to provide /usr/bin/editor (editor) in auto mode
update-alternatives: warning: skip creation of /usr/share/man/man1/editor.1.gz because associated file /usr/share/man/man1/nano.1.gz (of link group editor) doesn’t exist
update-alternatives: using /bin/nano to provide /usr/bin/pico (pico) in auto mode
update-alternatives: warning: skip creation of /usr/share/man/man1/pico.1.gz because associated file /usr/share/man/man1/nano.1.gz (of link group pico) doesn’t exist
Processing triggers for man-db (2.8.3-2ubuntu0.1) …
Errors were encountered while processing:
nvidia-l4t-bootloader
nvidia-l4t-xusb-firmware
nvidia-l4t-initrd
E: Sub-process /usr/bin/dpkg returned an error code (1)

Liked by 1 person

]]>