Software
5.
Run the following commands from the U-Boot command prompt:
setenv vxworks_bootfile DEV_RTC8260
setenv vxworks_active_partition 1
fatload ide 0:1 8000000 DEV_RTC8260
6.
If the fatload command succeeds, skip this step. If the fatload command fails, re-run
the last two commands with the partition number set to 4:
setenv vxworks_active_partition 4
fatload ide 0:4 8000000 DEV_RTC8260
7.
After the fatload completes successfully, run the following commands to boot the
VxWorks development image:
run vxworksargs_ata
bootvx 8000000
8.
After the VxWorks development image boots, run the following commands to reflash
both bootrom and FPGA:
Upgrade_Bootrom
Upgrade_Xilinx
9.
Run the following command to verify and update bootline if needed:
bootChange
Ensure that the partition number parameter is set to the partition number associated
with the successful fatload command in Step 6 (or Step 7), and that the file name is
set to RTC8260.
10.
Reboot the system:
reboot
The pre-9.0 MiVoice Business load that was running on the AX Controller before the
migration attempt starts booting.
U-Boot based E2T card in MXe III cannot boot E2T8260 Image after Reverse
Migration
This section applies only to MXe III systems featuring an E2T card with U-Boot as the
bootloader.
If the E2T card does not come up and connect to the RTC card (running a pre-9.0
MiVoice Business release) after 10 minutes of executing Step 1 of the procedure,
Appendix A: Reverse Migration > Reverse Migration of an E2T Card
in the
Migration
Document Version 1.0
Troubleshooting Guide
132
Summary of Contents for MiVoice Business 3300 ICP
Page 1: ...MiVoice Business Troubleshooting Guide Release 9 4 SP1 Document Version 1 0 June 2022 ...
Page 10: ...Introduction Document Version 1 0 Troubleshooting Guide 4 ...
Page 45: ...Figure 4 DNS setting on MSL server manager ...
Page 323: ...Diagnosing Problems Document Version 1 0 317 Troubleshooting Guide ...