[ECOS] Problems Running LED routine

Gary Thomas gary@mlbassoc.com
Mon Dec 6 11:15:00 GMT 2004

On Mon, 2004-12-06 at 00:52, leslie wrote:
> Hello,
> I posted this problem earlier on today. I realised the problem might
> not have to do with the program. Cuz in fact the major problem is, I
> can't even run a simple Helloworld in the example folder with the eCos
> library I built. I'll get the same line of string
> $T050f:180a0100;0d:ec7f0400;#b1 during execution.
> Could it have to do with my eCos library I built, missing packages? The
> following is the list of packages I used:
> C library
> Common error code support
> Dynamic Memory Allocation
> Generic Flash Memory support
> I/O Subsystem
> ISO C and POSIX Infra
> ISO C lib date/time function
> ISO C general utility function
> ISO C library internationalization
> ISO C library non-local jumps
> ISO C library signals
> ISO C library standard input/output function
> ISO C string function
> ISO environment startup/termination
> Infra
> eCos common HAL
> eCos kernel
> Could it be my Redboot not ported properly? But when I startup the
> board, Redboot is loaded successfully and I can execute the FIS
> commands, load program into the SRAM, etc.
> I have a program written in assembly which does everything from
> initialising the memory to the ports and testing the LEDs. It runs
> smoothly on the board. So I guess its not the hardware fault.

eCos programs are designed to run at a particular address
(either RAM or ROM, depending on the startup mode).  They
are not position independent.

Your problem is that when you issue the "go 0x1700" command,
the program was not loaded there (more likely, the starting
address will be 0x80040)

Gary Thomas <gary@mlbassoc.com>
MLB Associates

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

More information about the Ecos-discuss mailing list