OMS MAXv reset/power-up problem

["Ronald L. Sluiter" <sluiter@aps.anl.gov>]

 OMS MAXv users,

Kurt Goetze and I discovered a design problem with the OMS MAXv motion
control board .  The problem is that the MAXv board fails to initialize 
correctly
after reset or power-cycling approx. 15% of the time.  OMS explains,

> The FPGA that controlled VME communications of the MAXv controller was
> not consistently reset on initialization. The modification guarantees 
> that this
> FPGA is consistently reset on all initializations including power-up 
> and SYSRESET.

Of course, the greater the number of MAXv boards in a given IOC, the greater
the chance that one of them will not initialize correctly.

OMS has fixed the problem.  MAXv boards with FPGA code version A6 and
above are fixed.  Users with FPGA code version A5 and below should obtain
a RMA from OMS and request Engineering Change Order (ECO) #1432.
There is no charge for the upgrade.

You can determine the FPGA code version of your MAXv boards by issuing the
following command at the IOC shell (note the "FPGA:B1:A6" section);

> epics> dbior "drvMAXv"
> Driver: drvMAXv
>     Oms MAXv motor card #0 @ 0xFFFFF000, id: MAXv-8000 ver:1.29, 
> s/n:000122, FPGA:B1:A6 BOOT:1.1 - Oregon Micro Systems  
> epics>

Until all the MAXv boards in a give IOC are "fixed", I recommend that you
use the above 'dbior "drvMAXv"' command after every reset and power-cycle
to determine if all the MAXv boards have initialized correctly.  The MAXv
boards that did not initialize correctly will have the "... not found." 
message.
Example below;

> epics> dbior "drvMAXv"
> Driver: drvMAXv
>     Oms MAXv motor card #0 not found.
>     Oms MAXv motor card #1 @ 0xFFFFF000, id: MAXv-8000 ver:1.29, 
> s/n:000122, FPGA:B1:A6 BOOT:1.1 - Oregon Micro Systems  
> value = 0 = 0x0

The only course of action is to keep rebooting until all the MAXv boards
in a given IOC initialize correctly.

Best regards,
Ron Sluiter