Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] debug using eclipse

I suppose it is time to ask the group.
Perhaps this is the same problem as in
https://bugs.eclipse.org/bugs/show_bug.cgi?id=268081 (quotting)

Have you tried to specify the "File System directory" that corresponds
to \\HDTV\\applications\\hello_arm (also make sure you did not check
"seach subfolders")? Have you removed Default path?
Usually this works for me.

BTW, what is \\HDTV ? Is this a project name?

2009/3/19 DUCHASSIN Frédéric <duchassin@xxxxxxxxx>:
> Hello,
>
> This is the part of GDB output which give me an error:
>
> &"continue\n"
> ~"\nProgram received signal "
>
> Program received signal ~"SIGSTOP, Stopped (signal).\n"
> SIGSTOP, Stopped (signal).
> ~"main () at src/main.c:136\n"
> main () at src/main.c:136
> ~"136\t    FAPI_GPIO_SetPinFunction( TEST_UART0_TX_PIN,
> TEST_UART0_TX_FUNCTION );\n"
> 136         FAPI_GPIO_SetPinFunction( TEST_UART0_TX_PIN,
> TEST_UART0_TX_FUNCTION );
> 384^done
> (gdb)
> 385-break-list
> 385^done,BreakpointTable={nr_rows="1",nr_cols="6",hdr=[{width="3",alignment=
> "-1",col_name="number",colhdr="Num"},{width="14",alignment="-1",col_name="ty
> pe",colhdr="Type"},{width="4",alignment="-1",col_name="disp",colhdr="Disp"},
> {width="3",alignment="-1",col_name="enabled",colhdr="Enb"},{width="10",align
> ment="-1",col_name="addr",colhdr="Address"},{width="40",alignment="2",col_na
> me="what",colhdr="What"}],body=[bkpt={number="1",type="breakpoint",disp="kee
> p",enabled="y",addr="0x21b01210",func="main",file="src/main.c",fullname="\\H
> DTV\\applications\\hello_arm/src/main.c",line="136",times="0"}]}
> (gdb)
> 386 info threads
> &"info threads\n"
> &"warning: RMT ERROR : failed to get remote thread list.\n"
> 386^done
> (gdb)
> 387-stack-info-depth
> 387^done,depth="1"
> (gdb)
> 388-stack-list-frames 0 1
> 388^done,stack=[frame={level="0",addr="0x21b01210",func="main",file="src/mai
> n.c",fullname="\\HDTV\\applications\\hello_arm/src/main.c",line="136"}]
> (gdb)
> 389-data-list-changed-registers
> 389^done,changed-registers=["3","4","5","11","12","13","14","15","25"]
> (gdb)
> 390 info sharedlibrary
> &"info sharedlibrary\n"
> ~"No shared libraries loaded at this time.\n"
> 390^done
> (gdb)
> 391-data-disassemble -f \\HDTV\\applications\\hello_arm/src/main.c -l 136 -n
> 100 -- 1
> &"mi_cmd_disassemble: Invalid filename.\n"
> 391^error,msg="mi_cmd_disassemble: Invalid filename."
> (gdb)
> 392-data-disassemble -s 0x21b01210 -e 0x21b01274 -- 0
> mi_cmd_disassemble: Invalid filename.
> 392^done,asm_insns=[{address="0x21b01210",func-name="main",offset="16",inst=
> "mov\tr3, #0\t;
> 0x0"},{address="0x21b01214",func-name="main",offset="20",inst="str\tr3,
> [r11,
> #-16]"},{address="0x21b01218",func-name="main",offset="24",inst="mov\tr3,
> #5\t;
> 0x5"},{address="0x21b0121c",func-name="main",offset="28",inst="str\tr3,
> [r11,
> #-16]"},{address="0x21b01220",func-name="main",offset="32",inst="ldr\tr3,
> [r11,
> #-16]"},{address="0x21b01224",func-name="main",offset="36",inst="add\tr3,
> r3, #1\t;
> 0x1"},{address="0x21b01228",func-name="main",offset="40",inst="str\tr3,
> [r11,
> #-16]"},{address="0x21b0122c",func-name="main",offset="44",inst="ldr\tr3,
> [r11,
> #-16]"},{address="0x21b01230",func-name="main",offset="48",inst="add\tr3,
> r3, #1\t;
> 0x1"},{address="0x21b01234",func-name="main",offset="52",inst="str\tr3,
> [r11,
> #-16]"},{address="0x21b01238",func-name="main",offset="56",inst="mov\tr3,
> #10\t;
> 0xa"},{address="0x21b0123c",func-name="main",offset="60",inst="str\tr3,
> [r11,
> #-16]"},{address="0x21b01240",func-name="main",offset="64",inst="mov\tr3,
> #0\t;
> 0x0"},{address="0x21b01244",func-name="main",offset="68",inst="mov\tr0,
> r3"},{address="0x21b01248",func-name="main",offset="72",inst="ldmib\tsp,
> {r11, sp,
> pc}"},{address="0x21b0124c",func-name="main",offset="76",inst="mov\tr12,
> sp"},{address="0x21b01250",func-name="main",offset="80",inst="stmdb\tsp!,
> {r11, r12, lr,
> pc}"},{address="0x21b01254",func-name="main",offset="84",inst="sub\tr11,
> r12, #4\t;
> 0x4"},{address="0x21b01258",func-name="main",offset="88",inst="sub\tsp, sp,
> #104\t;
> 0x68"},{address="0x21b0125c",func-name="main",offset="92",inst="bl\t0x21b012
> 00
> <main>"},{address="0x21b01260",func-name="main",offset="96",inst="mov\tr3,
> r0"},{address="0x21b01264",func-name="main",offset="100",inst="str\tr3,
> [r11,
> #-24]"},{address="0x21b01268",func-name="main",offset="104",inst="mov\tr0,
> #33\t;
> 0x21"},{address="0x21b0126c",func-name="main",offset="108",inst="mov\tr1,
> #151\t;
> 0x97"},{address="0x21b01270",func-name="main",offset="112",inst="bl\t0x21b03
> 428 <FAPI_GPIO_SetPinFunction+88>"}]
> (gdb)
> 393-stack-list-arguments 0 0 0
> 393^done,stack-args=[frame={level="0",args=[]}]
> (gdb)
> 394-stack-list-locals 0
> 394^done,locals=[name="result",name="test_string",name="gpio_params",name="u
> art_index",name="conn0_rx_handle",name="conn0_tx_handle"]
> (gdb)
> 395 whatis result
> &"whatis result\n"
> ~"type = int32_t\n"
>
>
>
> I don't know why in path access there is / and \ ??? As you can see there is
> a problem in all path access !
> Have you an idea about path mapping i should write ? I do some test and
> nothing is working !
>
> Thanks in advance.
>
>
> -----Message d'origine-----
> De : Dmitry Smirnov [mailto:divis1969@xxxxxxxxx]
> Envoyé : mercredi 18 mars 2009 17:47
> À : DUCHASSIN Frédéric
> Objet : Re: [cdt-dev] debug using eclipse
>
> You need to configure the Source Lookup path of Debugger configuration
> (Source Tab).
> This is not trivial, again.
> I would recommend to remove the default paths added by CDT on creation.
> Then, check with CDT gdb console what is the name is reported by GDB as
> unknown.
> If this is relative path, try to add the workpace folder that is the root of
> your source.
> If you had compiled the project with cygwin, perhaps you need to add a "Path
> Mapping" with "/cygwing/c" mapped to "C:\"
>
> Also, I had noticed that Source Lookup mapping is not applied immediately on
> CDT 6.0M5. But it begins to work on the next debug session...
> Perhaps, this is not applicable to you, but you could try, JIC...
>
> 2009/3/18 DUCHASSIN Frédéric <duchassin@xxxxxxxxx>:
>>
>> Thank you very much for your help.
>> Now it's working using continue in "commands" of start tabulation.
>>
>> I have one other problem: debug is allowed on ASM only (on the left,
>> there is a window wich said "no source file" and a button "edit source
>> lookup path". And if i put my project path, i have always this message
>> .) Have you an idea please ?
>>
>>
>>
>> -----Message d'origine-----
>> De : Dmitry Smirnov [mailto:divis1969@xxxxxxxxx] Envoyé : mercredi 18
>> mars 2009 15:47 À : duchassin@xxxxxxxxx Objet : Re: [cdt-dev] debug
>> using eclipse
>>
>> You can use "help" command in GDB console to get additional info
>>
>> I suppose you should issue something like file <your_elf>
>> <some_of_yours_gdbinit_commands> target remote <your_host_port> load
>> break main continue
>>
>> Perhaps, you should not use "run", but use "continue"
>> Also, you can try to step through the code with "next" and check the
>> registers (especially PC) with "info r"
>>
>>
>> 2009/3/18 DUCHASSIN Frédéric <duchassin@xxxxxxxxx>:
>>>
>>>
>>>>I suppose TCL-related commands are for Insight only. Perhaps this is
>>> creation/modification of some UI items (like menus).
>>>>arm-elf-gdb does not understand it, of course. Don't worry.
>>>
>>> Yes i suppose it's insight configuration. (breakpoint at main and at
>>> exit)
>>>
>>>>BTW, perhaps your JTAG vendor is providing some Eclipse-oriented
>>>>tools
>>> (like Eclipse plugin).
>>>
>>> Unfotunately my vendor doesn't provide such tools.
>>>
>>>
>>> I tried using arm-elf-gdb using inline command:
>>> Can you explain me some basic fucntion of arm-elf-gdb to debug my
>>> hardware
>> ?
>>> (i already launch arm-elf-gdb and these inline commands:
>>> load
>>> run --> doesn't work and close my gdbserver.exe and told me : doesn't
>>> know how to run !
>>>
>>> How to set a breakpoint ( I try "break main" but nothing is writtien
>>> to my
>>> gdbserver.exe)
>>>
>>> How to init or restart ?
>>>
>>>
>>> Thanks in advance.
>>>
>>> Fred
>>>
>>> 2009/3/18 DUCHASSIN Frédéric <duchassin@xxxxxxxxx>:
>>>>
>>>>
>>>> Hello,
>>>>
>>>> In my gdbinit script this part is not accepted by eclipse : (as i
>>>> said i put this script in "Initialization commands" of "startup tab"
>>>> in configuration
>>>> debug)
>>>>
>>>>        ################################
>>>>        # Insight Tcl Variables        #
>>>>        ################################
>>>>        tk pref setd gdb/load/main 1
>>>>        tk pref setd gdb/load/exit 1
>>>>        tk pref setd gdb/load/gdbservertcp-runlist "1 1 0 1"
>>>>        tk pref setd gdb/load/gdbservertcp-hostname "127.0.0.1"
>>>>        tk pref setd gdb/load/gdbservertcp-portname 12345
>>>>        tk pref setd gdb/load/gdbservertcp-verbose 0
>>>>        tk pref setd gdb/load/remotetcp-runlist "1 1 0 1"
>>>>        tk pref setd gdb/load/remotetcp-hostname "127.0.0.1"
>>>>        tk pref setd gdb/load/remotetcp-portname 12345
>>>>        tk pref setd gdb/load/remotetcp-verbose 0
>>>>        tk WarningDlg
>>>>        tk set WarningDlg::ignore(signal) 1
>>>>        tk pref setd
>>>> gdb/session/[pwd]/build/MB86H60/M-arm11-winarm/hello_arm-g.elf/run_l
>>>> o
>>>> a
>>>> d 1
>>>>        tk pref setd
>>>> gdb/session/[pwd]/build/MB86H60/M-arm11-winarm/hello_arm-g.elf/execu
>>>> t a ble "[pwd]/build/MB86H60/M-arm11-winarm/hello_arm-g.elf"
>>>>        tk pref setd
>>>> gdb/session/[pwd]/build/MB86H60/M-arm11-winarm/hello_arm-g.elf/run_a
>>>> t
>>>> t
>>>> ach 1
>>>>        tk pref setd
>>>> gdb/session/[pwd]/build/MB86H60/M-arm11-winarm/hello_arm-g.elf/run_r
>>>> u
>>>> n
>>>> 0
>>>>        tk pref setd
>>>> gdb/session/[pwd]/build/MB86H60/M-arm11-winarm/hello_arm-g.elf/all-k
>>>> e y s "run_cont run_run executable target_cmd run_attach run_load
>>>> args target"
>>>>
>>>>        tk pref setd
>>>> gdb/session/[pwd]/build/MB86H60/M-arm11-winarm/hello_arm-g.elf/targe
>>>> t
>>>> _
>>>> cmd
>>>> "remote 127.0.0.1:12345"
>>>>        tk pref setd
>>>> gdb/session/[pwd]/build/MB86H60/M-arm11-winarm/hello_arm-g.elf/targe
>>>> t
>>>> "gdbservertcp"
>>>>
>>>>
>>>> Maybe it's a mistake and i forget to include some library ? As i
>>>> said, the .gdbinit file seems not to be used by GDB hardware debugging.
>>>>
>>>>
>>>> In order to explain all:
>>>>
>>>> gdbserver.exe is an application between my jtag sensor and the
>>>> arm-elf-insight.exe. With the following command line, the
>>>> arm-elf-insight is weel configured whereas i can't configure the
>>>> same using arm-elf-gdb.exe on eclipse :
>>>>
>>>>        ###############Lance insight#######################
>>>>        c:\WinARM\utils\insight\bin\arm-elf-insight.exe
>>>> --directory=build\MB86H60\M-arm11-winarm
>>>> --command=build\MB86H60\M-arm11-winarm\.gdbinit --nx
>>>> "./build/MB86H60/M-arm11-winarm/hello_arm-g.elf"
>>>>
>>>>
>>>> Thanks to help me.
>>>>
>>>> fred
>>>>
>>>>
>>>> -----Message d'origine-----
>>>> De : cdt-dev-bounces@xxxxxxxxxxx
>>>> [mailto:cdt-dev-bounces@xxxxxxxxxxx]
>>>> De la part de Dmitry Smirnov Envoyé : mardi 17 mars 2009 17:45 À :
>>>> CDT General developers list.
>>>> Objet : Re: [cdt-dev] debug using eclipse
>>>>
>>>> I meant the console in Eclipse. You had already provided a output
>>>> from
>> it.
>>>> But you can also issue GDB commands here.
>>>>
>>>> Yes, this is not so trivial. I do agree this is a problem. But,
>>>> look, someone has written the bat and .gdbinit for you, isn't it?
>>>> What if you will need to write it from scratch?
>>>>
>>>> I'm also interested where 0x21b10d9 comes from. Typically, when you
>>>> connect to remote system it tells current PC. In our case, it is
>>>> 0x0000083. Perhaps we had connected too early?
>>>>
>>>> BTW, can you debug you program with arm-elf-gdb (console mode)
>>>> instead of insight? If so, can you try and provide the console log?
>>>>
>>>> 2009/3/17 DUCHASSIN Frédéric <duchassin@xxxxxxxxx>:
>>>>>
>>>>>
>>>>> OK but what do you mean by CDT GDB console ? Is it a dos console ?
>>>>> or is it included in eclipse ?
>>>>> The only thing io had to understand is why i'm going to read
>>>>> address 0x00000000 whereas I should read 0x21b10d90. (where this
>>>>> adress is given ?) Is it gdb-insight which give this adress ? and
>>>>> how gdb-insight find this address ?
>>>>>
>>>>> All i can say is that i give you the *.bat file and this bat file
>>>>> is working with only 3 step :
>>>>> - launch Execute.exe
>>>>> - lanuch Gdbserver.exe
>>>>> - and launch Gdb insight.
>>>>>
>>>>> And i would only replace Gdb-insight by Eclipse Debug.
>>>>>
>>>>> But it's not so easy !
>>>>>
>>>>>
>>>>>
>>>>> -----Message d'origine-----
>>>>> De : cdt-dev-bounces@xxxxxxxxxxx
>>>>> [mailto:cdt-dev-bounces@xxxxxxxxxxx]
>>>>> De la part de Dmitry Smirnov Envoyé : mardi 17 mars 2009 17:16 À :
>>>>> CDT General developers list.
>>>>> Objet : Re: [cdt-dev] debug using eclipse
>>>>>
>>>>> I suppose you can remove "target remote tcp:127.0.0.1:12345" either
>>>>> from commands or from Debugger configuration.
>>>>> Unfortunately, I do not sure when this connection will happen
>>>>> (before or after command execution). I would check this first.
>>>>> Moreover, you can try to remove both and enter this command in
>>>>> console when all other commands are executed (you can enter any GDB
>>>>> command in CDT GDB console).
>>>>> Perhaps this could give us some hints...
>>>>>
>>>>>
>>>>> 2009/3/17 DUCHASSIN Frédéric <duchassin@xxxxxxxxx>:
>>>>>> This is my .gdbinit file:
>>>>>>
>>>>>> set remote hardware-breakpoint-limit  5 set remote
>>>>>> hardware-breakpoint-packet on set remote hardware-watchpoint-limit
>>>>>> 2 set can-use-hw-watchpoints            2 set remote
>>>>>> memory-write-packet-size   8192 set remote memory-write-packet
>>>>>> fixed set remote memory-read-packet-size    8192 set remote
>>>>>> memory-read-packet         limit set remote X-packet off set
>>>>>> remote P-packet                   on set remote p-packet
>>>>>
>>>>>> off set remote Z-packet                   on set remote
>>>>>> set-register-packet        on set remoteaddresssize
>>>>>> 32 handle SIGALRM                        nopass handle SIGALRM
>>>>>
>>>>>> nostop handle SIGALRM                        noprint handle
>>>>>> SIGSTOP
>>>>>
>>>>>> stop handle SIGSTOP                        nopass handle SIGSTOP
>>>>>
>>>>>> stop ################################ # Only for GDB Version <
>>>>>> 6.7.1 # ################################ set download-write-size
>>>>>> 2048 target remote tcp:127.0.0.1:12345 set prompt (FME-Gdb) set
>>>>>> prompt
>>>>>> (FME-Gdb) ################################ # Insight Tcl Variables
>>>>>> # ################################ tk pref setd gdb/load/main 1 tk
>>>>>> pref setd gdb/load/exit 1 tk pref setd
>>>>>> gdb/load/gdbservertcp-runlist
>>>>>> "1 1 0 1"
>>>>>> tk pref setd gdb/load/gdbservertcp-hostname "127.0.0.1"
>>>>>> tk pref setd gdb/load/gdbservertcp-portname 12345 tk pref setd
>>>>>> gdb/load/gdbservertcp-verbose 0 tk pref setd
>>>>>> gdb/load/remotetcp-runlist "1 1 0 1"
>>>>>> tk pref setd gdb/load/remotetcp-hostname "127.0.0.1"
>>>>>> tk pref setd gdb/load/remotetcp-portname 12345 tk pref setd
>>>>>> gdb/load/remotetcp-verbose 0 tk WarningDlg tk set
>>>>>> WarningDlg::ignore(signal) 1 tk pref setd
>>>>>> gdb/session/[pwd]/build/MB86H60/M-arm11-winarm/hello_arm-g.elf/run
>>>>>> _
>>>>>> l
>>>>>> o
>>>>>> a
>>>>>> d 1 tk pref setd
>>>>>> gdb/session/[pwd]/build/MB86H60/M-arm11-winarm/hello_arm-g.elf/exe
>>>>>> c u t a ble "[pwd]/build/MB86H60/M-arm11-winarm/hello_arm-g.elf"
>>>>>> tk pref setd
>>>>>> gdb/session/[pwd]/build/MB86H60/M-arm11-winarm/hello_arm-g.elf/run
>>>>>> _
>>>>>> a
>>>>>> t
>>>>>> t
>>>>>> ach 1 tk pref setd
>>>>>> gdb/session/[pwd]/build/MB86H60/M-arm11-winarm/hello_arm-g.elf/run
>>>>>> _
>>>>>> r
>>>>>> u
>>>>>> n
>>>>>> 0 tk pref setd
>>>>>> gdb/session/[pwd]/build/MB86H60/M-arm11-winarm/hello_arm-g.elf/all
>>>>>> - k e y s "run_cont run_run executable target_cmd run_attach
>>>>>> run_load args target"
>>>>>> tk pref setd
>>>>>> gdb/session/[pwd]/build/MB86H60/M-arm11-winarm/hello_arm-g.elf/tar
>>>>>> g
>>>>>> e
>>>>>> t
>>>>>> _
>>>>>> cmd
>>>>>> "remote 127.0.0.1:12345"
>>>>>> tk pref setd
>>>>>> gdb/session/[pwd]/build/MB86H60/M-arm11-winarm/hello_arm-g.elf/tar
>>>>>> g
>>>>>> e
>>>>>> t
>>>>>> "gdbservertcp"
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> And this is the output of gdb:
>>>>>>
>>>>>> 767^done
>>>>>> (gdb)
>>>>>> 768-gdb-set width 0
>>>>>> 768^done
>>>>>> (gdb)
>>>>>> 769-gdb-set height 0
>>>>>> 769^done
>>>>>> (gdb)
>>>>>> 770-interpreter-exec console echo
>>>>>> 770^done
>>>>>> (gdb)
>>>>>> 771-gdb-show prompt
>>>>>> 771^done,value="(gdb) "
>>>>>> 772-gdb-set new-console on
>>>>>> (gdb)
>>>>>> &"No symbol \"new\" in current context.\n"
>>>>>> 772^error,msg="No symbol \"new\" in current context."
>>>>>> (gdb)
>>>>>> 773-target-select remote 127.0.0.1:12345 No symbol "new" in
>>>>>> current context.
>>>>>> 773^connected,thread-id="0",frame={addr="0x00000838",func="??",arg
>>>>>> s
>>>>>> =
>>>>>> [
>>>>>> ]
>>>>>> }
>>>>>> (gdb)
>>>>>> 774
>>>>>> &"\n"
>>>>>> 774^done
>>>>>> (gdb)
>>>>>> 775-target-download
>>>>>> C:\\HDTV\\applications\\hello_arm\\build\\MB86H60\\M-arm11-winarm\
>>>>>> \
>>>>>> h
>>>>>> e
>>>>>> l
>>>>>> lo_arm
>>>>>> -g.elf
>>>>>>
>>>>>> 775+download,{section=".text",section-size="105196",total-size="38
>>>>>> 775+9
>>>>>> 775+7
>>>>>> 775+5
>>>>>> 775+9
>>>>>> 775+87"}
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> With this configuration, i only write 191 bytes by 191 bytes when
>>>>>> *.elf is send.
>>>>>>
>>>>>>
>>>>>>
>>>>>> So i add this in the "startup tab", in "Initialization command":
>>>>>>
>>>>>> set remote hardware-breakpoint-limit  5 set remote
>>>>>> hardware-breakpoint-packet on set remote hardware-watchpoint-limit
>>>>>> 2 set can-use-hw-watchpoints            2 set remote
>>>>>> memory-write-packet-size   8192 set remote memory-write-packet
>>>>>> fixed set remote memory-read-packet-size    8192 set remote
>>>>>> memory-read-packet         limit set remote X-packet off set
>>>>>> remote P-packet                   on set remote p-packet
>>>>>
>>>>>> off set remote Z-packet                   on set remote
>>>>>> set-register-packet        on set remoteaddresssize
>>>>>> 32 handle SIGALRM                        nopass handle SIGALRM
>>>>>
>>>>>> nostop handle SIGALRM                        noprint handle
>>>>>> SIGSTOP
>>>>>
>>>>>> stop handle SIGSTOP                        nopass handle SIGSTOP
>>>>>
>>>>>> stop
>>>>>>
>>>>>> set download-write-size               2048 target remote
>>>>>> tcp:127.0.0.1:12345
>>>>>>
>>>>>> And now, i send 2048 bytes bt 2048 bytes.
>>>>>>
>>>>>> But after this step, the gdbserver is going to read address
>>>>>> 0x00000000 whereas in working version , it should read 0x21b10d90.
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>>
>>>>>>
>>>>>> -----Message d'origine-----
>>>>>> De : cdt-dev-bounces@xxxxxxxxxxx
>>>>>> [mailto:cdt-dev-bounces@xxxxxxxxxxx]
>>>>>> De la part de Dmitry Smirnov Envoyé : mardi 17 mars 2009 16:36 À :
>>>>>> CDT General developers list.
>>>>>> Objet : Re: [cdt-dev] debug using eclipse
>>>>>>
>>>>>> what was in your .gdbinit and how did you configured Initialization?
>>>>>>
>>>>>> Also, can you turn on 'verbose console mode' and provide the ouput
>>>>>> from eclipse GDB console?
>>>>>>
>>>>>>
>>>>>> 2009/3/17 DUCHASSIN Frédéric <duchassin@xxxxxxxxx>:
>>>>>>>
>>>>>>> No it's a specific hardware register.
>>>>>>> I only know that debug is working when i launch .bat i give on
>>>>>>> mailling list.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> -----Message d'origine-----
>>>>>>> De : cdt-dev-bounces@xxxxxxxxxxx
>>>>>>> [mailto:cdt-dev-bounces@xxxxxxxxxxx]
>>>>>>> De la part de Elena Laskavaia Envoyé : mardi 17 mars 2009 16:12 À :
>>>>>>> CDT General developers list.
>>>>>>> Objet : Re: [cdt-dev] debug using eclipse
>>>>>>>
>>>>>>> Is it $pc register?
>>>>>>>
>>>>>>> DUCHASSIN Frédéric wrote:
>>>>>>>>  Hello,
>>>>>>>>
>>>>>>>> Thanks for your help.
>>>>>>>>
>>>>>>>> I try to run manually Execute.exe and GdbServer.exe.
>>>>>>>> I've downloaded Eclipse GDB hardware debugging.
>>>>>>>> But it seems this plugin don't use .gdbinit script (since i have
>>>>>>>> put this script in "GDB init File"). So i put these commands in
>>>>>>>> Initialization command and it seems to work. All The code seems
>>>>>>>> to be send
>>>>>>> to my hardware.
>>>>>>>> (like in original application)
>>>>>>>>
>>>>>>>> But at the end of the download, my GdbServer tell me:
>>>>>>>> - Read at address 0x00000000  4 bytes
>>>>>>>>
>>>>>>>> Whereas it should be --> Read at address 0x21b10d90   4 bytes
>>>>>>>> (with original application using insight debugger).
>>>>>>>>
>>>>>>>> I don't know where is the problem but it wasn't working.
>>>>>>>> (read at address 0x00000000 is blocking)
>>>>>>>>
>>>>>>>> Is it possible to enter an offset ? or have you an idea about my
>>>>> problem.
>>>>>>>>
>>>>>>>> Thanks in advance.
>>>>>>>>
>>>>>>>> Fred
>>>>>>>>
>>>>>>>>
>>>>>>>> -----Message d'origine-----
>>>>>>>> De : cdt-dev-bounces@xxxxxxxxxxx
>>>>>>>> [mailto:cdt-dev-bounces@xxxxxxxxxxx]
>>>>>>>> De la part de Elena Laskavaia Envoyé : mardi 17 mars 2009 15:04 À :
>>>>>>>> CDT General developers list.
>>>>>>>> Objet : Re: [cdt-dev] debug using eclipse
>>>>>>>>
>>>>>>>> The other stuff (besides last debugger launch) you can put into
>>>>>>>> external launch configuration.
>>>>>>>>
>>>>>>>>
>>>>>>>> DUCHASSIN Frédéric wrote:
>>>>>>>>> Hello Everybody,
>>>>>>>>>
>>>>>>>>> I'm asking for help because i didn't find any help for using
>>>>>>>>> debug in Eclipse.
>>>>>>>>> I would like to use eclipse as debug IDE in my project.
>>>>>>>>> I'm using WinARM and it's working quite well as compiler in
> eclipse.
>>>>>>>>>
>>>>>>>>> Now i would use eclipse debug but it's not working whereas it's
>>>>>>>>> possible to debug using inline command.
>>>>>>>>> This is my .bat file which allow to DEBUG in inline command :
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Code :
>>>>>>>>>
>>>>>>>>>  rem ###############Config Execute + USB port
>>>>>>>>> 2####################### ..\..\env\bin\M-win32\execute.exe
>>>>>>>>> -verbose -dll=..\..\env\bin\M-win32\usbdbgport.dll
>>>>>>>>> -port=USB2:SYSFREQ=324000000:STARTBAUD=38400:BAUDRATE=3000000:R
>>>>>>>>> A M B A S E = 0x02004000 -reg=..\..\env\execute\ddr_init.rvs
>>>>>>>>> -quiet
>>>>>>>>>
>>>>>>>>>  rem ###############gdbserver + USB port
>>>>>>>>> 1####################### cmd /C start /high
>>>>>>>>> ..\..\env\bin\M-win32\gdbserver.exe -verbose
>>>>>>>>> -dll=..\..\env\bin\M-win32\jtagport.dll -port=USB1
>>>>>>>>> -IP=127.0.0.1:12345 -verbose
>>>>>>>>>
>>>>>>>>>  rem ###############Lance insight#######################
>>>>>>>>> c:\WinARM\utils\insight\bin\arm-elf-insight.exe
>>>>>>>>> --directory=build\MB86H60\M-arm11-winarm
>>>>>>>>> --command=build\MB86H60\M-arm11-winarm\.gdbinit --nx
>>>>>>>>> "./build/MB86H60/M-arm11-winarm/hello_arm-g.elf"
>>>>>>>>>
>>>>>>>>> /Code :
>>>>>>>>>
>>>>>>>>> So my question is: How can i integrate this debug in Eclipse ?
>>>>>>>>> Help me please !
>>>>>>>>>
>>>>>>>>> Thanks in advance.
>>>>>>>>>
>>>>>>>>> ++++
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Fred
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------
>>>>>>>>> -
>>>>>>>>> -
>>>>>>>>> -
>>>>>>>>> -
>>>>>>>>> -
>>>>>>>>> -
>>>>>>>>> -
>>>>>>>>> --
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> cdt-dev mailing list
>>>>>>>>> cdt-dev@xxxxxxxxxxx
>>>>>>>>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>>>>>>> _______________________________________________
>>>>>>>> cdt-dev mailing list
>>>>>>>> cdt-dev@xxxxxxxxxxx
>>>>>>>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> cdt-dev mailing list
>>>>>>>> cdt-dev@xxxxxxxxxxx
>>>>>>>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>>>>>> _______________________________________________
>>>>>>> cdt-dev mailing list
>>>>>>> cdt-dev@xxxxxxxxxxx
>>>>>>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> cdt-dev mailing list
>>>>>>> cdt-dev@xxxxxxxxxxx
>>>>>>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>>>>>>
>>>>>> _______________________________________________
>>>>>> cdt-dev mailing list
>>>>>> cdt-dev@xxxxxxxxxxx
>>>>>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>>>>>
>>>>>> _______________________________________________
>>>>>> cdt-dev mailing list
>>>>>> cdt-dev@xxxxxxxxxxx
>>>>>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>>>>>
>>>>> _______________________________________________
>>>>> cdt-dev mailing list
>>>>> cdt-dev@xxxxxxxxxxx
>>>>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>>>>
>>>>> _______________________________________________
>>>>> cdt-dev mailing list
>>>>> cdt-dev@xxxxxxxxxxx
>>>>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>>>>
>>>> _______________________________________________
>>>> cdt-dev mailing list
>>>> cdt-dev@xxxxxxxxxxx
>>>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>>>
>>>> _______________________________________________
>>>> cdt-dev mailing list
>>>> cdt-dev@xxxxxxxxxxx
>>>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>>>
>>> _______________________________________________
>>> cdt-dev mailing list
>>> cdt-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>>
>>> _______________________________________________
>>> cdt-dev mailing list
>>> cdt-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>>
>>
>>
>
>


Back to the top