Eclipse Debug: Why looking for compile errors????

Development Boards MicroMod
1

Hi!

I am (since 1 month! in my free time) trying to debug my hardware (AT91SAM7X256 cpu) with ARM-USB-JTAG from Olimex. I can load the bin file into flash via this hardware. When i try to debug, using Eclipse, i get the following result:

Using E:/Program/yagarto/bin/arm-elf-gdb.exe

and Eclipse:

Debug perspective, Debug window:

  • Start OpenOCD [Program]

E:\Program\openocd-2007re128\bin\openocd-ftd2xx.exe

  • C OneMoreTime [Embedded debug (Native)]

E:\Program\yagarto\bin\arm-elf-gdb.exe (2007-03-08 11:20)

Debug perspective, Console window:

target remote localhost:3333

0x00200c4c in ?? ()

monitor soft_reset_halt

monitor arm7_9 force_hw_bkpts enable

symbol-file F:/ARMdev/workspace/OneMoreTime/main.out

thbreak main

Hardware assisted breakpoint 1 at 0x168: file main.c, line 112.

continue

Progress view shows:

Launching (10%)

OneMoreTime…:Searching for compile errors in OneMoreTime

WHY LOOKING FOR COMPILE ERRORS??? And keeping on for ever…

Can someone PLEASE give me an idea where i should start looking for the reason?

Best regards

Nils

2

Hello,

I have the same problem too

My config file:

#define our ports
telnet_port 4444
gdb_port 3333

#commands specific to the Amontec JTAGKey
interface ft2232
ft2232_device_desc "Olimex OpenOCD JTAG A"
ft2232_layout olimex-jtag
ft2232_vid_pid 0x15BA 0x0003
#jtag_speed 2
jtag_speed 100

jtag_nsrst_delay 500
jtag_ntrst_delay 500

#reset_config <signals> [combination] [trst_type] [srst_type]
reset_config srst_only srst_pulls_trst

#jtag_device <IR length> <IR capture> <IR mask> <IDCODE instruction>
jtag_device 4 0x1 0xf 0xe

#daemon_startup <'attach'|'reset'>
daemon_startup reset

#target <type> <endianess> <reset_mode> <jtag#> [variant]
target arm7tdmi little run_and_init 0 arm7tdmi_r4
#target arm7tdmi little run_and_halt 0 arm7tdmi

#run_and_halt_time <target#> <time_in_ms>
run_and_halt_time 0 30

My Debuger commands:

target  remote  localhost:3333
monitor  soft_reset_halt
monitor  arm7_9  force_hw_bkpts  enable
symbol-file  main.out
thbreak  main
continue

Have anybody a idea to solve the problem?

Thanks!

Helmut

3

This is how my system is set up, everythig an adaption of James Lynch

tutorial for Yagarto!

In Initialize:

target remote localhost:3333

In Run:

monitor reset

monitor sleep 500

monitor soft_reset_halt

monitor poll

monitor wait_halt

monitor arm7_9 force_hw_bkpts enable

symbol-file F:/ARMdev/WorkSpaceSF4G/SmartFront4G/main.out

thbreak main

load

continue

In configfile for programming: (at91sam7X256-armusbocd-flash-program.cfg)

#define our ports

telnet_port 4444

gdb_port 3333

#commands specific to the Olimex OpenOCD JTAG A

interface ft2232

ft2232_device_desc “Olimex OpenOCD JTAG A”

ft2232_layout “olimex-jtag”

ft2232_vid_pid 0x15BA 0x0003

jtag_speed 1

jtag_nsrst_delay 500

jtag_ntrst_delay 500

#reset_config [combination] [trst_type] [srst_type]

reset_config srst_only

#jtag_device

jtag_device 4 0x1 0xf 0xe

#daemon_startup <‘attach’|‘reset’>

daemon_startup reset

#target <reset_mode> <jtag#> [variant]

#target arm7tdmi little run_and_init 0 arm7tdmi_r4

target arm7tdmi little run_and_init 0 arm7tdmi_r4

#man kan oxo pröva med reset_halt och reset_init ist f run_and_halt

#run_and_halt_time <target#> <time_in_ms>

run_and_halt_time 0 30

#commands below are specific to AT91SAM7 Flash Programming

//What is written above is also at91sam7X256-armusbocd-start.cfg

#target script specifies the flash programming script file

target_script 0 reset C:/TEMP/temp.ocd

#Working area <target#> <‘backup’ | ‘nobackup’>

working_area 0 0x40000000 0x4000 nobackup

#flash bank at91sam7 0 0 0 0 <target#>

flash bank at91sam7 0 0 0 0 0

Startup of OpenOCD:

E:\Program\openocd-2007re128\bin\openocd-ftd2xx.exe

E:\Program\openocd-2007re128\bin

-f at91sam7X256-armusbocd-start.cfg

4

I changed the following and the problem was solved

Run → Debug…

“GDB debugger:” to “C:\GCCFD\Gnuarm\bin\arm-elf-gdb.exe”

5

Hello,

Can you explain me where should I change?

"

Run → Debug…

“GDB debugger:” to “C:\GCCFD\Gnuarm\bin\arm-elf-gdb.exe”

"

Is it initialization commands or openocd-config file?

I have got the same problem with AT91SAM7X256 cpu.

Regards,

Peter

6

Get the newest James Lynch tutorial for Yagarto! from Atmel website and follow the instructions! I have never found a better tutorial!

Best regards

Nils