Set the Jetson Dev Kit into Force Recovery Mode: Connect the Jetson using the USB-C port located next to the 40 pin GPIO header. Make sure to save any data you need before flashing!Ĭonnect the Dev Kit to the Host with a USB cable. WARNING: The AGX Orin is going to be wiped by the next procedure. The Orin Nano overlay will be installed in the Linux_for_Tegra folder. $ sudo tar xpf Orin_Nano_Overlay_35.1.tbz2 If you are using the Orin Nano overlay, then expand it. The command for untarring the SAMPLE_FS_PACKAGE is a little different than in the documentation, because we use the full path the package when we set the environment variable. You can source it from your open Terminal by: $ source ~/.bashrc SAMPLE_FS_PACKAGE=~/JetPack5.0.2/Tegra_Linux_Sample-Root-Filesystem_R35.1.0_aarch64.tbz2 Here’s a sample where the files are in the JetPack5.0.2 folder in the home directory: L4T_RELEASE_PACKAGE=~/JetPack5.0.2/Jetson_Linux_R35.1.0_aarch64.tbz2 These settings should reflect where you download the files. In the file ~/.bashrc In the video we use gedit to place the variables at the end of the file. One way to do this, as shown in the video, is to set the environment variables: After you complete the download, you need to set some OS environment variables. This is where the image to flash the Jetson will be built, so you should have plenty of room available before starting. I usually download the BSP and sample rootfs to a new folder. For this article we are using Jetson Linux 35.1.Ī couple of comments about the procedure. These are available by following this link to the appropriate download page. To emulate the Orin Nano, you will also need the orin-nano-overlay. On a host x86 computer running Ubuntu 18.04 or 20.04, download both the Driver Package (BSP) and Sample Root Filesystem. The official NVIDIA document for flashing a Jetson is here: To Flash the Jetson Developer Kit Operating Software. Download and install JetPack to the Jetson.After flashing, go through the initial Linux for Tegra configuration.Set the Orin Dev Kit into Force Recovery Mode.Select which Orin module you want to emulate.Extract the downloaded files and prepare the package that will be flashed to the Jetson.Another name for the Driver Package is the Board Support Package ( BSP).Download to the Host the Jetson Driver Package and sample rootfs for the AGX Orin.Preparing a Jetson AGX Orin Developer Kit for emulation is a three step process: You are working on critical applications, aren’t you? Setting up Emulation However, you should still do final verification testing on a real device for critical applications. I am guessing that the device tree is modified on the dev kit to exclude their availability.īecause the Jetson Orins are similar in their over all design, you should expect excellent fidelity in the emulation. For example, the Jetson Orin Nano module does not have hardware video encoding or a Programmable Vision Accelerator ( PVA). There are a couple of hardware features that may need to be disabled. Set the clock speeds for the CPU and GPU, limit the amount of memory, and assign the number of CPU and GPU cores for a given model. A lot of the emulation is done by changing hardware settings. The Orin Dev Kit has some advantages when it comes to emulating other Orin modules. That’s what makes it fun! Jetson Orin Developer Kit It will get you most of the way there, but there’s always a little bit of danger too. With that said, emulators are great tools for getting started with new designs, initial testing of designs on a variety of hardware configurations, and legacy testing. Emulators will bite you, given the chance. Many people have been bitten relying only on emulation for verifying their application or product. They are acting as a device, but they are not the device itself. Each play their own role in the development cycle. The game is emulated, but is able to run at much higher clock speeds, graphic resolutions, and so on. You’ll see this in applications such as game emulators. Other emulators are far more generous in their criteria. This is the result of the amount of knowledge that one has to have to replicate what is typically legacy hardware or software stacks. This tends to be where the serious developers live. Note that this usually requires special hardware to replicate the experience. The idea is that one should not be able to tell that the difference between the emulator and the real thing. All of the same architectural features, instruction sets, and even errata and flaws are reproduced. These emulators mimic the device they are trying to copy exactly. People have different ideas about the emulation experience. IntroductionĮmulators are a very interesting corner of Computer Science. Think about this article as supplemental. Note: that there is an excellent article on the NVIDIA Developer blog about this very subject: Develop for All Six NVIDIA Jetson Orin Modules with the Power of One Developer Kit.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |