• State Accepted Answer
  • Locked Locked
  • Replies 2 replies
  • Subscribers 349 subscribers
  • Views 5229 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

Break point at SWI handler

Henry

Hi everyone,

I'm using Jlink with openocd to debug ARM926EJ-S and encountered problem when executing SWI command.

Even though I don't set a break point at SWI handler but the CPU breaks at SWI handler automatically. How to remove the break point and make the CPU run continuously after every SWI command ?

Thank you very much.

Parents
  • 0

    Oh I know the reason,

    OpenOCD manual says that :

    Command: arm semihosting

    [enable|disable]

    Display status of semihosting, after optionally changing that status.

    Semihosting allows for code executing on an ARM target to use the I/O facilities on the host computer i.e. the system where OpenOCD is running. The target application must be linked against a library implementing the ARM semihosting convention that forwards operation requests by using a special SVC instruction that is trapped at the Supervisor Call vector by OpenOCD.

    So run command arm semihosting disable to solve the problem.

Reply
  • 0

    Oh I know the reason,

    OpenOCD manual says that :

    Command: arm semihosting

    [enable|disable]

    Display status of semihosting, after optionally changing that status.

    Semihosting allows for code executing on an ARM target to use the I/O facilities on the host computer i.e. the system where OpenOCD is running. The target application must be linked against a library implementing the ARM semihosting convention that forwards operation requests by using a special SVC instruction that is trapped at the Supervisor Call vector by OpenOCD.

    So run command arm semihosting disable to solve the problem.

Children
No data