« previous next »
Pages: [1] 2  All   Go Down

Author Topic: Debugging with Segger JLINK  (Read 47788 times)

Offline bartddgd

  • Single posting newcomer
  • *
  • Posts: 4
Debugging with Segger JLINK
« on: March 03, 2013, 08:42:14 pm »
Hi,

I'm using Code::Blocks together with the Yagarto ARM toolchain. Compiling and linking is working just fine using my custom Makefile.

Now I'm trying to get JTAG programming and debugging to work. As JTAG adapter I use a Segger JLINK EDU. Flashing works fine, but debugging always fails :-(

In the "Before connection" field of the GDB config in Code::Blocks I have:

file ./obj/lpc2387_88_test.elf
set mem inaccessible-by-default off
target remote localhost:2331
monitor flash device = LPC2387
monitor flash breakpoints = 1
monitor flash download = 1
monitor endian little
monitor speed auto
monitor reset
monitor long 0xE01FC040 = 1
load

The "After connection" field contains:

monitor reset
thbreak main
continue

My program gets uploaded and starts running if I remove the "thbreak main" line. If I leave this line in, the program gets uploaded and even seems to stop at main(), but from that point on no other debug function in Code::Blocks works. All the stepping options are greyed out and I cannot terminate the debug session. I have to close and restart Code::Blocks and the Segger GDB server.

Any ideas how to get debugging to work in Code::Blocks?

Best regards,
Bernd
Logged

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13413
    • Travis build status
Re: Debugging with Segger JLINK
« Reply #1 on: March 03, 2013, 09:13:33 pm »
Quote from: bartddgd on March 03, 2013, 08:42:14 pm
monitor reset
thbreak main
continue
Why don't you use the breakpoint and continue/step UI in codeblocks?
They should work just fine. The before/after connection options should be used only for setup not for controlling the execution.
Logged
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline bartddgd

  • Single posting newcomer
  • *
  • Posts: 4
Re: Debugging with Segger JLINK
« Reply #2 on: March 03, 2013, 09:27:35 pm »
So, you mean I should just have the "Before" options for uploading the firmware and no options in "After"?.

Just tried that: In the "Before" options I added "monitor reset" as the last line (right behind "load") and set a breakpoint in the GUI somewhere in my main while() loop.

After clicking on the "Debug/continue" button the GDB connection gets started and the firmware is uploaded. I can see a small window from Segger doing the flash upload for a short time. Then in the GUI my startup.s file gets focused with the reset entry address and program is still stopped and non of the debug icons work (most of them are greyed out).

If I repeat the procedure and add "continue" at the end of the "Before" options the program gets uploaded an started, but again none of the debug options work. Altough this time  none is greyed out.
Logged

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13413
    • Travis build status
Re: Debugging with Segger JLINK
« Reply #3 on: March 03, 2013, 09:50:56 pm »
Can you post the full log from the debugger (you should enable it first!)?
And yes, putting continue/break or other similar commands will mess up the communication between C::B and gdb.
Logged
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline bartddgd

  • Single posting newcomer
  • *
  • Posts: 4
Re: Debugging with Segger JLINK
« Reply #4 on: March 04, 2013, 04:18:40 pm »
Here is what's happening when I press the "Debug/Continue" button:

