public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: Carlos Eduardo dos Reis Rodrigues Sobrinho <epilog@netc.pt>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] Build eCos and Handle/Interrupts problems
Date: Wed, 28 Feb 2001 00:00:00 -0000	[thread overview]
Message-ID: <3A9CB01C.E0075686@redhat.com> (raw)
In-Reply-To: <00d501c0a158$d9137960$35bd12d4@netc.pt>

[ Ah this original has arrived ]

Carlos Eduardo dos Reis Rodrigues Sobrinho wrote:
> 
> 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).

> 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

> 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.

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

  reply	other threads:[~2001-02-28  0:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-27 23:34 Carlos Eduardo dos Reis Rodrigues Sobrinho
2001-02-28  0:00 ` Jonathan Larmour [this message]
2001-03-01  1:56   ` Carlos Eduardo dos Reis Rodrigues Sobrinho
2001-03-01  2:38     ` Wolfram Kattanek
  -- strict thread matches above, loose matches on Subject: below --
2001-02-27 23:29 [ECOS] Build eCos and Handle/Interrupts problems #2 Carlos Eduardo dos Reis Rodrigues Sobrinho
2001-02-27 23:38 ` Jonathan Larmour
2001-02-27 23:54   ` [ECOS] Build eCos and Handle/Interrupts problems Carlos Eduardo dos Reis Rodrigues Sobrinho
2001-02-28  0:05     ` Jonathan Larmour
2001-02-28 12:19       ` Carlos Eduardo dos Reis Rodrigues Sobrinho
2001-02-28  2:45     ` Hugo Tyson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3A9CB01C.E0075686@redhat.com \
    --to=jlarmour@redhat.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=epilog@netc.pt \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).