2021-05-15 01:53 PM
I noticed that all breakpoints are disabled in CubeIde. Windows 10 probably checks for updates automatically, so this IDE can't be very old version. What can I do?
Solved! Go to Solution.
2021-05-21 02:21 PM
I got the breakpoints back. I had several project on a panel at left side of the IDE. When I took off all extra, breakpoints appeared.
2021-05-15 04:30 PM
You don't have any breakpoints set. Press Ctrl+Shift+B on a line to set/unset one. Or click with the mouse left of the line.
Win10 doesn't check for updates to STM32CubeIDE automatically. You can do so with Help -> Check for Updates.
2021-05-16 01:52 AM
I'll try later today but I haven't seen any break points I could set, no matter what mouse button I use. But we'll see.
2021-05-16 08:14 AM
I can confirm, all breappoikts are disabled or not available.
2021-05-16 08:32 AM
2021-05-16 11:57 AM
The problem is that I can't create breakpoints.
With Keill and MS IDEs I just select a line and click or press something to put a breakpoint there. In Keil it is for instance F9. But here with CubeIde, choices are not active. See the picture in my first post. I think putting a breakpoint somewhere was easier earlier, or CubeIde has really strange logic with its breakpoints, which is possible.
2021-05-16 12:05 PM
2021-05-16 02:31 PM
Thanks. It is possible that I have done something to disable them, and i may have to reinstall the IDE.
2021-05-16 03:57 PM
Could it be that there is a problem wint STlink 3 mini or connections. The Ide says somewhere something like "Breakpoints supported by the CPU" :None.
I am not very spesific because the Ide is on the other HD on this machine, and I would have to boot Win 10 instead of this Win7. (Sometimes I wish I could give boot to CubeIde.)
2021-05-16 07:32 PM
From the posted picture it looks like the program is stopped at the 1st automatic breakpoint on main().
This means that the debugger can set breakpoints and generally works well.
To set breakpoints, click on the left margin in the editor, in the column where you see the small blue arrow.
Please take your time, practice with Eclipse. It is not the most intuitive IDE.
(now you understand why Keil's debugger costs money and is worth it.)
-- pa