1. Home
  2. Field-Programmable Gate Arrays
  3. Interrupt handler for Xilinx EMAC- URGENT!!

Interrupt handler for Xilinx EMAC- URGENT!!

hello

when i add a peripheral (plb EMAC in this case) from BSB to my embedded system (PPC405,ML300), do i have to explicitly write the drivers and, especially, an interrupt handler,and download them too? if yes, how do i add them?

further, in the drivers and examples provided by xilinx, where can i find out what the argument values are? (for example, an argument instance pointer[InstancePtr] appears in most functions. for EMAC, say, how do i find out what its value is? same thing with device id etc)

Or does xilinx EDK link the drivers too when the peripheral is added?

please help me out asap...

thanks

vikram

ps: i am new to this so please keep it simple....

Reply to
vikram
Loading thread data ...

Well..... EDK comes with OS-independent drivers for most of its peripherals. So from that standpoint, no you don't have to write the low-level driver. Now, you do have to write the "glue" logic to interface to this low-level driver. For each driver provided by EDK, there is an example of it being used. I'm not sure where they're at, but they do exist.

The drivers are enabled when you select them in the Software configuration portion of your EDK project. After you have enabled them, you build them by running libgen. This is performed from the command line by "make libs" or from the gui : Build software libraries.

After the libraries have been built, you can view all the source code to them since they'll be in:

// libsrc/.

HTH,

Mike

Reply to
morphiend

thanks for the prompt reply... will check it out.

regards vikram

Reply to
vikram

hi again...

how do i find out the unique device id of a device in a system? or do i have to assign IDs to all devices manually (if yes, how?)? also as regards instance pointers.... do i assign pointers or is it done by EDK?

thanks in advance vikram

Reply to
vikram

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.