xdc files can both be found on Kria documentation site. xdc file to create mappings between Xilinx MPSoC pins and connectors, as well as adding constraints. Developers will need to create a custom board file for their custom carrier card, and they can use KV260 as an example.ĭevelopers also need. Information on generating custom Vivado board files and where to place them can be found in UG895. K26C/K26I, and example KV260 board files can also be found here (Please note that board files are available in 21.1 as well, though starting in 2021.2, board xmls capture pcb_min_delay/pcb_max_delay for all pins extended to carrier card). In example carrier card projects, we have created two board configuration files used by Vivado to create board related configurations - one for K26 and one for KV260. wic image containing boot.src, Image, .u-boot, system.dtb, Input: Vivado K26 SOM board file, customer defined carrier card board configuration Developers can then use the artifacts to create applications to run on top of the base Linux, using the previously discussed workflows: Vitis Accelerator Flow, Vitis Platform Flow, or Vivado Accelerator Flow.Īssumption: Using SOM K26 with developer defined carrier card
If using Linux, developers then create a Petalinux project to generate boot and OS images for booting Linux. After creating the integrated SOM + CC configuration, a. Developers then design in their specific custom MIO and PL based physical interfaces to create their own custom HW configuration while following the Kria CC Design Guide ( UG1091). The K26 board file does not contain any information specific to a carrier card.
The K26 board file contains the MIO configuration defined by the SOM HW design, and provides a minimal HW configuration to boot to Linux. Developers creating their own carrier card will create a Vivado project using the Xilinx provided K26 production SOM Vivado board file as a starting point.
0 kommentar(er)
