Experimental Physics and
| |||||||||||||||||
|
The following is from an old copy of the "ei" driver, but it may still be relevant. As can be seen below, the "command field frozen" error message is from a software timeout that indicates the 82596 ethernet chip is unresponsive. /* ei82596End.c - END style Intel 82596 Ethernet network interface driver */ /* Copyright 1989-2000 Wind River Systems, Inc. */ #include "copyright_wrs.h" /* modification history -------------------- 02a,11jun00,ham removed reference to etherLib. 01z,27jan00,dat fixed use of NULL ... ... ... ... ... ... /******************************************************************************* * * ei82596Command - deliver a command to the 82596 via SCB * * This function causes the device to execute a command. It should be called * with interrupts from the device disabled. An error status is returned if * the command field does not return to zero, from a previous command, in a * reasonable amount of time. */ LOCAL STATUS ei82596Command(END_CTRL * pDrvCtrl, UINT16 cmd) { int loopy; SCB *pScb; pScb = pDrvCtrl->pScb; for(loopy = 0x8000; loopy--;) { if(pScb->scbCommand == 0) /* wait for cmd zero */ break; } if(loopy > 0) { pScb->scbCommand = cmd; /* fill in command */ sys596ChanAtn(pDrvCtrl->unit); /* channel attention */ return(OK); } else { logMsg("ei driver: command field frozen\n", 0, 0, 0, 0, 0, 0); return(ERROR); } } Mark Rivers wrote: Kevin,
| ||||||||||||||||
ANJ, 10 Aug 2010 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing · |