Home > Product > Robot control system > KEBA E-CPU-186B Network communication module

KEBA E-CPU-186B Network communication module

MVME177Bug is written largely in the “C” programming language, providing benefits of portability and maintainability. Where necessary, assembler has been used in the form of separately compiled modules containing only assembler code - no mixed language modules are used. Physically, 177Bug is contained in two 44-pin PLCC/CLCC EPROMs, providing 512KB (128K longwords) of storage. Both EPROMs are necessary regardless of how much space is actually occupied by the firmware, because of the 32-bit longword-oriented MC68060 memory bus architecture. The executable code is checksummed at every power-on or reset firmware entry, and the result (which includes a pre-calculated checksum contained in the EPROMs) is tested for an expected zero. Thus, users are cautioned against modification of the EPROMs unless re-checksum precautions are taken.

Autoboot

Autoboot is a software routine that is contained in the several 177Bug EPROMs to provide an independent mechanism for booting an operating system. This autoboot routine automatically scans for controllers and devices in a specified sequence until a valid bootable device containing a boot media is found, or the list is exhausted. If a valid bootable device is found, a boot from that device begins. The controller scanning sequence goes from the lowest controller Logical Unit Number (LUN) detected to the highest LUN detected.

Following this message

there is a delay to allow you an opportunity to abort the Autoboot process if you wish. Then the actual I/O begins: the program pointed to within the volume ID of the media specified loads into RAM and control passes to it. If, however, during this time you want to gain control without Autoboot, you can press the: ❏ BREAK key ❏ Software ABORT switch ❏ RESET switch Autoboot is controlled by parameters contained in the ENV command. These parameters allow: ❏ Selection of specific boot devices ❏ Selection of files ❏ Programming of the Boot delay Refer to the ENV command in the Commands Table for more details.