RE: [ECOS] Problem with go command

[<ecos-dev at bcsw dot net>]

The FAQ for eCos is close to worthless.  I have long given up trying to use
it for anything useful.

The output is from GDB and is a 'T' packet that is used to signal an
exception.  Look in the __build_t_packet function of
packages/hal/common/current/src/hal_stub.c for more information.

If you can, you may want to run the program under GDB or Insight to see if
it can give you better information.

Note that you can even get this kind output for non-errors.  When I ran may
first eCos 'Hello' example on an IXP2400, I did not know of the GDB mangler
and it took me a while to learn that it was saying 'hello' over the
diagnostic channel.

The comments at the top of
.../packages/hal/common/current/src/generic-stub.c has more information
related to the GDB communications if you are interested.  The actual packet
output function that does much of the mangling is also in this file and is
called __process_packet().

   - Chip Boling

-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of Prabhat
Shrivastav
Sent: Tuesday, September 28, 2004 5:29 AM
To: ecos-discuss@ecos.sourceware.org
Cc: ecos-discuss@sources.redhat.com
Subject: [ECOS] Problem with go command

Hi all


I am loading my application on RAM via RedBoot .
I am unable to execute the my application with "go <application start
location>" command.
Or its application is executing but I have got some garbage on the console.
After executing the go command .

$T0a10:0000028c;0f:980ffd8d;#f0

Can any body tell me what is the problem?
Regards
Prabhat Shrivastav



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






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