Closed JW94 closed 4 years ago
That looks close. pc1 is an input pin for SPI, so you want to change its nvidia,enable-input
property to be TEGRA_PIN_ENABLE
. You probably also want to disable tristate on all five pins.
One way to get the right settings is to download the pinmux spreadsheet for the Nano dev kit from the NV download center, load it into Excel on Windows, carefully reconfigure the pins you want to modify, and have the spreadsheet's macros generate the -pinmux-
and -gpio-
DTS files for you.
Another would be to use the jetson-io
python scripts that NV started including in L4T 32.3.1. You'd have to load up your Nano with the stock L4T image, run the scripts there, then look at the changes it makes to the device tree for your configuration choices and apply them back to your device tree source. They document its use here. I haven't tried it myself, though.
Thank you for your super fast response! You're right, there were some misconfigurations and they dropped after using the spreadsheets you recommended.
After generating a dts with the spreadsheet the spi is working properly!
I attach the patch file which I added to the bbappend in my custom meta-layer.
Thank you!
Hey guys,
I want to enable SPI-support for the Jetson Nano Developer Kit p3449 0000 a02. I started to create a new patch for the linux-tegra recipe. I add the diff to this issue that somebody can understand and help me.
As far as I know, I need to edit the pinmux configuration of the SPI-Pins but I cannot find any source which tells we what pins have to be edited. The only information I have is this commit https://github.com/rt-net/JetsonNano_DT_SPI/commit/79d4698ac518ab4cc9662ae8bd7e282f56f31cab
Thank you in advance!