Reasons for **JLink Warning: CPU could not be halted

⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.wsdof.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
4 posts / 0 new
Last post
Wed, 2018-04-25 22:14
#1
vrabo
Offline
Last seen:2 years 11 months ago
加入:2016-11-04 19:19
Reasons for **JLink Warning: CPU could not be halted

Hello!
I wanna know what are the possible reasons for the **JLink Warning: CPU could not be halted. I did some modifications in the code and now i get that all the time. I would like to know the reasons so i know where to find the errors.
Thank you!

Device:
DA14580
Thu, 2018-04-26 15:11
PM_Dialog
Offline
Last seen:1 hour 5 min ago
工作人员
加入:2018-02-08 11:03
Hi vrabo,

Hi vrabo,

A possible reason why you get this warning and the CPU could not be halted, is that the debugger is detached from the DA14580. So, that means that the DA14580 unexpectedly resets for some reason or your application code closes the debugger module of the device.

Thanks, PM_Dialog

Accepted answer
Thu, 2018-04-26 22:42
(Reply to #2)
vrabo
Offline
Last seen:2 years 11 months ago
加入:2016-11-04 19:19
so it could be a problem with

so it could be a problem with jumpers and not with the code... thanks for the answer!

Fri, 2018-04-27 16:25
PM_Dialog
Offline
Last seen:1 hour 5 min ago
工作人员
加入:2018-02-08 11:03
Hi vrabo,

Hi vrabo,

As I mentioned in the previous post, the reset reason might also be due to code. For example when trying to allocate memory and you don’t have enough left can lead you to a reset, if CFG_DEVELOPMENT_DEBUG in da1458x_stack_config.h is defined, the device will just issue an assertion if not the device will reset in most cases.

Thanks, PM_Dialog