I am currently conducting 802.11ah and 802.11s tests using MM8108-EKH19 (ML-GT3000, RD09).
As the next phase, I would like to change the main board from the ML-GT3000 to a Raspberry Pi 4b and perform the same tests.
I performed the following steps on Ubuntu 20.
git clone https://github.com/MorseMicro/openwrt.git
cd openwrt
./scripts/feeds update -a
./scripts/feeds install -a
./scripts/morse_setup.sh -i mm8108-ekh01
make menuconfig
*Target System: Broadcom BCM27xx*
*Subtarget: BCM2711 boards (64 bit)*
*Target Profile: Raspberry Pi 4B*
*Kernel Modules → Wireless Drivers → <*> kmod-morse → [*] USB support*
*Morse micro → essentials → [*] morsecli*
*Morse micro → features → [*] morse_mesh11sd*
*Network → WirelessAPD → <*> wpad-mesh-wolfssl*
make -j$(nproc)
When I booted up this image on Rpi4B, nothing showed up in ‘iw dev’.
When I asked copilot, it told me to set ‘enable_wiphy=1’.
However, on the ML-GT3000, it says ‘enable_wiphy=N’.
When I asked copilot further,
it said that this is because the ML-GT3000 generates a virtual interface using a unique method,
and that on the Rpi4B I should set firmware_type to fullmac and enable_wiphy=1.
Is what copilot is saying correct?
If not, what should I do?
We have a shortcut board target for OpenWrt to get you to a functioning configuration with the USB dongle used in the GL-MT3000 - rpi-4-mmeval. Simply run the following steps:
git clone https://github.com/MorseMicro/openwrt.git -b 2.9.3 # specify the branch here to get the release tag :)
cd openwrt
./scripts/morse_setup.sh -i -b rpi-4-mmeval
make -j$(nproc)
No need to adjust anything .
Note, you are missing the -b from setup script, so it may not have picked up the correct board configuration.
When I run it, it says that there is no board called “rpi-4-mmeval”.
Is the morse_setup.sh I’m using incorrectly?
Or is some clear operation required on the Ubuntu side?
str@str-VirtualBox:~/openwrt$ ./scripts/morse_setup.sh -i -b rpi-4-mmeval
Updating feed 'packages' from 'https://github.com/openwrt/packages.git^b5ed85f6e94aa08de1433272dc007550f4a28201' ...
Updating feed 'routing' from 'https://github.com/openwrt/routing.git^e351d1e623e9ef2ab78f28cb1ce8d271d28c902d' ...
Updating feed 'telephony' from 'https://github.com/openwrt/telephony.git^98c8a5aa4624312ed758e2e2b6d4039050a1649d' ...
Updating feed 'luci' from 'https://github.com/MorseMicro/luci.git;2.9-dev' ...
Already up to date.
(some parts omitted)
Installing all packages from feed prpl.
Collecting package info: done
Uninstalling package 'xtables-addons'
Collecting package info: done
Error: No rpi-4-mmeval board
(some parts omitted)
Available board (-b) options (can use build name or individual targets):
ekh-armsr_armv7
ekh-armsr_armv8
ekh-ath79
gl-x750 (glinet gl-x750)
gl-ar300m16 (glinet gl-ar300m16)
ekh-bcm2711
mmx108-ekh01-sdio (morse mmx108-ekh01-sdio)
mm8108-ekh01-spi (morse mm8108-ekh01-spi)
mm6108-ekh01-spi (morse mm6108-ekh01-spi)
ekh-filogic
ekh19 (morse ekh19)
rt-ax59u (asus rt-ax59u)
ekh-ipq806x-generic
r7800 (netgear r7800)
ekh-malta_be
ekh-malta_be64
ekh-malta_le
ekh-malta_le64
ekh-mt7621
rt-ax53u (asus rt-ax53u)
ekh-mt7622
e8450-ubi (linksys e8450-ubi)
ekh-mt76x8
ekh03v4 (morse ekh03v4)
ekh04v6 (morse ekh04v6)
ekh-mvebu-cortexa9
wrt1900acs (linksys wrt1900acs)
ekh-x86_64
halowlink1
halowlink1 (morse halowlink1)
Oh that’s interesting, I was under the impression it would pick it up as there is a target defined: CONFIG_TARGET_DEVICE_bcm27xx_bcm2711_DEVICE_rpi-4-mmeval
If the script isn’t picking it up, use
./scripts/morse_setup.sh -i -b ekh-bcm2711
which will build a set of bcm2711 based targets based on the configuration in the boards directory.
Dear ajudge:
By changing the following in menuconfig and building, we were able to confirm that it would start up in the same way as MM8108-EKH19. The GUI is also enabled. Target Profile: Raspberry Pi 4B