From: "Lambrecht Jürgen" <J.Lambrecht@TELEVIC.com>
To: "Jesper K. Pedersen" <linux@famped.dk>
Cc: "ecos-discuss@ecos.sourceware.org" <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] AT91SAM7S256 problem with test/example twothreads
Date: Tue, 19 Jun 2012 20:18:00 -0000 [thread overview]
Message-ID: <4FE0DE86.2030003@televic.com> (raw)
In-Reply-To: <20120619151658.2b387e48@io.solnet>
On 06/19/2012 03:16 PM, Jesper K. Pedersen wrote:
> On Sun, 17 Jun 2012 16:43:02 +0200
> "Jesper K. Pedersen"<linux@famped.dk> wrote:
>
>> I am at my wits end getting the twothreads example working on my
>> Olimex P256 board (AT91SAM7S256 based).
>>
>> Calling the cyg_mutex_init does not return. Also I notice that the
>> call to the printf line before the call to cyg_mutex_init prints
>> extremely slow on my terminal.
>>
>> I have set the default console up to tty0 going to ser0. This part
>> works fine with my other software running on the board (normal
>> expected transmission speed).
>>
>> Are there any "gotcha'" involving threading on the AT91 series
>> microcontrollers?
>>
> Problem was solved.
>
> For some reason if you put any output function (printf's) in the
> cyg_user_start the threading will hang.
>
> Removing all output will allow for threading and the example works as
> expected.
>
> I wonder if this is intended or if its a bug in the A91SAM7 eCos.
>
> Best regards
> JesperKP
>
I have lots of diag_printf's in my cyg_user_start() running on an AT91
ARM7 and a ARM9.
Maybe because you use printf?
Be carefull: Code running in initialization context runs with
interrupts disabled and the scheduler locked. Only after cyg_user_start,
the scheduler starts and resumes all threads.
Maybe (if I remember well; search the list for the diff between both
printfs) printf uses interrupts (to know when the hardware has sent a
byte), and diag_printf doesn't.
You must also realize that printf's can take a lot of CPU.
And no, it is certainly not intended or a bug in the ecos CVS code
(although I don't know the twothreads test): it is your bug ;-) .
Success,
Jürgen
--
Jürgen Lambrecht
R&D Associate
Tel: +32 (0)51 303045 Fax: +32 (0)51 310670
http://www.televic-rail.com
Televic Rail NV - Leo Bekaertlaan 1 - 8870 Izegem - Belgium
Company number 0825.539.581 - RPR Kortrijk
--
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:[~2012-06-19 20:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-17 14:43 Jesper K. Pedersen
2012-06-19 13:17 ` Jesper K. Pedersen
2012-06-19 20:18 ` Lambrecht Jürgen [this message]
2012-06-20 5:38 ` Jesper K. Pedersen
2012-06-20 9:54 ` Lambrecht Jürgen
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=4FE0DE86.2030003@televic.com \
--to=j.lambrecht@televic.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=linux@famped.dk \
/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).