Help me: problem download DemoRTOS

Kernel
1

pinnor wrote on Friday, January 04, 2008:

Hi to all, after a lot of work I was able to compile correctly the DemoRTOS software on my system: mcb2300 board with lpc2368 + Eclipse + yagarto gcc tools + openocd + jtagkey, but i still have a problem.
I’am able to start the openocd server using this config file:

#daemon configuration
telnet_port 4444
gdb_port 3333

#interface
interface ft2232
ft2232_device_desc "Amontec JTAGkey A"
ft2232_layout jtagkey
ft2232_vid_pid 0x0403 0xcff8

jtag_nsrst_delay 100
jtag_speed  10
jtag_nsrst_delay 100

#jtag_speed 20
#jtag_nsrst_delay 500
#jtag_ntrst_delay 500
#jtag_speed 10
#jtag_nsrst_delay 100
#jtag_ntrst_delay 100

#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
run_and_halt_time 0 30

working_area 0 0x40000000 0x4000 nobackup

#flash configuration
#flash bank lpc2000 <base> <size> 0 0 <target#> <variant>
flash bank lpc2000 0x0 0x40000 0 0 0 lpc2000_v1 14765 calc_checksum

# For more information about the configuration files, take a look at:
# http://openfacts.berlios.de/index-en.phtml?title=Open+On-Chip+Debugger

and when i start it i get this message: (is it ok)
Info:    openocd.c:93 main(): Open On-Chip Debugger (2007-12-30 17:00 CET) svn: 247
Info:    openocd.c:94 main(): $URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
Info:    jtag.c:1291 jtag_examine_chain(): JTAG device found: 0x4f1f0f0f (Manufacturer: 0x787, Part: 0xf1f0, Version: 0x4)
Warning: embeddedice.c:175 embeddedice_build_reg_cache(): EmbeddedICE version 7 detected, EmbeddedICE handling might be broken
Warning: arm7_9_common.c:742 arm7_9_assert_reset(): srst resets test logic, too

But the problem happens when I try to enter in debug mode downloading the demo project…the process freeze on 57% progress, and these are the messages on my console:
Info:    openocd.c:93 main(): Open On-Chip Debugger (2007-12-30 17:00 CET) svn: 247
Info:    openocd.c:94 main(): $URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
Info:    jtag.c:1291 jtag_examine_chain(): JTAG device found: 0x4f1f0f0f (Manufacturer: 0x787, Part: 0xf1f0, Version: 0x4)
Warning: embeddedice.c:175 embeddedice_build_reg_cache(): EmbeddedICE version 7 detected, EmbeddedICE handling might be broken
Warning: arm7_9_common.c:742 arm7_9_assert_reset(): srst resets test logic, too

Can sameone help me?

Regards,
Renato

2

woops_ wrote on Friday, January 04, 2008:

I had a similar thing using USB but not jtagkey. I figured it was not actually programming the flash so got stuck.

Make sure you have clicked on the OpenOCD server in the debug area of the Eclipse window before starting the download.

I suggest opening up a telnet link to the jtag key and typing in the commands manually. This give you better knowledge of where the success stops.

3

pinnor wrote on Friday, January 04, 2008:

As I reported above, when i click on the OpenOCD server i get this message:
Info: openocd.c:93 main(): Open On-Chip Debugger (2007-12-30 17:00 CET) svn: 247
Info: openocd.c:94 main(): $URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
Info: jtag.c:1291 jtag_examine_chain(): JTAG device found: 0x4f1f0f0f (Manufacturer: 0x787, Part: 0xf1f0, Version: 0x4)
Warning: embeddedice.c:175 embeddedice_build_reg_cache(): EmbeddedICE version 7 detected, EmbeddedICE handling might be broken
Warning: arm7_9_common.c:742 arm7_9_assert_reset(): srst resets test logic, too

Is it all ok?

And after, when I try to enter in debug mode downloading the demo project…the process freeze on 57% progress, and these are the messages on my console:

No symbol "new" in current context.
target remote:3333
0x00000320 in vEMAC_ISR_Wrapper () at webserver/EMAC_ISR.c:34
34        portSAVE_CONTEXT();
monitor sleep 500
monitor arm7_9 force_hw_bkpts enable
monitor sleep 500
monitor soft_reset_halt
delete
monitor sleep 500
Breakpoint 1 at 0x430: file main.c, line 246.
b main
monitor sleep 500
c

What can I do? Is there a simple “Hello world” example for the Eclipse toolsoute useful to try the complete debug process?(compile, open server, download on tarfet and the watch variables o put breakpoint?
Now I’m going to make test with telnet…but?!..I hope!!!
Thanck you in advance,
Renato

4

davedoors wrote on Friday, January 04, 2008:

> Warning: embeddedice.c:175 embeddedice_build_reg_cache():
> EmbeddedICE version
> 7 detected, EmbeddedICE handling might be broken

I get a similar message and it makes no problems for me, but I am using a different interface.

> Warning: arm7_9_common.c:742 arm7_9_assert_reset(): srst
> resets test logic,

Reset issues could be the cause of your problems.  I tend to use a bit of trial and error there.

> No symbol "new" in current context.

Weird.

> target remote:3333
> 0x00000320 in vEMAC_ISR_Wrapper () at webserver/EMAC_ISR.c:34
> 34        portSAVE_CONTEXT();

Don’t know why this is showing up here.  Never seen anything like this unless this is just where the code was when the jtag halted the system.

> monitor sleep 500
> monitor arm7_9 force_hw_bkpts enable
> monitor sleep 500
> monitor soft_reset_halt
> delete
> monitor sleep 500
> Breakpoint 1 at 0x430: file main.c, line 246.
> b main
> monitor sleep 500
> c

This all looks good. Its writing out the commands to try and stop the cpu at main. I presume you have first programmed the flash correctly before running these commands. Were any warning generated during programing?

>
> What can I do? Is there a simple “Hello world” example for
> the Eclipse toolsoute
> useful to try the complete debug process?(compile, open
> server, download on
> tarfet and the watch variables o put breakpoint?
> Now I’m going to make test with telnet…but?!..I hope!!!

Telnet is a good way to get more information on what might be wrong. Also take a look at the sparkfun forums where there is a specific OpenOCD forum with lots of good advice.