Stm32cube IDE debugger often quote the memory read errors and error-CodePudding

STM32CUBE IDE to use for more than a month, is easy to use, with HAL function, compile the efficiency is not high, want to more friendly interface, support for Chinese is better, had JLINKV10, V9, debugging when IDE connects to the emulator seconds after prompt memory read errors, mistakes or interrupt, or STARTING target CPU, is still running on the board, SWV tracking is normal, but the software can't simulation, must from the console stop debugging, I wonder if you encountered this kind of situation,

CodePudding user response:

refer to the original poster strabile response:

STM32CUBE IDE to use for more than a month, is easy to use, with HAL function, compile the efficiency is not high, want to more friendly interface, support for Chinese is better, had JLINKV10, V9, debugging when IDE connects to the emulator seconds after the prompt memory read error, mistake or interrupt, or STARTING target CPU, is still running on the board, SWV tracking is normal, but the software can't simulation, must from the console stop debugging, I wonder if you encountered this kind of situation,

Do the same encounter, try to avoid using single step debugging, key points in the set breakpoints to debug,

CodePudding user response:

I also encountered such a problem, behind another ST cc-link v2 wouldn't appear,

CodePudding user response:

A debug is starting target CPU,,,, not basic debugging,