2022-05-15 07:00 PM
Note: I can use stlink to download programs to other boards.But p_nulceo_wb55 doesn't work well. I use an external stlink instead of the on-board stlink, the errors are same.
I was learning Bluetooth, It would have worked well. After a while, an error has occurred.
Is it because I have downloaded some program?
The errors are as follows(use stm32cubeprogrammer :(
the erros in stm32cubeide:
2022-05-18 06:16 AM
Hello,
You can try to change the Mode to "Under reset" on STM32CubeProgrammer or press reset button SW4, keep SW4 pressed, click on Connect and release the button.
Best Regards
2022-05-18 07:22 AM
Thank you for your answer. The problems still exists. Once I pulled up boot0, I can connect the p_nucleo_wb55, but i can‘t read the flash and erase the flash,
, the error is 'Error: Mass erase operation failed.Please verify flash protection'. Later , the problem becom as mentioned above error ' no stm32 target found '.
2022-06-08 07:33 AM
Hello @�?� 丫饼 ,
Make sure that your STLink firmware is upgraded. Check pin configuration from the SWD connector. Can you try on another hardware?
If connect under reset doesn’t help, so probably the issue is related to power-supply configuration.
When your issue is solved, please close this topic by choosing Select as Best. This will help other users find that answer faster.
Imen
2022-06-09 06:09 AM
Thank you.
P_NUCLEO_WB55RGV6(MB1355C) :
2022-06-16 04:07 AM
Hi @�?� 丫饼 ,
Make sure that you use the latest release of CubeProgrammer and CubeIDE.
I advise you this FAQ: How to solve debugger connection issues, it may helps you.
> Another hardware can download ok.
Have you checked with STM32WB board or another series of hardware?
Maybe you can check with another toolchain as Keil or IAR, to identify if this problem is related to CubeIDE tool.
Imen
2022-06-17 05:45 AM
Thank you. I buy another P_NUCLEO_STM32WB55. And it works well.
I check the hardware configuration, and it's the same as the new.
I use STM32CUBEPRO to download the code. Keil and stm32cubeide can't download well.
2022-06-22 03:24 AM
Hello Lep (Community Member),
Check the Option bytes configurations, they might be different.
It could be a hardware limitation, please verify the Revision ID of the different chips (Can be displayed by CubeProg when connecting the board) and later check the Errata sheet of the MCU, in which you may find the reason of the limitation(if exists).
Sara.
2022-06-22 06:57 PM
Thank you, This problem has been bothering me for a long time, I have not been able to connect stm32 target.
2022-06-23 12:38 AM
Hello @�?� 丫饼 ,
Maybe the program you loaded in the MCU is causing this issue. If this is the case, I would advise you to boot from system memory.
You just need to connect BOOT0 to VDD, reset the board and then try to connect via CubeProgrammer and finally mass erase the Flash memory.
If the proposed solution didn't work could you please send me the code so that I can reproduce the issue ?
Thanks,
Sara.