Hello.
I am trying to use a Quectel FGH100MAAMD (MM6108) together with an ESP32-C6 over SPI, using MM-IoT-ESP32.
The porting_assistant example passes smoothly, all the tests, but the sta_connect example gives me the error: “FW manifest pointer not set“.
I am posting to ask whether i am missing something in the firmware/BCF setup, or whether this points to an incompatibility/mismatch between the SDK and BCF.
Software / version
- mm-iot-sdk: 2.10.4
- mm-iot-esp32 commit: 96d9bf4
- ESP-IDF: 5.5.3
Hardware
Custom board with:
- ESP32-C6-MINI-1
- Quectel FGH100MAAMD
- Supply: 3.3V
BCF / firmware setup
I am using the BCF .bin file from morse-firmware/bcf/quectel/bcf_fgh100maamd.bin at main · MorseMicro/morse-firmware · GitHub, and using the mm-iot-esp32/framework/tools/buildsystem/convert-bin-to-mbin.py at main · MorseMicro/mm-iot-esp32 · GitHub script to convert the .bin file to .mbin. And the MM Firmware File is set to mm6108.mbin. I just configured the project in the menuconfig, the rest of the example is unmodified.
porting_assistant output
MM-IoT-SDK Porting Assistant
----------------------------
Memory allocation [ PASS ]
Memory reallocation [ PASS ]
Passage of time [ PASS ]
Task creation and preemption [ PASS ]
WLAN HAL initialisation Actual SPI CLK 40000kHz
Hard reset device
SDIO/SPI Startup [ PASS ]
Read chip id from the MM chip [ PASS ]
Chip ID: 0x0306
Verify BUSY pin [ PASS ]
Bulk write/read into the MM chip [ PASS ]
Raw throughput test [ PASS ]
Note: This will not be the final WLAN TPUT. See test step for more info.
Time spent (ms): 2520
Transaction count: 9
Bytes xferred: 26928
Raw TPUT (kbit/s): 85
Validate MM firmware [ PASS ]
Validate BCF [ PASS ]
13 total test steps. 11 passed, 0 failed, 2 no result, 0 skipped
I (6511) main_task: Returned from app_main()
As i can tell, the communication between the IC’s is working and the MM6108 is fine.
sta_connect output
I (379) main_task: Calling app_main()
Morse STA Demo (Built Mar 17 2026 10:01:01)
Actual SPI CLK 40000kHz
E 5460 FW manifest pointer not set
E 5486 Failed
E 5512 Failed
E 5512 Firmware init failed
-----------------------------------
HW Version: esp32c6
BCF API version: 8.0.0
BCF build version: 6b00e4d 2031952 _Modified
BCF board description: mf08251
!! Error occured whilst retrieving version info !!
Morselib version:
Morse firmware version:
Morse chip ID: 0x0000
Morse chip name:
-----------------------------------
Its confusing to me, because porting_assistant can talk to the chip and read chip ID 0x306, but the sta_connect reports the chip ID as 0x0000.
And the BCF version appears to be recognized, as it reads the API version 8.0.0, build version and board description, but it fails with “FW manifest pointer not set”.
Questions
- What are the possible causes for the “FW manifest pointer not set” message, exactly?
- For FGH100MAAMD, is converting bcf_fgh100maamd.bin to .mbin with convert-bin-to-mbin.py the correct procedure for mm-iot-esp32?
- Is ESP32-C6 expected to work with this setup, or are there known limitations compared to S3?
- Since porting_assistant passes, does this suggests that the issue is not hardware/SPI, but purely firmware/software/configuration?
Any guidance would be much appreciated, i would be glad to provide any more information.
Thanks.