[ECOS] No RedBoot network after app start?

[ECOS] No RedBoot network after app start?

[Andre-John Mas]

Hi,

I have a RedBoot that replies to pings when it is waiting at the command prompt and the user hasn't started typing ( _rb_gets blocks until enter is pressed ). I then load my application:

  load -r -b 0x40000 app.bin
  go 0x40000

At this point my simple 'Hello World' displays its text. In the meantime the RedBoot stops replying to pings. My application is:

#include <stdio.h>
#include <stdlib.h>
#include <sys/types.h>

externC int  diag_printf( const char *fmt, ... );

int main( int argc, char * argv[] )
{
    diag_printf("Hello world 1\n");
    diag_printf("Hello world 2\n");
    diag_printf("Hello world 3\n");
    diag_printf("Hello world 4\n");
    diag_printf("Hello world 5\n");
}

Does anyone have any ideas what could be wrong. My RedBoot is set up to be a 'ROM Monitor'. We are using an Adder II (MPC852T) based board.

Andre


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] No RedBoot network after app start?

[Gary Thomas]

Andre-John Mas wrote:
> Hi,
> 
> I have a RedBoot that replies to pings when it is waiting at the command prompt and the user hasn't started typing ( _rb_gets blocks until enter is pressed ). I then load my application:
> 
>   load -r -b 0x40000 app.bin
>   go 0x40000
> 
> At this point my simple 'Hello World' displays its text. In the meantime the RedBoot stops replying to pings. My application is:
> 
> #include <stdio.h>
> #include <stdlib.h>
> #include <sys/types.h>
> 
> externC int  diag_printf( const char *fmt, ... );
> 
> int main( int argc, char * argv[] )
> {
>     diag_printf("Hello world 1\n");
>     diag_printf("Hello world 2\n");
>     diag_printf("Hello world 3\n");
>     diag_printf("Hello world 4\n");
>     diag_printf("Hello world 5\n");
> }
> 
> Does anyone have any ideas what could be wrong. My RedBoot is set up to be a 'ROM Monitor'. We are using an Adder II (MPC852T) based board.
> 

Once your application starts, RedBoot is no longer running.
If you've connected via telnet and started the program, then
RedBoot can print messages via the telnet session, but pings
will go unanswered (until the next message is printed).

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] No RedBoot network after app start?

[Gary Thomas]

Andre-John Mas wrote:
> I am a little confused then (I am new at this). I was 
 > under the impression that RedBoot needs to hang around,
 > so GDB can do its work. I have also been told that RedBoot
 > and the application needs separate IP addresses (supposedly
 > to avoid stack confusion), for this reason.

All true, but RedBoot is passive at this point.  It only
provides GDB services on demand (when you print or hit a
breakpoint, etc)

> 
> Our main issue is that we are unable to debug. We are using 
 > Eclipse to establish the GDB session, over ethernt. The image
 > gets uploaded by Eclipse, to port 9000 at the address of our card,
 > and we then reach the main function (we have break at main set).
 > At that point no more debugging is possible, which isn't very
 > useful. What I mean is that we can't step or display anything
 > further. At this point we just have to restart our card.

You get to the breakpoint at 'main' in your code?

Is your problem is that once you continue past this point, with
no other breakpoints set, you can't get back into GDB?  Can you
set other breakpoints, or single step?

> Andre
>  
>> From: Gary Thomas <gary@mlbassoc.com>
> 
>> Andre-John Mas wrote:
>>> Hi,
>>>
>>> I have a RedBoot that replies to pings when it is waiting at the command prompt and the user hasn't started typing ( _rb_gets blocks until enter is pressed ). I then load my application:
>>>
>>>   load -r -b 0x40000 app.bin
>>>   go 0x40000
>>>
>>> At this point my simple 'Hello World' displays its text. In the meantime the RedBoot stops replying to pings. My application is:
>>>
>>> #include <stdio.h>
>>> #include <stdlib.h>
>>> #include <sys/types.h>
>>>
>>> externC int  diag_printf( const char *fmt, ... );
>>>
>>> int main( int argc, char * argv[] )
>>> {
>>>     diag_printf("Hello world 1\n");
>>>     diag_printf("Hello world 2\n");
>>>     diag_printf("Hello world 3\n");
>>>     diag_printf("Hello world 4\n");
>>>     diag_printf("Hello world 5\n");
>>> }
>>>
>>> Does anyone have any ideas what could be wrong. My RedBoot is set up to be a 'ROM Monitor'. We are using an Adder II (MPC852T) based board.
>>>
>> Once your application starts, RedBoot is no longer running.
>> If you've connected via telnet and started the program, then
>> RedBoot can print messages via the telnet session, but pings
>> will go unanswered (until the next message is printed).
>>
>> -- 
>> ------------------------------------------------------------
>> Gary Thomas                 |  Consulting for the
>> MLB Associates              |    Embedded world
>> ------------------------------------------------------------
>>
>> -- 
>> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
>> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>>


-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss