This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Optimal timing slice , Thread qn


On Wed, Jan 19, 2005 at 09:11:51AM -0800, steve smith wrote:
> my first question had nothing to do with the second one. I am sorry i
> didnt make it clear in the email.
> Regarding your comments: I am sure that the USART is receiving data as
> I have seen the waveform on the scope. I have configured the serial
> driver for the board.
> I dont understand why cyg_io_write should block. it simply write a
> character to USART without flow control. so if mutex is unlocked on
> the USART it shall never block.
> Anyhow the main question is that the cyg_io_write hogs all the cpu and
> the cyg_io_read inspite of getting data is not running. I print out
> the values after cyg_io_read and thats how I guess that its not
> running.

I think we need to see your code so we have a better idea what is
going on. Is that possible?

        Thanks
                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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]