Robert Pace

I note that edge (6.14.0-rc4) also lacks the i2c2-m0 overlay, so I believe the only function build for i2c2-m0 is found in the older Armbian-unofficial_25.02.0-trunk_Orangepi5-plus_bookworm_vendor_6.1.84_xfce_desktop.img image.

After renaming it showed up in overlays in armbian-config, but takes a good minute to scan the i2c-2 bus, so not a solution for this issue. I note under that a bme280 sensor should show up under address 76 via i2cdetect -y 2. The sensor works fine with same hardware (after installing overlay for I2C2-M0 in armbian-config when using Armbian-unofficial_25.02.0-trunk_Orangepi5-plus_bookworm_vendor_6.1.84_xfce_desktop.img. armbianmonitor -u report: https://paste.next.armbian.com/zanaqiwici Problematic Image: Armbian-unofficial_25.05.0-trunk_Orangepi5-plus_bookworm_vendor_6.1.99_xfce_desktop.img SBC: Orange Pi 5 Plus (32gb) Kernel: Linux orangepi5-plus 6.1.99-vendor-rk35xx #1 SMP Fri Feb 21 18:11:03 UTC 2025 aarch64 GNU/Linux List of overlays in /boot/dtb/rockchip/overlays/*i2c*.dtbo after copying rk3588-i2c2-m0.dtbo to rockchip-rk3588-i2c2-m0.dtbo

Yes, I meant overlays. Hopefully switching filenames will make them appear. I may need to revisit the previous images for good measure. Thanks Werner, you are always handy with your insight.

I have built quite a few Debian12 Desktop images from github.com/armbian/build for a Debian Bookworm/XFCE/Vendor Kernel environment and noticed that recent vendor kernels do not have I2C-2.M0 as a kernel module listed within armbian-config. It appears that only two kernel modules are to be found, one being Panthos, the other involving a change in frequence of some item. This image does include I2C-2.mo: Armbian-unofficial_25.02.0-trunk_Orangepi5-plus_bookworm_vendor_6.1.84_xfce_desktop.img which includes kernel: Linux Atlas 6.1.99-vendor-rk35xx #1 SMP Fri Feb 21 18:11:03 UTC 2025 aarch64 GNU/Linux But these images do not contain the I2C-2.m0 kernel modules: Armbian-unofficial_25.02.0-trunk_Orangepi5-plus_bookworm_vendor_6.1.84_xfce_desktop.img (same kernel build as Ambian 25.0.2.0-trunk listed above sans I2C-2-m0) Armbian-unofficial_25.05.0-trunk_Orangepi5-plus_bookworm_current_6.12.17_xfce_desktop.img Armbian-unofficial_25.05.0-trunk_Orangepi5-plus_bookworm_vendor_6.1.99_xfce_desktop.img Is it now necessary to customize the compile options for the kernel and choose that module for compilation when building newer vendor images? It would make sense (to me at least) to have each build option to have vendor kernels contain the same precompiled kernel modules for simplicity sake. I'm not even sure if the I2C-2.m0 is available or an option in the later vendor kernels to build.

I use virtua lbox with the Ubuntu 22.04 image to a vm and have been able to compile images for Debian 12 and kernel 6.1.84 without issue for the Orange Pi 5 Plus and Orange Pi 5. As someone previously stated, this sounds like an out of disk space error, or issue expanding the vm file.

I somewhat recently used Armbian Build to compile a desktop Bookworm image, which is quite stable and functional except for EMMC support. Packages: Debian stable (bookworm) Support: DIY (custom image) Linux Atlas 6.1.84-vendor-rk35xx #1 SMP Tue Dec 24 13:36:04 UTC 2024 aarch64 GNU/Linux My question is where can one find the current status of the various kernel versions support for features like I2C, SPI, EMMC, MESA, etc.? I recognize that newer kernels like 6.12.yyy are very much a WIP. I also would love more information on the the RK3588 kit used with kernels to backport features.

I also can't see the EMMC module with Linux Atlas 6.1.84-vendor-rk35xx #1 SMP Tue Dec 24 13:36:04 UTC 2024 aarch64 GNU/Linux. NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 18.2T 0 disk └─sda1 8:1 0 18.2T 0 part /mnt/Elements sdb 8:16 0 7.3T 0 disk └─sdb1 8:17 0 7.3T 0 part /mnt/MyBook mtdblock0 31:0 0 16M 0 disk zram0 252:0 0 15.5G 0 disk [SWAP] zram1 252:1 0 50M 0 disk /var/log zram2 252:2 0 0B 0 disk nvme0n1 259:0 0 1.8T 0 disk └─nvme0n1p1 259:1 0 1.8T 0 part /var/log.hdd / Tested this on two of my Orange Pi 5+ (16gb & 32gb models) with 250 gb EMMC modules installed.

I've had issues with kernel 6.12 in the recent past with I2C hardware support, but Kernel 6.1.84 is rock solid.

Thanks! I believe kernel 6.1.84 is the solution to the I2C issues I was having.

I tested with https://dl.armbian.com/nightly/orangepi5-plus/Trixie_vendor_minimal and after installing i2c-tools and adding i2c2-m0 overlay with armbian-config I could see i2c2 with i2cdetect -l, and could see 0x76 show up on bus 2. I would love to have an desktop image with support for mesa that has functional i2c2-m0 functionality do you know of such an image?

I installed a vendor based desktop image (Armbian_24.11.2_Orangepi5-plus_bookworm_vendor_6.1.75_cinnamon-backported-mesa_desktop.img.xz), loaded the i2c2-m0 kernel overlay, and rebooted. Again no i2c2 bus available. This is on an Orange Pi 5 Plus (16gig) SBC. Here is a link to an armbian-monitor -u output https://paste.next.armbian.com/codiqumesu Attached are other diagnostic outputs. The desire is to read a bme280 sensor connected to the gpio pins via i2c. See original post for details of gpio wiring. Any help would be appreciated. I note that there is no I2C-2 device listed in /dev.

Where would one find an arbian vendor os image for the Orange Pi 5 Plus? I don't see anything on Orange Pi 5+ Download page labeled as "Armbian". I do see Orange PI OS with a similar naming structure (24.xxx). I also note that the Orange Pi OS images are still using the quite old Kernel 5.10.160 with no indication as to whether the kernel isn't as fresh as the Debian Bookworm image at Kernel 6.1.43 which has issues with RDP (even with xorgxrdp).

I'm using an Orange Pi 5 Plus 16GB SBC, with Armbian image (https://dl.armbian.com/orangepi5-plus/Bookworm_current_cinnamon-backported-mesa) which uses Kernel 6.12. I am trying to get a BME280 I2C sensor attached to the following pins of the 40 pins; 1 (3.3v), 3 (GPIO0C0), 5 (GPIO0B7), and 6 (GND). The BME280 sensor has the VIN wired to 3.3v (pin 1), SDA wired to SDA (pin 3), SCL wired to SCL (pin 5), and GND to GND (pin 6). The device should use address 0x76, but isn't listed under the four I2C buses found in /dev. This configuration worked fine when using the stock OrangePi 5 Plus Debian Bookworm image, but does not have I2C2 listed as a device under /dev under Armbian image listed above. My armbianEnv.txt is: verbosity=1 bootlogo=true console=both overlay_prefix=rockchip-rk3588 fdtfile=rockchip/rk3588-orangepi-5-plus.dtb rootdev=UUID=3cbd3c35-190b-4cc5-8db3-4334fa84ccbd rootfstype=ext4 overlays=rockchip-rk3588-i2c8-m2 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u I have attached 4 images (screenshots) with the following captions i2c.png - List of I2C buses and addresses (Armbian Image) i2c_2.png - List of DTBs (Armbian Image) i2c_3.png - List of DTBOs aka overlays (Armbian Image) i2c_opi2.png - List of I2C buses and addresses of I2C2 (Orange Pi Debian 12 Image) Why isn't I2C2 found in /dev of Armbian image?

I think I found the reason for my problem. I was using POE with a splitter for powering the OP5+ and after switching to a power adapter the system worked fine, and I have the Cinnamon variant of kernel 6.12 booting appropriately.

From a functional Orange Pi 5+ Debian Bookworm (vendor) OS I mounted the SD card containing the Armbian Bookworm with 6.12 kernel, I checked the uuid for the mounted mmblk1p1 (I don't have mmcblk0p1) /dev/mmcblk1p1: LABEL="armbi_root" UUID="baa71ffd-ca4c-4b04-acfa-956e263f56dc" with /boot/armbianEnv.txt being set to rootdev=UUID=baa71ffd-ca4c-4b04-acfa-956e263f56dc and /etc/fstab being set to UUID=baa71ffd-ca4c-4b04-acfa-956e263f56dc / ext4 defaults,noatime,commit=120,errors=remount-ro 0 1 A boot to the Armbian Debian Bookworm 6.12 Cinnamon desktop SD Card stops at the initramfs loading stage. I've downloaded the image several times and used balena etcher to write to a variety of sd cards, each failing at the same stage.