I've either got a bug in my code or the JLINK connection is dying. Either way it's a real headache to pinpoint and how to resolve. Knowing more about extracting info from the JLINK Log would probably be helpful in these cases.
Within Crossworks I see that the JLINK has halted with an error. However, my device continues to run. Crossworks shows what looks like a dereferenced null pointer. Stack is blown. Registers are all 0. IP is at 0x00000000.
The crash/disconnect happens at random times usually within 5 minutes. The device continues to operate and internal logging of events shows no errors.
The tail of the JLINK log shows:
T0B70 1112:717 JLINK_ReadMemU32(0xE000101C, 0x0001 Items, ...)-- failed - DWT_PCSR
T0B70 1112:765 JLINK_ReadMemU32(0xE000EDF0, 0x0001 Items, ...)-- failed - DHCSR
T0B70 1112:766 JLINK_Halt()
Is there any way to set a breakpoint to catch and see what's happening? Is there a way to implement more sophisticated breakpoints (e.g., break on read, break on write, etc.)
Many thanks for any pointers. I will followup with the solution if I find one.
Target device: nRF51822_xxAC with multiple I2C connected sensors, SD130 connected via SWD on nRF51-DK.
Please sign in to leave a comment.