From: Andrew Lunn <andrew@lunn.ch>
To: Jokke Ramberg <joakim.ramberg@ktc.se>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] porting ecos to at91sam7
Date: Fri, 17 Jun 2005 11:31:00 -0000 [thread overview]
Message-ID: <20050617113004.GB4982@lunn.ch> (raw)
In-Reply-To: <1118998149.3319.15.camel@localhost.localdomain>
On Fri, Jun 17, 2005 at 10:49:08AM +0200, Jokke Ramberg wrote:
> I am trying to port ecos to Atmels AT91sam7s64. I start out from
> AT91EB55 (from CVS 050504).
>
> Following the instructions in "embedded software development with ecos"
> and some debugging, have got to a stage where the I can build an example
> application from the two-threads example in ecos. I can load it and
> start.
>
> The two threads are started, I get the start messages from them, with
> the correct baudrate, on the serial port, the threads calls
> "cyg_thread_delay(20);", but this function never returns!
>
> I get the timer interrupts, the function "void Cyg_Counter::tick
> ( cyg_uint32 ticks )" is called regularly (I did not measure how often).
>
> What is more required for delay to return? Any defines or cdl stuff??
I suggest you run the standard tests and see what passes
fails. clocktruth can be used to make sure the clock is ticking at the
right rate etc.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2005-06-17 11:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-13 11:23 [ECOS] Serial and AT91 Edgar Grimberg
2005-06-13 12:16 ` Andrew Lunn
2005-06-13 14:08 ` Edgar Grimberg
2005-06-16 17:47 ` Edgar Grimberg
2005-06-17 8:49 ` [ECOS] porting ecos to at91sam7 Jokke Ramberg
2005-06-17 11:31 ` Andrew Lunn [this message]
2005-06-20 7:06 ` Jokke Ramberg
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=20050617113004.GB4982@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=joakim.ramberg@ktc.se \
/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).