The Command Interface provides a convenient set of inputs to command the controller to inject a bit error into configuration memory.
For more information on this interface, see Command Interface.
| Name | Sense | Direction | Description |
|---|---|---|---|
| command_strobe | High | In | The command control is used to indicate a command request. The command_strobe signal should be pulsed High for one cycle, synchronous to icap_clk, when command_busy is low concurrent with the application of a valid code to the command_code input. |
| command_code[width – 1:0] | High | In | The command_code bus is used to specify the command the controller should perform. The value on this bus is captured at the same time command_strobe is sampled active. The width of the command_code port is dependent on the target architecture. For UltraScale devices, the width is 40. For all other architecture, the width is 44. |
| command_busy | High | Out | The busy signal is used to indicate whether the controller is ready to process a command. Only assert command_strobe when command_busy is Low. |
The Command Interface provides a simple interface to perform error injection and software reset. For more information on how to use the interface and valid command codes, see Command Interface.
Note: The Monitor Interface is the comprehensive and preferred interface
for user interaction with the IP. See Monitor Interface.
The use of this interface is entirely optional. If not used, all inputs can be tied to Low.