Console problem update

[Etienne Fortin]

I use rtems_interrupt_catch().

And outputting characters works. At least, for little amount of human
readable characters on the console.

Etienne


-----Message d'origine-----
De : Joel Sherrill <joel at OARcorp.com> [mailto:joel.sherrill at OARcorp.com]

Envoyé : 4 novembre, 2004 15:21
À : Etienne Fortin
Cc : rtems-users at rtems.com
Objet : Re: Console problem update


Etienne Fortin wrote:
> Hello all, its me again, the console guy :)
> 
> Little update for the ones that have an interest, or wish to help me 
> on that matter.

Is your interrupt an RTEMS ISR or a raw one directly connected to 
hardware?  If you do not go through the RTEMS ISR wrapper, you will
NEVER schedule out of an interrupt.

Also are you sure you are geting the serial port interrupts?

> I tricked RTEMS to release the semaphore at each clock tick to make 
> sure the semaphore was the problem. And surprise surprise! It still 
> hang in the idle thread!!!!!!!!!
> 
> Theory: My task/scheduler/... config is fu***d up. Anyone here thinks 
> it can be possible? For what I know of the problem so far, it seems 
> that as soon as the idle thread is entered, no other thread ever gets 
> executed... Really seems a config problem to me...
> 
> Idea someone?
> 
> Etienne Fortin
> Sensio
> 


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