03:50 <aandrew> hello. I've got a banana pi m2 zero running Armbian 23.05; it's working, but I'm trying to get SPI working with the chip select on a non-standard pin (PA20, pin 40 on the 40-pin expansion connector)

03:50 <aandrew> I've modified the "cs1" device tree fragment to do so, but it doesn't appear to be doing the right thing.

03:51 <aandrew> using sunxi-pio -m PA20 I can see that after boot it's set up for pinmux 7 which is marked as "reserved"

03:51 <aandrew> and the SPI transfers don't appear to be working because the device isn't getting selected

03:52 <aandrew> if I use sunxi-pio -m 'PA20<1><0><0><0>' to set PA20 to an output and drive it low, then spi-pipe to do the transfer, then setting the pin back high it is working fine

03:52 <aandrew> so I know the hardware's connected up correctly, but I'm confused as to how to correctly set up an alternative CS1 pin

03:53 <aandrew> my fragment is here: https://pastebin.com/JrQ1bMq0

03:54 <aandrew> I just deleted the fragments for SPI1 and edited the cs-gpios line from cs-gpios = <0x00 0xffffffff 0x00 0x15 0x00>; to cs-gpios = <0x00 0xffffffff 0x00 0x14 0x00>; which should be moving the CS1 for SPI0 from PA21 to PA20

03:55 <aandrew> my armbianEnv.txt loads the compiled user overlay and selects CS1:

03:55 <aandrew> user_overlays=spi0-cs1-pa20

03:55 <aandrew> param_spidev_spi_bus=0

03:55 <aandrew> param_spidev_spi_cs=1

18:05 <DC-IRC> [Discord] <sqilson> Hello, I am looking to use Armbian for a robotics project, which will require real-time kernel. Is it possible to configure this functionality with the Armbian build system kernel configurations? If someone could point me in the right direction, that would be much appreciated. Thanks

18:21 <DC-IRC> [Discord] <c0rnelius77> Didn't RT recently get merged into the Kernel? Like officially.

18:31 <DC-IRC> [Discord] <c0rnelius77> yea its in 6.12.y `( ) Fully Preemptible Kernel (Real-Time`

18:56 <DC-IRC> [Discord] <lands39> how do i flash the generic image to an sd card?

18:56 <DC-IRC> [Discord] <lands39> its a qcow2 image, i'm not using qemu though

19:32 <DC-IRC> [Discord] <lands39> that didn't work so i used the image made for the device which did work

19:32 <DC-IRC> [Discord] <lands39> then used dd to copy the image to emmc and we're good

19:32 <DC-IRC> [Discord] <lands39> does this bridge bot forward images?

19:45 <DC-IRC> [Discord] <Github> ⤴️ **Pull request** to [armbian/build](<https://github.com/armbian/build>) by [igorpecovnik](<https://github.com/igorpecovnik>) - **Please review!** 👉 [Link](<https://github.com/armbian/build/pull/7189>): *`Userspace`: Switch armbian-config to new generation. It has very small footprint, thus it will be installed by default*

19:59 <archetech> c0rnelius77 feel like makin a rock5 image

20:23 <DC-IRC> [Discord] <sqilson> I heard that as well. But on the other hand, the chip I am using (RK3588S) is not fully supported in mainline linux. Has anyone tried this?

20:23 <DC-IRC> [Discord] <sqilson> https://gitlab.collabora.com/hardware-enablement/rockchip-3588/notes-for-rockchip-3588/-/blob/main/mainline-status.md

20:24 <DC-IRC> [Discord] <sqilson> I heard that as well. But on the other hand, the chip I am using (RK3588S) is not fully supported in mainline linux, so there may be conflicts. Has anyone tried this with a real-time kernel?

20:24 <DC-IRC> [Discord] <sqilson> https://gitlab.collabora.com/hardware-enablement/rockchip-3588/notes-for-rockchip-3588/-/blob/main/mainline-status.md