This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

KEIL debugger behavior different on two different computers - using STM32F303K8 Nucleo board

I am developing simple applications for the STM32F303k8 Nucleo board. I have the same version of KEIL uvision and MDK-Lite (5.28.0.0) installed on both a personal computer and a networked computer at my institution. I have developed simple code to test a 'hello world' situation - blinking a light - using STM32CubeMX to configure the peripherals and it works fine when loaded onto the board using either computer.

The problem is that while the debugger works fine on my personal computer, the debugger doesn't work on the networked institution computer at all. I am unable to set breakpoints on the networked computer and while the debugger still steps through code in the disassembly window, it doesn't step through any of the C code and just loads the startup file, even though "run to main()" is selected in the debug settings. Additionally, in the debugger, none of the *.c files on the networked computer have the standard gray left edge where breakpoints are typically set. I also have the optimization level set to 0 in both cases, and I can't find any difference between any settings on either computer.

I am also using the same Nucleo board with both computers.

  • Tough to answer. 

    What's the result if you compare with the "CMSIS-RTOS Blinky (STM32F3-Discovery)" example project offered by the Pack Installer?

  • After a lot of experimenting, it seems that STM32CubeMX does not create project folders correctly when a certain filepath on a networked computer is used. By specifying a simpler filepath, the project folder is created correctly, and this has something to do with the debugger in KEIL being able to access the *.c or *.h files used in the project. I will try and compile images and instructions so that this will be of help to anyone who runs into this problem in the future.

  • it seems that STM32CubeMX does not create project folders correctly

    Have you notified ST of that ?

    I will try and compile images and instructions so that this will be of help to anyone who runs into this problem in the future.

    To make sure it's visible as the solution, be sure to mark it as such: