Re: [ECOS] RedBoot

[Jonathan Larmour <jlarmour at redhat dot com>]

Anthony Massa wrote:
> 
> I found that I was having the same problems as the ones discussed in this
> post:
> http://sources.redhat.com/ml/ecos-discuss/2001-04/msg00006.html
> 
> After getting past that, I am now finding that my code loads over the
> Ethernet port.  However, when I run my code it prints out the networking
> information, such as "Network stack using..." then I get a message:
> 
> [New thread 1]
> 
> The board then seems to hang for a little while and then the program stops.
> I have breakpoints at cyg_start and cyg_user_start, however, neither of
> these get hit by the debugger.  The target disconnects from the debugger as
> well.

Well, this may indicate that it did hit the breakpoint, but has failed for
some other reason. Does it do the same thing when you don't set
breakpoints?

Also try enabling remote protocol debugging in GDB using "set remotedebug
1" (or in newer versions, "set debug remote 1"). 

Earlier you wrote:
> I have rebuilt ecos using the default configuration for the MBX template.  I
> rebuilt my application using the new ecos build.  I then downloaded the code
> and set a breakpoint at cyg_start().  I am still seeing the board hang when
> I run the code.  On the RedBoot serial port I get a $T... string GDB output
> message.  I can hit return when I am on the terminal connected to the serial
> port and I get the same $T string GDB message.  I'm really confused as to
> why this is hanging.

The $T string means that the target is reporting a signal and trying to
inform GDB - probably the breakpoint you hit. But if it's coming out the
serial port, whereas if GDB is connected over ethernet you won't see it.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine