SPI1 not worker on AGX orin

[Yanhou.LI]

I’m using JetPack 5.1.2, custom board for AGX Orin
use SPI1 connections to imu

I see the SPI pinmux setting is GPIO. Is this the right setup?
If set to SPI, How to set Pin Direction/Req. Initial State/Wake Pin/Initiator Target Mode/3.3V Tolerance Enable/LPDR .

[KevinFFF]

Hi Yanhou.LI,

@Yanhou.LI

I see the SPI pinmux setting is GPIO. Is this the right setup?

No, please configure the Column “Customer Usage” to SPI1_XXX.
You can just select he Pin Direction and Req. Initial State for them.
(let me take SPI mode 0 as example)
SPI1_SCK: Output/Drive 0
SPI1_DIN: Input/Int PD
SPI1_DOUT: Output/Drive 0
SPI1_CS0: Output/Drive 1
SPI1_CS1: Output/Drive 1

[Yanhou.LI]

It looks like SPI is not working

[KevinFFF]

@Yanhou.LI

It looks like SPI is not working

Please share the steps how you verify SPI.

Have you also tried using AGX Orin devkit to verify SPI?

[Yanhou.LI]

I connected SPI_MOSI_LVS and SPI_MISO_LVS on Orin devkit
It is possible to test SPI devices using spidev_test.

I have a problem, is that using /opt/nvidia/jetson-io/jetson-io.py this tool will not refresh the tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi this file has been flashed by flash.sh
If did not refresh the tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi file, it means that the SPI configuration of this file at the beginning can be used, right？

[KevinFFF]

@Yanhou.LI

is that using /opt/nvidia/jetson-io/jetson-io.py this tool will not refresh the tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi this file has been flashed by flash.sh

Jetson-IO should only be available for the devkit and it is used to configure the pinmux register.
It will generate the modified dtb under /boot/ on your board and load it during next boot.

For the custom carrier board, we would suggest just configuring pinmux spreadsheet before flash.