• State Accepted Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 4 replies
  • Subscribers 25 subscribers
  • Views 4315 views
  • Users 0 members are here
Options
Related
How was your experience today?
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

How to avoid BKPT 0xAB instruction

Bhanu subrahmanyam

I am using MCU Cortex-M4 and running keil on simulation. while running keil in debug mode, code is stopping at BKPT 0xAB instruction and we have to re initialize run to continue like break point. I am not using break points. I need code to run with out stopping at BKPT instruction. How is it possible? How to avoid BKPT instruction? please help any one.

Parents
  • 0

    You're right that this breakpoint instruction is being used to trigger some kind of semihosting operation. If your code contains such instructions, you'll need to always run it attached to a debugger that knows what to do when such an instruction is encountered. If you need to run the device standalone, find out what code you're using that causes the semihosting operations to take place, and make sure that code isn't in the standalone build. This situation is a good opportunity to set up "debug" and "release" builds of your software - maybe using #ifdef DEBUG or something along those lines to exclude the semihosting code from your release build.

    LiteBlue

Reply
  • 0

    You're right that this breakpoint instruction is being used to trigger some kind of semihosting operation. If your code contains such instructions, you'll need to always run it attached to a debugger that knows what to do when such an instruction is encountered. If you need to run the device standalone, find out what code you're using that causes the semihosting operations to take place, and make sure that code isn't in the standalone build. This situation is a good opportunity to set up "debug" and "release" builds of your software - maybe using #ifdef DEBUG or something along those lines to exclude the semihosting code from your release build.

    LiteBlue

Children
No data