EmbDev.net

Forum: ARM programming with GCC/GNU tools Problems debugging with Insight and WinARM


Author: fjrg76 (Guest)
Posted on:

Rate this post
0 useful
not useful
Hi, I'm newby in using ARM mpu, and I've compiled and uploaded (through
the ISP tool) my very first program under WinARM (great tool-chain).
However it's not posible to debug with Insight. I used the openOCD that
it's included. My target (Olimex LPC-E2129) can connect via jtag, but
these messages shows up, and I'm not able to debug:

Info:    arm7_9_common.c:265 arm7_9_add_breakpoint(): sw breakpoint
requested, b
ut software breakpoints not enabled
Info:    breakpoints.c:63 breakpoint_add(): can't add software
breakpoint, resou
rce not available
Info:    arm7_9_common.c:265 arm7_9_add_breakpoint(): sw breakpoint
requested, b
ut software breakpoints not enabled
Info:    breakpoints.c:63 breakpoint_add(): can't add software
breakpoint, resou
rce not available
Info:    arm7_9_common.c:265 arm7_9_add_breakpoint(): sw breakpoint
requested, b
ut software breakpoints not enabled
Info:    breakpoints.c:63 breakpoint_add(): can't add software
breakpoint, resou
rce not available
Error:   arm7_9_common.c:1906 arm7_9_write_memory(): memory write caused
data ab
ort
Error:   arm7_9_common.c:1906 arm7_9_write_memory(): memory write caused
data ab
ort
Info:    arm7_9_common.c:265 arm7_9_add_breakpoint(): sw breakpoint
requested, b
ut software breakpoints not enabled
Info:    breakpoints.c:63 breakpoint_add(): can't add software
breakpoint, resou
rce not available
Info:    arm7_9_common.c:265 arm7_9_add_breakpoint(): sw breakpoint
requested, b
ut software breakpoints not enabled
Info:    breakpoints.c:63 breakpoint_add(): can't add software
breakpoint, resou
rce not available


Does anyone has had the same problem and is able to help me?? Thanks in
advance. I'm from Mexico City

Author: Stefan (Guest)
Posted on:

Rate this post
0 useful
not useful

Author: fjrg76 (Guest)
Posted on:

Rate this post
0 useful
not useful
Thanks, that has resolved a part of my problem. When starting I disable
the breakpoints that Insight has set by default, in my case in main and
crt0. After that it jumps to the first instruction

Vectors:
b _start
...

and it suposes to jump to that label, but it doesn't. Instead it jumps
to the next instruction and crashes. But now I'm one step beyond this
afternoon. If I still don't get this thing to work, I'll bother you
again. Thanks again =)

Author: Jonathan Dumaresq (dumarjo)
Posted on:

Rate this post
0 useful
not useful
fjrg76 wrote:
> Thanks, that has resolved a part of my problem. When starting I disable
> the breakpoints that Insight has set by default, in my case in main and
> crt0. After that it jumps to the first instruction
>
> Vectors:
> b _start
> ...
>
> and it suposes to jump to that label, but it doesn't. Instead it jumps
> to the next instruction and crashes. But now I'm one step beyond this
> afternoon. If I still don't get this thing to work, I'll bother you
> again. Thanks again =)

this question should be ask in the openocd forum. you will have a better
chance to get the right answer,

but for now, could you put here your cfg files ?

Jonathan

Author: fjrg76 (Guest)
Posted on:

Rate this post
0 useful
not useful
Hi

