How to enable IP Forwarding in RTEMS

[mansoor]

Hi All
    How to enable IP forwarding in RTEMS

thanx in advance
Mansoor Ahamed Basheer


----- Original Message ----- 
From: "Ian Caddy" <ianc at microsol.iinet.net.au>
To: "Chris Xenophontos" <cxenophontos at hammers.com>
Cc: <rtems-users at rtems.com>
Sent: Wednesday, June 02, 2004 7:26 AM
Subject: Re: MCF5307C3 NE2000 Network Driver


> Hi Chris,
>
> We haven't worked directly with that board, but we use the 5307 and
> there are a couple of things that you need to check to make sure
> interrupts are working.
>
> I assume that you are talking about an external interrupt, is it setup
> for autovectoring?
>
> Also if you have a BDM, you can check how the IMR is set or cleared (bit
> 3 should be cleared) (it must be cleared for the interrupt to work, it
> always gets me, I am used to a bit being set in the IMR to get my
> interrupt, but not in this processor).
>
> You can also check the IPR (interrupt pending register) to see if the
> interrupt is pending (is bit 3 set?).  If it is, it is likely masked in
> the IMR.
>
> Also, you will need to check the value in IRQPAR which sets the IRQ3 to
> either level 3 or level 6 interrupts.  If IRQPAR bit 6 is cleared, then
> it is a level 3 interrupt and the info I gave you above is correct.  If
> it is set, then it is a level 6 interrupt and you must look at different
> bits in the IMR and IPR and the level 6 autovector must be filled in.
>
> I hope this helps.
>
> regards,
>
> Ian Caddy
>
>
>
> Chris Xenophontos wrote:
>
> > This is going back a few years, but has any further progress has been
made
> > with D. Fiddes’ NE2000/DM9008 network driver for the Coldfire 5307?
> >
> > I’m referring to the one at:
> > http://sca.uwaterloo.ca/www.calm.hw.ac.uk/davidf/coldfire/rtems.htm
> >
> > We have taken the existing sbc5307/network directory, integrated it into
a
> > BSP (RTEMS 4.6.0) for the MCF5307C3 Development board, built it, etc.
Upon
> > initialization, (no bootp), we can observe the following:
> >
> > -driver attach is successful
> > -rtems_interrupt_attach returns successful
> > -tx, rx daemons initialize, and wait for events
> > -ARP request is seen on the network, with expected mac and Ethernet
> > addresses.
> >
> > It appears that the ISR (attached to IRQ3) never gets called.
> >
> > We’ve checked IRQ3 with an oscilloscope, which is seen to go low
(active),
> > sometime after the ARP request, and stays low, meaning that it is still
> > masked(?)
> >
> > Has any more progress been made on this network driver?  Any help would
be
> > greatly appreciated.
> >
> >
> > Thanks
> > Chris Xenophontos
> > cxenophontos at hammers.com
> >
> >