Configuration and Remote System Upgrades in Cyclone IV ... - Altera
Configuration and Remote System Upgrades in Cyclone IV ... - Altera
Configuration and Remote System Upgrades in Cyclone IV ... - Altera
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Chapter 8: <strong>Configuration</strong> <strong>and</strong> <strong>Remote</strong> <strong>System</strong> <strong>Upgrades</strong> <strong>in</strong> <strong>Cyclone</strong> <strong>IV</strong> Devices 8–59<br />
<strong>Configuration</strong><br />
ACT<strong>IV</strong>E_DISENGAGE<br />
The ACT<strong>IV</strong>E_DISENGAGE <strong>in</strong>struction places the active configuration controller (AS <strong>and</strong><br />
AP) <strong>in</strong>to an idle state prior to JTAG programm<strong>in</strong>g. The two purposes of plac<strong>in</strong>g the<br />
active controller <strong>in</strong> an idle state are:<br />
■ To ensure that it is not try<strong>in</strong>g to configure the device dur<strong>in</strong>g JTAG programm<strong>in</strong>g<br />
■ To allow the controllers to properly recognize a successful JTAG programm<strong>in</strong>g<br />
that results <strong>in</strong> the device reach<strong>in</strong>g user mode<br />
The ACT<strong>IV</strong>E_DISENGAGE <strong>in</strong>struction is required before JTAG programm<strong>in</strong>g regardless<br />
of the current state of the <strong>Cyclone</strong> <strong>IV</strong> device if the MSEL p<strong>in</strong>s are set to an AS or AP<br />
configuration scheme. If the ACT<strong>IV</strong>E_DISENGAGE <strong>in</strong>struction is issued dur<strong>in</strong>g a passive<br />
configuration scheme (PS or FPP), it has no effect on the <strong>Cyclone</strong> <strong>IV</strong> device. Similarly,<br />
the CONFIG_IO <strong>in</strong>struction is issued after an ACT<strong>IV</strong>E_DISENGAGE <strong>in</strong>struction, but is no<br />
longer required to properly halt configuration. Table 8–16 lists the required,<br />
recommended, <strong>and</strong> optional <strong>in</strong>structions for each configuration mode. The order<strong>in</strong>g<br />
of the required <strong>in</strong>structions is a hard requirement <strong>and</strong> must be met to ensure<br />
functionality.<br />
Table 8–16. JTAG Programm<strong>in</strong>g Instruction Flows (1)<br />
JTAG Instruction<br />
<strong>Configuration</strong> Scheme <strong>and</strong> Current State of the <strong>Cyclone</strong> <strong>IV</strong> Device<br />
Prior to User Mode (Interrupt<strong>in</strong>g<br />
<strong>Configuration</strong>)<br />
User Mode Power Up<br />
PS FPP AS AP PS FPP AS AP PS FPP AS AP<br />
ACT<strong>IV</strong>E_DISENGAGE O O R R O O O R O O R R<br />
CONFIG_IO Rc Rc O O O O O 0 NA NA NA NA<br />
Other JTAG <strong>in</strong>structions O O O O O O O 0 O O O 0<br />
JTAG_PROGRAM R R R R R R R R R R R R<br />
CHECK_STATUS Rc Rc Rc Rc Rc Rc Rc Rc Rc Rc Rc Rc<br />
JTAG_STARTUP R R R R R R R R R R R R<br />
JTAG TAP Reset/other<br />
<strong>in</strong>struction<br />
R R R R R R R R R R R R<br />
Note to Table 8–16:<br />
(1) “R” <strong>in</strong>dicates that the <strong>in</strong>struction must be executed before the next <strong>in</strong>struction, “O” <strong>in</strong>dicates the optional <strong>in</strong>struction, “Rc” <strong>in</strong>dicates the<br />
recommended <strong>in</strong>struction, <strong>and</strong> “NA” <strong>in</strong>dicates that the <strong>in</strong>struction is not allowed <strong>in</strong> this mode.<br />
In the AS or AP configuration scheme, the ACT<strong>IV</strong>E_DISENGAGE <strong>in</strong>struction puts the<br />
active configuration controller <strong>in</strong>to idle state. If a successful JTAG programm<strong>in</strong>g is<br />
executed, the active controller is automatically re-engaged after user mode is reached<br />
through JTAG programm<strong>in</strong>g. This causes the active controller to transition to their<br />
respective user mode states.<br />
If JTAG programm<strong>in</strong>g fails to get the <strong>Cyclone</strong> <strong>IV</strong> device to enter user mode <strong>and</strong><br />
re-engage active programm<strong>in</strong>g, there are available methods to achieve this:<br />
■ In AS configuration scheme, you can re-engage the AS controller by mov<strong>in</strong>g the<br />
JTAG TAP controller to the reset state or by issu<strong>in</strong>g the ACT<strong>IV</strong>E_ENGAGE <strong>in</strong>struction.<br />
February 2013 <strong>Altera</strong> Corporation <strong>Cyclone</strong> <strong>IV</strong> Device H<strong>and</strong>book,<br />
Volume 1