@drewcephus hold down the maskrom button, plug in the power, then plug in the data cable to your computer. I am running the cli tool so it is rkdeveloptool ld DevNo=1 Vid=0x2207,Pid=0x350b,LocationID=201 Maskrom The light doesn't blink or anything but itll show up as a device there (and when plugged in to the machine initially even)

Collabora's involvement in Open Source XR development continues to grow today as we welcome the libsurvive project, the open source lighthouse tracking system, into the fold! View the full article

Using Radxa U-Boot version "2023.07.02-3-b1eb2bde-gb1eb2bde" makes no difference.

I want to say that Armbian, for any developer listening, has been a pleasure to use, of its stability features. Running my board off a name via Arbitbian-config has been very nice. I would like to let you all know that I have found a solution (sorta) to the slow desktop environment for anyone interested in this. It appears that currently, it is using Softpipe for its graphics rendering (I am no expert in any of this, I am trying to learn). What I did (unintentionally) was getting llvmpipe working. With llvmpipe, the desktop environment works much snappier and is pretty usable (even though it is not using the GPU). I am not too sure how I got this working, but what appears to be my steps is first compiling the MESA drivers from https://gitlab.freedesktop.org/imagination/mesa. Then what I did was download the source code from https://bianbu.spacemit.com/en/development/kernel_compile/. After applying these, the desktop environment became much snappier. The thing though is the kernel I compiled was not being used, so I am not sure what I exactly did. I am very new to working with this kinda thing so if anyone more experienced wants to shed some light on what I did that would be great.

Unfortunately, something random is happening as after a reboot, the NVMe is again not found if SATA overlay is used. The only PCI-e related text in dmesg is then: root@rock3a:~# dmesg | grep -e pcie -e nvme [ 0.174540] /pcie@fe280000: Fixed dependency cycle(s) with /pcie@fe280000/legacy-interrupt-controller [ 4.702382] rockchip-dw-pcie 3c0800000.pcie: probe with driver rockchip-dw-pcie failed with error -110 At least I know now that the used U-Boot does not find my NVME, so that is maybe already the (random) showstopper. So I have to see if maybe a Radxa U-Boot makes it work.