Re: which bootrom.hex?

[Joe Sullivan <sullivan@aps.anl.gov>]

The APS distribution of vxWorks 5.2p1 includes some development config 
directories that should be ignored. The production config direction is
vxV52p1/vw/config. Under this config directory the production board
supports
are 'all', 'mv162' and 'mv167' the others should be ignored. The mv162
BSP runs on all models of the MVME162 product line that are compatable
with
the MVME712 transition module and have at lest 4MB of memory. 

The first 8 bytes of the bootrom.hex codes is a jump table. To 
start running out of RAM  you would have to 'GO' from 10008(hex).
Running bootrom out of RAM is complicated by the fact that the code is  
using fixed sections of RAM for it's workspace so it may write over
itself.

The procedure for flashing the bootrom.hex file in a (out of the box)
MVME162-532 ...
1) Remove jumper J22 [9-10]
2) Connect to Front Panel Port 1 
	ie: Using Sun Solaris  -> cu -l cua/a -s9600 -b8
3) From 162-Bug prompt  -> 'lo 0 10000'
4) Upload ./vxV52p1/vw/config/mv162/bootrom.hex via serial port
	ie: Using unix cu command -> 
	          ~$cat /usr/local/vw/vxV52p1/vw/config/mv162/bootrom.hex
	NOTE: Hit <RETURN> several times and wait for 162-Bug prompt
	      to return.
5) Program Flash memory from RAM 
	from 162-Bug prompt -> 'pflash 10000 8ffff ffa00000'
	You should see this

----------------- Start 162-Bug include ---------------------

Source Starting/Ending Addresses      =00010000/0008FFFF
Destination Starting/Ending Addresses =FFA00000/FFA7FFFF
Number of Effective Bytes             =00080000 (&amp;524288)

Program FLASH Memory (Y/N)? y
Erasing Block Number     =00 ($FFA00000)
Erasing Block Number     =01 ($FFA10000)
Erasing Block Number     =02 ($FFA20000)
Erasing Block Number     =03 ($FFA30000)
Erasing Block Number     =04 ($FFA40000)
Erasing Block Number     =05 ($FFA50000)
Erasing Block Number     =06 ($FFA60000)
Erasing Block Number     =07 ($FFA70000)
Programming Block Number =00 ($FFA00000)
Programming Block Number =01 ($FFA10000)
Programming Block Number =02 ($FFA20000)
Programming Block Number =03 ($FFA30000)
Programming Block Number =04 ($FFA40000)
Programming Block Number =05 ($FFA50000)
Programming Block Number =06 ($FFA60000)
Programming Block Number =07 ($FFA70000)
FLASH Memory Programming Complete
----------------------- End 162-Bug include --------------------

6) Replace jumper J22 [9-10] and the next reboot will
   run the vxWorks bootrom.
		


Joe Sullivan
APS/UPD/BCDA
x28657
    		


Dale L. Brewe wrote...
> 
> Can anyone tell me which bootrom.hex file I should use to program the flash
> rom of an mvme162-532A board for vxWorks 5.2p1? In the distribution of
> vxWorks 5.2p1 I was given, I count 6 apparently different versions. I used
> the bootrom.hex in <path>/vxV52p1/config/mv162, which is 371203 bytes, and
> I can't get that one to work. One thing I noticed is that if I load in this
> file, with say lo 0 10000, etc., and try GO 100000, I get an error message
> like 'Exception: Line 1111 Emulator (unimplemented F-line opcode)'. So, I
> thought maybe I could be using a version with some fatal bug?