This is my cfg file, it's for a LPC2129 uC. Removing by hand all the
breakpoints I'm able to debug step by step, but I cannot set any
breakpoints (it's anoying). I saw the command to force hw brakpoints,
however I don't know where tu put it =(. Also, in the console window of
Insight shows this

warning: (Internal error: pc 0x00 in read in psymtab, but not in
symtab.)

(pc may be other number than 0x00). I've tried with dwarf-2 and stabs
formats, but that message still remains. I read this is an error of GDB
(doesn't like 0x00 addresses).

Well this is the cfg file. Thanks =)

#daemon configuration
telnet_port 4444
gdb_port 3333

#interface
interface parport
parport_port 0x378
parport_cable wiggler
jtag_speed 0
#use combined on interfaces or targets that can't set TRST/SRST
separately
reset_config trst_and_srst srst_pulls_trst

#jtag scan chain
#format L IRC IRCM IDCODE (Length, IR Capture, IR Capture Mask, IDCODE)
jtag_device 4 0x1 0xf 0xe

#target configuration
daemon_startup reset
#target <type> <startup mode>
#target arm7tdmi <reset mode> <chainpos> <endianness> <variant>
target arm7tdmi little run_and_halt 0 arm7tdmi-s_r4
target_script 0 reset h2294_init.script
run_and_halt_time 0 30
working_area 0 0x40000000 0x40000 nobackup

#flash configuration
flash bank lpc2000 0x0 0x40000 0 0 lpc2000_v1 0 14765 calc_checksum
flash bank cfi 0x80000000 0x400000 2 2 0

Author: Jonathan Dumaresq (dumarjo)
Posted on:

Rate this post
0 useful
not useful
fjrg76 wrote:
> Hi
>
> breakpoints (it's anoying). I saw the command to force hw brakpoints,
> however I don't know where tu put it =(. Also, in the console window of
> Insight shows this

yes you need to provide this command if you debug in flash. if you use
eclipse you can put this in the gdb command tabs sheet.

>
> warning: (Internal error: pc 0x00 in read in psymtab, but not in
> symtab.)

you need to use dwarf-2. I don't know if this will correct your problem
but this is the output that you need.

>
> (pc may be other number than 0x00). I've tried with dwarf-2 and stabs
> formats, but that message still remains. I read this is an error of GDB
> (doesn't like 0x00 addresses).
>
> Well this is the cfg file. Thanks =)
>

what is the command that you send to gdb to init your debugging process
?

you should turn off the optimizator. -O0

Jonathan

Author: fjrg76 (Guest)
Posted on:

Rate this post
0 useful
not useful
Hi

I don't send any command to DBG, at least manually. The procedure is
this

1. Activate openocd in a command window
2. Double-click on arm-elf-insigth.exe in the WinARM directory structure

that's all

After that I reset the breakpoints by hand, and start debbuging (in
RAM). About the commands you told me I read something about them,
however I have no clue where to put them =(, remember i'm newbie in
using ARM uC. If you have time please tell me how to do so. Thanks =)





Jonathan Dumaresq wrote:
> fjrg76 wrote:
>> Hi
>>
>> breakpoints (it's anoying). I saw the command to force hw brakpoints,
>> however I don't know where tu put it =(. Also, in the console window of
>> Insight shows this
>
> yes you need to provide this command if you debug in flash. if you use
> eclipse you can put this in the gdb command tabs sheet.
>
>>
>> warning: (Internal error: pc 0x00 in read in psymtab, but not in
>> symtab.)
>
> you need to use dwarf-2. I don't know if this will correct your problem
> but this is the output that you need.
>
>>
>> (pc may be other number than 0x00). I've tried with dwarf-2 and stabs
>> formats, but that message still remains. I read this is an error of GDB
>> (doesn't like 0x00 addresses).
>>
>> Well this is the cfg file. Thanks =)
>>
>
> what is the command that you send to gdb to init your debugging process
> ?
>
> you should turn off the optimizator. -O0
>
> Jonathan

Author: Jonathan Dumaresq (dumarjo)
Posted on:

Rate this post
0 useful
not useful
fjrg76 wrote:
> Hi
>
> I don't send any command to DBG, at least manually. The procedure is
> this
>
> 1. Activate openocd in a command window
> 2. Double-click on arm-elf-insigth.exe in the WinARM directory structure
>
> that's all
>
> After that I reset the breakpoints by hand, and start debbuging (in
> RAM). About the commands you told me I read something about them,
> however I have no clue where to put them =(, remember i'm newbie in
> using ARM uC. If you have time please tell me how to do so. Thanks =)
>
>

you should read this document to know how to settup eclipse with arm
tools

http://gnuarm.alexthegeek.com/

Jonathan

Reply

Entering an e-mail address is optional. If you want to receive reply notifications by e-mail, please log in.

Rules — please read before posting

  • Post long source code as attachment, not in the text
  • Posting advertisements is forbidden.

Formatting options

  • [c]C code[/c]
  • [avrasm]AVR assembler code[/avrasm]
  • [code]code in other languages, ASCII drawings[/code]
  • [math]formula (LaTeX syntax)[/math]




Bild automatisch verkleinern, falls nötig
Note: the original post is older than 6 months. Please don't ask any new questions in this thread, but start a new one.