[ECOS] how to run the program

[ECOS] how to run the program

[Andreas.Karlsson]

Hi,

I've been using gdb all the time but how do I download the program on my AEB
and run it without wanting to debug it? 

I want to see if the interrupts and timers work...

Re: [ECOS] how to run the program

[Jonathan Larmour]

Andreas.Karlsson@combitechsystems.com wrote:
> 
> I've been using gdb all the time but how do I download the program on my AEB
> and run it without wanting to debug it?
>
> I want to see if the interrupts and timers work...

You mean without using GDB as the loader? Since there isn't a port of
RedBoot or CygMon to the AEB then the only real alternative is to program
it into the flash. This means build eCos for "ROM" startup, and relink your
app against it. 

Then follow the same procedure you used to program the GDB stubs images
into flash.

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault

Re: [ECOS] how to run the program

[Jesper Skov]

>>>>> "Jonathan" == Jonathan Larmour <jlarmour@redhat.com> writes:

Jonathan> Then follow the same procedure you used to program the GDB
Jonathan> stubs images into flash.

Unfortunately it's a bit of a fiddle to program the flash on the
AEB. And as far as I remember it's not very big.

Anyway, you need to make a wrapper file which adds the necessary flash
identification magic - just as is done for the stubs, indeed. But you
need to change the name used in the wrapper, just as you have to add
build rules to execute the same commands as is used when producing the
stubs image.

See the CDL file - it contains all the details.

Jesper

RE: [ECOS] how to run the program

[Jesper Skov]

>>>>> "Andreas" ==   <Andreas.Karlsson@combitechsystems.com> writes:

Andreas> Which CDL file hal_arm_aeb.cdl?

Yes.

Andreas> This can't be the first time. Anyone out there who have done
Andreas> this and want to share experiences? Why inventing the wheel
Andreas> twice?

The eCos build system builds eCos. Application building/linkage
is done by whatever system the user is using. The output image from
that process needs further mangling to be installed in the AEB flash
(due to the AEB rom monitor).


Basically, the process is just more cumbersome than what is also
required for other platforms - on other platforms you may have to
convert the ELF object to binary for EPROM programming, or convert it
to SREC format for downloading and in-situ flash updating.

For the AEB you simply need to do more than just an objcopy. Indeed,
if you are lucky, someone has already written something to simplify
that process. But it is outside the scope of the eCos build system.

Jesper

RE: [ECOS] how to run the program

[Andreas.Karlsson]

Jonathan> Then follow the same procedure you used to program the GDB

Jonathan> stubs images into flash.



>Unfortunately it's a bit of a fiddle to program the flash on the

>AEB. And as far as I remember it's not very big.

256K I think.



>Anyway, you need to make a wrapper file which adds the necessary flash

>identification magic - just as is done for the stubs, indeed. But you

>need to change the name used in the wrapper, just as you have to add

>build rules to execute the same commands as is used when producing the

>stubs image.

>

>See the CDL file - it contains all the details.



Which CDL file hal_arm_aeb.cdl? 

This can't be the first time. Anyone out there who have done this and want
to share experiences? Why inventing the wheel twice?