• State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 22 subscribers
  • Views 1747 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

Help: Could not stop ARM device!

Syed T

Hello,

I am facing a problem with the ULINK.

I have my board with a custom made Soc with ARM7TDMI-S core. I want to use the ULINK tool along with the keil debugger. When I connect my device to the ulink and try to enter the debug mode it gives me the following error.

“Error: Could not stop ARM device, Please Check the JTAG Cableâ€
when I say OK to this error it gives one more error
"Error: Target DLL has been cancelled Debugger aborted!â€

The following are the settings I have done
1.I have selected device as “NXP’s LPC2378â€. (Since mine is a custom Soc, I have tried to select a device whose core matches with that of mine)
2.I have not selected any of the of the debugging options because I don’t want to run any code, I just want to enter into debug mode.
3.The following I see in the ulink ARM debugger settings. a. My Ulink device is detected. b. The core is detected automatically and it shows ARM7TDMI-S c. I have selected the “Use Reset at Startup†option
4. Following are my signal status
·nTRST (Pin 3 of the JTAG connector) pulled to 3.3V through a 10K resistor.
·RESET (Pin 15 of the JTAG connector) pulled to 3.3V through 4.7K resistor.
·Both the resets either shorted or otherwise generate the above condition.

Please help me solve the problem.

Thanks in advance.

Regards,
Syed T

Parents
  • 0 Arm Employee Badge in reply to Syed T

    Have you tried un-checking the Load Application at Startup box in the "Options for Target -> Debug" tab? That will prevent the IDE from trying to flash your device when starting the debugger.

    I think you would still want to at least erase the chip before entering debug mode. This would ensure that you are starting from a reproducible state as opposed to a possible random state considering this is a custom SoC. Being able to erase the device would also prove that you dont have some sort of underlying hardware/connection problem(s).

Reply
  • 0 Arm Employee Badge in reply to Syed T

    Have you tried un-checking the Load Application at Startup box in the "Options for Target -> Debug" tab? That will prevent the IDE from trying to flash your device when starting the debugger.

    I think you would still want to at least erase the chip before entering debug mode. This would ensure that you are starting from a reproducible state as opposed to a possible random state considering this is a custom SoC. Being able to erase the device would also prove that you dont have some sort of underlying hardware/connection problem(s).

Children