I’m using the Seeed HaLow module with the FGH100M for a project that would benefit from having a working IBSS mode. I know mm-iot-esp32 doesn’t expose IBSS mode right now despite having some plumbing for it, so I’m considering implementing driver support for it myself. However, I’m not actually sure if the published firmware blobs support the AdHoc interface type even if the driver were to be updated to include it.
Would someone be able to confirm if the published firmware is able to support IBSS mode, or if the chip is capable of it at all?
Thanks for the reply, that is encouraging! However, I’m targeting the ESP32 for this project, and the firmware images I’ve found seem to reject the commands needed to enter ad-hoc mode (MORSE_CMD_INTERFACE_TYPE_ADHOC returns EINVAL).
I was using the mm6108.mbin version v1.17.6, pulled from the Espressif registry (morsemicro/firmware, 2.10.4-esp32-1). Is there a firmware image suitable for ESP32 that includes IBSS support?
Okay, scratch that, looks like I had my init sequence wrong. IBSS is present in the ESP32 firmware and I’ve tentatively got things working now, thanks again for your time
Hi @timothyb89 , you mentioned you got IBSS tentatively working on the ESP32 firmware after fixing your init sequence. I’m chasing the same thing on an ESP32-S3 + MM6108, but hitting a slightly different error: -17, which I believe is EEXIST, rather than the EINVAL you saw.
Any chance you’d share the init ordering that fixed it? even a rough outline of the call sequence, and whether you used the mmwlan API or the low-level morse_commands path?
Thanks!
Hmm, not sure I ran into that specifically. If you have some tolerance for some AI slop, I have a hackily forked driver here with more or less full IBSS support: GitHub - momentary-systems/esp-halow-ibss: A fork of the mm-iot-sdk for the ESP32 with IBSS support · GitHub, with the main caveat being that there is no encryption (WPA, etc). I’m hoping Morse ends up publishing the repo beyond what gets published to the espressif component registry but for now the hacky fork seems to be the only way forward.
Sorry for the late reply. Thanks you so much! Yeah AI Slop here and there is fine as long as we can test it. Thanks a lot for the code share, that helps a lot!
, it is something we offer support for on our Linux driver.