Console operation ERC32

Joel Sherrill joel.sherrill at OARcorp.com
Wed May 21 13:17:36 UTC 2008


Neil Mayes wrote:
> Not explicitly, I thought you did not have to when using printf.
>   
Yep.  This is not specific to RTEMS.  It is defined in
the Open Group specification and I am sure it has been
this way since the earliest days of UNIX.  stdin is buffered,
stderr is not.

http://www.opengroup.org/onlinepubs/007908799/xsh/stdin.html

--joel
> Regards,
> Neil
>
>   
>> -----Original Message-----
>> From: Chris Johns [mailto:chrisj at rtems.org]
>> Sent: 21 May 2008 00:33
>> To: Neil Mayes
>> Cc: rtems-users at rtems.org
>> Subject: Re: Console operation ERC32
>>
>> Neil Mayes wrote:
>>     
>>> Hi All,
>>>
>>> I have been using the ERC32, real HW, and have found some strange
>>> console effects, maybe someone could explain. I have built
>>>       
>> the BSP as
>>     
>>> released for version 4.8 and have a couple of tasks that
>>>       
>> sleep for 5,
>>     
>>> 10 and 15 seconds. They wake up and print the current time, however
>>> the complete line of text is not always printed until the 5 second
>>> sleep task wakes. I thought the console (as standard) was polled,
>>> however I would have thought it would have a poll time wrt
>>>       
>> baud rate?
>>     
>>> For the
>>> ERC32 there is no BSP support for changing the baud rate so I guess
>>> the poll time is not linked to the baud. The baud rate
>>>       
>> appears to be
>>     
>>> whatever the bootloader has configured it to be, in my case 38K4.
>>> Could we have a bug here with the way the polled console works?
>>>       
>> Did you flush stdout ?
>>
>> Regards
>> Chris
>>
>>
>>     
> _______________________________________________
> rtems-users mailing list
> rtems-users at rtems.com
> http://rtems.rtems.org/mailman/listinfo/rtems-users
>   


-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel.sherrill at OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
   Support Available             (256) 722-9985





More information about the users mailing list