Replies: 2 comments 1 reply
|
I suggest you do a diff between the default dtsi and this one you've generated, and compare it between the 8gb default and 8gb generated ones. If you can report that here we might be able to help you. I'm assuming you've double checked all the assignments in your project and the correct files are getting picked up. |
0 replies
|
My custom gpio (generated from XLMS) and defsult gpio has some good difference. After I copied the missing pin and it is working. But these pin data does not needed for 4gb SOM. Where can I find these PIn details so that I can make decission. tegra234-mb1-bct-gpio-p3767-dp-a03.dtsi.txt |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi developers,
Though it is not directly connected with the meta-tegra layer, I would like to ask, as my full project is based on the Ycto tool now.
I am working with the Jetson Orin Nano custom carrier board with 4 GB SOM. For the custom board, we got an updated XLMs file where I generate pinmux, padvoltage, and GPIO DTSI file, and apply it to my image. Till now, everything was working.
Recently, I got an 8 GB SOM to test with this custom board. Default dtsi files are working, but when I am trying to apply the 4 GB version's dtsi file, the flash is failing. Specifically, pinmix dtsi (gpio is calling from here) is the main reason.
I have attached the XLSM file. Why is it failing?
Custom_Pinmux_Config.xlsm
All reactions