Good morning
This is my first post in this forum so I guess hello and welcome everyone. I've owned a JLink for a couple of years now and never had any problems whatsoever, so
for that. Sadly there is a first time for everything...
I've just switched from linux mint to manjaro and tried to set up my development platform, consisting of eclipse, the gnu arm plugin and my beloved jlink. Up until 15 minutes ago I'd have said everything works like a charm. I git cloned one of my projects, ran a debug session with multiple breakpoints and SWO output and it all worked pretty much out of the box. What doesn't work however is to set a breakpoint into a running target and this starts to annoy me... a lot. I've reinstalled eclipse a couple of times by now and tried different jlink versions from 5.12 to the current one without any success. I've also tinkered with the .rules file within etc/udev, but I guess since I can actually connect to my target there is no problem to be found with permissions.
I've also created a log file of one debug session with SWO turned off and attached it to this post. I'm not very familiar with GDB, its messages or its command line, but I guess the problem starts somewhere around line 737 where I remove a breakpoint and run the target.
03-00000000-00-00008497-0032: Removing breakpoint @ address 0x08005734, Size = 2
02-00000000-00-00008497-005B: T15265700 008:499 JLINK_ClrBPEx(BPHandle = 0x00000004) returns 0x00 (0000ms, 1752ms total)
02-00000000-00-00009013-004D: T19E6F700 009:013 JLINK_GetHWStatus(...) returns 0x00 (0002ms, 1754ms total)
03-00000000-00-00010362-0016: Starting target CPU...
02-00000000-00-00010374-0047: T15265700 010:375 JLINK_IsHalted() returns TRUE (0001ms, 1755ms total)
02-00000000-00-00010381-00C5: T15265700 010:376 JLINK_GoEx(MaxEmulInsts = -1, Flags = 0x00) -- CPU_ReadMem(4 bytes @ 0xE0001000) -- CPU_WriteMem(4 bytes @ 0xE000ED30) -- CPU_WriteMem(4 bytes @ 0xE0002008) (0007ms, 1761ms total)
02-00000000-00-00010383-0048: T15265700 010:383 JLINK_IsHalted() returns FALSE (0002ms, 1763ms total)
Suddenly the rest of the log is filled with "IsHalted()" calls which all return FALSE. I can tell that the target is actually running since it reacts to my inputs (buttons, commands over various interfaces). What simply doesn't work from this point on is to set a breakpoint into the code with eclipse. Also trying to terminate the session ends with an error.
/edit
ok, I found the issue
its with the release of arm-none-eabi-gdb I'm using
details here:
bugs.eclipse.org/bugs/show_bug.cgi?id=509812
bugs.launchpad.net/gcc-arm-embedded/+bug/1594341
This is my first post in this forum so I guess hello and welcome everyone. I've owned a JLink for a couple of years now and never had any problems whatsoever, so
for that. Sadly there is a first time for everything...I've just switched from linux mint to manjaro and tried to set up my development platform, consisting of eclipse, the gnu arm plugin and my beloved jlink. Up until 15 minutes ago I'd have said everything works like a charm. I git cloned one of my projects, ran a debug session with multiple breakpoints and SWO output and it all worked pretty much out of the box. What doesn't work however is to set a breakpoint into a running target and this starts to annoy me... a lot. I've reinstalled eclipse a couple of times by now and tried different jlink versions from 5.12 to the current one without any success. I've also tinkered with the .rules file within etc/udev, but I guess since I can actually connect to my target there is no problem to be found with permissions.
I've also created a log file of one debug session with SWO turned off and attached it to this post. I'm not very familiar with GDB, its messages or its command line, but I guess the problem starts somewhere around line 737 where I remove a breakpoint and run the target.
03-00000000-00-00008497-0032: Removing breakpoint @ address 0x08005734, Size = 2
02-00000000-00-00008497-005B: T15265700 008:499 JLINK_ClrBPEx(BPHandle = 0x00000004) returns 0x00 (0000ms, 1752ms total)
02-00000000-00-00009013-004D: T19E6F700 009:013 JLINK_GetHWStatus(...) returns 0x00 (0002ms, 1754ms total)
03-00000000-00-00010362-0016: Starting target CPU...
02-00000000-00-00010374-0047: T15265700 010:375 JLINK_IsHalted() returns TRUE (0001ms, 1755ms total)
02-00000000-00-00010381-00C5: T15265700 010:376 JLINK_GoEx(MaxEmulInsts = -1, Flags = 0x00) -- CPU_ReadMem(4 bytes @ 0xE0001000) -- CPU_WriteMem(4 bytes @ 0xE000ED30) -- CPU_WriteMem(4 bytes @ 0xE0002008) (0007ms, 1761ms total)
02-00000000-00-00010383-0048: T15265700 010:383 JLINK_IsHalted() returns FALSE (0002ms, 1763ms total)
Suddenly the rest of the log is filled with "IsHalted()" calls which all return FALSE. I can tell that the target is actually running since it reacts to my inputs (buttons, commands over various interfaces). What simply doesn't work from this point on is to set a breakpoint into the code with eclipse. Also trying to terminate the session ends with an error.
/edit
ok, I found the issue
its with the release of arm-none-eabi-gdb I'm using
details here:
bugs.eclipse.org/bugs/show_bug.cgi?id=509812
bugs.launchpad.net/gcc-arm-embedded/+bug/1594341