martinayotte

Sorry, I forgot to use "raw" URL which is https://raw.githubusercontent.com/torvalds/linux/master/tools/spi/spidev_test.c

Grab the file and compile it, then run it : wget https://github.com/torvalds/linux/blob/master/tools/spi/spidev_test.c gcc -o spidev_test spidev_test.c ./spidev_test -D /dev/spidev1.0

I'm not even sure if there is cs-gpio support in Rockchip, it is another thing-to-do on top of spi-add-cs1 overlay.

You can make minimal test byt using a loopback wire between MISO/MOSI, and run ./spidev_test from : https://github.com/torvalds/linux/blob/master/tools/spi/spidev_test.c

Yes, except the typo of missing underscores, it is correct as long as you don't have SPINOR Flash soldered on bottom side of the board, since it is using CS0. For multiple SPIs, you need to write a custom overlay yourself. For spi-add-cs1, we will provide it some days in the futur, it only available for AllWinners for now, not for Rockchip or Meson.

Dual CS isn't yet supported. You can only use channel 0 for the moment, except if you manually handle gpios yourself.

When using "sudo", it only affect the left part, here "echo", everything at right of ">" isn't "sudo" applied ... So, if you wish to use "sudo", syntax would be : echo "default-on" | sudo tee /sys/class/leds/orangepi:green:pwr/trigger Note here : "power" is not an available choice, do "cat /sys/class/leds/orangepi:green:pwr/trigger", it will show you all possible choices and the current setting is indicated with brackets. The choice you probably wish is "default-on".

Your log look like "console=serial" wasn't present, did you verify for some typo ?

https://www.cnx-software.com/2019/11/19/orange-pi-4-4b-sbc-rockchip-rk3399-soc-gyrfalcon-2801s-npu/

armbianEnv.txt is not a script, it is environment. So change the following : rootdev=UUID=69c4417e-e866-4934-8625-bd5fed6f21d5 to : rootdev=/dev/mmcblk0p2

It seems that I'm not in the user list ...

Most probably, you can turn it on at this line for DEV : https://github.com/armbian/build/blob/master/config/kernel/linux-mvebu-dev.config#L1902 or at this line for NEXT : https://github.com/armbian/build/blob/master/config/kernel/linux-mvebu-next.config#L1752

I've done private builds using Megous's 5.4.0 branch for almost all my SUNXI boards, so, I'm pretty confident that we can switch to it soon ...

How did you specified UART4 overlay in /boot/armbianEnv.txt ? It should be : overlays=uart4 EDIT: Also, "uart4" should be placed AFTER any spi-spidev, since this UART sharing pins with SPI.

GPIO2_B1 = SPI2_MISO GPIO2_B2 = SPI2_MOSI GPIO2_B3 = SPI2_CLK GPIO2_B4 = SPI2_CS0 So, you don't need spi-add-cs1 overlay in such case. The UART4 overlay is working fine on both my RockPro64 and RockPi. Check "dmesg | grep tty" to see if it became active. You can also use a looback wire to test it. EDIT: I've just tested UART4 overlay also on my NanoPiM4 ...