Hello,
I'm facing one issue which drives me mad, I'm missing something.
I have bought a brand new compute module 5 with eMMC (CM5102016) to create an OpenWRT router thanks to this board : https://www.dfrobot.com/product-2242.html
I went to OpenWRT firmware selector to download a customized version of OpenWRT https://firmware-selector.openwrt.org/? ... 2&id=rpi-5
I added the following modules : kmod-r8169, kmod-usb-dwc2, bcm27xx-userland, r8169-firmware and pciutils.
I redirected the console to UART by modding cmdline.txt (console=ttyAMA0,115200) and config.txt dtoverlay= / dtparam=uart0_console
This way I can see the kernel boots successfully but does not seem to mount the filesystem partition to continue the boot sequence. Here are the last lines of the boot process :
[ 0.561375] mmc0: CQHCI version 5.10
[ 2.755570] pl011-axi 1f00030000.serial: DMA channel TX dma2chan0
[ 2.761678] pl011-axi 1f00030000.serial: DMA channel RX dma2chan1
[ 2.803455] mmc0: SDHCI controller on 1000fff000.mmc [1000fff000.mmc] using t
[ 2.943771] mmc1: SDHCI controller on 1001100000.mmc [1001100000.mmc] using t
[ 2.951830] Waiting for root device PARTUUID=661a1cf7-02...
[ 2.983861] mmc1: new ultra high speed DDR50 SDIO card at address 0001
I used the exact same image on a raspberry pi5 and it boots sucessfully and I managed to go to the openWRT administration page.
So what could be wrong ?
- Wrong image flash
I used rpi-imager, balena etcher, rufus, even dd with exact same results.
- Wrong filesystem
I tried both sqashfs and ext4 and same result.
- Wrong HW. The base board is designed for CM4, maybe incompatibility issue
I flashed raspberry OS lite from rpi-imager. It then works like a charm: complete boot, then working prompt
- Wrong kernel
I replaced the image's kernel with the one of the working raspberry OS. Still not booting to the end.
- Issue with the partition
The second partition is correctly flashed and can be mounted with rpiboot. The partition UUID seems correct. I tried replacing root=PARTUUID=xxx with root=/dev/mmcblk0p2 or root=/dev/sda2 with no more success. The only modification is the error log adapts with "Waiting for root device" which reflects the cmdline.txt configuration
- Boot with the RPi5 working USB key to see if more success than eMMC
I was not able to boot with the USB key plugged to the USB port of the carrier board thanks to an USB-C to USB-A adapter but with no success, it seems the USB key was not detected as I got nothing on the serial console
Then I don't know what I'm missing :
- The CM5 + carrier board works altogether because raspberry OS works
- The image is OK as it boots fine installed on an USB stick on a RPi5
I thought about a missing eMMC driver in the kernel but even the official kernel does not allow booting, and only bcm2712_defconfig is found in the kernel repository, which makes me thinking that there are no differences between CM5 and RPi5 or at least the kernel contains everything and adapts to both platforms.
Although my goal is running OpenWRT, my issue is more about booting issues than OpenWRT itself that's why I'm posting here.
Would somebody be kind enough to provide me some help, maybe I'm missing something obvious ?
Thank you in advance
I'm facing one issue which drives me mad, I'm missing something.
I have bought a brand new compute module 5 with eMMC (CM5102016) to create an OpenWRT router thanks to this board : https://www.dfrobot.com/product-2242.html
I went to OpenWRT firmware selector to download a customized version of OpenWRT https://firmware-selector.openwrt.org/? ... 2&id=rpi-5
I added the following modules : kmod-r8169, kmod-usb-dwc2, bcm27xx-userland, r8169-firmware and pciutils.
I redirected the console to UART by modding cmdline.txt (console=ttyAMA0,115200) and config.txt dtoverlay= / dtparam=uart0_console
This way I can see the kernel boots successfully but does not seem to mount the filesystem partition to continue the boot sequence. Here are the last lines of the boot process :
[ 0.561375] mmc0: CQHCI version 5.10
[ 2.755570] pl011-axi 1f00030000.serial: DMA channel TX dma2chan0
[ 2.761678] pl011-axi 1f00030000.serial: DMA channel RX dma2chan1
[ 2.803455] mmc0: SDHCI controller on 1000fff000.mmc [1000fff000.mmc] using t
[ 2.943771] mmc1: SDHCI controller on 1001100000.mmc [1001100000.mmc] using t
[ 2.951830] Waiting for root device PARTUUID=661a1cf7-02...
[ 2.983861] mmc1: new ultra high speed DDR50 SDIO card at address 0001
I used the exact same image on a raspberry pi5 and it boots sucessfully and I managed to go to the openWRT administration page.
So what could be wrong ?
- Wrong image flash
I used rpi-imager, balena etcher, rufus, even dd with exact same results.
- Wrong filesystem
I tried both sqashfs and ext4 and same result.
- Wrong HW. The base board is designed for CM4, maybe incompatibility issue
I flashed raspberry OS lite from rpi-imager. It then works like a charm: complete boot, then working prompt
- Wrong kernel
I replaced the image's kernel with the one of the working raspberry OS. Still not booting to the end.
- Issue with the partition
The second partition is correctly flashed and can be mounted with rpiboot. The partition UUID seems correct. I tried replacing root=PARTUUID=xxx with root=/dev/mmcblk0p2 or root=/dev/sda2 with no more success. The only modification is the error log adapts with "Waiting for root device" which reflects the cmdline.txt configuration
- Boot with the RPi5 working USB key to see if more success than eMMC
I was not able to boot with the USB key plugged to the USB port of the carrier board thanks to an USB-C to USB-A adapter but with no success, it seems the USB key was not detected as I got nothing on the serial console
Then I don't know what I'm missing :
- The CM5 + carrier board works altogether because raspberry OS works
- The image is OK as it boots fine installed on an USB stick on a RPi5
I thought about a missing eMMC driver in the kernel but even the official kernel does not allow booting, and only bcm2712_defconfig is found in the kernel repository, which makes me thinking that there are no differences between CM5 and RPi5 or at least the kernel contains everything and adapts to both platforms.
Although my goal is running OpenWRT, my issue is more about booting issues than OpenWRT itself that's why I'm posting here.
Would somebody be kind enough to provide me some help, maybe I'm missing something obvious ?
Thank you in advance
Statistics: Posted by Screwface2591 — Sun Mar 16, 2025 2:58 pm