This is a collection of items related to the MV2100 T202 Board Support package that may help get you out of a bind.
If the boot stops after "Loading... 1109976, Starting at 0x100000..." then one of several possibilities exist.
One of the things that may prevent the Network kernel from starting is that the ROM kernel failed to initialize the hardware correctly. This can happen if the kernels are incompatible. The ROM kernel vs. the Network kernel have to both be derived from the APS Board Support Package. The BSP displays a version number shown when the kernel starts, the APS BSP displays "BSP version: 1.2/1-asd1", while SNS kernels, derived from the APS BSP, display: "BSP version 1.2/SNSXX [XRSIO FEI]". The Network kernel does not initialize the hardware if the ROM kernel has already initialized the hardware. To force the Network kernel to initialize the hardware a flag must be reset in the ROM kernel.
Resetting the "hardware initialized" flag.
Get the ROM boot prompt by stopping the countdown at cold boot.
Type "m 4c00 <CR> 0 <CR> ."
Type "@"
At 701SCA your boot parameters should be like this:
boot device : dc
unit number : 0
processor number : 0
host name : ics-srv02
file name : /ade/vxWorks/t202/mv2100-prod/vxWorks
inet on ethernet (e) : 160.91.225.72:fffffc00
host inet (h) : 160.91.224.216
gateway inet (g) : 160.91.224.1
user (u) : vxuser
flags (f) : 0x0
target name (tn) : icsdev-ioc2
startup script (s) : /ade/epics/iocTop/R3.13.5/mps_test/iocBoot/ioc603/st.cmd
-> ipAttach 0,"fei"
value = 0 = 0x0
-> ifAddrSet "fei0","192.168.1.2"
value = 0 = 0x0
That's it.