I have failed to get the data on spi interface on the jetson nano. The module I am using interface on spi is ADIS16470 which I have test on ardiuno uno to reverify the module
Hi roysuraj39,
Are you using the devkit or custom board for Jetson Nano?
What’s the Jetpack version in use?
Could you refer to the following thread for the steps to verify SPI loopback test first?
Jetson Nano SPI Bus Not Working - #10 by KevinFFF
It seems a custom carrier board developed by Seeed Studio.
Please refer to the following thread to verify SPI loopback test first.
Please provide the flash log first, but I would suggest you opening another topic for better tracking.
Can provide me the further steps and link
after doing all step as given in Jetson Nano SPI Bus Not Working - #10 by KevinFFF but still failed to enable the spi. Done both method tegra210-p3448-0000-p3449-0000-b00.dtb and tegra210-porg-gpio-p3448-0000-b00.dtsi.
After making change in tegra210-p3448-0000-p3449-0000-b00.dtb assemble the dts back to dtb and then flash to nano but still in nano if i still check for tegra210-p3448-0000-p3449-0000-b00.dtb inside nano remain default in dissemble the dtb to dts
It is not our official devkit so that you have to configure the pinmux from pinmux spreadsheet instead.
Could you just perform dissembling DTB and update the dts on the device and reboot to apply the change?
After making change in tegra210-p3448-0000-p3449-0000-b00.dtb assemble the dts back to dtb then reboot nano. gpio-input parameter get change but still spi not getting up.
After run this command only showing CSI CONNECTOR header no spi.
I am upload my default tegra210-p3448-0000-p3449-0000-b00.dts file
tegra210-p3448-0000-p3449-0000-b00.txt (318.9 KB)
The current values of pinmux register are not expected for SPI usage.
Please use pinmux spreadsheet to configure the pinmux instead.
From which file I can change pinmux?
ano@nano-desktop:~$ sudo grep -C 4 spi1 /sys/kernel/debug/pinctrl/pinctrl-maps
device 700008d4.pinmux
state unused
type MUX_GROUP (2)
controlling device 700008d4.pinmux
group spi1_mosi_pc0
function rsvd1
device 700008d4.pinmux
state unused
type CONFIGS_GROUP (4)
controlling device 700008d4.pinmux
group spi1_mosi_pc0
config pull=1
config tristate=1
config enable-input=0
device 700008d4.pinmux
state unused
type MUX_GROUP (2)
controlling device 700008d4.pinmux
group spi1_miso_pc1
function rsvd1
device 700008d4.pinmux
state unused
type CONFIGS_GROUP (4)
controlling device 700008d4.pinmux
group spi1_miso_pc1
config pull=1
config tristate=1
config enable-input=0
device 700008d4.pinmux
state unused
type MUX_GROUP (2)
controlling device 700008d4.pinmux
group spi1_sck_pc2
function rsvd1
device 700008d4.pinmux
state unused
type CONFIGS_GROUP (4)
controlling device 700008d4.pinmux
group spi1_sck_pc2
config pull=1
config tristate=1
config enable-input=0
device 700008d4.pinmux
state unused
type MUX_GROUP (2)
controlling device 700008d4.pinmux
group spi1_cs0_pc3
function rsvd1
device 700008d4.pinmux
state unused
type CONFIGS_GROUP (4)
controlling device 700008d4.pinmux
group spi1_cs0_pc3
config pull=1
config tristate=1
config enable-input=0
device 700008d4.pinmux
state unused
type MUX_GROUP (2)
controlling device 700008d4.pinmux
group spi1_cs1_pc4
function rsvd1
device 700008d4.pinmux
state unused
type CONFIGS_GROUP (4)
controlling device 700008d4.pinmux
group spi1_cs1_pc4
config pull=1
config tristate=1
config enable-input=0
Please refer to the following link for the pinmux change on Jetson Nano.
NVIDIA Jetson Linux Developer Guide : Jetson Module Adaptation and Bring-Up | NVIDIA Docs
Pinmux spreadsheet can be downloaded from Jetson Download Center | NVIDIA Developer
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.