Hi,
We are using Segger J-Link to gebug our firmware on NXP LPC4078 microcontroller. IDE: VisualStudio 2015; VisualGDB 5.4 preview 3 build 2193 (latest at this moment).
JLinkARM.dll V6.32d (DLL compiled May 25 2018 17:03:12)
Sometimes gebugging process fails with error:
This error repeates infinitely, if we try to stop debugging, read registers, set breakpoints, etc (after any command to gdb server).
We can't determine cause ot this bug, but usually it occurs when we set many breakpoints, when we debug firmware step-by-step, when we jump between breakpoints many times.
In previous version of JLink driver (V6.12j) we got another kind of error - crashing of JLinkGDBServerCL.exe without any possibility of reading debugger logs.
How can we determine cause of this bug? What means code in "remote failure reply"?
We are using Segger J-Link to gebug our firmware on NXP LPC4078 microcontroller. IDE: VisualStudio 2015; VisualGDB 5.4 preview 3 build 2193 (latest at this moment).
JLinkARM.dll V6.32d (DLL compiled May 25 2018 17:03:12)
Sometimes gebugging process fails with error:
Source Code
- Remote failure reply: E0790010BC790010010000001400000032340000C8E70010107A0010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A59B780010B8790010C99002006691020000000021
- Remote failure reply: E0790010BC790010010000001400000032340000C8E70010107A0010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A59B780010B8790010C99002006691020000000021
- Remote failure reply: E0790010BC790010010000001400000032340000C8E70010107A0010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A59B780010B8790010C99002006691020000000021
- Remote failure reply: E0790010BC790010010000001400000032340000C8E70010107A0010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A59B780010B8790010C99002006691020000000021
- Remote failure reply: E0790010BC790010010000001400000032340000C8E70010107A0010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A59B780010B8790010C99002006691020000000021
This error repeates infinitely, if we try to stop debugging, read registers, set breakpoints, etc (after any command to gdb server).
We can't determine cause ot this bug, but usually it occurs when we set many breakpoints, when we debug firmware step-by-step, when we jump between breakpoints many times.
In previous version of JLink driver (V6.12j) we got another kind of error - crashing of JLinkGDBServerCL.exe without any possibility of reading debugger logs.
How can we determine cause of this bug? What means code in "remote failure reply"?