• State Accepted Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 120 subscribers
  • Views 2948 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

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

Cortex-R5 target cannot be stopped

James.sun

After DS-5 connected to target, "Debug Control" tab shows "Cortex-R5_0#1 running", but "Commands" tab shows

"ERROR(TAD9-NAL30):
! Unable to stop device Cortex-R5_0
! Cannot stop target."

in response to "stop" cmd. Any idea about it? what issue usually causes this? 

Thanks

James

Parents
  • 0 in reply to Kaiyou Wang

    Hi Kaiyou,

    I am using ARM DS 2021.2 and DSTREAM ST as debugger probe, on a real chip, and is my first time to use an ARM debugger to talk to it, and it happens 100%.  It was set as "connect only" and "stop" is the only cmd in "execute debugger commands" box.  I have captured daplog and will send it to you.  Thanks for help! 

Reply
  • 0 in reply to Kaiyou Wang

    Hi Kaiyou,

    I am using ARM DS 2021.2 and DSTREAM ST as debugger probe, on a real chip, and is my first time to use an ARM debugger to talk to it, and it happens 100%.  It was set as "connect only" and "stop" is the only cmd in "execute debugger commands" box.  I have captured daplog and will send it to you.  Thanks for help! 

Children
  • +1 Arm Employee Badge in reply to James.sun

    Hi James,

    Thanks for your log. I can see the debugger has already try to halt the processor by write 1 to the DBGDRCR[0], but the Core doesn't give response, I suspect the Core already hangs when the debugger connected. I suggest you to connect more earlier or look at your code flow, generally hang causes from peripherial device access.