Personal tools
You are here: Home Exp Spec Info musr flash_MVME2305_bootrom.html

flash_MVME2305_bootrom.html

by admin last modified Oct 16, 2007 11:39 AM

Flashing the Boot ROM on the MVME2305 PowerPC

Troubleshooting

Introduction

Instructions on Flashing the Boot Rom on the MVME2300 series PowerPC boards using Motorola PPC1-Bug are in the file target.txt. Similar information for other MVME series are in "sundown/usr1/local/tornado_ppc_1.0.1/target/config/mv*/target.txt". The following instructions refer to the MVME2300 series of boards, and refer to pages 13-14 of target.txt.

A copy of the manual provided with the board: MOTOROLA MVME2300-Series VME Processor Module Installation and Use (referred to here as the Hardware Manual) may be useful.

Refer to the PPCbug manual  for more information.

1. Set Jumper J15 for socketed flash

i.e. connect J15 pins 2 & 3. See Hardware Manual pp 1-9 and 1-10.

2. Connect Ethernet and System Consol

  • Ethernet
Warning : use 10baseT connection for flashing the Boot Rom. 100baseT does not seem to work for this (but can
be used once the board has been flashed).
 
  • System console  (Debug Serial port)
Connet to either VT100 at 9600 baud, to an NCD terminal, or to a linux box (use/install "seyon" software) .  See Hardware Manual pp 1-12  and 1-13. Cables/pinouts may be available in the DAQ office.

3. Power board up

The prompt:
        PPC1-Bug >
should appear on power-up.
 
 
NOTE:
    If  the RS-232 connection does not respond even after reboot/power down (and was previously working)
    or the amber BFL light remains lit after the power-up sequence
the  NVRAM Board Information may be corrupted or lost.



 

4. Start the clock

The clock must be running for the niot command to work properly. New boards are shipped without the clock running. To check if it is running, issue the command :
        PPC1-Bug >TIME
If it gives the correct data and time, the clock is running.

If not, to set it running, use the command "set". The format is : set MMDDYYhhmm, e.g.

        PPC1-Bug >set 1112981200

5. Setup addresses with NIOT

Use default values where carriage return (CR) is shown below:
 
PPC1-Bug >niot  
Controller LUN  (CR)
Device LUN      (CR)
Node Control Memory Address    (CR)
Client IP Address 142.90.102.6   Substitute your address here  - this is m15hmvw
Server IP Address 142.90.106.82  (dasdevpc - runs TFTP)
Subnet IP Address Mask 255.255.0.0
Broadcast IP Address Mask 142.90.255.255
Gateway IP Address 142.90.100.19 (tgate)
Boot file name   . 
Update non-volatile RAM (Y/N) Y

6. Transfer boot file from TFTP host using NIOP

PPC1-Bug >niop            
Controller LUN (CR)
Device LUN (CR)
Get/Put  =G?(CR)
File Name =vxWorks/ppc/boot.bin
Memory Address =00004000? (CR)
Length         =00000000? (CR)
Byte Offset    = 00000000? (CR)

 At this point, after a short delay, you should get: 

Bytes Received =&250912, Bytes Loaded =&250912
Bytes/Second   =&125456, Elapsed Time =2 Second(s)
PPC1-Bug>

 Otherwise, you may get an error code.

7. Program the flash memory

PPC1-Bug>pflash 4000:FFF00 ff000100

Source Starting/Ending Addresses      =00004000/00103EFF
Destination Starting/Ending Addresses =FF000100/FF0FFFFF
Number of Effective Bytes             =000FFF00 (&1048320)

Program FLASH Memory (Y/N)? y
FLASH Memory Programming Complete                  
PPC1-Bug>

8. Set Jumper J15 for soldered flash

i.e. connect J15 pins 1 & 2. See Hardware Manual pp 1-9 and 1-10.

9. Replace board, power up and boot.

The usual set-up parameter display of VxWorks should result.

10. Configure the setup parameters.

Set up the parameters with reference to these examples.
 
     Back to top

 

