...
Rommon keeps rebooting with the following console error messages: Initializing Hardware... ERROR: IOFPGA0, host DMA valid not set in 2 seconds IOFPGA0, addr=0x70000000, tid=0x10, type=0x18, op=0x02, size=0, owner=0x1, status=0x0 dw[0]: 0x7000000010060281 dw[1]: 0x00000000A4314418 dw[2]: 0x0000000000000006 dw[3]: 0x0000000000000000 IOFPGA ownership is 0x1 Indirect data[0]: 0x00000B4131020080 IOFPGA0 version = 0x0 *********** Host DMA Area Dump 0x0000:0x000000x00000 0x0010:0x000000x00000 0x0020:0x000000x00000 0x0030:0x000000x00000 *********** PCIe Base Addr Dump 0x0400:0x000000x00000 *********** Write Buffer Status Dump 0x0800:0x000000x00000 *********** DMA Engine Status Register Dump 0x3040:0x000000x00000 *********** DMA Engine State Dump 0x5120:0x000000x00000 *********** Debug Block Dump 0x5A00:0x000000x00000 0x5A10:0x000000x00000 0x5A20:0x000000x00000 0x5A30:0x000000x00000 0x5A40:0x000000x00000 ERROR: IOFPGA0, DMA is not ready for next transaction for 2 seconds Host DMA ESC REG = data.u64 = 80000008 Performing System Soft Reset to recover Please wait while the system restarts.
When an active supervisor reloads with 171017 CPLD version, there is a small chance that the supervisor gets stuck in a (rommon) boot loop. The Catalyst 9400 CPLD upgrade instructions are likely detailed in the Release-Notes specific for each version of IOS-XE. For example, here is a link to the CPLD upgrade instructions found in the IOS-XE 16.12 Release Notes: https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst9400/software/release/16-12/release_notes/ol-16-12-9400.html#task_kzg_cws_zgb For some Cisco platforms there are both FPGAs and CPLDs - similar but distinct device types. For the Catalyst 9400 series, the "show hw-programmable all" command is likely to display a CPLD version, BUT the FPGA version is likely to be marked as N/A. Aside: Unfortunately, you may find individuals who (erroneously) use the terms FPGA and CPLD interchangeably.
1. Unseat the supervisor that was successfully upgraded. 2. Power cycle the chassis with only the affected supervisor seated. 3. Perform the upgrade on the standalone sup. 4. Insert the other supervisor to form SSO.
Team working on automatic SW recovery when this condition is encountered. Target release is 17.5.1 and later images.