The following table describes how to troubleshoot the AXI4-Lite interface.
| Symptom | Solution |
|---|---|
| Readback from the Version Register through the AXI4-Lite interface times out, or a core instance without an AXI4-Lite interface seems non-responsive. | Are the S_AXI_ACLK and ACLK
pins connected?The VERSION_REGISTER readout issue can be indicative of the core not receiving the AXI4-Lite interface. |
| Readback from the Version Register through the AXI4-Lite interface times out, or a core instance without an AXI4-Lite interface seems non-responsive. | Is the core enabled? Is s_axi_aclken connected to vcc? Verify that signal ACLKEN is connected to either net_vcc or to a designated clock enable signal. |
| Readback from the Version Register through the AXI4-Lite interface times out, or a core instance without an AXI4-Lite interface seems non-responsive. | Is the core in reset? S_AXI_ARESETn and ARESETnmust connect to vcc for the core not to be in reset. Verify that the S_AXI_ARESETn and ARESETn signals are connected to either net_vcc or to a designated reset signal. |
| Readback value for the VERSION_REGISTER is different from expected default values | The core and/or the driver in a legacy project has not been updated. Ensure that old core versions, implementation files, and implementation caches have been cleared. |
Assuming the AXI4-Lite interface works, the second step is to bring up theAXI4-Stream interfaces.