Softap application failing to start because of channel problem

Software Embedded
1

Hello:
I compiled softap application for my board, with wlan.country_code = “EU”. It is not starting. Below is the error log and config details

Error log

Note: This firmware has been built with debug in stop mode enabled.
This will impact power consumption and should be disabled for production firmwa.

SoftAP Example (Built Feb 4 2026 16:49:22)

/-----------------------------------
BCF API version: 12.1.0
BCF build version: _Modified
BCF board description: mf10220_eu
Morselib version: 2.9.7
Morse firmware version: 1.16.4
Morse chip ID: 0x0306
Morse chip name: MM6108A1
/-----------------------------------
Morse LwIP interface initialised. MAC address 00:0a:52:09:19:9a
E 338 Specified channel not found in configured channel list
Failed to start Soft AP (status 2)

Config details

   "wlan.country_code": "EU"
   /* The following settings are required only for the softap app */
    /* Operating Class (S1G or Global) to use for Soft AP. This together with
     * S1G_CHANNEL must correspond to a channel in the regulatory database. */
    "wlan.op_class": "131"
    /* S1G Channel to use for Soft AP. This together with OP_CLASS must correspond to a
     * channel in the regulatory database. */
    "wlan.s1g_chan_num": "1"
    /* Primary Bandwidth to use for Soft AP. Valid values:
     *   * 0 (auto)
     *   * 1
     *   * 2 */
    "wlan.pri_bw_mhz": "0"
    /* Primary 1 MHz Channel Index to use for Soft AP. */
    "wlan.pri_1mhz_chan_idx": "1"
2

Where is the configured channel list defined? (In the bcf file???)

3

You probably want an op class of 66 here. The available channels are in mmregdb.c, but these can be blocked by the BCF. If you’re using the AsiaRF module you mentioned before, I think it may not be designed for use in the EU.

4

For your reference, you can find the regulatory database definition in the example application in this file: mm-iot-sdk/examples/softap/src/mm_app_regdb.c at main · MorseMicro/mm-iot-sdk · GitHub

The channel list will be selected based on the configured country code, mm-iot-sdk/examples/softap/src/mm_app_loadconfig.c at 4f4eb7fc7a2f1c761d542af8c97825d8a3482825 · MorseMicro/mm-iot-sdk · GitHub
Called from mm-iot-sdk/examples/softap/src/softap.c at 4f4eb7fc7a2f1c761d542af8c97825d8a3482825 · MorseMicro/mm-iot-sdk · GitHub

5

Thanks James and Matt for your help so far. I am able to run softap on one board and ping on other board with static ip and i am able to perform ping
(a) Will you support dynamic ip in future
(b) The ping appears very slow with some packet loss
orse Ping Demo (Built Feb 3 2026 12:23:15)

/-----------------------------------
BCF API version: 12.1.0
BCF build version: _Modified
BCF board description: mf10220_eu
Morselib version: 2.9.7
Morse firmware version: 1.16.4
Morse chip ID: 0x0306
Morse chip name: MM6108A1
/-----------------------------------
Initialize IPv4 with static IP: 192.168.1.2…
Initialize IPv6 using Autoconfig…
Morse LwIP interface initialised. MAC address 00:0a:52:09:19:90
Attempting to connect to emq-wifi-halow with passphrase 12345678
This may take some time (~10 seconds)
WLAN STA connecting
WLAN STA connecting
WLAN STA connected
DNS server 0: 192.168.1.1
DNS server 1: 8.8.8.8
Link is up. Time: 25944 ms, IP: 192.168.1.2, Netmask: 255.255.255.0, Gateway: 192.168.1.1, DNS server 0: 192.168.1.1
, DNS server 1: 8.8.8.8

Ping 192.168.1.1 56(64) bytes of data.
(192.168.1.1) packets transmitted/received = 2/0, round-trip min/avg/max = 0/0/0 ms
(192.168.1.1) packets transmitted/received = 2/1, round-trip min/avg/max = 110/110/110 ms
(192.168.1.1) packets transmitted/received = 4/2, round-trip min/avg/max = 110/113/117 ms
(192.168.1.1) packets transmitted/received = 5/3, round-trip min/avg/max = 108/111/117 ms
(192.168.1.1) packets transmitted/received = 6/4, round-trip min/avg/max = 108/137/216 ms
(192.168.1.1) packets transmitted/received = 7/5, round-trip min/avg/max = 44/119/216 ms
(192.168.1.1) packets transmitted/received = 8/6, round-trip min/avg/max = 44/118/216 ms
(192.168.1.1) packets transmitted/received = 9/7, round-trip min/avg/max = 44/110/216 ms

— 192.168.1.1 ping statistics —
10 packets transmitted, 7 packets received, 30.000% packet loss
round-trip min/avg/max = 44/110/216 ms
WLAN STA disabled
Link is down. Time: 52747 ms

6

To compare, these are the ping times in normal wifi from ubuntu PC
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.84 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1.99 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=3.44 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=4.66 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=2.57 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=1.35 ms