MCF5272 Network Driver Problems - Solved with reservations?

[Joel Sherrill]

I have seen this behavior before -- initially with 80186 on-CPU
DMA LONG ago.  I recommend using a BSP specific IDLE task body
and configuring it in the CPU Table.

If we can nail this down to specific CPU model, we could
consider moing the IDLE thread over to libcpu but that's 
pretty drastic at first glance.

--joel

Brett Swimley wrote:
> 
> Hi All,
> 
> While stubbing in another task into my application, I discovered that just
> having another task active, even doing nothing but yielding the processor,
> causes my Fast Ethernet Controller driver to work correctly.
> 
> Previously, my Init task initialized the network and then exited.
> 
> Now, as a test, I have my Init task only yielding the processor after
> perfoming the network initialization.
> 
> for (;;) {
>         rtems_task_wake_after( RTEMS_YIELD_PROCESSOR );
> }
> 
> Would one still suspect my network driver or could this be indicative of an
> issue with the network code?
> 
> Regards,
> 
> Brett Swimley

-- 
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