E25 booting, green led flashing on CM3 module

I’ve used rbuild to build a bullseye release with a kernel I built via bsp (the latest mainline so I am aware there may be bugs).

My board boots and I’m able to login via serial console (no network as the r8152_dkms would not compile).

There is a green flashing led on the compute module. It flashes quickly twice, then a pause before flashing quickly twice again, and this repeats. What does this mean? The main ring of led is a steady blue colour, not very bright.

Can you confirm where the 4 pin power header is:

“DC 5V on 4-pin header”

Is this on the GPIO?

Regarding the GPIO, can you confirm the order of the pins, it’s not marked on the board.

Thanks!

One further question - for power and serial over usb-c, do you have any recommended hubs? Anything I try doesn’t work for serial, I only get power. My host machine just shows

ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0
ch341 5-2:1.0: device disconnected

I can power via my usb a-a cable with a usb a-c adapter, but I was concerned it might not be providing enough power.

This is the “heartbeat” LED, it means the kernel is running.

sorry for the inconvenience. for now, please try this fix
https://github.com/awesometic/realtek-r8125-dkms/commit/65f9a5775a17b32ada4cdfbefc7de73b0644f9d4

or you may use this package
https://github.com/awesometic/realtek-r8125-dkms

you can control the ring of RGB led via /sys/class/leds/rgb:torch/

Ah that’s great. Thanks for the info.

I hadn’t noticed it when I had tested with a radxa build.

1 Like

Thanks for the link, that is a great help.

It’s no inconvenience, I didn’t expect it to work straight away as the realtek site only mentioned support up to 5.19, so I removed it from the build.

Good to know. I’ll leave it alone just now, the dim blue is nice while the board isn’t in it’s case! :smiley:

The updated r8125_dkms worked fine and I’ve got networking on the board now.

However there is only one network interface. I didn’t spot anything immediatly obvious in the logs. I’ve installed the radxa e25 bullseye image (radxa-e25-debian-bullseye-xfce4-arm64-20221028-0509-gpt.img.xz) to check if it was a problem with my kernel/build.

The bullseye image also only has one network interface, but it contains rk-pcie errors:

[    3.716630] rk-pcie 3c0400000.pcie: PCIe Linking... LTSSM is 0x0
[    3.716792] rk-pcie 3c0800000.pcie: PCIe Linking... LTSSM is 0x3
[    4.729909] rk-pcie 3c0400000.pcie: PCIe Linking... LTSSM is 0x0
[    4.730934] rk-pcie 3c0800000.pcie: PCIe Linking... LTSSM is 0x3
[    5.743252] rk-pcie 3c0400000.pcie: PCIe Linking... LTSSM is 0x0
[    6.756724] rk_pcie_establish_link: 1 callbacks suppressed
[    6.756746] rk-pcie 3c0800000.pcie: PCIe Linking... LTSSM is 0x3
[    6.756840] rk-pcie 3c0400000.pcie: PCIe Linking... LTSSM is 0x0
[    7.769998] rk-pcie 3c0800000.pcie: PCIe Linking... LTSSM is 0x3
[    8.783289] rk-pcie 3c0800000.pcie: PCIe Linking... LTSSM is 0x3
[    8.783423] rk-pcie 3c0400000.pcie: PCIe Linking... LTSSM is 0x0
[    9.796707] rk-pcie 3c0800000.pcie: PCIe Linking... LTSSM is 0x3
[    9.796710] rk-pcie 3c0400000.pcie: PCIe Linking... LTSSM is 0x0
[   10.813366] rk-pcie 3c0400000.pcie: PCIe Linking... LTSSM is 0x0
[   10.813369] rk-pcie 3c0800000.pcie: PCIe Linking... LTSSM is 0x3
[   11.823443] rk-pcie 3c0400000.pcie: PCIe Link Fail
[   11.823532] rk-pcie 3c0400000.pcie: failed to initialize host
[   11.823829] rk-pcie 3c0800000.pcie: PCIe Link Fail
[   11.823855] rk-pcie 3c0800000.pcie: failed to initialize host

I’m digging into this to see what might be causing these errors.

i get those same errors in my desmg too…