Flashing the Boot ROM on the MVME162

This note is specific to the MVME162 boards used by the MUSR group for running CAMP. A special kernel has been built for these boards (on sundown) called camp023.bin. This has been copied to the tftp area on sunset for downloading to the MVME162 boards. More information is available in the file /usr1/local/tornado/target/config/mv162-023/target.txt on one of the Electronics Sun Machines.

Set bootup parameter "startup script" blank

Temporarily set the bootup parameter "startup script" blank, so that no automatic startup file will be loaded.

startup script (s)   : /ram/stcamp.m9b  .

This is very important if a ram disk is present, or any problem with the startup file can cause the board to go off into limbo. If this should happen, follow procedure to overwrite parameter for startup script.

Boot board into 162-bug

Boot up the debugger , 162-bug.

Supply Ethernet addresses with niot

Note example shown is using devvw, with dasdevpc as the host machine. Dasdevpc has the kernel file (camp023.bin) available in its tftp area (i.e. /home/tftpboot/vxWorks/mv162/camp023.bin).

Note lines marked with "*" are important - you must supply the correct values.

162-Bug>niot
Controller LUN =00?
Device LUN     =00?
Node Control Memory Address =FFE10000?
Client IP Address      =0?  142.90.106.103     * MVME board ip address (e.g. devvw)
Server IP Address      =0?  142.90.106.82      * tftp host ip address (e.g. dasdevpc)
Subnet IP Address Mask =255.255.255.0?  255.255.0.0          * mask
Broadcast IP Address   =255.255.255.255? 142.90.255.255      * broadcast
Gateway IP Address     =0.0.0.0? 142.90.100.19               * tgate
Boot File Name ("NULL" for None)     =? .     * exit from niop

Update Non-Volatile RAM (Y/N)? y

 Use niop to download the kernel 
162-Bug>niop
Controller LUN =00?
Device LUN     =00?
Get/Put        =G?                         default is Get
File Name      =00? vxWorks/mv162/camp023.bin    * kernel in tftp area
Memory Address =00000E000? 0x10008?       * supply correct number here
Length         =00000000?
Byte Offset    =00000000?

Bytes Received =&301912, Bytes Loaded =&301912
Bytes/Second   =&60382, Elapsed Time =5 Second(s)

If you don't get the Bytes Received message here, there may be a problem with the file not being in the correct tftp area, or with the network connection.

Correct first 8 bytes

According to procedure detailed in target.txt (see above), do the following:

162-Bug>mm 0x10000
00010000 0000? 0000      * supply these values
00010002 0000? 1000
00010004 0000? ff80
00010006 0000? 0008
00010008 46FC? .         * to exit from mm

Transfer image to flash memory

 
162-Bug>pflash 0x10000:0x7fff0 0xffa00000
Source Starting/Ending Addresses      =00010000/0008FFEF
Destination Starting/Ending Addresses =FFA00000/FFA7FFEF
Number of Effective Bytes             =0007FFF0 (&524272)

Program FLASH Memory (Y/N)? y
Zeroing Block Number     =00 ($FFA00000)
Zeroing Block Number     =01 ($FFA40000)
Erasing Block Number     =00 ($FFA00000)
Erasing Block Number     =01 ($FFA40000)
Programming Block Number =00 ($FFA00000)
Programming Block Number =01 ($FFA40000)
FLASH Memory Programming Complete
162-Bug>

Boot vxWorks

Power down the board, replace the jumper (J22 see above), power up and reboot. The large VxWorks banner should come up.

 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
      ]]]]]]]]]]]  ]]]]     ]]]]]]]]]]       ]]              ]]]]         (R)
 ]     ]]]]]]]]]  ]]]]]]     ]]]]]]]]       ]]               ]]]]            
 ]]     ]]]]]]]  ]]]]]]]]     ]]]]]] ]     ]]                ]]]]            
 ]]]     ]]]]] ]    ]]]  ]     ]]]] ]]]   ]]]]]]]]]  ]]]] ]] ]]]]  ]]   ]]]]]
 ]]]]     ]]]  ]]    ]  ]]]     ]] ]]]]] ]]]]]]   ]] ]]]]]]] ]]]] ]]   ]]]]  
 ]]]]]     ]  ]]]]     ]]]]]      ]]]]]]]] ]]]]   ]] ]]]]    ]]]]]]]    ]]]] 
 ]]]]]]      ]]]]]     ]]]]]]    ]  ]]]]]  ]]]]   ]] ]]]]    ]]]]]]]]    ]]]]
 ]]]]]]]    ]]]]]  ]    ]]]]]]  ]    ]]]   ]]]]   ]] ]]]]    ]]]] ]]]]    ]]]]
 ]]]]]]]]  ]]]]]  ]]]    ]]]]]]]      ]     ]]]]]]]  ]]]]    ]]]]  ]]]] ]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]       Development System
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]       VxWorks version 5.3.1
 ]]]]]]]]]]]]]]]]]]]]]]]]]]       KERNEL: WIND version 2.5
 ]]]]]]]]]]]]]]]]]]]]]]]]]       Copyright Wind River Systems, Inc., 1984-1997

                               CPU: Motorola MVME162.  Processor #0.
                              Memory Size: 0x400000.  BSP version 1.1/4.
                             WDB: Ready.

ramDiskInit: making new DOS filesystem, "/ram" initialized.
-> 

Update the ram if necessary

If a new version of VxWorks is installed, the ram disk will be initialized. The files that reside on the ram disk will need to be recompiled and recopied to ram. It is assumed that recompiled versions are available on the host in the area usually nfs-mounted by the MVME as "/vw". Using a copy of the startup file on the host machine for reference, type in at the consol the commands to nfsMount the appropriate directory as "/vw", and update the ram disk.

Try the startup file

Reboot (or nfsUnmount "/vw") and try the startup file by hand, e.g.

-> < /vw/stcamp.dev
or
-> < /ram/stcamp.dev

Occasionally one or more of the files on ram become corrupted, so if the startup procedure does not work (and you have not just updated the ram disk), determine where it is failing. Try recopying the appropriate object file to ram & reboot.

Reset the bootup parameter "startup script"

Reset the bootup parameter "startup script" when it is established that the startup script is working.