Hello:
I am trying to setup two boards(with wifi halow module MM610X) with same SSID/password/security/country_code to form adhoc networks like wifi networks. They are not connecting to each other.
I have flashed one board with http application (since the server application also supports ping protocol), with static ip 192.168.1.1
I have flashed another board with ping application with another static ip. They are not connecting and talking to each other. Please help.
Can you give us more details about what software/hardware you’re using, how you’re configuring it, and logs from a failed connection attempt? There’s no reason to start looking at ping or http until we can figure out what’s happening with the connection 
Hi, I think the problem is because both the boards are getting configure in STA mode, instead of one in AP mode. I am using the EVK board software provided by ASIA RF for their evaluation board, and I modified it for my HW. In that repository there is no example of how to set it in AP mode instead of STA mode.
Please find the log output http server application
This may take some time (~30 seconds)
Note: This firmware has been built with debug in stop mode enabled.
This will impact power consumption and should be disabled for production firmware.
Morse HTTP Demo (Built Feb 2 2026 13:38:18)
/-----------------------------------
BCF API version: 6.3.0
BCF board description: MM_LP3
Morselib version: 2.5.2
Morse firmware version: 1.12.4
Morse chip ID: 0x0306
/-----------------------------------
Initialize IPv4 with static IP: 192.168.1.1…
Initialize IPv6 using Autoconfig…
Morse LwIP interface initialised. MAC address 00:0a:52:09:19:90
Attempting to connect to emqos-wifi-halow-test with passphrase 12345678
This may take some time (~30 seconds)
It looks like you are running on an embedded system. Unfortunately, this only supports STA mode at the moment, though we hope to release AP support soon.
You should purchase an AP to test this (such as our HaLowLink 1 or HaLowLink 2).
EDIT: as you pointed out below, I’m out of date and SoftAP is in the latest release. Sorry! I’ve only actually used the Linux driver.
Thanks James. In git hub I see version 2.9.7 version of mm-iot-sdk. It has SoftAP in example. What is that application?
Since 2.9.7 version of mm-iot-sdk has SoftAP, i tried to migrate to that. I am seeing initialization failures. I think it could be because of version mismatch between the morsedriver version and the FW running in MM610X chip. Can you confirm that? If so, is it possible to upgrade FW in MM610X chip to work with this version?
(a) Error seen with new SDK
Morse Ping Demo (Built Feb 3 2026 12:23:15)
E 1672 FW manifest pointer not set
E 3331 FW manifest pointer not set
E 4987 FW manifest pointer not set
E 4987 Firmware init failed
/-----------------------------------
BCF API version: 6.3.0
BCF board description: MM_LP3
!! Error occured whilst retrieving version info !!
Morselib version:
Morse firmware version:
Morse chip ID: 0x0000
Morse chip name:
/-----------------------------------
Note: This firmware has been built with debug in stop mode enabled.
This will impact power consumption and should be disabled for production firmwa.
Failure 0 logged at pc 0x08008ede, lr 0x08008f77, line 180 in 92aa040f
0x00000000
0x00000000
0x00000000
0x00000000
(b) Version output with the working old sdk
/-----------------------------------
BCF API version: 6.3.0
BCF board description: MM_LP3
Morselib version: 2.5.2
Morse firmware version: 1.12.4
Morse chip ID: 0x0306
/-----------------------------------
The firmware for the MM6108 is uploaded as part of the chip initialisation. See:
If you have 2.9.7 checked out, you should have a compatible firmware. Perhaps you didn’t pick this up in your migration process?
On the other hand, the ‘bcf’ (board configuration file) needs to be compatible as well, and I’m not sure if AsiaRF has released one for the latest version. @Zandr will know more about this.
James/Zandr: We were using the BCF file from version 2.5.2. Asia RF has not released bcf file for 2.9.7. Is it possible for me to make bcf file or reuse some other bcf file?
I tried to use some other bcf file(bcf_mf08551.mbin) that came with the 2.9.7 SDK. The FW crash is gone, but it is not able to connect to the gateway. I am using wlan country code EU.
Below is the log
orse Ping Demo (Built Feb 3 2026 12:23:15)
/-----------------------------------
BCF API version: 12.1.0
BCF build version: 88fa91f8 a02e363
BCF board description: {“module”: “mm6108-mf08551”, "s
Morselib version: 2.9.7
Morse firmware version: 1.16.4
Morse chip ID: 0x0306
Morse chip name: MM6108A1
/-----------------------------------
Initialize IPv4 using DHCP…
Initialize IPv6 using Autoconfig…
Morse LwIP interface initialised. MAC address 00:0a:52:09:19:9a
Attempting to connect to AsiaRF-HaLow-C3A4 with passphrase Emqos123@
This may take some time (~10 seconds)
I got BCF file from AsiaRF and it worked with ping application. I am just curious about the contents of the bcf file. Can you please provide some details on the format and contents of bcf file
The BCF file is not user modifiable, and is provided by our module or board partners. You should not try different BCFs, as they may exceed regulatory requirements, not function at all, or in the worst case cause damage.
The softap application is not starting. I have created a new thread for that and provided the error. Kindly look into this and help me