royk

@CryBaby Could you explain why? Because when I set my TTL adapter to 5v there is 5v on the rx and tx pins, since you connect at least gnd and tx or rx......

@elsabz After setting "gpio export 46 in" and "gpio export 54 in" I can see it counts interrupts when I connect it to ground. test.c

@elsabz You could try to run first: "gpio export 92 out"

@ArmBoy1988 You'll need one @3.3v there is also voltage on the data pins. To only read the serial data you only need to connect 2 wires OPI. Adapter Gnd - gnd TX - RX I don't think that the UART pins are 5v tolerant.

I don't have experiences with wiringpi in c code, but did you look at the examples and do you use the "next" branch for the library? https://github.com/orangepi-xunlong/wiringOP/tree/next/examples

@ArmBoy1988 This one should do https://www.amazon.ca/DSD-TECH-SH-U09F-Adapter-Featuring/dp/B07K76Q2DX/

@going TBH I don't know how he did test it, I assumed he connected a monitor via HDMI. I've never tested it with 4 cores isolated because isolating core 5 and 7 is good enough. This is the result of a test I did with Wayland and xwayland and isolcpus=5,7 (connected with HDMI) https://forum.linuxcnc.org/18-computer/48079-can-the-opi5-be-configured-to-run-lcnc?start=40#268426 With XFCE It shall be around the same but the graphics acceleration will be worse. Without isolating cpus the latency will be around 20 uS With the 6.2 kernel I've tried with XFCE, it worked well, but its hw support is still in progress: https://forum.linuxcnc.org/18-computer/48079-can-the-opi5-be-configured-to-run-lcnc?start=120#270027 A bit off-topic but read someone from this forum was busy creating a rt-kernel for a s922 sbc, the s9xx kernel did also work fine for a s912 tv-box (connected with HDMI): https://forum.linuxcnc.org/18-computer/39371-results-of-latency-test-list-of-computers-tested-for-use-with-linuxcnc?start=330#270625

Yes I've compiled a few rt kernels and it does work pretty well. To use the legacy kernel you really don't want to patch it yourself, some parts are patched many versions ahead and some parts are left behind. But there luckily is an already by Rockchip rt patched kernel. You only need to use the right config and add the dtb to make it work. I've made a patch for it so you could make your own, a bit messy but works very well (at least for LinuxCNC). https://mega.nz/folder/zhwVyJBK#iWqElAfYL21Rn08PmB55DA You want to use it for music? DJ-ing? It depends on what you exactly need for that, the 5.10.x kernel has a lot of issues with usb audio interfaces, this seems to be fixed since 5.15 or 5.16, my Motu M4 is unusable with it but you could try yours. If you want to use USB audio interface as input and output I recommend to use a newer kernel version, the rt patches over the 6.2 kernel from balbes150 his github did compile without problems, compare the kernel config with the 5.10.x rt kernel but keep the pancsf module. The 6.2 kernel I didn't upload but should have it somewhere laying around. The armbian build system has issues with local versions, the rt patches adds that so you'll need to remove that. Results with the 5.10.x kernel: https://forum.linuxcnc.org/18-computer/48079-can-the-opi5-be-configured-to-run-lcnc?start=170#271679

Yup packaging looks good indeed, ordered one too so I could use the "old" one for LinuxCNC (great machine for it). Would've been better if it had a 12v dc input, atm I'm using a 5v 4a usb c adapter, it seems like this is giving me sporadic issues. Hopefully this isn't the case with the OPi5+. Otherwise power direct on the pins worked fine. I hesitated to buy the NanoPC-T6 which has a nice case (20,-) and 12v input, but it doesn't have MTD and no choice to buy without emmc. @Avatar Ng Did you buy a case/heatsink with it?

https://github.com/ptitSeb/gl4es/tree/master Should be in the repo of amazingfate sudo apt install libgl4es

@balbes150Yes I know I meant it's on the image, not that it has to be. I like your images a lot but assumed he downloaded the "official" Armbian version. @ArmBoy1988 You could find balbes150 his images with EFI bootloader in his topic.

