It should be PIN19(SPI0_MOSI) and PIN21(SPI0_MISO) of 40-pins expansion header.
Could you take a picture of your connection?
Have you measured the waveform when you’ve shorted PIN19 and PIN21?
Please share the result of $ cat /etc/nv_boot_control.conf on your board.
For Jetson Nano, please refer to Jetson Nano SPI Bus Not Working - #10 by KevinFFF
busybox is just used for devmem command.
I will attach a picture of my connection here. Also I have not measured the waveform when the pins are shorted, I did measure them individually though as shown earlier in the forum.
Here is the result of running this command.
From the previous waveform result, it looks good to me.
Please also help to check if it is the same when you short them.
Im not sure how to conduct that measurement, but I am going to reflash the NVIDIA Jetson Orin Nano Developer Kit using the SDK manager using a virtual machine on my windows PC.
So I reflashed the Orin Nano with a JP6.0 image from the following link:
When doing so, I did not install anything else other than the brave browser, installed spidev 3.6, updated and upgraded any packages that needed to be upgraded, VSCODE , and I am still getting the same error using the following commands.
1. Run Jetson-IO to configure the SPI pins
$ sudo /opt/nvidia/jetson-io/jetson-io.py
Configure Jetson 40pin Header => Configure header pins manually => Select "spi1 (19,21,23,24,26)" => Back -> Save pin changes => Save and reboot to reconfigure pins
2. Probe SPI driver
$ sudo modprobe spidev
3. Build spidev_test tool
$ wget https://raw.githubusercontent.com/torvalds/linux/v4.9/tools/spi/spidev_test.c
$ gcc -o spidev_test spidev_test.c
4. Run the tool to verify
$ sudo ./spidev_test -D /dev/spidev0.0 -O -H -v -p "HelloWorld123456789abcdef"
I did make sure that I shorted pins 19 and 21 as well as probing spidev, yet I still receive the same error as previously seen.
I would like to check the MOSI and MISO signal when they are disconnected and also they are connected to check if you can get the expected signal.
Do you have another Orin Nano devkit to reproduce the same issue to check if the issue is specific to current board? (since I’ve verified it working on my devkit)