DFRobot Router + CM4 + OpenWrt = unsupported board
FrantisekZustin 2022-09-03 00:19:49 2756 Views7 Replies Hello all,
I installed an openWrt into my CM4 with eMMC (using rpiboot/rufus (or Etcher)), but after successful flashing and enabling nVME Boot, when I plug the USB cable into the DFRobot Router, ACT LED flashes 4 long and 4 short times after a short time. This repeats after a while.
No Luci interface at 192.168.1.1, no ssh, no nothing.
As I read somewhere else, this LED flashing pattern means "unsupported board".
Yes, CM4 and DFRobot board is good - tried to flash with other images (raspbian), and it worked like a charm with no errors.
I tried to use the DFRobot/openWrt image from your wiki page, I tried also the factory CM4 image from OpenWrt site, but still 4 long and 4 short ACT Led.
Using powerful (3A) power supply, so no undervoltage for the board.
CM4 is in this configuration:
1GB RAM, 8GB nVME, no Wifi
I tried this with 8GB RAM, 32GB nVME, Wifi+BT - same result.
Please help me with this.
Hi Everyone! Just made a step by step tutorial to create a custom OpenWRT image for DFROBOT Router Board + CM4, can anyone can test it out to see if it solves the problem?
Link for the tutorial: https://viniciuspaes.com/raspberry-pi/how-to-build-custom-openwrt-image-raspberry-pi-router/
Link for the image files generated by the tutorial: https://drive.google.com/drive/folders/1ETjAfQOTZthzX6gUCI4hoGncGX8F7RNg?usp=sharing
I can redo the tutorial and add any custom driver that is necessary, just let me know if it is working.
Best Regards,
Vinicius
viniciuspaes I've tried the generated image and haven't manage to make it work.
While generating my own builds using OpenWRT Firmware Selector for CM4+DFrobot and installing I alway face with the following issues:
- eth0 and eth1 are swapped comparing to original FW from DFrobot- when i physically disconnect the cable both interface are going sown then up.
This means that when I unplug internet cable, the PC connected to the other ethernet port of the router shows that it is disconnected and then after a while connected back and getting IP again.
Can somebody build reliable FW which will behave as original DFrobot FW and won't have the issues I mentioned?
UPDATE:
FW which will include luci, lan, wan pre-configured, same as on DFrobot FW.
Hey!
Sorry to necro this thread.
I have a similar problem. I've got an 8 month old CM4 with 1GB RAM, no eMMC or WiFi and it works perfectly fine.
I bought a new CM4 with 2GB RAM, 32GB eMMC and WiFi and it refuses to boot, despite me installing the OS correctly to the eMMC. I even tried installing a new image to the eMMC of the CM4. I initially thought the new CM4 board was broken, but I can get it to boot other OSes.
I appreciate that we can use a newer image without the 2nd NIC, but I am unsure how to go about this if can't get my board connected to the internet to install the drivers. Can I somehow download the OpenWRT packages and then install them via SSH/SFTP?
SteveWi The dfrobot custom image of OpenWRT is outdated, it does not work with newer boards. DFROBOT: Please update the image.
The latest OpenWRT image works fine but does not have the driver for the second ethernet adapter (https://openwrt.org/toh/hwdata/raspberry_pi_foundation/raspberry_pi_foundation_raspberry_pi_cm4)
JohannesF 