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]

Re: strange serial (or scheduler?) problem.


Andreas Bürgel wrote:
> 
> I running "serialReader" as single thread connected to a minicom
> terminal program. Everything's working fine until I send characters to
> the device. If I don't send characters to the device for a few seconds,
> the device crashes and gdb looses the connection. I don't know if it
> crashes in the meantime or while receiving the first character after the
> break.
> 
> If I let the "dumbWork" thread run while this test, everything works
> stable.

With the thread priorities you give, I can't see how serialReader would
ever run if dumbWork runs, because it is at a higher priority in a tight
for loop.

Have you tried enabling assertions? Do this by enabling CYG_INFRA_DEBUG.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
Come to the Red Hat TechWorld open source conference in Brussels!
Keynotes, techie talks and exhibitions    http://www.redhat-techworld.com/


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