P2P_Client needs to be placed in bootloader mode after executing

[Fernb2000]

Hello;

 

I am very new to STM32 products. I have been working with the P2P_Server and P2P_client examples using the STM32WB05KZV6TR MCU.

As I use the P2P_clent example in both the Nucleo board WB05KZ and a custom board and load the built image, the next time I try to download a new image I need to put the nucleo board into Bootloader mode(BOOT0 jumped to Vcc) and download the new image that way. The custom board that I am working with currently has no hardware way of putting it into bootloader mode therefore I cannot load a new image.

My question is, why do I need to put the nucleo board into bootloader mode to load an P2P_Client image?, The P2P_server does not have this issue

 

Is there a way to prevent this?

 

thanks

 

Fernando

[STTwo-32]

Hello @Fernb2000 @and welcome to the ST Community. 
I think this is due to the fact that with the example you are using, the Low-power mode is enabled to offer the best low-power performances. Therefore, on STM32WB05KZ, the SWD lines are OFF and the tool cannot connect with the device anymore. So you need to enter Bootloader mood before being able to download the new code. So I suggest you to set both CFG_LPM_SUPPORTED to 0 and CFG_FULL_LOW_EMULATED to 1 on the  app_conf.h file of your project.

Best Reagrds.

STTwo-32

[Fernb2000]

@STTwo-32 thank you, I was close to doing your suggestion.  This is what I found in the header file that you mentioned that confused me:

 

* When CFG_LPM_SUPPORTED and CFG_FULL_LOW_EMULATED are both set to 1, the system is configured to
* emulate the Deepstop mode without losing the debugger connection and breakpoints nor watchpoints.

 

That is what I did and it wouldn't workyour change nad it seems to what as you mention.

 

Is there any functionality that would be impacted besides the LPM? Like timers, button response?

 

Thank you

 

Fernando