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: PowerPC FEC interrupt handler problem


Hi .
Thanks for your kind responce. I have one more doudbt

See When an interrupt comes the control should go to 0x500 location and then
it has to branch to the appropriate handler based on the interrupt.

I dont find any such code which is doing this . Please tell me how interrupt
handler registration is done here.
I saw the function  cyg_drv_interrupt_create

Which is creating an interrupt object but how this will be used when an
interrupt occurs.

What all parts of the code I need to change If I have to incorparate the
changes required for my board compared to viper board.

Thanks in anticipation

Khasim

----- Original Message -----
From: "Wolfgang Heppner" <hep@iis.fhg.de>
To: "Khasim" <khasim@iwavesystems.com>
Cc: "eCos-discuss" <ecos-discuss@sources.redhat.com>
Sent: Thursday, July 11, 2002 1:07 PM
Subject: Re: [ECOS] PowerPC FEC interrupt handler problem


> Khasim wrote:
> >
> > Greetings.
> >
> > I am porting ecos to Mpc860 based processor. I have built the TCP/IP
stack
> > and FEC driver. The FEC interrupt handler is not at all called when I
ping
> > from other system.
>
> When you are using your own hardware, you may have to adapt the FEC
> driver.
> The driver is currently written for the Viper board. Look in function
> fec_eth_init (file if_fec.c) for the section "// Reset PHY" and change
> the IOs appropriate to your hardware design (as a quick workaround).
>
> >
> > I am getting one more warning saying ESA unknown.Can any body say what
is
> > ESA why it is telling ESA unknown?
> >
>
> ESA is the Ethernet- (or MAC-) address (i think so). If the init
> function does not find a Flash configuration (= ESA unknown) it uses a
> default address. I have to fix this myself, but for now this
> configuration is working for me.
>
> > How exactly the FEC interrupt handler is called when an interrupt occurs
can
> > anybody explain.
> >
> > With regards.
> >
> > Khasim
> >
> > --
> > Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
> > and search the list archive: http://sources.redhat.com/ml/ecos-discuss
>
> --
> Wolfgang Heppner
>
> High Speed Kamerasysteme  - Abt. Bildsensorik (ESY-B)
> High Speed Camera Systems - Dept. Electronic Imaging (ESY-B)
>
> Fraunhofer
> Institut Integrierte Schaltungen
> Angewandte Elektronik
>
> Am Wolfsmantel 33
> 91058 Erlangen
> (Germany)
>
> Tel:   +49 (0) 9131 776 528
> Fax:   +49 (0) 9131 776 598
>
> email: hep@iis.fhg.de
> web:   http://www.iis.fhg.de
>
> --
> Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
> and search the list archive: http://sources.redhat.com/ml/ecos-discuss
>
>


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss


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