@ArmBoy1988Yes it will pick the first partition. You don't have to do anything special when you use the installer. When you edit the partitions after the installation you'll need to change the UUID in ArmbianEnv.txt en fstab.

@ArmBoy1988 You don't need a boot partition, this is only on the image for the sd-card. The partition created for Armbian has to be the first partition and you should install the bootloader to MTD indeed.

I'd once problems after setting the alignment to 4k after setting it back to 512 it did work as it should, although this was when I dd copied an image to the nvme so I don't know if it applies when you install it via armbian-install. https://carlosfelic.io/misc/how-to-switch-your-nvme-ssd-to-4kn-advanced-format/

@Al.DYou could search these things with for example "apt search Kodi repo" Then: sudo apt install ..... For Kodi Matrix you would need to compile one with gles2 support, on the GitHub of Kodi you could find instructions.

At least the PWM fan works fine with the thermal governor on step_wise. Are you sure that you've the overlay files in the right folder? Or did you also activate other overlays that use the same pin?

Perhaps this site will help: https://techwiser.com/fix-bluetooth-device-doesnt-auto-connect-in-linux/ Maybe you need to reset the keyboard since it's paired with macbook?

HDR10 does work under GBM, dolby vision isn't supported in Linux because it isn't open sourced and needs a license. (it does on a licensed android box) You could play dolby vision movies in GBM with panfork, but it won't play as HDR. With the Mali blob driver and without panfork mesa it does also play under Wayland (as SDR) On the site of LibreELEC you could find an explanation about dolby vision: https://wiki.libreelec.tv/configuration/4k-hdr#hdr

What is the output of "aplay -L" And please first follow some computer courses instead of making nonsense comments.

In gnome settings -> network -> settings wired -> identity -> choose mac -> set on permanent Or this config file might help: https://github.com/Joshua-Riek/ubuntu-orange-pi5/blob/main/overlay/usr/lib/NetworkManager/conf.d/10-override-wifi-random-mac-disable.conf

Those are microcontrollers. You probably would need to find the right way to communicate with it. I've seen there is some python code to communicate with the module but those are made for the RPI so'll need some adjustments. https://github.com/pedestrian0423/DW1000_Raspi_Python_library/tree/master Python gpio libraries for the Orange Pi 5: RPI.GPIO replacement: https://github.com/jer021/OPi.GPIO WiringPi: https://github.com/orangepi-xunlong/wiringOP-Python/tree/next For branch next and recursive: git clone --recursive https://github.com/orangepi-xunlong/wiringOP-Python.git --branch next I can't help you further, maybe someone else who has the module.

If you receive the same as you've sent and the cs pin is pulled down I would say there is nothing wrong with the overlay. You probably need to check the wiring/config to your Qorvo DWM1000. So the fixup is implemented in the overlay.

Do you have the following line in armbianEnv.txt? fdtfile=rockchip/rk3588s-orangepi-5b.dts

@gLush The fixup.scr seems like it's deprecated. At least in the repo of orange pi all lines are comment out: https://github.com/orangepi-xunlong/linux-orangepi/blob/orange-pi-5.10-rk3588/arch/arm64/boot/dts/rockchip/overlay/rk3588-fixup.scr-cmd The CS should be pulled low the moment it sends data, does it get pulled down during the internal loop test? Did you follow the test from the manual? and did you receive the same as the output? sudo spidev_test -v -D /dev/spidev4.1 spi mode: 0x0 bits per word: 8 max speed: 500000 Hz (500 KHz) TX | FF FF FF FF FF FF 40 00 00 00 00 95 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@....▒..................▒. RX | FF FF FF FF FF FF 40 00 00 00 00 95 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@....▒..................▒.

@gLush I don't have experience with spi on this device, but shouldn't you connect miso to miso and mosi to mosi? https://www.circuitbasics.com/how-to-set-up-spi-communication-for-arduino/ Sorry I didn't read it correctly, this was for the internal loop which did work. Not sure if it's helpful but firefly has some documentation about how to use the spi: https://wiki.t-firefly.com/en/ROC-RK3588-PC/usage_spi.html#drive-coding