Commands
CSMIM-T1 Hardware Installation Guide 3-7
The status word “! ~XXXX~”, where XXXX are four hexadecimal digits,
decodes as follows:
8000 = Command complete
4000 = Chip is busy
2000 = Command completed without error
1000 = Command aborted by an abort command
800 = Late collision detected
400 = Carrier lost
200 = CTS lost
100 = DMA underrun
80 = Transmission deferred because link was busy
40 = Collision detected during interframe spacing
(SQE/Heartbeat detected)
20 = Excessive collisions
10 = Reserved
The lowest nibble (bits 3 to 0) are a count of collisions during this
transmission. For example:
~8802~ = Complete, Late collision, 2 collisions
~8841~ = Complete, Late Collision, SQE detected, 1 collision
The boot command display (using bfs) looks like this:
monitor:: boot
Enter boot file name[(ip) “oper.56.enet”,\
(mop) “OPER_56_ENET.SYS”]::
Requesting default boot file “OPER_56_ENET.SYS” for MOP/VMS\
loads and “oper.56.enet” for all other protocols.
Unanswered requests shown as ‘?’,transmission errors as ‘*’.
Requesting boot from 192.9.200.88 via Ethernet...
Booting BFS file using open delay of 8
Booting BFS file from 192.9.200.88
Header received OK. Received data blocks shown as ‘.’.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. .. . . . . . . . . . . ? . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. * . . . . . . . . . . . . . . . . . . . . . . . . . . . . * .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . ? . . . . . . . . . . . . . . . .
. . . . . . . . . . EOF