Custom carrier board

[chris40knaack]

Is there a good guide or example for dealing with customer carrier board. I have a AGX Orin SoM on a custom carrier board that requires changes to the pinmux template. I am not understanding the workflow to create a new MACHINE type and where to apply the pin mux changes. Additionally I have to integrate some new PCIe devices which I have drivers for but not sure how to add these? Are the recipe specific out of tree modules? Would they be deployed as ko files in the filesystem image?

Assumptions
Pinmux template changes generate dtsi files thay some python tool manipulates in the build process. Ultimately those effect the DTB file associated with the kernel during MB1/2 boots?

New devices added to carrier board, a dts/dtsi file can be added to the build process to get combined into the dtb file saved on the disk? or the overlay version?

Does the MACHINE type in the conf let you define the ODMDATA field that seems to effect the assumed PCIe setup.

[dwalkes]

https://github.com/OE4T/meta-tegra/wiki/Creating-a-custom-MACHINE is probably the best starting place, maybe also https://github.com/OE4T/meta-tegra/wiki/Using-device-tree-overlays. I'm sure both could use some cross-links or improvements so as you find things that are missing updates are appreciated. Searching the OE4T org and filtering first by wikis and then by discussions/issues is probably the best way to find what we currently have. See https://github.com/search?q=org%3AOE4T+custom+carrier&type=wikis for instance.

Also note that the process depends a lot on which branch you are on, so in most cases you'll want to start discussions like this by mentioning a target branch.