2025-04-25 7:41 AM - edited 2025-04-25 8:12 AM
I was able to flash the BLE full extended and run the Ble Transparent Mode in the dongle correctly. But when I want to use the Thread Cli Cmd application it simply won't work. I flash the correct stack (thread ftd bin v1.22.0 (at 0x0808B000 as the Release notes says) and the FUS version is 1.2.0 (from release 1.22.0).
The APP_THREAD_CheckWirelessFirmwareInfo() returns p_wireless_info->StackType = 0, so the Leds starts blinking in error. This happens when after uploading the stack I press Start FUS and then proceed to debug.
But if I press Start Wireless stack (as I had to do with the nucleo and the ble_thread_dyn stack), when I debug and boot CPU2 it won't send the Ready Notification (which it correctly does when it start with the fus). So the problem is that from the FUS I cannot start the Thread Stack but when I read the Stack version from the CubeProgrammer it says the correct one.
Also if I follow this: from CubeProg Start Wireless Stack - Run App (won't even start) - Start FUS returns ERROR the 1st time! I have to press Start FUS again and then it works. This happens every time a follow those steps.
If instead I do: Start FUS - Run App (blinking leds in error of stack) - Start FUS works fine.
I don't know what the problem is? The stack version? The FUS version? The combination of both? I tried with a different stack version (1.21 at 0x0808C000) and the behaviour is the same.
Please help!
EDIT: Also, it seems that all the Thread Applications for the Dongle, are copy-pasted from the Nucleo, because all of them have the wrong .ld and startup files (stm32wb55rvgx instead of stm32cgux). Only the BSP file is correctly changed to the dongle one