Adaptation of NVIDIA Code r36 on Jetson Orin Nano for Custom Hardware Platform

Autonomous Machines Jetson & Embedded Systems Jetson Orin Nano
,
1

I am currently working on adapting NVIDIA code r36 for the Jetson Orin Nano to support a custom hardware platform. The only adaptation document I have found is the one for the Jetson Orin AGX, located at the following link: https://developer.download.nvidia.com/assets/embedded/secure/jetson/agx_orin/Adaptation_and_Bringup_for_Jetson_AGX_Orin.pdf?dlFwy1kqbwF7xpeZ-DBXhKjYphkJpqnPY1Wfufl93zdTGgrrCYE3C108pY7dZY6j7ZBf8M6ak6eHBgeJLNA5aq2MrGNE3hB3k2eGURG4cNXqVEZqTymDPPWnkSB8n58koQdkXesEsPM4jiZnxXfDKCEapLELhwPu7jIEQ4mZNpVu7KhmtnuY-OriGwjD0dpGz82tXQ==&t=eyJscyI6ImdzZW8iLCJsc2QiOiJodHRwczovL3d3dy5nb29nbGUuY29tLyIsIm5jaWQiOiJwYS1zcmNoLWdvb2ctMzAzMzgzIn0=

I would like to confirm whether this document is applicable for adapting the r36 code to the Jetson Nano. If it is not, could you please provide the correct documentation or instructions specific to the Jetson Nano for this adaptation process?

2

Please refer to Jetson Orin NX and Nano Series — NVIDIA Jetson Linux Developer Guide 1 documentation

3

I went through the process as outline in Jetson Orin NX and Nano Series — NVIDIA Jetson Linux Developer Guide 1 documentation
but I’m having problem with the process
my steps were -

  1. define pinmux/gpio/padvoltage using Excel spreadsheets
  2. copy over new custom specific .dtsi per the document
  3. create new .conf. used p3768-0000-p3767-0000-a0.conf as starting point. added new .dtsi in please of existing pinmux/padvoltage, noted that new gpio .dtsi in pulled in through include in pinmux
  4. from my ubunut 20.04 performed - sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1
    -c tools/kernel_flash/flash_l4t_t234_nvme.xml -p “-c bootloader/generic/cfg/flash_t234_qspi.xml” \
    –showlogs --network usb0 cernis internal

processed did not complete successfully and I’m not sure where to start looking for the problem. would be great is someone could look at the logs (terminal and debug port) see if they see something that could push me along

Thanks
Fred

4

flash log
https://www.dropbox.com/scl/fi/064c03y8146jbz6nbsruk/flash_log_101724.txt?rlkey=mbw61x7vrbg90mde3tu4ox48z&st=zy1wx26v&dl=0
flash debug log
https://www.dropbox.com/scl/fi/0nxl1se61b1hoyummrkaw/flash_debug_101724.txt?rlkey=pgmqsbzg9ggz2h4jftg9883p3&st=c6tj2vef&dl=0

6

Hi fhardy,

Do you mean Jetson Nano or Orin Nano?

cp: cannot stat '/home/fred/code/nano-bsp/Linux_for_Tegra/rootfs/lib/modules/5.15.136-tegra/kernel/drivers/nvme': No such file or directory
Cleaning up...

From the log you shared, is there <Linux_for_Tegra>/rootfs/lib/modules/5.15.136-tegra/kernel/drivers/nvme in your host?

How did you create BSP package and setup for sample rootfs?

7

Hey Kevin

You’re right I meant Orin Nano. I pulled files using the linked shell script Dropbox

8

Kevin

I did a clean checkout and build and now everything looks good. Sorry for the trouble and thanks for you help

Cheer
Fred

9

I don’t see my changes being incorporated into the dtb. can you specify whether my steps are correct -

  1. define pinmux/gpio/padvoltage using Excel spreadsheets
  2. copy over new custom specific .dtsi per the document
  3. create new .conf. used p3768-0000-p3767-0000-a0.conf as starting point.
  4. add new .dtsi in place of existing pinmux/padvoltage, noted that new gpio .dtsi in pulled in through include in pinmux
  5. from my ubunut 20.04 performed - sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1
    -c tools/kernel_flash/flash_l4t_t234_nvme.xml -p “-c bootloader/generic/cfg/flash_t234_qspi.xml”
    –showlogs --network usb0 cernis internal
10

Are you trying to develop a custom board for Orin Nano?

Please just refer to our adaptation guide and customize them according to your design.

11

Kevin

I am using the adaptation guide. It is not as clear as I would like, that’s why I am not sure of my implementation.Does it look right to you?

Thanks
Fred

12

Kevin

I created new issue to cover current problem. Please take a look if you have some time

Thanks
Fred

13

okay, let’s just move to that topic to discuss in details.

15

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.