Open main menu

Humanoid Robots Wiki β

Changes

Nvidia Jetson: Flashing Custom Firmware

3,841 bytes added, 19:56, 30 August 2024
→‎Flashing the Kernel
= Developing Custom Flashing Standard Firmware = == SDKManager ==SDKManager is available only on Linux, and can be installed here: <code>https://developer.nvidia.com/sdk-manager</code># Start up the SDKManager# Put the Jetson into recovery mode. For the AGX, this can be done by pressing the recovery button while powering on the device. For the Jetson Orin Nano ==and NX, however, a jumper will be required. # Connect the Target Jetson to the host device and ensure that the target device is recognized.= Flashing = # Follow the instructions on the application, choosing configurations as necessary.
= Flashing Custom Firmware (For Jetson 36.3) =
== Pre-requisites ==
# Please install required packages with the command <code>sudo apt install build-essential bc && sudo apt install build-essential bc</code>.
=== Downloading the Toolchain ===
# Download the Toolchain binaries located in <code>https://developer.nvidia.com/embedded/jetson-linux</code>.
# From there, <code>mkdir $HOME/l4t-gcc</code>, <code>cd $HOME/l4t-gcc</code> and extract the installed toolchain into this newly created directory using the <code>tar</code> command.
== Downloading the Kernel ==
# Follow steps 1 to 3 as mentioned in Flashing Standard Firmware.
# Proceed to the second step of the SDKManager, where the respective individual dependencies and Jetson Images are listed and are to be installed. Proceed with the installation.
# When prompted to actually flash the Jetson, opt to skip. This will install the <code>nvidia</code> folder on your home directory, in which the <code>rootfs</code>, <code>kernel</code>, and <code>bootloader</code> are located.
# Navigate to <code>nvidia</code> and <code>cd</code> through its subdirectories, until <code>Linux for Tegra</code> is reached.
# Inside <code>Linux for Tegra</code>, <code>cd</code> into the <code>sources</code> folder. It should be unpopulated with the exception of some bash scripts. Run the <code>source_sync.sh</code> script and when asked to specify the release tag of the downloadable sources, enter <code>jetson_36.3</code>. This will install the sources for the respective Jetson version as necessary. To find the release tag of future iterations of the Jetson firmware, please refer to its respective release notes.
# Once sources have been synced, the <code>sources</code> directory should now be populated with the required files.
Notes:== Customizing Kernel ==- Current Design constraints: - Based off of # Within <code>source</code>, enter the <code>kernel</code> eventually navigate to the availability of parts in JLCPCB. Possibility of parts not being found or existing. <code>kernel-  jammy- Flashing is done with the flash.sh script through the following command $ sudo .src</flash.sh code> folder and run <boardcode> make menuconfig ARCH=arm64<rootdev/code> where board is the actual board (Jetson-Nano-XX, etc.)rootdev determines what type of device is being flahed. Use mmcblk0pc1 to flash This will bring up a local storage device (eMMC or SD card)- TO begin flashing, put the device into force recovery mode UI with configurable drivers and then press resetperipherals. - Run the flash script using the previous command specifiedSelect desired configurations and save. Flash using a convenient script: - To avoid having to specify the rootdev and the board # The configurations, can use be found within a <code>.config</code> file located within the custom flashing script: -  Using GPIO Pins to program protocol:- you can use same directory. Copy the rasberry pi libraries to interface with contents and locate the pins<code>defconfig</code> file in <code>./arch/arm64/configs/</code>, configuring them to whatever layout that is needed. - Example: overwriting it is possible to direclty interface with the i2c system in the nano by using the linux terminal itselfcopied contents.
== Building Custom Kernel and Installing Modules ==
# Navigate back out to <code>sources</code>.
# Define the Cross-compilation toolchain with the commands <code>export CROSS_COMPILE=<toolchain-path>/bin/aarch64-buildroot-linux-gnu-</code>. If installation was done correctly as per the pre-requisites section, the command <code>export CROSS_COMPILE=$HOME/l4t-gcc/aarch64--glibc--stable-2022.08-1/bin/aarch64-buildroot-linux-gnu-</code> should work.
# Define the Cross-compilation toolchain with the commands <code>export CROSS_COMPILE_AARCH64_PATH=</code>, and <code>export CROSS_COMPILE_AARCH64=/bin/aarch64-buildroot-linux-gnu-</code>. (Potentially deprecated)
# Inside the sources, directory, make an output directory for built kernel files using <code>mkdir kernel_out</code>.
# Build the modules using the command <code>./nvbuild.sh -o kernel_out</code>. This will compile the drivers and device trees for the new kernel.
# Navigate out from the <code>sources</code> directory into the <code>Linux for Tegra</code>.
# Use the <code>cp</code> to overwrite <code>./rootfs/usr/lib/modules/5.15.136-tegra/updates/nvgpu.ko</code> with <code>./source/kernel_out/nvgpu/drivers/gpu/nvgpu/nvgpu.ko</code>.
# Repeat the previous step to replace <code>Linux_for_Tegra/kernel/dtb/</code> with </code>source/kernel_out/kernel/kernel-jammy-src/arch/arm64/boot/dts/nvidia</code>. Ensure that instead of overwriting the directory, only the files are copied over.
# Overwrite the Image file in <code>./kernel</code> with <code>./source/kernel_out/kernel/kernel-jammy-src/arch/arm64/boot/Image
</code>.
# To specify the installation path for the compiled modules, use the command <code>export INSTALL_MOD_PATH=$HOME/nvidia/nvidia_sdk/JetPack_6.0_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra/rootfs/</code>.
# Install modules using the command <code>./nvbuild -i</code>. The Jetson is now ready to be flashed.
Current Game Plan:== Flashing the Kernel ==- mess around with Ensure that the programming of target Jetson is connected to the GPIO pins: Figure out if there are ways host device and is in recovery mode. Navigate to choose access teh data that the GPIO pins are Or Receiving<code>Linux for Tegra</code> directory and run <code>sudo .Test if /nvsdkmanager_flash.sh</code>. When prompted, disconnect the Jetson from host device and allow it is possible to reconfigure the pins on the jetson on the boot. Congratulations, you have successfully flashed your Jetson with custom firmware side.
Vedant
49
edits
Retrieved from "http://54.204.126.50/w/Special:MobileDiff/1435...1832"