Scan demo error messages

I try to test scan demo app with stm32h563 unit and seeed quectel board.
i receive the following errors.
how could we investigate the error messages?

Morse Scan Demo (Built Sep 16 2025 16:40:40)

Morse firmware version 1.13.1, morselib version 2.6.4, Morse chip ID 0x306

Scan started on US channels, Waiting for results…
E    70897 morse_pageset_write failed to write page: -32768
E    70897 morse_pageset_tx could not write 1 pkts - rc=-32768 items=1 pages=1
E    72897 morse_pageset_write failed to write page: -32768
E    72897 morse_pageset_tx could not write 1 pkts - rc=-32768 items=1 pages=1
E    74897 morse_pageset_write failed to write page: -32768
W HAL recovery: morse_pageset_write failures exceeded threshold, issuing WLAN hard reset
E    74935 morse_pageset_tx could not write 1 pkts - rc=-32768 items=1 pages=1
E    76897 Command 19:92 timed out
E    76897 Health check failed (errno=-116)
Scanning completed.

any reply from mm team?

Hi @blaa , apologies for the delay

Firstly you may find it will help to upgrade to 2.8.2 GitHub - MorseMicro/mm-iot-sdk

Secondly, the issue may be caused by the default configuration of the Seeed module re. powersave pins. It may help to disable powersave in your application: mmwlan_set_power_save_mode(MMWLAN_PS_DISABLED)

I hope this helps

Hi,
I have updated the library to 2.8.2 and deactivate power save mode as you suggested
but the problem still persist.
Could you suggest BCF - firmware combination which is best fit for 2.8.2 and Seeed module?

@blaa do you have an updated error log with 2.8.2? The above log indicates the chip isn’t responding to host communications.

The above log is not related to the BCF, but you will need something more appropriate for 2.8.2. Best recommendation would be to take the Quectel BCF for the Seeed module from morse-firmware/bcf/quectel at 1.15 · MorseMicro/morse-firmware · GitHub and run the .bin file through the convert-bin-to-mbin.py script included in the mm-iot-sdk.

@ajudge the messages are below

BCF API version:         6.7.0
BCF build version:       d94b4c8 598ae0a26b_Modified
BCF board description:   custom
Morselib version:        2.8.2
Morse firmware version:  1.12.4
Morse chip ID:           0x0306
Station configuration summary:
SSID length: 10
Security: sae
SAE passphrase length: 8
BSSID filter: not specified
Station type: non_sensor
PMF: required, CAC: disabled
RAW priority: -1
Reconnect scan intervals: base 2s, limit 512s
E    31375 morse_pageset_write failed to write page: -32768
E    31375 morse_pageset_tx could not write 1 pkts - rc=-32768 items=1 pages=1
E    31975 morse_pageset_write failed to write page: -32768
E    31975 morse_pageset_tx could not write 1 pkts - rc=-32768 items=1 pages=1
E    32575 morse_pageset_write failed to write page: -32768
W HAL recovery: morse_pageset_write failures exceeded threshold, issuing WLAN hard reset
E    32613 morse_pageset_tx could not write 1 pkts - rc=-32768 items=1 pages=1
E    33174 Command 800c:b2 timed out
E    33175 morse_pageset_write failed to write page: -32768
E    33175 morse_pageset_tx could not write 1 pkts - rc=-32768 items=1 pages=1
E    33775 morse_pageset_write failed to write page: -32768
E    33775 morse_pageset_tx could not write 1 pkts - rc=-32768 items=1 pages=1
E    34375 morse_pageset_write failed to write page: -32768
W HAL recovery: morse_pageset_write failures exceeded threshold, issuing WLAN hard reset

if we keep the library and the bcf the same but we use newer firmware we get the messages below


## BCF API version:         6.7.0
BCF build version:       d94b4c8 598ae0a26b_Modified
BCF board description:   custom
Morselib version:        2.8.2
Morse firmware version:  0.0.0
Morse chip ID:           0x0000

Initialize IPv4 using DHCP…
Initialize IPv6 using Autoconfig…
E     9240 FW manifest pointer not set
E    11542 FW manifest pointer not set
E    13844 FW manifest pointer not set

it is really exhausting here to make the system functional.
almost all the combinations are tried: bcf x firmware x library
what are we missing?

the messages are below

This log is the same as above and indicates comms failure over the SPI bus. If calling the powersave disable command after mmwlan_boot does not fix the problem, then you will need to get a full logic analyzer capture of the SPI Clock, Data, Chip Select and RESET lines so we can understand better why your comms are failing.

if we keep the library and the bcf the same but we use newer firmware we get the messages below

This is expected. You must use a version of firmware, BCF and library which match. To update to 2.8.2 use the libmorse.a AND mm6108.mbin from the 2.8.2 SDK.
See the morse-firmware git repository branch I linked above for a BCF version of the Quectel module which will which match 2.8.2. You will need to convert them to .mbin using the convert-bin-to-mbin.py script provided in the SDK.

TRC05.CSV (339.9 KB)
Please check the logic traces which includes:
clk, miso, mosi, rst, cs, irq, bsuy, wake signals

Hi @blaa

I’ve plotted your csv capture as below

I am noting a few issues - but these could be due to capture resolution, what sample rate was the logic analyzer output captured?

I’m also assuming that these captures were taken from boot of the chip. A full logic analyzer capture from boot of the chip is essential when debugging these SPI bringup issues.

See below a capture from a working board (I believe an h753). Note that the reset line is also toggled before the shown init sequence.


Have you tried running the porting_assistant application on your board first? Before attempting any other sample application, it is imperative that you pass the tests run by the porting assistant. This application is helpful in verifying that the code you are required to write is working as our library expects.

Lastly, if you are familiar with Zephyr (which has it’s own learning curve), you might be interested in using our Zephyr module instead. This allows configuration of the hardware via devicetree instead.