Code
Building to ensure sources are up-to-date
Selecting target: 
All
Adding source dir: D:\Devel\X711_Test\
Adding source dir: D:\Devel\X711_Test\
Adding file: D:\Devel\X711_Test\obj\lpc2387_88_test.sys
Changing directory to: D:/Devel/X711_Test/
Set variable: PATH=.;C:\yagarto-20121222\bin;C:\yagarto-20121222;C:\Program Files (x86)\AMD APP\bin\x86_64;C:\Program Files (x86)\AMD APP\bin\x86;C:\Program Files (x86)\VMware\VMware vSphere CLI\Perl\site\bin;C:\Program Files (x86)\VMware\VMware vSphere CLI\Perl\bin;C:\Perl64\site\bin;C:\Perl64\bin;C:\MentorGraphics\9.3.1PADS\SDD_HOME\common\win32\bin;C:\MentorGraphics\9.3.1PADS\SDD_HOME\common\win32\lib;C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;C:\WinAVR-20100110\bin;C:\WinAVR-20100110\utils\bin;C:\Windows\System32;C:\Windows;C:\Windows\System32\wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files\Microsoft Windows Performance Toolkit;C:\Program Files (x86)\IVI Foundation\IVI\Bin;C:\Program Files\IVI Foundation\IVI\Bin;C:\Program Files\IVI Foundation\VISA\Win64\Bin;C:\Program Files (x86)\IVI Foundation\VISA\WinNT\Bin;C:\Program Files\TortoiseSVN\bin;C:\Program Files (x86)\Windows Live\Shared;C:\Program Files (x86)\Common Files\Acronis\SnapAPI;C:\MentorGraphics\9.3.1PADS\MGC_HOME.ixn\bin;C:\MentorGraphics\9.3.1PADS\MGC_HOME.ixn\lib;C:\Program Files (x86)\doxygen\bin;C:\Program Files (x86)\GTK2-Runtime\bin;C:\Program Files (x86)\MiKTeX 2.9\miktex\bin;C:\Program Files (x86)\Graphviz 2.28\bin;C:\Program Files\doxygen\bin;C:\Program Files (x86)\Haufe\iDesk\iDeskService;C:\yagarto-tools-20121018\bin;C:\Program Files (x86)\Flash Magic;C:\Program Files (x86)\Acronis\BackupAndRecovery;C:\Program Files (x86)\IDM Computer Solutions\UltraEdit;C:\Program Files (x86)\IDM Computer Solutions\UltraCompare;c:\Program Files (x86)\gs\gs9.05\bin

[debug]Command-line: C:\yagarto-20121222\bin\arm-none-eabi-gdb.exe -nx -fullname  -quiet  -args D:/Devel/X711_Test/obj/lpc2387_88_test.sys
[debug]Working dir : D:\Devel\X711_Test

Starting debugger: C:\yagarto-20121222\bin\arm-none-eabi-gdb.exe -nx -fullname  -quiet  -args D:/Devel/X711_Test/obj/lpc2387_88_test.sys
done

[debug]> set prompt >>>>>>cb_gdb:

Registered new type: wxString
Registered new type: STL String
Registered new type: STL Vector
Setting breakpoints

[debug]D:/Devel/X711_Test/obj/lpc2387_88_test.sys: No such file or directory.
[debug](gdb) >>>>>>cb_gdb:
[debug]> show version
[debug]GNU gdb (GDB) 7.5.1
[debug]Copyright (C) 2012 Free Software Foundation, Inc.
[debug]License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
[debug]This is free software: you are free to change and redistribute it.
[debug]There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
[debug]and "show warranty" for details.
[debug]This GDB was configured as "--host=i686-pc-mingw32 --target=arm-none-eabi".
[debug]For bug reporting instructions, please see:
[debug]<http://www.gnu.org/software/gdb/bugs/>.
[debug]>>>>>>cb_gdb:
[debug]> set confirm off

Debugger name and version: GNU gdb (GDB) 7.5.1

[debug]>>>>>>cb_gdb:
[debug]> set width 0
[debug]>>>>>>cb_gdb:
[debug]> set height 0
[debug]>>>>>>cb_gdb:
[debug]> set breakpoint pending on
[debug]>>>>>>cb_gdb:
[debug]> set print asm-demangle on
[debug]>>>>>>cb_gdb:
[debug]> set unwindonsignal on
[debug]>>>>>>cb_gdb:
[debug]> set print elements 0
[debug]>>>>>>cb_gdb:
[debug]> set disassembly-flavor att
[debug]No symbol table is loaded.  Use the "file" command.
[debug]>>>>>>cb_gdb:
[debug]> catch throw
[debug]No symbol table is loaded.  Use the "file" command.
[debug]Catchpoint 1 (throw)
[debug]>>>>>>cb_gdb:
[debug]> source C:\Users\bart\AppData\Local\CodeBlocks\share\codeblocks/scripts/stl-views-1.0.3.gdb
[debug]>>>>>>cb_gdb:
[debug]> directory D:/Devel/X711_Test/
[debug]Source directories searched: D:/Devel/X711_Test;$cdir;$cwd
[debug]>>>>>>cb_gdb:
[debug]> file ./obj/lpc2387_88_test.elf
[debug]Reading symbols from D:\Devel\X711_Test\obj\lpc2387_88_test.elf...done.
[debug]>>>>>>cb_gdb:
[debug]> set mem inaccessible-by-default off
[debug]>>>>>>cb_gdb:
[debug]> target remote localhost:2331
[debug]Remote debugging using localhost:2331
[debug]Vectors () at src/lpc23xx_startup.s:120
[debug]D:\Devel\X711_Test\src\lpc23xx_startup.s:120:3990:beg:0x0
[debug]>>>>>>cb_gdb:
[debug]> monitor flash device = LPC2387

