Struggling with installation on the DF Robot IoT Router Carrier Board

Hello, I have a IoT Router Carrier Board that I'm not able to connect to. This is what I've done so far:
Connected the RPi CM 4 with the IoT Router board. The RPi CM I'm using has 1GB RAM (eMMC) and 16GB Flash.

Flipped over the switch on the IoT Router board.

Connected a Usb A to my Ubuntu running PC.

Installed rpiboot on my server, started it up and verified that the IoT was connected through sdc.

Downloaded the (special) image and wrote it to sdc:

sudo dd if=openwrt-21.02.3-bcm27xx-bcm2711-rpi-4-ext4-factory.img of=/dev/sdc bs=4MiB

Verified that the disk was ok:

sudo fdisk -l

Device     Boot  Start     End Sectors  Size Id Type
/dev/sdc1  *      8192  139263  131072   64M  c W95 FAT32 (LBA)
/dev/sdc2       147456 2113535 1966080  960M 83 Linux

Resized the sdc2 partition using the method stated on the DF Robot webiste, checked again:

Device     Boot  Start      End  Sectors  Size Id Type
/dev/sdc1  *      8192   139263   131072   64M  c W95 FAT32 (LBA)
/dev/sdc2       147456 30535679 30388224 14.5G 83 Linux

Flipped over the switch again and rebooted. Connected a PC through the ETH1 port, but no connection at

Any suggestions on why it isn't working. Any ways I can do error checking? Will e.g a USB-C to HDMI cable give me screen output from the IOT Router board?

Thanks and regards,

I would assume eth0 to be LAN (and eth1 WAN), but check bother nevertheless, as the enumeration order might be different from their labelling.

The easiest approach would probably connecting a (USB2)serial adapter and checking what's happening, but with RPi device, connecting screen and keyboard might also work.

Seems like it was something wrong with the OpenWrt image provided by DFRobot, sorted now by changing some of the boot files :grinning:

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.