Vivado Software SOM Connector Abstraction
The SOM board files introduce a SOM connector abstraction that allows the hardware
configuration to focus on SOM connector level physical mapping. This is intended to help
eliminate the need for the carrier card designer to have to create a physical pin translation table.
The SOM connector infrastructure uses the convention of: <connector name> + <_> +
<connector_pin_number>. For example, a SOM connector pin name of som240_1_c18
refers to the pin C18 of the SOM240_1 connector. Using this convention and the XDC get ports
functionality, a carrier card constraints file can be described in terms of a SOM physical interface
when combined with a SOM constraint file that captures the Zynq UltraScale+ MPSoC to SOM
connector pin definition.
SOM Vivado Tools XDC Files
The SOM Vivado board file includes an XDC file that captures the Zynq UltraScale+ MPSoC
package mapping to SOM connector pin definitions. This file can be used by the carrier card
designer to identify the full SOM plus carrier card design constraints.
A carrier card designer can also refer to the KV260 Starter Kit carrier card XDC files for an
example implementation of a decoupled SOM and carrier card constraint definition.
UG1091 (v1.0) April 20, 2021
Carrier Card Design for Kria SOM
Chapter 4: Hardware Configuration Using Vivado Tools
Send Feedback
www.xilinx.com
56
Need help?
Do you have a question about the Kria K26 SOM and is the answer not in the manual?
Questions and answers