Kontron Modular Computers GmbH rejects any liability for the correctness and
completeness of this manual as well as its suitability for any particular purpose.
This document contains information proprietary to Kontron Modular Computers GmbH. It may
not be copied or transmitted by any means, disclosed to others, or stored in any retrieval
system or media without the prior written consent of Kontron Modular Computers GmbH or one
of its authorized agents.
The information contained in this document is, to the best of our knowledge, entirely correct.
However, Kontron Modular Computers GmbH cannot accept liability for any inaccuracies or the
consequences thereof, or for any liability arising from the use or application of any circuit,
product, or example shown in this document.
Kontron Modular Computers GmbH reserves the right to change, modify, or improve this
document or the product described herein, as seen fit by Kontron Modular Computers GmbH
without further notice.
Trademarks
Kontron Modular Computers GmbH, the PEP logo and, if occurring in this manual, “CXM” are
trade marks owned by Kontron Modular Computers GmbH, Kaufbeuren (Germany). In addition, this document may include names, company logos and trademarks, which are registered
trademarks and, therefore, proprietary to their respective owners.
Environmental Protection Statement
This product has been manufactured to satisfy environmental protection requirements where
possible. Many of the components used (structural parts, printed circuit boards, connectors,
batteries, etc.) are capable of being recycled.
Final disposition of this product after its service life must be accomplished in accordance with
applicable country, state, or local laws or regulations.
This symbol indicates that the product described in this manual is in
compliance with all applied CE standards. Please refer also to the
section “Applied Standards” in this manual.
Caution, Electric Shock!
This symbol and title warn of hazards due to electrical shocks (> 60V)
when touching products or parts of them. Failure to observe the precautions indicated and/or prescribed by the law may endanger your
life/health and/or result in damage to your material.
Please refer also to the section “High Voltage Safety Instructions” on
the following page.
Warning, ESD Sensitive Device!
This symbol and title inform that electronic boards and their components are sensitive to static electricity. Therefore, care must be taken
during all handling operations and inspections of this product, in
order to ensure product integrity at all times.
Please read also the section “Special Handling and Unpacking
Instructions” on the following page.
Warning!
This symbol and title emphasize points which, if not fully understood
and taken into consideration by the reader, may endanger your health
and/or result in damage to your material.
Note...
This symbol and title emphasize aspects the reader should read
Your new Kontron product was developed and tested carefully to provide all features necessary
to ensure its compliance with electrical safety requirements. It was also designed for a long
fault-free life. However, the life expectancy of your product can be drastically reduced by
improper treatment during unpacking and installation. Therefore, in the interest of your own
safety and of the correct operation of your new Kontron product, you are requested to conform
with the following guidelines.
High Voltage Safety Instructions
Warning!
All operations on this device must be carried out by sufficiently skilled
personnel only.
Caution, Electric Shock!
Before installing your new Kontron product into a system always
ensure that the mains power is switched off. This applies also to the
installation of piggybacks.
Serious electrical shock hazards can exist during all installation,
repair and maintenance operations with this product. Therefore,
always unplug the power cable and any other cables which provide
external voltages before performing work.
Special Handling and Unpacking Instructions
ESD Sensitive Device!
Electronic boards and their components are sensitive to static electricity. Therefore, care must be taken during all handling operations
and inspections of this product, in order to ensure product integrity at
all times.
Do not handle this product out of its protective enclosure while it is not used for operational
purposes unless it is otherwise protected.
P R E L I M I N A R Y
Whenever possible, unpack or pack this product only at EOS/ESD safe work stations. Where
a safe work station is not guaranteed, it is important for the user to be electrically discharged
before touching the product with his/her hands or tools. This is most easily done by touching a
metal part of your system housing.
It is particularly important to observe standard anti-static precautions when changing piggybacks, ROM devices, jumper settings etc. If the product contains batteries for RTC or memory
back-up, ensure that the board is not placed on conductive surfaces, including anti-static plastics or sponges. They can cause short circuits and damage the batteries or conductive circuits
on the board.
In order to maintain Kontron’s product warranty, this product must not be altered or modified in
any way. Changes or modifications to the device, which are not explicitly approved by Kontron
Modular Computers GmbH and described in this manual or received from Kontron’s Technical
Support as a special handling instruction, will void your warranty.
This device should only be installed in or connected to systems that fulfill all necessary
technical and specific environmental requirements. This applies also to the operational
temperature range of the specific board version, which must not be exceeded. If batteries are
present their temperature restrictions must be taken into account.
In performing all necessary installation and application operations, please follow only the
instructions supplied by the present manual.
Keep all the original packaging material for future storage or warranty shipments. If it is
necessary to store or ship the board please re-pack it as nearly as possible in the manner in
which it was delivered. In the event that the original packaging material is not available for
storage or warranty shipments, packaging which complies with the standards indicated in
section 1.8 may be used to ensure the proper protection of this product.
Special care is necessary when handling or unpacking the product. Please, consult the special
handling and unpacking instruction on the previous page of this manual.
Kontron Modular Computers GmbH grants the original purchaser of Kontron’s products aTWO
YEAR
LIMITEDHARDWAREWARRANTYas described in the following. However, no other warranties
that may be granted or implied by anyone on behalf of Kontron are valid unless the consumer
has the express written consent of Kontron Modular Computers GmbH.
Kontron Modular Computers GmbH warrants their own products, excluding software, to be free
from manufacturing and material defects for a period of 24 consecutive months from the date
of purchase. This warranty is not transferable nor extendible to cover any other users or longterm storage of the product. It does not cover products which have been modified, altered or
repaired by any other party than Kontron Modular Computers GmbH or their authorized agents.
Furthermore, any product which has been, or is suspected of being damaged as a result of negligence, improper use, incorrect handling, servicing or maintenance, or which has been damaged as a result of excessive current/voltage or temperature, or which has had its serial
number(s), any other markings or parts thereof altered, defaced or removed will also be excluded from this warranty.
If the customer’s eligibility for warranty has not been voided, in the event of any claim, he may
return the product at the earliest possible convenience to the original place of purchase, together with a copy of the original document of purchase, a full description of the application the
product is used on and a description of the defect. Pack the product in such a way as to ensure
safe transportation (see our safety instructions).
Kontron provides for repair or replacement of any part, assembly or sub-assembly at their own
discretion, or to refund the original cost of purchase, if appropriate. In the event of repair, refunding or replacement of any part, the ownership of the removed or replaced parts reverts to
Kontron Modular Computers GmbH, and the remaining part of the original guarantee, or any
new guarantee to cover the repaired or replaced items, will be transferred to cover the new or
repaired items. Any extensions to the original guarantee are considered gestures of goodwill,
and will be defined in the “Repair Report” issued by Kontron with the repaired or replaced item.
Kontron Modular Computers GmbH will not accept liability for any further claims resulting
directly or indirectly from any warranty claim, other than the above specified repair,
replacement or refunding. In particular, all claims for damage to any system or process in which
the product was employed, or any loss incurred as a result of the product not functioning at any
given time, are excluded. The extent of Kontron Modular Computers GmbH liability to the
customer shall not exceed the original purchase price of the item for which the claim exists.
Kontron Modular Computers GmbH issues no warranty or representation, either explicit or
implicit, with respect to its products’ reliability, fitness, quality, marketability or ability to fulfil any
particular application or purpose. As a result, the products are sold “as is,” and the responsibility
to ensure their suitability for any given task remains that of the purchaser. In no event will
Kontron be liable for direct, indirect or consequential damages resulting from the use of our
hardware or software products, or documentation, even if Kontron were advised of the
possibility of such claims prior to the purchase of the product or during any period since the
date of its purchase.
P R E L I M I N A R Y
Please remember that no Kontron Modular Computers GmbH employee, dealer or agent is
authorized to make any modification or addition to the above specified terms, either verbally or
in any other form, written or electronically transmitted, without the company’s consent.
The VMP3 is a comprehensive computing platform which brings together the latest advances
in computing technology in a board designed for maximum performance, flexibility, and versatility within a rugged compact format.
The VMP3 is designed to accept the E²Brain™ module EB8541 as its core processor unit. This
module which is based on the MPC8541E PowerPC CPU – a highly integrated microprocessor
containing a PowerPC e500 core – provides a very comprehensive set of system and communications interfaces.
In addition to the standard VME system interface, the VMP3 incorporates a PCI extension interface for a full range of PCI peripherals, two Gigabit Ethernet interfaces, one Fast Ethernet
interface, high speed serial connectivity, an optional CompactFlash socket, and an IO extension interface which provides optional high speed serial as well as CAN interfacing, LPC interfacing, and an external I²C interface. For board logic and CPU test and debugging there is a
JTAG interface.
The VMP3 employs an OS-independent boot loader that enables the loading of any PowerPC
enabled operating system. This boot loader makes an update of the Flash contents and automatically downloads from Flash to SDRAM before booting the OS. For performance reasons
the OS is started from the DDR-SDRAM.
The power of the board is greatly enhanced by means of the PCI expansion connector which
makes it possible to cascade one or two additional VMP1-IO1 modules onto the board resulting
in a total package of up to 14HP. Both VMP1-IO1 modules may be used to carry PMC modules.
Given the wide range of PMC modules now available, this feature affords the user a very wide
range of options. Additionally, one can substitute a module designed to provide an even greater
range of PCI peripherals in place of either of the IO1 modules. These features enable, for example, the connection of the widest range of system I/O components such as various field busses and Ultra 2 SCSI, to name just a few. The complete range of expansion possibilities is thus
made available to the user by the VMP3.
The VMP3 is a VME PowerPC-based single-board computer specifically designed for use in
highly integrated platforms with solid mechanical interfacing for a wide range of industrial environment applications.
Some of the VMP3’s outstanding features are:
• PowerPC MPC8541E Power QUICC III (e500 core)
• 32 kB data cache
• 32 kB instruction cache
• 256 kB L2 cache
• up to 256 MB DDR-I-SDRAM, 64-bit, 264 MHz with ECC support
• up to 64 MB onboard Flash
• onboard PCI bus with expansion connector
• a Fast Ethernet interface
• two Gigabit Ethernet interfaces
• one serial terminal interface
• an IO extension interface for optional interfacing:
• up to five high speed serial I/O’s (RS232, RS422/485)
• a CAN interface
• an LPC interface
• an I²C interface
• optional CompactFlash socket (6 or 10 HP versions)
• programmable watchdog timer
• programmable hardware delay timer
• real-time clock
• optional versions for PCI expansion
• PCI-to-VME Bridge
• compliance with VITA VME-Specification ANSI / IEEE STD1014-1987 / IEC 821 and 297
The following system relevant information is general in nature but should still be considered
when developing applications using the VMP3.
Table 1-1: System Relevant Information
SUBJECTINFORMATION
System ConfigurationThe VMP3 operates onboard with a PCI system clock frequency of 33.
System ControllerThe VMP3 provides first slot detection, therefore it can be the system con-
troller.
Application InterfacingThe application interfacing to the VMP3 must comply with the specifications
set forth in this manual.
1.2.1System Configuration
System configuration is solely a function of the application, however, when implementing applications, precautions must be taken to ensure that the signals of the VMP3 are properly terminated in accordance with the specifications set forth in this manual. For this reason it will be
necessary for system integrators to ensure proper signal conditioning for their applications before interfacing with the VMP3. In addition, it is imperative that signal interference be kept to a
minimum.
1.2.2Operating Software
The VMP3 is supplied with appropriate operating system and board support software for board
operation.
1.3Board Diagrams
The following diagrams provide additional information concerning board functionality and component layout.
CANController Area Network interface (Philips SJA1000)
External Interfaces
Serial PortsTerminal and Console:
Two serial ports: RS232: TERM1 (Terminal on front panel)
TTL: TERM2 (Console on I/O expansion)
High Speed Serial:
Four ports, full modem: SER1 (on I/O expansion)
(Local Bus): SER2 (on I/O expansion)
(Support for RS485 direction control): SER3 (on I/O expansion)
: SER4 (on I/O expansion)
P R E L I M I N A R Y
JTAG/DebugJTAG/Debug interface for MPC8541E emulation probe
The following chapters present more detailed, board level information about the VMP3
E²Brain™ High Performance PowerPC Processor VME board whereby the board components
and their basic functionality are discussed in general.
2.1General Information
The VMP3 is comprised basically of the EB8541 E²Brain™ module and the EBC-VME3 carrier
board.
The EB8541 E²Brain™ module consists of the following:
• a Motorola MPC8541E Integrated Processor, Power QUICC III with a PPC e500 core
• a Board Process/Communications Controller (BPCC)
• System and Communications interfacing to the EBC-VME3 for:
•I²C bus
• LPC bus
• PCI bus
• CompactFlash (CF) interface
• Terminal and Console (T/C) serial interfacing
• Monitor and Control (M/C) interfacing
• Test and Programming (T/P) interfacing
• High Speed Serial (HSS) communications
• Communications Area Network (CAN) bus
• Fast Ethernet (FE)
• Gigabit Ethernet (TSE)
• Memory elements:
• Main memory DDR-I-SDRAM, soldered
• Soldered SRAM, backed-up using an auxiliary power line
• Soldered FLASH
• Serial EEPROM
• a BrainCAP™ heat sink for the EB8541
• Software
• Operating system
• Board support package
• Boot strap loader (NetBootLoader)
P R E L I M I N A R Y
The EB8541 carrier board, EBC-VME3, consists of the following:
• a Tundra Universe II PCI-to-VME bridge and VME-bus connector for VME-bus system
interfacing
• PHYs, magnetics, and connectors for Gigabit Ethernet interfacing
• magnetics and connector for Fast Ethernet interfacing
• a Terminal connector for serial interfacing
• a PCI expansion connector for PCI peripheral interfacing
• an I/O expansion connector for additional system and communications interfacing
• two test and programming connectors for JTAG and ISP logic interfacing
• switches and LEDs for Monitor and Control interfacing
• an optional CompactFlash socket for Type I and II CF cards
The following figure demonstrates the interfacing structure between the internal processing elements of the EBC-VME3 and other major VMP3 module components. Where system elements have common interfacing they are grouped into a block. Interfacing common to only one
element of a block is indicated with a direct connecting line. The interfacing lines are shown in
white where they are on board and in black for board external interfacing.
The following sections provide a very brief description of the interfacing between the E²Brain™
module and the EBC-VME3 board.
2.3.1System Interface
As the name implies, this interface provides the basic application connection functionality required to integrate the EB8541 E²Brain™ module as the high performance core of the VMP3.
The System Interface is realized using a 140-pin, HIROSE FX8C-140P-SV connector. The following table provides an overview of the signal types and a brief description of the interfacing
realized on this connector.
MONITOR AND CONTROL (M/C)Control signals for E²Brain™ module operation, configuration, and addi-
tional GPIO interfacing
TEST AND PROGRAMMING (T/P)JTAG/Debug signals for Emulator interfacing
TERMINAL AND
CONSOLE (T/C)
I2COne I2C standard interface for low speed, serial, inter-chip communica-
LPCOne LPC standard interface for (GP)IOs and simple memory interfacing
PCIOne PCI standard interface for PCI-bus interfacing
Two 2-wire serial interfaces:
RxD1/TxD1: Used by the boot loader during startup as a terminal interface;
once the system has been booted, is available as general purpose serial interface (Terminal)
RxD2/TxD2: general purpose serial interface (Console)
tions
2.3.2System Interface Extension
The System Interface Extension is realized using an 80-pin, HIROSE FX8C-80P-SV connector,
P R E L I M I N A R Y
and it is used to provide CPU architecture specific system interfaces.
In the case of the VMP3, a CompactFlash interface is made available on the System Interface
Extension.
Table 2-2:System Interface Extension Signal Types
SIGNAL TYPEDESCRIPTION
COMPACTFLASHOne CompactFlash interface (true IDE mode)
POWERVMP3 E²Brain™ module input power and grounds
2.3.3Communications Interface
The Communications Interface Connector is used to provide a set of standard communications
interfaces. In the case of the VMP3, there are three types of interfaces provided: four high
speed serial interfaces, one CAN interface, and one Fast Ethernet interface.
High Speed Serial (HSS)Four high speed serial interfaces
Fast EthernetOne Fast Ethernet 10/100 Mbps interface
CANOne standard CAN interface
2.3.4Communications Interface Extension
The Communications Interface Extension is realized using a 140-pin, HIROSE FX8C-140P-SV
connector. The following table provides an overview of the signal types and a brief description
of the interfacing realized on this connector.
Table 2-4:Communications Interface Extension Signal Type
This connector provides two three speed Ethernet (TSE1 and TSE2) interfaces (10/100/1000
mega-bit operation) for application communications interfacing. This is a dual RJ45 connector
with LEDs to indicate the status of the links.
The following figure and table provide pinout and signal information for this interface.
This connector provides a single Fast Ethernet interface (10/100 mega-bit operation) for application communications interfacing. This is a single RJ45 connector without link status LEDs.
Link status LEDs for this interface are located on the bottom side of the EBC-VME3 board.
The following figure and table provide pinout and signal information for this interface.
The VMP3 provides one serial interface for supporting a terminal port (TERM1). This interface
is realized using one of the MPC8541E on-chip UARTs, and as such provides only a two wire
interface without hardware handshake signals.
The connector J7 provides interfacing to the TERM1 port. This port can also be used as a low
speed solution for firmware updating. The signal levels on this connector are RS232 compliant.
The UART itself is a 16550 type UART.
The following figure and table provide pinout and signal information for the TERM1 interface.
This Test and Programming interface supports JTAG/Debug operations. This interface can be
used for connecting hardware emulators and debuggers (e.g. BDM, COP, …). It is comprised
of a set of ten signals whereby some are common to both interfaces and some are dedicated
to only one.
The following figure and tables provide pinout and signal information for this connector.
Figure 2-6: J8 - JTAG/Debug Connector
15
1
216
Table 2-9:Pinout of J8
SIGNALPINPINSIGNAL
TDO12NC
TDI34TRST
(pulled to +3.3V with 10 kΩ)56EMU_VCC
TCK78CHKSTP_IN (pulled to +3.3V with 10 kΩ)
TMS910NC
SRST1112NC
HRST1314NC
CHKSTP_OUT (pulled to +3.3V with 10 kΩ)15 16GND
Table 2-10: JTAG/Debug Signal Descriptions
TCKTest Clock in for JTAG and emulator/debugger
TDITest Data In for JTAG and emulator/debugger
TDOTest Data Out JTAG and emulator/debugger
TMSTest Mode Select, input for JTAG and emulator/debugger
TRSTTest Reset, input for JTAG and emulator/debugger
HRSTHard Reset, emulator/debugger hard reset input
The PCI Expansion connector provides the possibility to mount several transition boards above
the VMP3 for adding special functionality which is not provided on the VMP3 main board or on
the VME bus. All the PCI signals of the onboard PCI bus are routed to this connector, so that
a complete PCI bus is provided on this connector. In addition, almost the same number of
ground and power pins (3.3V and 5V) as are on a PCI or PMC connector are provided.
The PCI signalling voltage is 5V on this connector.
Page 50
Functional DescriptionVMP3
2.4.7J11 I/O Expansion Interface
The I/O Expansion connector provides additional capability for LPC, TERM2, M/C, CAN, and
HSS/UART interfacing. All signals on this connector are at TTL levels which means that they
will require additional signal conditioning prior to interfacing to VMP3 external devices.
Figure 2-8: J11 I/O Expansion Connector
72
2
711
Table 2-12: Pinout of J11
SIGNALPINPINSIGNALSIGNALPINPINSIGNAL
+BAT (see Note)12GNDSER4_RI3738SER4_RTS
MC434LPC_CLKSER3_CD3940SER4_DSR
LAD156+3V3SER3_RXD4142GND
+5V78LAD0SER3_CTS4344SER3_DTR
LAD3910LAD2SER3_RI4546SER3_TXD
PCI_RST1112GND+3V34748SER3_RTS
TXD21314LFRAMESER2_CD4950SER3_DSR
RXD21516+5VSER2_RXD5152GND
GND1718SERIRQGND5354SER2_DTR
CAN1_RX11920+3V3SER2_CTS5556SER2_TXD
CAN1_RX02122CAN1_TX1SER2_RI5758SER2_RTS
GND2324CAN1_TX0+5V5960SER2_DSR
P R E L I M I N A R Y
CAN2_RX12526+5VSER1_CD6162+3V3
CAN2_RX02728CAN2_TX1SER1_RXD6364SER1_DTR
GND2930CAN2_TX0GND6566SER1_TXD
SER4_CD3132GNDSER1_CTS6768SER1_RTS
SER4_RXD3334SER4_DTRSER1_RI6970SER1_DSR
SER4_CTS3536SER4_TXD+3V37172+5V
Note...
+BAT = 3.2V is derived from the 5V standby (is not regulated)
One Low Pin Count (LPC) interface for supporting simple IOs, simple static memory devices,
and IO controllers is available via the I/O Expansion interface.
The controller is completely integrated in the BPCC and offers a 8-bit data access port to devices which use LPC IO or memory access protocols. I/O and memory area are selected using
different address spaces.
The I/O address space is 64 kByte in size, whereas the memory area offers 16 MByte address
space. DMA is not supported by this interface.
In addition, a serial IRQ controller is also implemented in the BPCC, controlling and collecting
the serial LPC IRQs and converting and processing them to IRQs for the CPU.
The serial IRQ controller is realized according to the “Serialized IRQ Support for PCI Systems”
Specification, Rev. 6.0, Sept. 1, 1995
The following table provides a listing of the LPC interface signals and a brief description.
Table 2-13: LPC Interface Signal Description
SIGNALDESCRIPTION
LAD[0:3]Multiplexed Command, Address, and Data lines
LFRAME#Indicates start of a new cycle, termination of broken cycle
LPCCLK33 MHz clock
SERIRQSerialized IRQ, optional for peripherals that need interrupt
2.4.7.2Terminal Interface
A second serial interface for supporting a terminal port and a low speed communications interface (TERM2) for firmware updating is provided on this connector. This interface is realized using one of the MPC8541E on-chip UARTs, and, as such, provides only a two wire interface
without hardware handshake signals.
Note...
The corresponding serial signals on the VMP3 are TTL logic level signals.
Therefore, the transceivers for RS232 must be provided by the carrier board.
WARNING!
The signal level on the receive lines must not exceed 3.3V. Transients and signal levels higher than 3.3V may damage the VMP3 board.
To provide field bus support, there are signals available to implement a CAN bus interface
(Philips SJA 1000) via the J11 connector. The signals provided are at 5V TTL voltage levels
and must be adapted to the CAN bus levels through the use of appropriate CAN transceivers
on the carrier board.
Table 2-14: CAN Interface Signal Type and Description
SIGNALDESCRIPTION
CAN1_TX[0:1]Transmit data output driver
CAN1_RX[0:1]Receive data input channel
Note...
For more information concerning interfacing of the SJA 1000 to the CAN PHY,
refer to the Philips Application Note: AN97076 or the datasheet of the PCA
82C250 CAN controller interface.
2.4.7.4High Speed Serial Interfaces
Four, full modem, serial ports (SER1, 2, 3, and 4) are available on the I/O expansion connector.
Eight signals per port are provided to realize asynchronous high speed serial links interfaced
using dedicated controlling/handshaking. The VMP3 uses DUARTs (EXAR XR 16C2850 or
XR16L2750) which are 16550 compatible and provide hardware handshaking support for
RS485 operation.
Table 2-15: High Speed Serial Interface Signal Type and Description
SIGNALDESCRIPTION
SERn_TXDTransmit data output
SERn_RXDReceive data input
SERn_RTSRequest to send output
P R E L I M I N A R Y
SERn_CTSClear to send input
SERn_DTRData terminal ready output
SERn_CDCarrier detect input
SERn_DSRData set ready input
SERn_RIRing indicator input
Note...
All signals are available and supplied at 3.3V TTL levels. Further signal conditioning via appropriate transceivers on the carrier board is required to support
the respective communications standards.
The VMP3 has been designed for easy installation. However, the following standard precautions, installation procedures, and general information must be observed to ensure proper installation and to preclude damage to the board or injury to personnel.
3.1Hardware Installation
The product described in this manual can be installed in any available slot of a VMEbus system.
However, to function as a system controller it must be installed in slot 1 (far left).
3.1.1Safety Requirements
The module must be securely fastened to the carrier board using the mounting standoffs and
screws provided with the module.
In addition the following electrical hazard precautions must be observed.
Caution, Electric Shock Hazard!
Ensure that the system main power is removed prior to installing or removing
this board. Ensure that there are no other external voltages or signals being
applied to this board or other boards within the system. Failure to comply with
the above could endanger your life or health and may cause damage to this
board or other system components including process-side signal conditioning
equipment.
ESD Equipment!
This Kontron board contains electrostatic sensitive devices. Please observe
the following precautions to avoid damage to your board:
Discharge your clothing before touching the assembly. Tools must be discharged before use.
Do not touch any on board components, connector pins, or board conductive
circuits.
If working at an anti-static workbench with professional discharging equipment, ensure compliance with its usage when handling this product.
1. Ensure that the safety requirements indicated above are observed.
Warning!
Failure to comply with the instruction below may cause damage to the
board or result in improper system operation. Please refer to chapter 4 for
configuration information.
2. Ensure that the board is properly configured for operation before installing.
Note...
Care must be taken when applying the procedures below to ensure that
when the board is inserted it is not damaged through contact with other
boards in the system.
3. Install the board in the appropriate slot and ensure that it is properly seated in the backplane (front panel is flush with the rack front).
4. Fasten the front panel retaining screws.
5. Connect external interfacing cables to the board as required.
6. Ensure that the board and interfacing cables are properly secured.
3.1.3Removal Procedures
To remove the board proceed as follows:
1. Ensure that the safety requirements indicated above are observed.
Warning!
Care must be taken when applying the procedures below to ensure that
when the board is removed it is not damaged through contact with other
boards in the system. This applies in particular when complementary
P R E L I M I N A R Y
2. Disconnect any interfacing cables that may be connected to the board.
3. Loosen the front panel retaining screws.
boards are connected to the VMP3 via the J9 or J11 connectors. In this
case, both boards must be removed together as a unit and not separately.
4. Disengage the board from the backplane by pressing down on the front panel handle and
pull the board out of the slot.
5. Dispose of the module as required observing applicable environmental regulations governing the handling and disposition of this type of product.
If the removed board is to be returned to the manufacturer, ensure that
the packaging and ESD requirements are observed as specified by the
following sections of this guide:
• page xv, "Special Handling and Unpacking Instructions"
• page xvi, "General Instructions on Usage"
• section 1.8, "Applied Standards"
3.2Software Installation
Software installation is a function of the NetBootLoader and is described in chapter 5 of this
manual.
The Board Control registers may be accessed through byte-wide read and write operations.
4.2.1Board ID Register
The Board ID is used to identify the VMP3 in a E²Brain™ system. The value for the VMP3 is
0x45 which is factory set and cannot be changed.
Table 4-2: Board ID Register
REGISTER NAMEBOARD IDACCESS
ADDRESS0xFFFF A000R
BIT POSITION
CONTENTBID7BID6BID5BID4BID3BID2BID1BID0
DEFAULT01000101
76543210
MSB
4.2.2Software Compatibility ID
The Software Compatibility ID will signal to the software when differences in hardware require
different handling by the software. It starts with the value 0x00 and will be incremented with
each change in hardware (software sensitive only). This register is set at the factory and is for
use only by the boot strap loader “NetBootLoader” and the BSP software, and, as such, is not
user relevant.
This information is required in order to configure the PLL settings inside
1
the SOC.
0
1
P R E L I M I N A R Y
Page 66
ConfigurationVMP3
4.2.4Control Register
The Control register provides output interfacing to the application software. Assertion of the appropriate bits by the application software will cause the BPCC to generate outputs accordingly.
During startup, the state of Bit 0 is controlled by the NetBootLoader software. After the startup
is completed, the NetBootLoader sets Bit 0 to 1.
Table 4-5: Control Register
REGISTER NAMECONTROLACCESS
ADDRESS0xFFFF A003RW
BIT POSITION
CONTENTres.res.MC10S_RSTMC9res.MC11MC6
DEFAULTn/an/a0n/a0n/a0n/a
BITCONTENTSTATEDESCRIPTION
0MC6
1MC11
2reserved
3MC9
4S_RST
5MC10
76543210
MSB
Logical high on the MC6 output pin
0
Logical low on the MC6 output pin
1
Logical high on the MC11 output pin
0
Logical low on the MC11 output pin
1
0
1
Logical low on the MC9 output pin
0
High impedance (Z) on the MC9 output pin
1
no operation
0
Causes a complete system reset (S_RST) to be initiated
1
Logical low on the MC10 output pin
0
High impedance (Z) on the MC10 output pin
1
LSB
P R E L I M I N A R Y
6reserved
7reserved
0
1
0
1
4.2.5Event Register
The Event register provides status information about the Watchdog timer and various monitor
and control inputs. Depending on the type of event which occurs, interrupts may be generated
automatically which then require servicing. The application software is responsible for servicing
the interrupts as well as the other events, and, where applicable, the resetting of the event bits.
For information regarding the required hardware resources, refer to chapter “Interrupt
Mapping” in this manual. A logical ’1’ indicates that an interrupt has been asserted.
76543210
MSB
LSB
4.2.8Watchdog Control Register
The Watchdog Control register is the interface between applications and the operating system
for controlling the functioning of the Watchdog timer. There are four possible modes of operation involving the Watchdog timer:
• Timer only
• Reset
• Interrupt
• Dual stage
At power on the Watchdog is not enabled. If not required, it is not necessary to enable it. If required, the bits of the Watchdog Control register must be set according to application requirements. To operate the Watchdog, the mode and time period required must first be set and then
the Watchdog enabled. Once enabled, the Watchdog can only be disabled or the mode
changed by powering down and then up again. To prevent a Watchdog timeout the Watchdog
must be retriggered before timing out. This is done by writing a ’1’ to the WTR bit. In the event
a Watchdog timeout does occur, the WTE bit is set to ’1’. What transpires after this depends on
the mode selected. The four operational Watchdog timer modes are described as follows.
Timer only - In this mode the Watchdog is enabled using the required timeout period. Normally
the Watchdog is retriggered by writing a ’1’ to the WTR bit. In the event a timeout occurs, the
WTE bit is set to ’1’. This bit can then be polled by the application and handled accordingly. To
continue using the Watchdog, write a ’1’ to the WTE bit, and then retrigger the Watchdog using
WTR. The WTE bit retains its setting as long as no power down-up is done. Therefore, this bit
may be used to verify the status of the Watchdog.
Reset mode - This mode is used to force a hard reset in the event of a Watchdog timeout. To
be effective, the hard reset must not be masked or otherwise negated. In addition, the WTE bit
is not reset by the hard reset which makes it available if necessary to determine the status of
the Watchdog prior to the reset.
Interrupt mode - This mode causes the generation of an interrupt in the event of a Watchdog
timeout. The interrupt handling is a function of the application. If required the WTE bit can be
used to determine if a Watchdog timeout has occurred.
Dual stage mode - This a complex mode where in the event of a timeout two things occur: 1)
an interrupt is generated, and 2) the Watchdog is retriggered automatically. In the event a
second timeout occurs immediately following the first timeout, a hard reset will be generated.
If the Watchdog is retriggered normally, operation continues. The interrupt generated at the first
timeout is available to the application to handle the first timeout if required. As with all of the
The Board Revision Register provides the hardware (BRn) and logic (LRn) status of the board.
It is set at the factory and starts with the value 0x00 for the initial board prototypes and will be
incremented with each redesign / logic release.
The Serial Interrupt Pending 1 Register in conjunction with the Serial Interrupt Pending 2
Register is used to identify the source of the pending interrupt request. All serial interrupts are
coupled together to one CPU Interrupt (IRQ8). A logical 1 indicates that an interrupt has been
asserted.
Table 4-11: Serial Interrupt Pending 1 Register
REGISTER NAMESERIAL INTERRUPT PENDING 1ACCESS
ADDRESS0xFFFF A00CR
BIT POSITION
CONTENT
DEFAULT
76543210
MSB
SIRQ7SIRQ6SIRQ5SIRQ4SIRQ3SIRQ2SIRQ1SIRQ0
00000000
LSB
4.2.11Serial Interrupt Pending 2 Register
The Serial Interrupt Pending 2 Register in conjunction with the Serial Interrupt Pending 1
Register is used to identify the source of the pending interrupt request. All serial interrupts are
coupled together to one CPU Interrupt (IRQ8). A logical 1 indicates that an interrupt has been
asserted.
Table 4-12: Serial Interrupt Pending 2 Register
REGISTER NAMESERIAL INTERRUPT PENDING 2ACCESS
ADDRESS0xFFFF A00DR
BIT POSITION
CONTENT
DEFAULT
76543210
MSB
SIRQ15SIRQ14SIRQ13SIRQ12SIRQ11SIRQ10SIRQ9SIRQ8
00000000
LSB
4.2.12Serial Interrupt Mask 1 Register
The Serial Interrupt Mask 1 and 2 Registers enable the generation of a CPU interrupt. Writing
P R E L I M I N A R Y
a '1' to the bit “SIRQ_ENx” enables the generation of a CPU interrupt and enables the
corresponding bit in the Serial Interrupt Pending 1 and 2 Register.
The Serial Interrupt Mask Registers 1 and 2 enable the generation of a CPU interrupt. Writing
a '1' to the bit “SIRQ_ENx” enables the generation of a CPU interrupt and enables the
corresponding bit in the Serial Interrupt Pending Registers 1 and 2.
The Serial Interrupt Polarity 1 Register bits define the polarity of their corresponding serial
interrupt. A '1' written to the required bit position results in an active high sensitivity of the
corresponding interrupt and vice versa.
The Serial Interrupt Polarity 2 Register bits define the polarity of their corresponding serial
interrupt. A '1' written to the required bit position results in an active high sensitivity of the
corresponding interrupt and vice versa.
The register provides the capability to disable certain internal functions of the CPU and is
reserved for manufacturing use only.
Table 4-17: Device Disable Register
REGISTER NAMEDEVICE DISABLE REGISTERACCESS
ADDRESS0xFFFF A013R
BIT POSITION
CONTENT
DEFAULT
76543210
MSB
res.res.res.res.DIS_ENCRres.res.DIS_PCI
n/an/an/an/an/an/an/an/a
LSB
4.2.17Delay Timer Control/Status Register
The delay timer provides the capability to realize short, reliable delay times. The delay timer
control/status register provides three functions for operating the delay timer. The first function
is to indicate the timing intervals available, the second function is to trigger/reset the timer, and
the third is to indicate the time elapsed since the initial triggering or the last timer reset.
Writing a 0x00 and then reading the register will provide the timer intervals that are available
for application usage. In the case of the VMP3, all of the possible timer intervals are available.
Writing anything other than 0x00 to the register sets the timer to zero and restarts it, and sets
all of this register’s bits to 0. As time elaspes, interval bits are set accordingly and remain set
until the timer is retriggered.
For example, the timer is started, after 1 µs bit 0 is set to 1, after 5 µs bit 1 is set 1. This process
continues until all bits are set or the timer is retriggered. Once a bit is set it remains set until the
timer is again retriggered.
The following table indicate the address mapping of the UART A (SER1). For a more detailed
description please refer to the EXAR XR16C2850 or XR16C2750 DUART manual.
The following table indicate the address mapping of the UART B (SER2). For a more detailed
description please refer to the EXAR XR16C2850 or XR16C2750 DUART manual.
The following table indicate the address mapping of the UART C (SER3). For a more detailed
description please refer to the EXAR XR16C2850 or XR16C2750 DUART manual.
The following table indicate the address mapping of the UART D (SER4). For a more detailed
description please refer to the EXAR XR16C2850 or XR16C2750 DUART manual.
Access to the real-time clock (RTC) is effected via the I2C bus. The RTC uses address 0xD0.
For more detailed information please refer to the manuals for the ST - Microelectronics M41T81
and the Motorola MPC8541E (I2C bus).
When the RTC has once been stopped due to low voltage, it is
necessary to re-initialize the “Seconds” “Minutes” and “Hours”
registers before it will run again.
The Embedded Programmable Interrupt Controller of the MPC8541E (CPU) supports 12 external IRQs. The IRQ routing is listed below. All VME interrupts are accumulated to PCI_INTA.
Write access to the CompactFlash address area is only possible using word-wide (16-bit) write
commands.
Table 4-33: CompactFlash Register
REGISTERREAD/WRITEADDRESS
Data RegisterR/W0xFFFE 0000
Error RegisterR0xFFFE 8003
Feature RegisterW0xFFFE 8003
Sector Count RegisterR/W0xFFFE 8005
Sector Number RegisterR/W0xFFFE 8007
Cylinder Low RegisterR/W0xFFFE 8009
Cylinder High RegisterR/W0xFFFE 800B
Drive/Head RegisterR/W0xFFFE 800D
Status RegisterR0xFFFE 800F
Device Control RegisterW0xFFFE 801D
Alternate Status RegisterR0xFFFE 801D
Card Drive Address RegisterR0xFFFE 801F
4.7EEPROM
Access to the EEPROM is effected via the I2C bus controller of the MPC8541E and not the
CPM I2C channel. The EEPROM uses the I2C address 0xA0. Write protection is achieved by
installing a 0 ohm resistor (R22) and removing a 0 ohm resistor (R23). Default is unprotected.
For more detailed information please refer to the manuals for the MICROCHIP 24LC64 or Catalyst 24WC64, and the MOTOROLA MPC8555 (chapter 11, I2C Interface).
4.8Digital Temperature Sensor, LM75
Access to the onboard digital temperature sensor (DTS) is effected via the I2C bus controller
of the MPC8541E. The DTS uses the I2C address 0x90.
P R E L I M I N A R Y
For more detailed information please refer to the manuals for the National Semiconductor
LM75 and the MOTOROLA MPC8555 (chapter 11, I2C Interface).
4.9Ethernet PHY Addresses
The Gigabit Ethernet PHYs of the VMP3 are accessible via the MDIO interface of the
MPC8541. Their addresses are 0x01 for the PHY of the TSEC1 and 0x00 for the TSEC2. The
PHY of the FCC1 is accessible via the parallel port pins PD[18] (MDIO) and PD[17] (MDC) and
has the PHY address 0x04.
This E²Brain™ module is delivered with the NetBootLoader software already programmed into
the onboard soldered Flash memory. The NetBootLoader itself is a software utility which initializes the module for operation before turning control over to either an application or to an operator. This software also provides the capability to monitor and control the operation of the
NetBootLoader itself, display system status information, to program executable code and data
to the Flash memory, and to load and start application software.
To attain full operational capability, the VMP3 FLASH must be programmed by the user with
application software. Once the application has been programmed to Flash memory, the NetBootLoader will support the complete boot operation. The following chapters describe the functioning of the NetBootLoader and how to program the Flash memory.
Note...
The following description assumes a standard CPU board with appropriate
hardware. In the event such hardware is not available, disregard the text that
applies to the missing hardware and proceed as appropriate.
5.1General Operation
Upon power on or a system reset, the NetBootLoader is started. The CPU board is configured
for operation and control is either passed to an application or an operator. In the event a valid
application has been programmed into the Flash memory and no operator intervention takes
place, the application is copied from FLASH into SDRAM and control is passed to the application. If the NetBootLoader does not find a valid application or operator intervention has occurred, control is passed to the operator. The operator now has control to determine the system
status, make configuration changes, read or program the Flash memory, or to restart or shut
down the system.
The operator command interfacing with the NetBootLoader is accomplished either via the
TERM serial port or the Ethernet port FCC1 (FE). During the boot operation a command interpreter is started which allows the operator to input commands to the NetBootLoader. Prior to
interfacing via the Ethernet port FCC1 (FE), the port must be configured. This is done either via
the TERM port or via a dhcp/bootp server.
5.2NetBootLoader Interfaces
There are four possibilities to interface with the NetBootLoader:
• Via the MC1 (Abort) signal
• Via the TERM serial interface
• Via the SER0 serial interface
• Via the Ethernet port FCC1 (FE) interface
P R E L I M I N A R Y
Gaining access to the NetBootLoader is a function of the contents of the Flash memory and the
“BootWaitTime” setting. If there is not a valid application programmed into the Flash memory,
the boot operation automatically terminates after the module has been initialized and control is
passed to the command interpreter.
If there is a valid application in the Flash memory, the boot operation is delayed according to
the setting of the boot wait time, and the MC6 (LED1) output signal is alternately asserted indicating that the boot operation is in a wait state. During this time the operator may intervene
in the boot operation either by asserting the MC1 (Abort) signal, entering the “abort” command
via the TERM interface, or by performing a successful telnet login via the Ethernet port FCC1
(FE). If the operator does not intervene, the boot operation is continued after the boot wait time
has been exceeded.
5.2.1MC1 (Abort) Signal
The MC1 (Abort) signal is routed to the VMP3 from the carrier board via the System Interface
(CON1 connector) and, if made available from the carrier, provides the operator with the ability
to directly terminate the boot operation during the boot wait time which is indicated by the alternately asserted MC6 (LED1) signal. This is the sole purpose of the MC1 (Abort) signal during
the NetBootLoader operation.
5.2.2TERM Serial Interface
The TERM serial port, if realized on the carrier board, is used to provide direct operator interfacing to the NetBootLoader. As soon as the CPU board has been initialized this port is activated and the operator may input commands. During the boot wait time the operator may
terminate the boot operation and take control of the NetBootLoader. Once the boot wait time is
exceeded the command interpreter is normally deactivated and the boot process is continued.
If the NetBootLoader does not find a valid boot image, the boot process is discontinued and
system control is returned to the operator via the NetBootLoader.
The TERM serial interface may either be directly connected to a terminal device or may interface with a terminal emulator.
5.2.3SER0 Serial Interface
The SER0 serial port is used to provide the NetBootLoader with the ability to access Motorola
S-Records for programming an application to FLASH. No command interpreter is available for
this interface.
5.2.4Ethernet Port FCC1 (FE) Interface
The Ethernet port FCC1 (FE) provides the capability of remotely interfacing with the NetBootLoader. Prior to using this interface it is necessary to configure the Ethernet port settings. This
is accomplished via the TERM interface or a dhcp/bootp server. Once the port settings have
been configured, the remote operator has the same capabilities as with the TERM interface.
During the boot wait time the operator gains control of the NetBootLoader by performing a telnet login it via the Ethernet port FCC1 (FE). This causes the boot operation to be terminated
P R E L I M I N A R Y
and gives control to the remote operator.
In addition to the operator interface via this interface, the NetBootLoader can also use it for tftp
and ftp server accessing.
In addition to initializing the CPU board for operation and the loading and starting of applications, the NetBootLoader provides the following operator monitor and control functions:
• NetBootLoader control
• system status monitoring
•network accessing
• FLASH reading and programming operations
• Motorola S-Record acquisition
These functions are described in detail in the following chapters.
NOTE ...
The command title (CMD TITLE) is expressed in capital letters and is not the
same as the syntax of the command. The command syntax is always written
using small letters
5.3.1NetBootLoader Control
The NetBootLoader provides various functions for controlling the operation of the
NetBootLoader itself as well as the setting of operational parameters. The following table
provides an overview of available NetBootLoader control functions.
Table 5-1: NetBootLoader Control Commands
CMD TITLEALIASFUNCTIONREMARKS
ABORT-Terminate boot wait
BWBoot WaitSet or display BootWaitTime
CBLChange BootlineSet or display a bootlineApplies to a specific kernel
DHCP-Dynamically set Ethernet port
FCC1 (FE) parameters
HELP or ?-Display online HELP pages
LOGOUT-Terminate telnet session
NET-Manually set Ethernet port
FCC1 (FE) parameters
Requires that a dhcp or bootp server be
available in the same network as the VMP3
Must be set before attempting to use the
Ethernet port; see also the DHCP command
P R E L I M I N A R Y
PASSWDPasswordSet telnet passwordMust be set before attempting telnet login
PFPort FormatSet serial port parametersUsed for the TERM and SER0 ports
RSResetResets system
SCRIPT-Command scriptingContents are executed only during boot up
SQBoot SequenceSet or display boot sequenceDefines selection order of image booting
The NetBootLoader provides various functions for monitoring the overall status of the system
during the operation of the NetBootLoader. The following table provides an overview of available system status monitoring functions.
Table 5-2: System Status Monitoring Commands
CMD TITLEALIASFUNCTIONREMARKS
CHECK-Application validation; displays
information for each image
INFO-Display system information
MDMemory
Display
PCI-Display PCI device information
PING-Verify network status
VERVersionDisplay version number of
Display memory contentsApplies to all visible memory
NetBootLoader
Verifies validity of user image programmed
to FLASH
5.3.3Network Accessing
To support application development and operational requirements for various boot strategies,
the NetBootLoader provides several functions for gaining access to network services. These
functions include: access to dhcp/bootp servers, accessing tftp servers, and accessing ftp
servers.
At initial startup of the VMP3, only the NetBootLoader is installed in onboard FLASH. To support application development or remote boot capability, the NetBootLoader can provide networking interfacing via the Ethernet port FCC1 (FE).
To achieve this, certain network parameters must first be configured. This can be done manually via a terminal or dynamically via the network. The command DHCP makes it possible to
download such parameters and to configure the Ethernet port FCC1 (FE) for network opera-
P R E L I M I N A R Y
tion. Once the Ethernet port is configured, the commands TFTP and FTP are available to download bootable images or other files as required.
5.3.3.1dhcp/bootp Server Access
Use of this access method requires the availability of either a dhcp or bootp server in the same
network as the VMP3. The DHCP command causes the NetBootLoader to first attempt to establish contact with a DHCP server. If contact is not achieved, it then tries to contact a BootP
server. When contact is established, parameters required by the VMP3 are provided accordingly and the Ethernet port is configured and then made available for normal operation.
In the event the VMP3 is reset or cold started the configuration parameters set by the above
method are lost. Only if the parameters have been set by the NET command are they still available.
Prior to using the "dhcp" command, the IP address of the VMP3 must be set to
The NetBootLoader provides various functions for interfacing with either a tftp or ftp server.
The tftp server access is a simple method of acquiring a userimage from a remote source. Its
primary use is to download a single executable userimage from a given source. For example,
once an application has been programmed it would be possible to store it at a remote location
where it then would be available for remote booting of an VMP3 via the Ethernet port FCC1
(FE).
The ftp server commands provide various functions consistent with interfacing with such a
server.
The following table provides an overview of available tftp/ftp server functions.
Table 5-3: tftp/ftp Server Commands
CMD TITLEALIASFUNCTIONREMARKS
BYE-Terminate session with ftp server
CDChange
Directory
GET-Download a file from ftp serverOnly for executable applications.
LOGIN-Login to ftp server
LSList DirectoryList ftp server directoryLists contents of directory.
PUT-Upload a file to ftp serverData buffer is source.
PWDPrint Working
Directory
TFTP-Download a file from tftp server
Change ftp server directory
Data buffer is target.
Display current ftp server directoryLists name of directory
5.3.4FLASH Operation
The NetBootLoader provides various functions for performing operations with Flash memory.
The following table provides an overview of available FLASH operation functions.
Table 5-4: FLASH Operation Commands
CMD TITLEALIASFUNCTIONREMARKS
P R E L I M I N A R Y
CLONE-Program NetBootLoader to FLASHUses data buffer or socket as source
LFLoad FLASHProgram application to FLASHUses data buffer as source
SFStore FLASHReads FLASH to data bufferUses data buffer as target
The NetBootLoader provides one function for acquiring Motorola S-Records. The following table provides an overview of this function.
Table 5-5: Motorola S-Records Commands
CMD TITLEALIASFUNCTIONREMARKS
SLSLoadDownload Motorola S-RecordsUses data buffer as target
5.4Operating the NetBootLoader
5.4.1Initial Setup
The VMP3 is delivered with the NetBootLoader already installed in the onboard soldered
FLASH and is ready for operation. However, in order for the CPU board to be used in a system,
application software must be made available for use. This is accomplished by programming the
application also to the onboard soldered Flash memory where the NetBootLoader is located.
Upon initial power up the NetBootLoader is started automatically. As soon as the NetBootLoader has completed initialization of the CPU board, it checks to see if there is a valid application
programmed in FLASH and at the same time initiates a command interpreter which the operator can access either via the TERM or the Ethernet port FCC1 (FE) interfaces. If there is not a
valid application in memory, the NetBootLoader terminates the boot operation, and waits for operator intervention. As this is the case when the CPU board is first powered up, the operator
now has the opportunity to program an application.
Prior to programming an application it may be necessary to configure the NetBootLoader or
perform other functions depending on the user’s application development environment or application requirements. Once this has be accomplished and the application has been programmed, the CPU board is ready for operation.
The following chapters provide information on how to set up and operate the NetBootLoader
itself, initiation of the telnet interface, and how to program an application to FLASH.
5.4.2Accessing the NetBootLoader
P R E L I M I N A R Y
Initial access to the NetBootLoader can only be achieved via the TERM interface. Prior to using
the telnet interface, the Ethernet port parameters must be set and this can only be accomplished initially via the TERM interface.
The operator must either manually set the parameters using the "net" command or dynamically
via the "dhcp" command. Prior to using the "dhcp" command, the IP address of the VMP3 must
be set to 255.255.255.255 using the "net" command.
Once valid Ethernet port parameters and the telnet login password have be set, the telnet interface is available for operation.
Use of the TERM interface requires either a terminal or a terminal emulator. Use of the telnet
interface requires a remote telnet login to the NetBootLoader.
Availability of the command interpreter depends on the system status. If there is no valid application programmed, the command interpreter is available as long as the operator requires it. If
a valid application is programmed, the command interpreter is only available for the duration of
the boot wait time. If the operator requires the command interpreter for a longer time he must
terminate the boot operation before the boot wait time is exceeded.
Upon initiation of the command interpreter, a prompt is sent to the TERM interface and commands may be entered. To gain access to the NetBootLoader from a remote location via the
Ethernet port FCC1 (FE), a telnet login must be performed. If the boot wait time has not been
exceeded, a telnet login automatically terminates the boot operation and a command prompt
is sent to the telnet remote interface.
Once the operator has control of the NetBootLoader, he may perform any required action. To
continue with the operation of the CPU board, the system must either be cold started or the
operator must issue a “reset” command. In either event, the NetBootLoader is restarted and
the boot operation begins anew.
5.4.3NetBootLoader Configuration
There are several NetBootLoader commands which provide the operator with the capability to
configure specific parameters which are used by the NetBootLoader for interfacing operations.
These commands are:
• BW (BootWait)
• CBL (Change Bootline)
• DHCP
•NET
• PASSWD
• PF (Port Format)
• SCRIPT
• SQ (Boot Sequence)
Default settings are available for all the above commands except for "dhcp, net, and script”.
5.4.3.1BW
This command is used to display or set the actual boot wait time used by the NetBootLoader
to delay the boot operation before proceeding with the loading and starting of an application. If
this time is set too short it may only be possible to gain access to the NetBootLoader via the
MC1 (Abort) signal.
The BootWaitTime value is stored in the boot section of the serial EEPROM. This section is
validated with a CRC code to avoid the setting of random parameters.
Note ...
If the CRC of the boot section is not valid, changing the BootWaitTime will have
no effect because the “bw” command does not validate an invalid CRC. In this
case, a default timing of 5 seconds is always used.
To validate an invalid CRC, an operating system utility must be used, or, alternatively, the “-f”
option of the “bw” command must be issued.
Warning !!!
Using the “bw -f” command to validate invalid entries may adversely impact the
operation of the operating system.
5.4.3.2CBL
This command is used to set or display the bootline associated with a particular kernel image
or which is common to all images.
5.4.3.3DHCP
This command is used to obtain automatically networking parameters from either a dhcp or
bootp server for the Ethernet port FCC1 (FE). Its use requires the availability of one or the other
of these servers to function.
5.4.3.4NET
This command is used to set or display the parameters for the configuration of the Fast
Ethernet interface of the CPU board. The Fast Ethernet interface is only available after these
settings have been made. Once these settings have been made, the system must be cold
started or reset for them to take effect.
5.4.3.5PASSWD
This command is used to set the password used by the NetBootLoader for the operation of the
telnet interface. No password is required for access from the TERM interface.
5.4.3.6PF
This command is used to set the port parameters for the TERM and SER0 serial interfaces only
for the current operator session. The next system restart will cause these settings to revert to
the default settings of: 9600 Baud, 8 bits per character, 1 stop bit, and no parity. This is done
to preclude a system lockout when restarting due to incompatible settings.
P R E L I M I N A R Y
5.4.3.7SCRIPT
This command permits the automatic invoking of NetBootLoader commands during boot up.
The operator issues this command with appropriate options and then restarts the system. During the boot operation at boot wait time expiration, the "script" commands will be executed.
Use of this command permits, for example, remote booting from an tftp server.
5.4.3.8SQ
This command is used to set or display the order in which application images are to be booted.
The NetBootLoader provides the capability to program up to four application images into the
FLASH. With this command the operator can define the order in which images may be used
when the system is booted. This provides operational flexibility as well as the possibility for the
system to compensate for a defective image.
For example, in the event the first image specified is defect, the NetBootLoader will attempt to
load the next image specified. This is continued until either a valid image is loaded or no further
image is available.
If no valid image is found, the NetBootLoader invokes its command interpreter and remains
available for inputs.
5.4.4telnet Login
A telnet login to the NetBootLoader is only possible during the boot wait time and only after the
Ethernet port FCC1 (FE) parameters have been set.
To effect a telnet login the operator performs the standard telnet login procedure during the boot
wait time. The NetBootLoader responds by suspending the boot wait and requests a login
password. The operator then enters a password. If the password is valid, the boot wait is terminated and the operator can now access the NetBootLoader. If the password is invalid, the
telnet login procedure is terminated and the boot operation continues.
In the case of an invalid password, the login procedure may be repeated as often as required
within the boot wait time. Once the boot wait time is exceeded, a telnet login is no longer possible.
5.4.5FLASH Operations
To achieve an operable system for an application, the application software may be programmed to FLASH. As mentioned before, the NetBootLoader supports the programming of
up to four application images to FLASH whereby each image is assigned its own image number. In addition to this, it also supports the updating of the NetBootLoader itself as well as data
transfer from the FLASH to the data buffer and from the data buffer to an ftp server. The following chapters provide information on performing the various types of FLASH operations.
5.4.5.1FLASH Offsets
All FLASH is treated as one uniform FLASH, regardless of the physical addresses of the devices involved. All offsets are based from the beginning of the FLASH area. This means that
0x0 is the beginning of the first FLASH bank. The NetBootLoader itself is located at the beginning of the first bank of the FLASH area and for this reason this area cannot be used for application image programming. Figure 5-1 on the next page illustrates this concept. To display an
overview of the current FLASH organization use the “info” command.
If the application image is an operating system (which is the default case), it must be programmed without an offset. When such an image is programmed to FLASH, the image length
and CRC information is also programmed along with the image to FLASH. This information is
used by the NetBootLoader to determine the validity of the image during the boot operation.
During system startup, a valid image is copied to SDRAM address 0x0 and started at offset
0x100 after the boot wait time is exceeded.
P R E L I M I N A R Y
If an offset is specified, the image will be programmed exactly at this offset without adding
length or CRC information. This option is intended for the storing of configuration information
which is required to be located in FLASH.
The application image itself must be compiled and linked to run from the SDRAM base address
0x0 of the CPU. The image must contain executable PPC code at offset 0x100 which is the
usual case with ROM/Flash images.
Gaining access to the image for programming to FLASH depends on where it is located. The
NetBootLoader can access four different sources for images:
• tftp server
• ftp server
• Motorola S-Records
• memory within the visible address range of the CPU board
The NetBootLoader uses a single data buffer for downloading an image from a tftp server, ftp
server, or an image as Motorola S-Records. These images must first be downloaded to the data
buffer prior to being programmed to FLASH. An image located within the visible address range
of the CPU board is directly accessible for programming.
To access an image located on an tftp server, the “tftp” command is used. To access an image
located on an ftp server, the “get” command is used. To perform Motorola S-Record acquisition,
the “sl” (SLoad) command is used. Once the image is in the data buffer, the FLASH is programmed using the “lf” (Load Flash) command. For an image within visible memory, the “lf”
(LoadFlash) command is used to program directly to FLASH.
5.4.5.3Accessing tftp and ftp Servers
To gain access to an application image file stored on a tftp or ftp server the Ethernet port FCC1
(FE) is used. Images are downloaded to the data buffer using the ftp protocol. To use this
interface the Ethernet port parameters must first be set and the operator must have control of
the NetBootLoader.
To download an application image from a tftp server, the command "tftp" is used. The tftp server
IP and file name of the application must be known and provided to the "tftp" command or be
provided by the dhcp server via the "dhcp" command.
To perform a download from an ftp server, the operator must first login to the ftp server. After a
successful login, the operator then locates the image file required and downloads it to the data
buffer. As with any type of server session, the operator should logout when the session is finished.
Note ...
The commands "tftp", “get”, and “ls” use the same data buffer. Therefore if an “ls”
command is issued after a "tftp" or “get” command the data buffer will be overwritten. If an “lf” command follows the “ls” the NetBootLoader refuses to program
the overwritten data buffer to the FLASH.
5.4.5.4Motorola S-Records
The NetBootLoader will also accept Motorola S-Records as an application image. The “sl”’
command accepts S1, S2 and S3 records. Operation is terminated by the appropriate S9, S8
or S7 record. Other types of records are ignored.
The checksum of every record except end records is checked. Bad records are rejected by the
NetBootLoader. The address range of every record is also checked. Records which fall outside
of the internal buffer are rejected.
The records must be 0-based. This means that it’s address must correspond to the address
where they will be loaded in the data buffer relative to its start. If necessary, the base address
can be modified with the -o option of the “sl” command.
Note ...
If the data buffer is programmed to FLASH without the -o option (program a startable image) the downloaded image is copied to RAM during startup and is executed there. For this reason application images which require to be programmed
must start at the address 0x0.
The image must start at the absolute address 0x0 and must contain executable PPC code at
the absolute address 0x100. If S1 or S2 record input is preferred, please note that these
records only include 16 and 24-bit wide addresses. If no switch to another record type is included it must be ensured that the code is not larger than the address range covered.
Note ...
Neither the “sl” nor “If” command can be used to program Motorola S-Records to
RAM areas.
For accessing the Motorola S-Records, both the TERM and SER0 interfaces can be used. The
MC6 (LED1) signal is asserted alternately at a low rate while downloading indicating that the
transfer is in progress. The transfer itself may take several minutes to complete.
Ensure that the XON/XOFF protocol is used on the host side. This is a fixed setting and cannot
be changed. Additionally, ensure that the host does not stop transmission after a number of
lines (e.g. OS-9: use the ‘nopause’ attribute).
The TERM and SER0 serial interface parameters can be modified with the “pf” command.
5.4.6Updating the NetBootLoader
In addition to programming an application to FLASH, the NetBootLoader itself can be updated.
P R E L I M I N A R Y
The new version of the image must be made available via an ftp server.
5.4.7Updating With an Image Loaded Via an ftp Server
The image is downloaded in the same way as an application image (refer to chapter 5.4.5.3).
The new version of NetBootLoader image is then programmed using the “clone -n” command.
5.4.8Uploading a FLASH Area
The NetBootLoader also has the possibility to upload certain areas of the FLASH to a host using the Ethernet port FCC1 (FE). To use this interface this Ethernet port parameters must first
be set and then the operator must gain control of the NetBootLoader and perform an ftp server
login. After a successful login, the operator then stores the FLASH area to be uploaded to the
local data buffer using the “sf” command. Using the “put” command transfers the contents of
the data buffer to the ftp server. As with any type of server session, the operator should logout
when the session is finished.
On the CPU board the NetBootLoader includes “Plug and Play” functionality. This ensures that
the board is completely initialized and that all resources necessary for PCI devices (addresses,
interrupts etc.) are assigned automatically. This important feature has the advantage that conflicts do not arise when PCI devices are added or removed. Furthermore, the operating system
itself does not include the board initialization code.
5.6Porting an Operating System to the CPU Board
The image for the absolute address 0x0 should be linked with an entry point at the absolute
address 0x100.
One should not attempt to reassign the PCI BAR registers. The assigned values should be read
back and these should always be used in the drivers.
The “interrupt line” field in the PCI configuration header is initialized with the IRQ line number
to which the INTA of the device is routed.
Downloaded images are never executed from the FLASH. The programmed image is always
downloaded to SDRAM, the absolute address 0x0 being downloaded first. There is no configuration option available to amend this process. If it is necessary to relocate the image to another address after download, simply add a small assembly routine at the beginning of the code
which will move the image to the correct address.
The following commands are available with the NetBootLoader. Where an ellipsis (…) appears
in the command syntax it means that the command is continued from the previous line. Observe any spaces that may be between the ellipsis and the remainder of the command.
ABORT
FUNCTION:Terminate the NetBootLoader boot operation
SYNTAX:
DESCRIPTION:This command is used by the operator to terminate the boot
abort
operation during the boot wait time to allow the operator to perform
other NetBootLoader operations. To be asserted it must be issued
during the boot wait time which is indicated by the alternating
assertion of the MC6 (LED1) signal.
BW
FUNCTION:Set or display the parameters of the boot wait function of the