At D:\Devel\X711_Test\src\lpc23xx_startup.s:120

[debug]> monitor flash device = LPC2387
[debug]Selecting device: LPC2387
[debug]Selecting device: LPC2387
[debug]>>>>>>cb_gdb:>>>>>>cb_gdb:
[debug]> monitor flash breakpoints = 1
[debug]Flash breakpoints enabled
[debug]>>>>>>cb_gdb:
[debug]> monitor flash download = 1
[debug]Flash download enabled
[debug]>>>>>>cb_gdb:
[debug]> monitor endian little
[debug]Target endianess set to "little endian"
[debug]>>>>>>cb_gdb:
[debug]> monitor speed auto
[debug]Select auto target interface speed (65535 kHz)
[debug]>>>>>>cb_gdb:
[debug]> monitor reset
[debug]Resetting target
[debug]>>>>>>cb_gdb:
[debug]> monitor long 0xE01FC040 = 1
[debug]Writing 0x00000001 @ address 0xE01FC040
[debug]>>>>>>cb_gdb:
[debug]> load
[debug]Loading section .text, size 0xa94 lma 0x0
[debug]Start address 0x0, load size 2708
[debug]Transfer rate: 377 KB/sec, 2708 bytes/write.
[debug]>>>>>>cb_gdb:
[debug]> monitor reset
[debug]Resetting target
[debug]>>>>>>cb_gdb:
[debug]> break "D:/Devel/X711_Test/src/app_main.c:123"
[debug]Breakpoint 2 at 0x494: file src/app_main.c, line 123.
[debug]>>>>>>cb_gdb:
[debug]> run
[debug]The "remote" target does not support "run".  Try "help target" or "continue".
[debug]>>>>>>cb_gdb:

This is what I see in the Segger GDB server log window:

Code
SEGGER J-Link GDB Server V4.60a

JLinkARM.dll V4.60a (DLL compiled Jan 16 2013 17:15:30)

Connecting to J-Link...
J-Link is connected.
Firmware: J-Link ARM V8 compiled Nov 14 2012 22:34:52
Hardware: V8.00
S/N: 268004267
OEM: SEGGER-EDU
Feature(s): FlashBP, GDB
Checking target voltage...
Listening on TCP/IP port 2331
Connecting to target...
J-Link found 1 JTAG device, Total IRLen = 4
JTAG ID: 0x4F1F0F0F (ARM7)
Connected to target
Waiting for GDB connection...Connected to 127.0.0.1
Reading all registers
Read 4 bytes @ address 0x00000000 (Data = 0xE59FF018)
Selecting device: LPC2387
Selecting device: LPC2387
Flash breakpoints enabled
Flash download enabled
Target endianess set to "little endian"
Select auto target interface speed (65535 kHz)
Resetting target
Writing 0x00000001 @ address 0xE01FC040
Downloading 2708 bytes @ address 0x00000000
WARNING: CPU is running at low speed (4017 kHz).
Resetting target
Read 4 bytes @ address 0x00000000 (Data = 0xE59FF018)
Read 4 bytes @ address 0x000003A0 (Data = 0xE3A03001)
Read 4 bytes @ address 0x00000494 (Data = 0xE51B3008)


Contents of GDB "Before" commands:

Code
file ./obj/lpc2387_88_test.elf
set mem inaccessible-by-default off
target remote localhost:2331
monitor flash device = LPC2387
monitor flash breakpoints = 1
monitor flash download = 1
monitor endian little
monitor speed auto
monitor reset 
monitor long 0xE01FC040 = 1
load
monitor reset

The firmware gets uploaded, the editor shows the startup.s file with a small little yellow triangle on the reset entry vector line.
The buttons "Break debugger" and "Stop debugger" are available, but clicking on them has no effect. All other debug buttons are greyed out.

Logged

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13413
    • Travis build status
Re: Debugging with Segger JLINK
« Reply #5 on: March 04, 2013, 04:26:55 pm »
Quote from: bartddgd on March 04, 2013, 04:18:40 pm
Contents of GDB "Before" commands:

