Disk I/O Via 167Bug Commands; Ioi (Input/Output Inquiry); Iop (Physical I/O To Disk); Iot (I/O Teach) - Motorola MVME167 Series Installation Manual

Disk I/O via 167Bug Commands

These following 167Bug commands are provided for disk I/O.
Detailed instructions for their use are found in the Debugging
Package for Motorola 68K CISC CPUs User's Manual. When a
command is issued to a particular controller LUN and device LUN,
these LUNs are remembered by 167Bug so that the next disk
command defaults to use the same controller and device.

IOI (Input/Output Inquiry)

This command is used to probe the system for all possible
CLUN/DLUN combinations and display inquiry data for devices
which support it. The device descriptor table only has space for 16
device descriptors; with the IOI command, you can view the table
and clear it if necessary.

IOP (Physical I/O to Disk)

IOP allows you to read or write blocks of data, or to format the
specified device in a certain way. IOP creates a command packet
from the arguments you have specified, and then invokes the
proper system call function to carry out the operation.

IOT (I/O Teach)

IOT allows you to change any configurable parameters and
attributes of the device. In addition, it allows you to see the
controllers available in the system.

IOC (I/O Control)

IOC allows you to send command packets as defined by the
particular controller directly. IOC can also be used to look at the
resultant device packet after using the IOP command.

BO (Bootstrap Operating System)

BO reads an operating system or control program from the
specified device into memory, and then transfers control to it.
Disk I/O Support
4-15
4