On Thu, May 15, 2014 at 3:16 PM, David Riley <fraveydank at gmail.com> wrote:
On May 15, 2014, at 5:12 PM, Mark J. Blair <nf6x at
nf6x.net> wrote:
My system's bootstrap ROMs don't include code for MSCP-compatible controllers,
but the UC07 is supposed to have its own built-in bootstrap. I don't know if I'll
still have access to the original bootstrap ROMs after I jumper everything for the UC07
bootstrap. Maybe I'll need to route one or more jumpers out to some external
switch(es) to let me boot from the RX02 when desired?
The way it works for my CMD CQD-220 is that you can have its
bootstrap ROMs respond to 1773000, the typical bootstrap location,
or 1771000 (my recollection). It's jumper-selectable (including
no bootstrap access at all). Fortunately, my 11/23+ has MSCP boot
in its ROMs, so I don't need to worry about it.
With the CMD CQD controllers you can disable the controller bootstrap
at either 773000 or 771000 if you want to coexist with another
bootstrap in the system (for example on a BDV11), and then if the
other bootstrap is not MSCP or TMSCP capable you can still get the CMD
CQD controller to boot by halting to ODT and using the magic sequence
to access the on board utility and use that to boot:
17772152/005400 123456 <CR>
17772152/001000 100 <CR>
5000G
(where 17772152 is the configured base CSR address + 2)
According to the Emulex UC07 manual it requires the CPU to be
configured in power-up mode 0 to boot through PC at 24 and PS at 26
instead of power-up mode 2 to boot at 773000. (How does that work,
does the controller DMA the bootstrap into system memory on bus
initialization?) I suppose in that case you could configure the CPU
and the UC07 to autoboot, and then if you wanted an alternate boot you
could halt to ODT and then manually execute your other bootstrap at
773000.