Re: [ECOS] Build eCos and Handle/Interrupts problems

["Carlos Eduardo dos Reis Rodrigues Sobrinho" <epilog at netc dot pt>]

BTW how can I do an application and store it in a certain address(for
example 0x4016969) in the flash so I do:
"go 0x4016969" or "gos 0x4016969" for instance and it copies all it has to
copy to SRAM and ran?

Thanks for the info in advance
Best regards Carlos Sobrinho

----- Original Message -----
From: Jonathan Larmour <jlarmour@redhat.com>
To: Carlos Eduardo dos Reis Rodrigues Sobrinho <epilog@netc.pt>
Cc: <ecos-discuss@sourceware.cygnus.com>
Sent: Wednesday, February 28, 2001 8:00 AM
Subject: Re: [ECOS] Build eCos and Handle/Interrupts problems


> > I also have some questions about interrupts and handles like how can I
make
> > a program with two threads, one that printf the cosine of a number and
the
> > other one (don't know if i need another one or if one thread is enough)
that
> > is only active when the push button of the AEB is pressed for
example.The
> > one near the reset button.
>
> You mean the interrupt button? That only delivers an interrupt. Even if
you
> configure it to be level triggered (rather than edge triggered) it would
> mean getting far too many interrupts while the button is depressed.
>
> If my understanding is wrong, then find out what interrupt the button is
> associated with, and write an application using the kernel C API that
> attaches an ISR and DSR to that interrupt. In the DSR, suspend the thread
> whatever way you like depending on what its doing (and whether it needs to
> finish it whenever the button is released).

Sorry to being so anoying but could you or anyone give me and example of
using and interrupt to call a thread
Thanks

>
> > BTW I'm trying to add a board to the AEB with two more chip of SRAM 512
> > Kbytes and one more chip of flash with 1 Mb along with the other three
that
> > the board bring (2 SRAM and one FLASH). It's going to be build using
almost
> > the same maner that the other ones use. My other question is: is it to
> > dificult to build the ecos OS for that board, I mean to use the RAM as a
> > whole and the FLASH as a whole?
>
> It should be fine although you will need to use the memory layout tool to
> redefine your memory layout obviously. And you will need to change the
> memory mappings (AEB_SRAM/AEB_BAD) in
> hal/arm/aeb/VERSION/include/hal_platform_setup.h

By memory layout do you mean "mlt_arm_aebC_rom.ldi" and "mlt_arm_aebC_rom.h"

> > Another BTW since I can't use the configtool in Win98 can I use it 100%
in
> > Win NT or win95?I also have RH6.2 in another partition, should I use it?
>
> Windows 95 will suffer from the some problems as Windows 98. NT is a
better
> bet, especially since you want to use the memory layout tool. If you don't
> mind, or prefer command line operation, Linux is also fine.

Now I'm using cygwin 1.1.8

> 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