Code
file ./obj/lpc2387_88_test.elf
set mem inaccessible-by-default off
target remote localhost:2331
monitor flash device = LPC2387
monitor flash breakpoints = 1
monitor flash download = 1
monitor endian little
monitor speed auto
monitor reset 
monitor long 0xE01FC040 = 1
load
monitor reset

C::B still think you're not in remote debugging mode, because you've setup the connection parameters manually using gdb commands.
Please use the UI, for things like ip, domain, port, speed, etc. Then it should work.
Logged
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline bartddgd

  • Single posting newcomer
  • *
  • Posts: 4
Re: Debugging with Segger JLINK
« Reply #6 on: March 04, 2013, 04:34:10 pm »
Thanks a lot! Now I understood what you meant.

After removing the "target remote localhost:2331" line from the "Before" commands and adding "localhost" and port 2331 in the "Remote connection" tab of the debugger project settings everything works fine. The program break where it should and single stepping also works.

Again, thanks for your quick help!

Best regards,
Bernd
Logged

Offline dirk_1980

  • Multiple posting newcomer
  • *
  • Posts: 25
Re: Debugging with Segger JLINK
« Reply #7 on: March 08, 2013, 03:08:58 pm »
Maybe the easiest way is to use the emIDE.
It is a Code::Blocks clone with some really nice changes to CB.
And there is a special J-Link Plugin.


Logged

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13413
    • Travis build status
Re: Debugging with Segger JLINK
« Reply #8 on: March 08, 2013, 03:50:42 pm »
Quote from: dirk_1980 on March 08, 2013, 03:08:58 pm
Maybe the easiest way is to use the emIDE.
This is something new, someone has forked C::B instead of providing patches...
Logged
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9694
Re: Debugging with Segger JLINK
« Reply #9 on: March 09, 2013, 01:48:16 pm »
Quote from: oBFusCATed on March 08, 2013, 03:50:42 pm
This is something new, someone has forked C::B instead of providing patches...
dunno - it seems its based on 12.11 sources with additional plugins.

But still: Weird (s)he didn't start here in the forums...
Logged
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: https://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: https://wiki.codeblocks.org/index.php?title=FAQ

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9694
Re: Debugging with Segger JLINK
« Reply #10 on: March 09, 2013, 04:22:33 pm »
Quote from: MortenMacFly on March 09, 2013, 01:48:16 pm
But still: Weird (s)he didn't start here in the forums...
...interesting to notice: There is a "debug locals" dialog implemented. Maybe worth a look...
Logged
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: https://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: https://wiki.codeblocks.org/index.php?title=FAQ

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13413
    • Travis build status
Re: Debugging with Segger JLINK
« Reply #11 on: March 09, 2013, 04:50:13 pm »
Quote from: MortenMacFly on March 09, 2013, 04:22:33 pm
...interesting to notice: There is a "debug locals" dialog implemented. Maybe worth a look...
It is not general and not reusing the wxPropGrid code...
Logged
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline dirk_1980

  • Multiple posting newcomer
  • *
  • Posts: 25
Re: Debugging with Segger JLINK
« Reply #12 on: March 11, 2013, 09:27:04 am »
I think he sad something like:
 
He forked C::B because You (CB)  didn't used his patches.

But i don't know what is right.

For me it would be the best if YOU could use his patches and Plugin directly inside CB.
Logged

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13413
    • Travis build status
Re: Debugging with Segger JLINK
« Reply #13 on: March 11, 2013, 05:37:50 pm »
Quote from: dirk_1980 on March 11, 2013, 09:27:04 am
For me it would be the best if YOU could use his patches and Plugin directly inside CB.
Some of them might get in, but not all.
Logged
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline Grad

  • Single posting newcomer
  • *
  • Posts: 9
Re: Debugging with Segger JLINK
« Reply #14 on: March 14, 2013, 04:01:32 pm »
Quote from: oBFusCATed on March 08, 2013, 03:50:42 pm
Quote from: dirk_1980 on March 08, 2013, 03:08:58 pm
Maybe the easiest way is to use the emIDE.
This is something new, someone has forked C::B instead of providing patches...

There are a lot forked code::blocks just for embedded fun.

http://www.emide.org
http://www.emblocks.org
http://www.imagecraft.com

I guess they all acknowledge the strength of code::blocks but are searching for a more embedded tailored  environment.

I think, it's a compliment.
Logged
Pages: [1] 2  All   Go Up
« previous next »