BELK-WP-001: Xilinx Zynq-7000 Errata management

From DAVE Developer's Wiki
Jump to: navigation, search
Info Box
Bora5-small.jpg Applies to Bora
BORA Xpress.png Applies to BORA Xpress
BORALite-TOP.png Applies to BORA Lite
BORA TOP.png Applies to BORA White Papers


Introduction[edit | edit source]

Using a complex SOC (SystemOnChip) should take into account that this kind of silicon devices may have some issue on the silicon itself and the errata list - available form the silicon manufacturer - has to be taken into account.

This page shows how to cope with Zynq-7000 errata notices using the available information on Xilinx's documentation.

DAVE's errata policy[edit | edit source]

Regarding the hardware errata, generally, we can say that the design takes care of the errata that were known at the design/qualification stage.

For what regards the software errata, we have to take into account that our BSP's derive from the ones released by the silicon vendor BSP's. As such, we inherit the fixes/workarounds implemented by the silicon vendor.

Zynq-7000 errata[edit | edit source]

The main errata page for the Zynq-7000 devices is the official document Zynq-7000 AP SoCProduction Errata.

For the Zynq-7000 AP SoC Devices there is a web page which lists the various errata in relation to the Silicon Revision Differences. As reported, This answer record contains a list of answer records related to the Zynq-7000 AP SoC errata items.

It is worth remembering that known errata have been already fixed (Engineering Samples vs Production) or are tagged as No plan to fix because of there are only two Zynq silicon version: ES or Production (as you can see in the main errata page).

Errata workaround[edit | edit source]

There is an official Xilinx Zynq page with an item list with the errata description and their possible solutions. This is the first page that should be looked at for checking if any issues or errata item is still present and how to cope with.

BSP errata management[edit | edit source]

The bug fix list and the new features for any Petalinux release is available in the following Release Notes Open Source components Atlassian web page. As an example for the 2020.2 release, this is the related release note and Bug fixes documentation.

These notes refer to the Xilinx github software repositories officially maintanined by Xilinx.

Petalinux[edit | edit source]

For any Petalinux release, there are commit IDs and git tags: see https://www.xilinx.com/support/answers/75775.html

As an example for the 2020.2 release, this is the Petalinux table

Petalinux 2020.2


Looking for a specific errata[edit | edit source]

If you are looking for a specific errata, it is required to search in the BSP sources in order to find any relation between the errata and an eventual fix in the BSP code.

errata searching example[edit | edit source]

As an example, we can use the errata SMC - NAND with ECC might not Deassert CS between Data Transactions which is tagged as Device Revision(s) Affected: All, no plan to fix. Refer to (Xilinx Answer 47916) Zynq-7000 SoC Silicon Revision Differences.

  • start searching in the proper Atlassian driver documentation, i.e. Zynq Pl353 SMC and NAND drivers
  • open the Change Log section
  • search for any words like: Deassert, Chip select, etc.
  • you can find in the 2018.3 the fix Implement De-select in chip select
Zynq-7000 2018.3 change log
  • for this fix, there is the related commit list and the related commit for the errata