Introduction
...
| S.No | Platform | Board Name | BSP | BSP File.list |
| 1 | Zynq UltraScale+ MPSoC - RFSoC | zcu111 | xilinx-zcu111-v2019.2-final.bsp | xilinx-zcu111-2019.2-sources.list |
| 2 | Zynq UltraScale+ MPSoC - RFSoC | zcu1275 | xilinx-zcu1275-v2019.2-final.bsp | xilinx-zcu1275-2019.2-sources.list |
| 3 | Zynq UltraScale+ MPSoC - RFSoC | zcu1285 | xilinx-zcu1285-v2019.2-final.bsp | xilinx-zcu1285-2019.2-sources.list |
| 4 | Zynq UltraScale+ MPSoC | zcu106 | xilinx-zcu106-v2019.2-final.bsp | xilinx-zcu106-2019.2-sources.list |
| 5 | Zynq UltraScale+ MPSoC | zcu104 | xilinx-zcu104-v2019.2-final.bsp | xilinx-zcu104-2019.2-sources.list |
| 6 | Zynq UltraScale+ MPSoC | zcu102 | xilinx-zcu102-v2019.2-final.bsp | xilinx-zcu102-2019.2-sources.list |
| 7 | Zynq 7000 | zc706 | xilinx-zc706-v2019.2-final.bsp | xilinx-zc706-2019.2-sources.list |
| 8 | Zynq 7000 | zc702 | xilinx-zc702-v2019.2-final.bsp | xilinx-zc706-2019.2-sources.list |
| 9 | Zynq 7000 | zed | avnet-digilent-zedboard-v2019.2-final.bsp | avnet-digilent-zedboard-2019.2-sources.list |
| 10 | MicroBlaze | kc705 | xilinx-kc705-axi-full-v2019.2-final.bsp | xilinx-kc705-axi-full-2019.2-sources.list |
| 11 | MicroBlaze | kcu105 | xilinx-kcu105-axi-full-v2019.2-final.bsp | xilinx-kcu105-axi-full-2019.2-sources.list |
| 12 | MicroBlaze | ac701 | xilinx-ac701-axi-full-v2019.2-final.bsp | xilinx-ac701-axi-full-2019.2-sources.list |
| 13 | MB | vcu118 | xilinx-vcu118-v2019.2-final.bsp | xilinx-vcu118-2019.2-sources.list |
| 14 | MB | sp701 | xilinx-sp701-v2019.2-final.bsp | xilinx-sp701-2019.2-sources.list |
Obtaining License and Source Code for Root File System in a BSP
A script is provided here for ease of use to a user to fetch the Licenses and Source code of the rootfs Root File System in a given BSP.
The script can be downloaded here fetch.sh
...
./fetch.sh -a aarch64 -r 2019 -f filename.list -t sources
- Boards under "Zynq UltraScale+ MPSoC Board Support Packages" will use aarch64 ARCH
- Boards under "Zynq-7000 SoC Board Support Packages" will use arm ARCH
- Boards under "MicroBlaze Board Support Packages" will user arm microblaze
How does the script work?
...
The input of the script is a manifest file which indicates the rootfs Root File System components that are part of the BSP.
...
udev-extraconf can be ignored as it is startup script of embedded Linux on target and does not have any source code related to it.
watchdog-init has the source script along with licenses in licenses
...
| Code Block |
|---|
Add the below configuration in :
project-spec/meta-user/conf/petalinuxbsp.conf
INHERIT += "archiver"
ARCHIVER_MODE[src] = "original"
COPYLEFT_LICENSE_INCLUDE =""
COPYLEFT_LICENSE_EXCLUDE ="" |
...
| Code Block |
|---|
petalinux-build
All the source code is deployed : build/tmp/deploy/sources/
and license files is deployed : build/tmp/deploy/licenses/
Sometimes TMPDIR value is not as mentioned above.
Check build/conf/plnxtool.conf and get the TMPDIR value
Navigate (cd command) to TMPDIR to find the sources and licenses
|
Please note:
Build times are slower while generating licenses and source files
FAQ
- Why and who needs this ?
Users who have concerns on the Licenses or Source code in a given BSP Root File System should use the methodology described here to check if it meet their requirement.
...
Users who has their own procedures to check Licenses and Source code for their BSP their Root File System development might not need this
...
Users who want to verify the BSP contents and check all the Licenses before using the BSP Root File System can use the script published here
...
The prebuilt images in each BSP has all the licenses in of the rootfs Root File System at /usr/share/licenses in the Root File System.
The manifest file which list all the rootfs Root File System components in a BSP is also available in prebuilts.
...
The same is also available at https://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/embedded-design-tools.html
The "Open Source License and Source code" section contains all the Licenses and Source code files
- What is different between the information in the PetaLinux Tool/BSP download area vs the script provided here?
The script helps to extract just the information of Licenses and Source code related to a given BSP Root File System.
In addition, the script provided here is an added flexibility for an user to fetch Licenses or Source code for a given BSP BSP Root File System even before using the PetaLinux Tool or BSP.
...