-
Positions
-
Part time technical support
Position: Technical supportNumber of places: 12Applicants: 16 -
Single board computer maintainer
Position: Board maintainerNumber of places: 64Applicants: 77 -
Code reviewer
Position: Framework maintainerNumber of places: UnlimitedApplicants: 11 -
Test Automation Engineer
Position: Software integration test engineerNumber of places: 16Applicants: 10 -
Build framework maintainer
Position: Framework maintainerNumber of places: 16Applicants: 6
-
-
Chat | Social Media
#armbian at
irc.libera.chat or irc.oftc.net
Matrix or Discord
Mastodon | 𝕏 -
Activity Stream
-
52
RK3566 and Armbian
I got a small progress here with a RKNN (TPU). 1. note from previous posts: rk3566-box-demo.dtb looks like does not support our USB. Use rk3566-box-X88PRO20.dtb that other shared. I tried to use the NPU, looked across the forum. Managed to get our .dtb running with the correct settings - however the Kernel didn't had the RKNN packages + it could not link the 'rocket' to our NPU. While the NPU was recognized after my tweaks. Read that it runs only on kernel v. 6.1 from VENDOR - recompiled the kernel for our board, installed it over the existing installation - .dtb didn't run... When I switched to box-demo from the kernel the NPU and RKNN were recognized instantly. I will not attach the kernel itself for now, as it is ~300 Mb, however you can compile it from Armbian: ./compile.sh kernel BOARD=station-m2 BRANCH=vendor \ KERNEL_BTF=no KERNEL_GIT=full it have to be installed like that: dpkg -i linux-image-vendor-rk35xx_*.deb linux-dtb-vendor-rk35xx_*.deb update-initramfs -c -k 6.1.115-vendor-rk35xx Probably will be a task for today to tweak .dtb for this kernel version and get board running with RKNN. I want to try immich with a local image classification. -
228
Orange Pi RV2
Some NVMe's just don't play nice with some units. I have one such NVMe, which is why I rarely try to use it. Also u-boot is not set up to look for an infinite amount of $devnum. Currently it is hard coded to look for nvme 0:1. So I suggest moving the NVMe to the first available. According to the boot log you have more than one PCIE link up [ 1.438] PCIE-0: Link up (Gen2-x2, Bus0) <-- Thats where you want to attach the NVMe [ 1.600] PCIE-2: Link up (Gen2-x2, Bus2) Honestly though. It looks like the NVMe you are trying to use isn't compat. -
228
Orange Pi RV2
@sven-ola For my next debugging: To make a separate boot MicroSD, how should I go about? I guess I boot from the MicroSD but in single-user mode (how?) and then mount /dev/nvme0n1p1 / . Then, I re-flash the MicroSD with the image from you: dd if=Armbian.. of=/dev/sd0c bs=1M And then create a new Ext4 filesystem on the now-system partition, for use as boot: mkfs.ext4 /dev/sd0a And then move all the boot files there: mv /boot /boot.orig; mkdir /boot; mount /dev/sd0a /boot; cp -rf /boot.orig/* /boot/ And in addition to this, what files should I change and what commands should I run, for the MicroSD to boot to the SSD i.e. /dev/nvme0n1p1 ? (I'd think some file in /boot , perhaps /etc/fstab ) Aside from trying other power supplies, any thoughts about how to get it going would be much appreciated. One thing I should test is disconnect the SSD from the computer and then try to boot the 7.1 kernel Armbian from MicroSD and see if that works. -
2
NPU not working in OrangePi5Plus Vendor Kernel
@Werner here is the URL: https://paste.armbian.com/yoyimafolu -
53
-
-
Member Statistics
