After Changing BCF from basic to QUECTEL's for XIAO esp32s3 sense + XIAO Wifi halow(Quetel FGH100M-H)

Hello,

I try to change BCF to increase tx power. I have read somewhere Quectel could transmit 27dBm.

  1. Download [bcf_fgh100mhaamd.bin] and convert to bcf_fgh100mhaamd.mbin.
  2. To make obj, I use the command
       xtensa-esp32s3-elf-objcopy -I binary -O elf32-xtensa-le -B xtensa bcf_fgh100mhaamd.mbin bcf_fgh100mhaamd.mbin.o --redefine-sym _binary_bcf_fgh100mhaamd_mbin_start=bcf_binary_start --redefine-sym _binary_bcf_fgh100mhaamd_mbin_end=bcf_binary_end --rename-section .data=.rodata,contents,alloc,load,readonly,data

3. Test using command : xtensa-esp32s3-elf-objdump -t bcf_fgh100mhaamd.mbin.o

 

4. change Kconfig and CMakeLists.txt.

In Kconfig,

In CMakeLists

After building and flashing, I got this error.

Thanks

ESP error.txt (6.1 KB)

What version of the BCF are you using, and what version of the SDK are you using?

How do I know that?

I just use seeedstudio’s github for mm-iot-esp32 and idf 5.1.1 which is mentioned seeedstudio’s tutorial maybe. And quectel’s bcf is morsemicro’s github. Seeed Studio FGH100M-H BCF and FW binary files for IoT SDK ESP32 v2.9.7 - #2 by xflash linked here.

I check the version of MM-IOT-SDK version 2.6.4-esp32

Hi, Dear

I try to other version, mm-iot-esp32-v2.8.2 with firmware version 1.15’s QUECTEL’s BCF.

I have test a sta_connect example with new BCF.

I think it is ok.

But I could not use camera example of SEEEDSTUDIO. Is there an examples using camera?

how do I check the tx power? 27dBm?

Thanks.

Hi @denny

Glad you resolved it. Unfortunately the MM-IoT-SDK does not have examples using the camera, but it shouldn’t be too hard to carry the example over from the SeeedStudio SDK. The commit adding support is here: feat: add web_camera_serve demo. · Seeed-Studio/mm-iot-esp32@4bf7775 · GitHub

Hi,

Thanks,

I modify the code. just add mm_app_regdb.c, mm_app_regdb.h andchange the include.

Finally, How to check Tx power is 27dBm?

Thanks.

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?

Hi,

mf16858 is correct. And I just use mm6108.bin in v2.8.2 repo.

For BCF, Go to GitHub - MorseMicro/morse-firmware · GitHub and branch 1.15 and you could find quetel’s. I think I have used it. And convert it following Seeed Studio FGH100M-H BCF and FW binary files for IoT SDK ESP32 v2.9.7 - #2 by xflash .
Good luck..