Following your setup — E 127 with matched v2.8.2 morselib, what mm6108.mbin did you use?
I’ve replicated your setup as closely as possible: XIAO ESP32-S3 Sense + Quectel FGH100M-H + upstream mm-iot-esp32 at commit 4b84c7f (v2.8.2). Morselib is confirmed v2.8.2-esp32. BCF is bcf_fgh100mhaamd.mbin (MMBC magic bytes confirmed, board description: mf16858). RESET_N GPIO fix applied.
Monitor output:
Morselib version: 2.8.2-esp32
BCF API version: 8.0.0
BCF board description: mf16858
Morse firmware version: 0.0.0
Morse chip ID: 0x0000
E 127 Transport init failed
Firmware version 0.0.0 and chip ID 0x0000 indicate the firmware upload handshake over SPI is not completing. The chip does assert BUSY=1 after reset (confirmed via GPIO read).
Which mm6108.mbin did you use — the one that ships in the v2.8.2 repo, or a Quectel-specific firmware from the other forum thread (seeed-studio-fgh100m-h-bcf-and-fw-binary-files)? And did your BCF board description also show mf16858 or mf1685B?