Commands are presented by applying a value
to the command_code bus and pulsing the command_strobe signal. After a command is presented, the command_busy signal asserts and stays asserted until the command has been queued.
Do not present another command until the command_busy signal
deasserts. The following table lists all the commands and how to generate them. The following
sections describe the commands in detail.
| Command |
Command_code[n – 1:0] Format n = 40 for UltraScale and n = 44 for UltraScale+ Devices |
||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Directed State Change to Idle |
UltraScale =
UltraScale+ =
Valid when controller in Observation and Detect only states. |
||||||||||
| Error Injection Using LFA |
UltraScale =
UltraScale+ =
Valid when controller in Idle state. Valid for Mitigation and Testing, Detect and Testing, or Emulation modes only. For additional guidance on how to use error injection to test a design, see Error Injection Guidance. |
||||||||||
| Directed State Change to Observation |
UltraScale =
UltraScale+ =
Valid when controller in Idle state. Valid for mitigation modes only. |
||||||||||
| Directed State Change to Detect only |
UltraScale =
UltraScale+ =
Valid when controller in Idle state. |
||||||||||
| Directed State Change to Diagnostic Scan |
UltraScale = UltraScale+ = 1101 xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx
Valid when controller in Idle state. |
||||||||||
| Software Reset |
UltraScale =
UltraScale+ =
Valid when controller in Idle state. |