STM32WLxx DFU Error

[ethan2]

Hi,

I ported the SBSFU project to the LoRaWAN_AT_Slave routine, and tested DFU normally and it worked fine, but when I used the wrong file to upgrade, such as readme.txt, the upgrade process ran for a while, and then stopped, showed " Fw header authentication error" and "No valid FW found in the active slots nor new FW to be installed". As a result, the firmware of my application cannot run normally, and I must re-DFU the normal firmware before I can restore it. Is this normal?

[STTwo-32]

Hello @ethan2 

Please add more details on your configurations what steps have you been following, what is the readme you are toking about, what is the "Wrong file"...

Best Regards.

STTwo-32

[ethan2]

Hi STTwo-32,

I refer to < UM2767-geting-start-with-the-SBsfu-of-STM32Cubewl-stmicroelectronics > for the upgrade. The error readme.txt simply means that I did not use the generated xx.sfb file, but imported a txt file.

[ethan2]

Hi STTwo-32,

I did another split test using "BFU_1_Slot" routine of STM32Cube_FW_WL_V1.3.0 to rule out an exception in my project. Apart from turning on the BFU log, I made almost no changes, and the test results were the same as before.

Here is the.sfb file I tested:

When I am in 'A' and 'C' mutual upgrade, everything is normal

 When I loaded the wrong file 2025.txt, the upgrade failed and I could not access the application firmware again.

 I think this is not very reasonable, the verification of failed firmware, can not affect the operation of the device itself.