Over the last week I spent some time looking into some of the problems
we have been having with the programming of the mv162 FLASH memory.
What I have found is that the following is a usable way to handle the
problem. Please comment on any errors/problems you encounter. This is
a simple process (once you know how.) And we all know how easy it is
to leave out a zero or a jumper when trying to type up a procedure.
1) Unpack your new mv162 card.
2) Insert the mv162BUG rom that is shipped with the board into the
socket labeled U47 (it is the only one that can accept it.)
3) Remove the jumper in J22 that short pins 10 and 11 (the 4th from the
front of the board.) [This tells the board to use that ROM you just
4) Insert the board into a VME crate and plug the console serial port
into your host computer.
5) Set the serial port rate of your host computer to 9600 bps.
6) Power it all up.
7) You should eventually see the 162BUG monitor prompt at which you
should first change the baud rate to 4800 bps. For example:
Baud Rate [110,300,600,1200,2400,4800,9600,19200] = 9600? 4800
Even, Odd, or No Parity [E,O,N] = N? .
OK to proceed (y/n)? y
Update Non-Volatile RAM (Y/N)? y
[Yes, that is a period on the second line that you type in.] After
the baud rate is changed, you will probably get garbage back for the
next prompt. After the change to 4800 bps, you will have to
reconfigure your host to operate at 4800 bps as well. That task is
left to the reader to deal with. [If you are using a Berkeley variant
of UNIX like SunOS, you can look into the /etc/remotes file and set up
a configuration there.]
Once this is complete, connect back to the mv162, hit return a few
times, and you should see your prompt again.
8) Dowload the vxWorks bootrom binary image. This is a file that is
built in your vw/config/mv162 directory named bootrom.hex. To do
the download you will enter a command on the 162 that readies it for
an ascii download, then escape to your local system and upload
the file. If you are using tip to connect to your mv162, the
proper sequence will end up looking like this:
162-Bug>lo 0 100000
~$Local command? cat <your full path to vxV52>/vw/config/mv162/bootrom.hex
away for 12 minutes 24 seconds
What you type is the "lo 0 100000" and press return, then you enter
the "~$" and it will ask "Local command?", you then type in what
ever it takes to get the file listed and press return. Ex:
The upload will take a while and (if you use tip) will print how
long thing took to complete. As you can see it takes about 12
minutes. After that you be able to press the return key and see the
prompt again. If you see anything else... like "Overflow" messages,
it did not work properly. You might try a slower baud rate or mess
with the flow control options and start over.
9) When your upload is successful, you simply program the FLASH memory
from the now in-core binary image using the following commands:
162-Bug>pflash 100000 13ffff ffa00000
Source Starting/Ending Addresses =00100000/0013FFFF
Destination Starting/Ending Addresses =FFA00000/FFA3FFFF
Number of Effective Bytes =00040000 (&262144)
Program FLASH Memory (Y/N)? y
This takes about 20 seconds and should return the prompt when
complete. If you don't get the prompt back, something has failed,
you should start over.
10) Power down the mv162 board/crate and reinstall that jumper in J22
to short pins 10 and 11 [tells the 162 to use the FLASH again.]
Set jumper J1 to determine the board's status as system
controller... short pins 1 & 2 if it is to be the system controller
(the syscon LED on the front will come on to let you know.)
Your mv162 should now boot into the vxWorks startup prompt at 9600
bps the next time it is powered up.
- Navigate by Date:
GCC for EPICS Unix code? William Lupton
[no subject] Gary P. Carr
- Navigate by Thread:
Re: GCC for EPICS Unix code? William Lupton
[no subject] Gary P. Carr