Help with new board.conf file

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin Nano
1

It’s my first time bringing up an orin jeston custom board and I’ve got a couple questions

  1. after the instructions relating to pinmux dtsi files it says “ensure that you point these files to the new board.conf file” how do I do this? is it the PINMUX_CONFIG and PMC_CONFIG terms in the .conf file? what do I need to change or keep the same in the file as the example configuration script? the example flash script references a source, how do I select the source document? what are its implications? where should this .conf file be kept?

  2. what is a VPR Carve out and what is it used for?

  3. The eeprom modification example points to a specific dts file "booloader/generic/BCT/tegra234-mb2-bct-misc-p3767-0000.dts, is it the same file for a custom carrier as well? or do we need to create a new one.

Thanks!

2

Forget about that creating new file things. Those are for someone who is really familiar with how things work here.

If you are totally new to these, then don’t need to create your own config, just use the original one.

what is a VPR Carve out and what is it used for?

This has nothing to do with any interface bring up. Please don’t try to change it.

The eeprom modification example points to a specific dts file "booloader/generic/BCT/tegra234-mb2-bct-misc-p3767-0000.dts, is it the same file for a custom carrier as well? or do we need to create a new one.

No need to create new one. Just use it for your custom board.

3

Hi thanks for the fast response!

So you would recommend just changing the eeprom setting and nothing else?

4

Modifying eeprom is just the basic item. The rest of things depend on your custom board design.

For example, if the USB setting is not same as NV devkit, then it needs to be changed in device tree too. As I said in another post, you should find someone who is familiar with Linux kernel to help here. Otherwise it would have painful learning.

5

Hi WayneWWW,

I appreciate the warnings but unfortunately this is something I need to deal with, so if painful learning is what’s needed, then it’s what’s going to have to happen.

  1. I think the only thing I need to do to at least get this to flash (even if several interfaces dont work) is to change the eeprom file setting as I suspect it’s causing issues. what are the necessary steps (at a high level) required to make this change to the default dev kit image and flash it?

  2. Do you have any sources you’d recommend for learning the required context for this?