sivert

I was wrong, the dafault baudrate is 100 kHz - the sensor is not responding at first try, when it is in sleep mode.

The kernel 6.18 has the driver i2c-k1x, which is not present in 7.x. There is also i2c-k1, present in both releases. I'm using 6.18 with i2c-k1x, it seems that 10-bit addressing is not supported `i2cdetect -F 4` shows: 10-bit addressing no It seems that the bus is working with 400 kHz frequency, but I don't know why. I was reading driver source and for me if spacemit,i2c-fast-mode or //spacemit,i2c-high-mode is not present, then it shall be 100 kHz. I have no idea how to verify or change the baudrate. I have two sensors, first requires 100 kHz and it is not working, and the second is up to 400 kHz and it seems to be working (I can read some registers, but nothing special). Therefore I assume that bus is operating at 400 kHz.

I'm back. I have UART converter. My plan is to test the peripherals - I2C at this moment. Since the armbian-config does not allow to configure device tree overlays I figured it out how to do it manually. I edit the file: `/boot/extlinux/extlinux.conf` to add additional line: fdtoverlays /boot/dtb/spacemit/overlay/k1-i2c4.dtbo It seems that U-Boot is ok with this: [ 9.909] Retrieving file: /boot/dtb/spacemit/k1-orangepi-rv2.dtb [ 9.935] Retrieving file: /boot/dtb/spacemit/overlay/k1-i2c4.dtbo [ 9.964] Uncompressing Kernel Image [ 10.316] Moving Image from 0x10000000 to 0x200000, end=27c4000 [ 10.337] ## Loading init Ramdisk from Legacy Image at 21000000 ... [ 10.340] Image Name: uInitrd [ 10.343] Image Type: RISC-V Linux RAMDisk Image (gzip compressed) [ 10.349] Data Size: 21020117 Bytes = 20 MiB [ 10.354] Load Address: 00000000 [ 10.357] Entry Point: 00000000 Verifying Checksum ... OK [ 10.458] ## Flattened Device Tree blob at 31000000 [ 10.459] Booting using the fdt blob at 0x31000000 [ 10.565] Loading Ramdisk to 7c974000, end 7dd7fdd5 ... OK [ 10.584] Loading Device Tree to 000000007c952000, end 000000007c973fff ... OK Starting kernel ... And I'm able to see additional `i2c-4` device: $ sudo i2cdetect -l i2c-0 i2c spacemit-i2c-adapter I2C adapter i2c-1 i2c spacemit-i2c-adapter I2C adapter i2c-2 i2c spacemit-i2c-adapter I2C adapter i2c-4 i2c spacemit-i2c-adapter I2C adapter i2c-8 i2c spacemit-i2c-adapter I2C adapter I'll test some sensors now...

I have wifi and it worked without building or installing anything. During the first boot I was asked if I would like to use wifi, I saw the list of SSIDs, but I was unable to connect. I used nmcli and I'm connected now. dkms status outputs: bcmdhd-spacemit-sdio/101.10.591.84.37-4, 6.18.36-current-spacemit, riscv64: installed Update: It boots from eMMC

Hi @sven-ola, thanks for the reply. Before you edited it, I have seen different set of commands to build the module. I'm not using ubuntu, I tried a debian trixie without desktop. I build the image few days ago and I have no exact command but it seems to be something like: ./compile.sh BOARD=orangepirv2 BRANCH=current RELEASE=trixie KERNEL_CONFIGURE=no BUILD_MINIMAL=no BUILD_DESKTOP=no and there is no (apt) package with bcmdhd in the name, I suppose that the older version of your post was helpful, because it was about compiling from the source. I just started a new build using: ./compile.sh BOARD=orangepirv2 BRANCH=current RELEASE=trixie KERNEL_CONFIGURE=yes KERNEL_GIT=shallow BUILD_MINIMAL=no SKIP_ARMBIAN_REPO=yes KERNEL_BTF=no INSTALL_HEADERS=yes I'll report the status later.

Hi, I'm new here. I tested official Orange PI image and it worked. Then I tried Armbian, the current version with 6.18.35 worked, but without WiFi. I tried the edge few times (today, yesterday) and every time there was no HDMI signal or the screen was blank - the green LED was blinking so I assumed that that the system booted. I have no UART converter to debug this now, but I noticed that few users had similar issue - I haven't found a solution. Did I missed something?