Visible to Intel only — GUID: kap1489594214787
Ixiasoft
Visible to Intel only — GUID: kap1489594214787
Ixiasoft
6.1.4.7.1. CONFIG_IO
This instruction allows you to perform board-level testing before configuring the Intel® Cyclone® 10 LP device or waiting for a configuration device to complete configuration. After the configuration is interrupted and JTAG testing is complete, you must reconfigure the part through the PULSE_NCONFIG JTAG instruction or by pulsing the nCONFIG pin low.
You can issue the CONFIG_IO instruction any time during user mode.
- The CONFIG_IO instruction cannot be issued when the nCONFIG pin is low.
- You must observe a 230µs minimum wait time after any of the following conditions:
- nCONFIG pin goes high
- Issue the PULSE_NCONFIG instruction
- Issue the ACTIVE_ENGAGE instruction, before issuing the CONFIG_IO instruction
- You must wait 230 µs after power up, with the nCONFIG pin high before issuing the CONFIG_IO instruction (or wait for the nSTATUS pin to go high).
Use the ACTIVE_DISENGAGE instruction with the CONFIG_IO instruction to interrupt configuration.
JTAG Instruction | Prior to User Mode(Interrupting Configuration) | User Mode | Power Up | ||||||
---|---|---|---|---|---|---|---|---|---|
PS | FPP | AS | PS | FPP | AS | PS | FPP | AS | |
ACTIVE_DISENGAGE | O | O | O | O | O | O | – | – | – |
CONFIG_IO | R | R | R | R | R | R | NA | NA | NA |
JTAG Boundary Scan Instructions (no JTAG_PROGRAM ) | O | O | O | O | O | O | – | – | – |
ACTIVE_ENGAGE | A | A | R 27 | A | A | R 27 | – | – | – |
PULSE_nCONFIG | A 28 | O | – | – | – | ||||
Pulse nCONFIG pin | A 28 | O | – | – | – | ||||
JTAG TAP Reset | R | R | R | R | R | R | – | – | – |
If reconfiguration after interruption is performed using configuration modes (rather than using JTAG_PROGRAM), it is not necessary to issue the ACTIVE_DISENGAGE instruction prior to CONFIG_IO. You can start reconfiguration by either pulling nCONFIG low for at least 500 ns or issuing the PULSE_NCONFIG instruction. If the ACTIVE_DISENGAGE instruction was issued and the JTAG_PROGRAM instruction fails to enter user mode, you must issue the ACTIVE_ENGAGE instruction to reactivate the active configuration controller. Issuing the ACTIVE_ENGAGE instruction also triggers reconfiguration in configuration modes; therefore, it is not necessary to pull nCONFIG low or issue the PULSE_NCONFIG instruction.