We are pleased to announce that the release 1.18.0 of STM32CubeIDE is available. What is new in 1.18.0: Microcontrollers, microprocessors, and board lists aligned with STM32CubeMX 6.14.0: Added the support for STM32WBA6xxx microcontrollers in the STM...
The optimization options for GCC compilation are: Optimize for size(-Os),The compiled result is as follows: The size of MCU Flash resources occupied is: text+data = 47264 Byte The.ld link script is shown below: Question: In my program, the....
This is the sample error that pops up. How can I fix this? I'm very new to this so I'm not very familiar with this error. Hope that someone could help me with this. Tell me what else I need to provide so you can help me better./Applications/STM32Cube...
I have tried to add a library with .a extension but all tries had been unsuccessfully.I have added the search path to "Library Search Path (L)" section in MCU GCC Linker.I have added the library name to "Libraries (-l)" section in MCU GCC Linker.With...
I am making a DFU for stm32f4-discovery board.My DFU is using a project generated by STM32CubeMX V1.0. And It worked well with the program generated by the STM32CubeMX V1.0But when I worked with a project generated by STM32CubeIDE, I cannot make the ...
Hello everyone,I just migrate from Keil. I can use __attribute__((at(0x6000000))) directive place a variable at a given absolute address ,but how to do this in STM32CubeIDE?Thanks.
I just started using the STM32L552ZET6Q board. So, I wrote a program and built it successfully without any error, but I am getting an error while debugging with the error message Failed to execute MI command: target remote localhost:61234.I use ST-LI...
Updated CubeIDE from version 9 to 10. Imported projects from workspace OLD created with 9 into 10. Projects are listed in 10 but cannot be opened due to missing product description files.
Hi,I get the following error when I tried to debug my custom application.Error in final launch sequence: Failed to execute MI command: -exec-run Error message from debugger back end: During startup program exited with code 126. Failed to execute MI...
Programming is ok when using ST-link software.
