Regarding activation of jetson nano devkit spi

Hello,

I use the jetson-io tool to activate the spi and use the spi well.
If you make /proc/device-tree with dts as shown below,
nvidia,function = “rsvd2”; It’s like this.
Shouldn’t it be spi1 instead of rsvd2?

sudo dtc -I fs -O dts -o extracted_proc_coding_new.dts /proc/device-tree

Thank you.

Yes and need to confirm which pin. Like spi1_/spi2_

                        spi1_mosi_pc0 {
                                nvidia,enable-input = <0x1>;
                                nvidia,pins = "spi1_mosi_pc0";
                                nvidia,tristate = <0x0>;
                                nvidia,function = "spi1";
                                nvidia,pull = <0x1>;
                        };

1 Like

Hello, @ShaneCCC

But, what is the reason that there is no problem with spi communication even when nvidia,function = “rsvd2” like this?

The contents of spi activation using jetson-io.py are
Is it not reflected in /proc/device-tree?

After activating spi using jetson-io.py, you can check the waveform change through the oscilloscope.

So, as expected, if you extract dts through the following command,
I was expecting nvidia,function = '“spi1”, but
nvidia,function = “rsvd2”
I want to know the reason.

sudo dtc -I fs -O dts -o extracted_proc_coding_new.dts /proc/device-tree

Thank you.

If using jetson-io that will override those pins like.

			pin21 {
				nvidia,enable-input = <0x1>;
				nvidia,tristate = <0x0>;
				nvidia,pull = <0x1>;
				nvidia,pins = "spi1_miso_pc1";
				nvidia,function = "spi1";
			};
1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.