We are pleased to announce that STM32CubeProgrammer 2.19 is available What is new in 2.19: Support for the STM32WBA6xxx microcontrollers: Internal memory programmingOption byte/OTP programmingRDP regression with passwordSFI support Support for MCE N...
Is it possible to display the data from the ITM over the SWV viewer (NUCLEO-F401RE) in STM32CubeProgrammer in HEX? ITM_SendChar could be used to send just a 32-bit code, which takes far less CPU time than a printf-style debug output?
Virgin STM32L4 always shows "Mass erase operation failed. Pleaes verify flash protection" error in STM32CubeProg. It is a virgin device, I guess as factory setting there should be no write protection. How could I flash it at all?Thank you very much!
Hello,I cannot use the STM32CUBEprogrammer standalone program, however my programmer works just fine with stm32CUBEIDE V1.7. During programming in STM32cubeide the configuration is visible and it loads STM32cubeprogrammer V2.8 I copied the settings o...
Hello,I am using the STM32CubeProgrammer, version 2.10.0, and it does not detect the STM32L152VD-X reserved memory space, at address 0x0803000.The STM32CubeProgrammer detects the correct device ID which is 0x437 but does not detect the correct device...
In the introduce page of STM32CubeProgrammer, it descrips that this software support CAN bootloader interface, but I just find the ST-link Uart and USB. How can I configure it to CAN?
The method is as follows:1. First, set the flash option byte to force boot from the main flash.2. Set the read protection level to level 1.After this setting, the st-link tool will no longer be able to connect to the chip, which is equivalent to losi...
Hi all,The goal is to embed option bytes in hexfile, such that when production are doing their thing, the correct settings are automagically selected.But stm32cubeprogrammer fails with:Error: Data mismatch found at address 0x1FFF781B (byte = 0x00 ins...
We are working on our own firmware update utility, and need a way to get the Device Id from default USB DFU bootloader in order to avoid wrong firmware flashing. On CubeProgrammer, we can see that info: 21:36:20 : Device ID : 0x0423The question is: ...
When we program the any stm32 mcu, we can choice between erase the memory or no in STM32CubeProgrammer. Why in code time we can't write in flash without erasing the memory?