Error codes

Niop may return an error code.  Error codes commonly returned are:
  •     error status: 8200 TFTP access violation (file not found?)
  • Try using tftp to log onto host and get the file.
    [fred@dasdevpc ~]$ tftp dasdevpc
    tftp> ?              (for help)
    tftp> get vxWorks/ppc/boot.bin
    There may be something in the error logs of the machine, e.g. /var/log/messages/
     
  •     error status: 0018 Transmitter no carrier (100baseT?)
  • status:0018 occurred when using a direct network connection to 100baseT, on all boards tried. This error vanished as soon as a 10BaseT connection was used. There was no problem with 100baseT in normal use.
     
  •     nothing at all  ( ip addresses may be wrong)

  • Recheck all niot addresses (including broadcast & gateway)
     
     

                                     Back to top

    Troubleshooting
     
     

    Loss of board information


    In the case where the RS-232 connection does not respond even after a reboot or a power down
    or
    the amber BFL (board failure light) remains lit after the power-up sequence

    you may be experiencing the loss of the "Board Information" stored in the NVRAM.

    You will likely see the following message on the consol: WARNING: Board Configuration Data Failure
     

    • This information specifies the CPU speed, Bus speed, Ethernet address, Serial number, etc..

    •  
    • The procedure to recover part of this information is the following:

    •  
      • Check the current board information:
             
            ---------------------------------------------------
            PPC1-Bug>cnfg

            Board (PWA) Serial Number = "3&*$%55     "
            Board Identifier          = "AA#^&$YB%%  "
            Artwork (PWA) Identifier  = "01-W....6H    "
            MPU Clock Speed           = "3?r"
            BUS Clock Speed           = "0@?5"
            Ethernet Address          = 0409802BHH
            Primary SCSI Identifier   = "0)"
            System Serial Number      = "???????????????"
            System Identifier         = "...........?///,,,,,,"
            License Identifier        = ".   .54553"
            ---------------------------------------------------
             

        Physically retrieve information from the board. On the actual PPC board you can find the serial number, Artwork Identifier (below the SN) and the ethernet address on different stickers (you will have to remove the board from the crate if this information has not yet been recorded).
         
      • Enter the basic Board Information by modifying the configuration block (see below for defaults):
            ---------------------------
            PPC1-Bug>cnfg;M
                ---------------------------
         
      • Save the Board Information in NVRAM:
        • --------------------------------
          Update Non-Volatile RAM (Y/N)? y
          --------------------------------
      • Repeating the "cnfg" command the Board Information should look like the following:
                   -----------------------------------------------
            PPC1-Bug>cnfg

            Board (PWA) Serial Number = "3408645     "     << from what you read
            Board Identifier          = "MVME2306        " << from what you know
            Artwork (PWA) Identifier  = "01-W3345F06H    " << from what you read
            MPU Clock Speed           = "300"              << from what you know
            BUS Clock Speed           = "067"              << from what you know
            Ethernet Address          = 08004A89FC34       << from what you read
            Primary SCSI Identifier   = "07"               << default
            System Serial Number      = "0000000000000000" << default
            System Identifier         = "Motorola MVME2300" << default
            License Identifier        = "3567896 0"        << you may know it

                 ----------------------------------------------
         
      • At this point you can carry on the TFTP kernel-boot loading through the time command.
      • allow there me command.

    Double Reset Procedure/ removal of battery:

    Motorola suggested the following procedures when the board had failed and could not be re-flashed:
       
    • Double reset

    • After power-up,  wait until the ppc-bug prompt  appears.
      Press abort & reset together for at least 15s
      Release reset, hold abort for at least another 15s, then release

      SelfTest/Boot messages should appear on the consol.  To return to the ppc-bug prompt, press Reset.
       

    • Removal of battery

    • Remove the board from the crate, locate the battery on the board, and carefully remove it. Wait 15 seconds, then replace it.


    Note: If you see the message on the consol:  "WARNING: Board Configuration Data Failure"  reconfigure the board information.

    Document Actions