From: Manuel Borchers <manuel@matronix.de>
To: Ecos Discuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] printf problem
Date: Tue, 01 Jun 2010 16:56:00 -0000 [thread overview]
Message-ID: <1275411398.2516.57.camel@netxaccos> (raw)
In-Reply-To: <1275389544.2516.22.camel@netxaccos>
Am Dienstag, den 01.06.2010, 12:52 +0200 schrieb Manuel Borchers:
> Am Dienstag, den 01.06.2010, 10:49 +0200 schrieb Manuel Borchers:
> > They are in the resulting application. At least lookup and write are
> > working, because that's what I used to test my serial drivers in the
> > first place.
> >
> > I need to write some simple tests to see if set/get and read are
> > working. Will do that later.
>
> I did just that. get_conf works, using set_conf I am able to change the
> baudrate on the fly and read also is able to read chars from the
> terminal.
>
> The driver seems to be okay. So I guess it's something related to the
> stdio streams. Any pointers for me to look at?
>
Thanks to Sergei, again, and a lot of single-stepping through the
StreamBuffer initialization, I found the problem. malloc couldn't
allocate space for the io_bufs of stdin and stdout.
That was caused by a wrong calculation for the heap-size in the
memory-layout definition. I fixed that and printf is working fine now.
Cheers and thanks to Sergei!
Manuel
--
Manuel Borchers
Web: http://www.matronix.de
eMail: manuel@matronix.de
--
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:[~2010-06-01 16:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 18:27 Manuel Borchers
[not found] ` <alpine.DEB.2.00.1005312056160.5904@sg-laptop>
2010-06-01 8:49 ` Manuel Borchers
2010-06-01 9:54 ` [ECOS] cyg_flash_mutex_lock vs. cyg_flash_lock AlanCC Wu (吳俊杰)
2010-06-01 10:52 ` [ECOS] printf problem Manuel Borchers
2010-06-01 16:56 ` Manuel Borchers [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-10 14:57 Tathagata Das
2006-08-10 15:02 ` Gary Thomas
2006-08-10 15:09 ` Tathagata Das
2004-08-30 15:52 [ECOS] Printf problem Aniket S Joshi
2004-08-30 14:10 Aniket S Joshi
2004-08-30 14:31 ` Andrew Lunn
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=1275411398.2516.57.camel@netxaccos \
--to=manuel@matronix.de \
--cc=ecos-discuss@ecos.sourceware.org \
/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).