p
This interface is unusual in that it requires loading firmware
into the controller before it may be used as a network link-level interface.
This is accomplished by opening a character special device,
and writing data to it.
It is also possible to do post-mortem debugging of firmware failures
by reading the local memory of the device.
.Pp
A program to load the image is provided in
.Pa /usr/src/new/np100 .
The sequence of commands would be:
.Bd -literal -offset indent
# ./npload np.image [/dev/np00]
# sleep 10
# ifconfig ix0 ...
.Ed
p Multiple control processes are allowed by opening separate minor devices; secondary interfaces are specified by shifting the interface number by 4 bits.
p The device also responds to commands passed through the driver by the following .Xr ioctl 2 Ns s : l -tag -width NPNETBOOT t Dv NPRESET kills off all active network processes. t Dv NPSTART begins execution of the board at the specified address (usually .Li 0x400 ) . t Dv NPNETBOOT downloads the image from a server on the network. [Contact .Tn MICOM-INTERLAN for details.] .El .Sh DIAGNOSTICS l -diag t np%d: Bad Maintenance command: %x! An invalid .Xr ioctl was passed to the np driver.
p t np%d: Panic NP100 bad buffer chain. An error occurred in an read or write operation causing it to run out of buffers before it finished the operation. This indicates a kernel failure rather than a device failure.
p t NP100 unit %d not found! A failure occurred during initialization, such that the unibus address expected for the board was found to be bad. Probably indicates hardware problems with the board, as do the following:
p d -filled -offset indent -compact t NP100 Unit %d timed out! t NP100 Unit %d Failed diagnostics! t Status from CSR0: %x. .Ed
p t "Panic from NP100 unit %d!" t "Panic Message: %s." An occurrence on the board was deemed serious enough to have the vax print it out.
p t NP100 unit #%d available! The board was successfully loaded and started.
p t np%d: Bad Req: %x. The board made a maintenance request to the vax that it did not understand.
p t np%d: No more room on Command Queue! The np driver allowed an internal resource to be exhausted. This should never happen. .El
p There are 110 other diagnostic messages that can be enabled by setting bits in a debugging mask. Consult the driver for details. .Sh SEE ALSO .Xr netintro 4 , .Xr inet 4 , .Xr arp 4 , .Xr ix 4 .Sh HISTORY The .Nm driver appeared in x 4.3 .