diff options
author | Mark Hatle <mark.hatle@xilinx.com> | 2022-01-21 13:11:55 -0800 |
---|---|---|
committer | Mark Hatle <mark.hatle@xilinx.com> | 2022-01-23 12:17:00 -0800 |
commit | af6e0c28644acd07890182fdadb34c6370481428 (patch) | |
tree | b6e72e9ba4c38fbbbdae520ec7775b26b3744c82 | |
parent | 1167ecec3dbbda5e1ffffdef723ce26455851072 (diff) | |
download | meta-xilinx-af6e0c28644acd07890182fdadb34c6370481428.tar.gz |
meta-xilinx-core: README.md update to explain recent changes
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
-rw-r--r-- | meta-xilinx-core/README.md | 33 |
1 files changed, 32 insertions, 1 deletions
diff --git a/meta-xilinx-core/README.md b/meta-xilinx-core/README.md index cb6c06c8..8997760c 100644 --- a/meta-xilinx-core/README.md +++ b/meta-xilinx-core/README.md | |||
@@ -27,6 +27,37 @@ This layer depends on: | |||
27 | URI: git://git.openembedded.org/openembedded-core | 27 | URI: git://git.openembedded.org/openembedded-core |
28 | layers: meta | 28 | layers: meta |
29 | 29 | ||
30 | Configuring Machines | ||
31 | ==================== | ||
32 | |||
33 | All machines that use meta-xilinx-tools should be derived from one of the | ||
34 | following: microblaze-generic, zynq-generic, zynqmp-generic, or | ||
35 | versal-generic. | ||
36 | |||
37 | microblaze-generic requries the include of the meta-microblaze layer | ||
38 | |||
39 | zynq-generic, zynqmp-generic and versal-generic each require a device-tree | ||
40 | to be defined. The device tree can be manually passed in via the | ||
41 | variable CONFIG_DTFILE. Note, some items in the system may expect the | ||
42 | device-tree to be referenced to system-top.dtb. | ||
43 | Enabling meta-xilinx-tools will generate the appropriate device tree in most | ||
44 | cases. | ||
45 | |||
46 | Zynqmp-generic requires pmu-firmware. The firmware can be passed directly | ||
47 | as a path to a binary: PMU_FILE, you may use the generic built version | ||
48 | by including meta-xilinx-standalone, the XSCT version by adding | ||
49 | meta-xilinx-tools or the DTB workflow version using | ||
50 | meta-xilinx-standalone-experimental. | ||
51 | |||
52 | Versal-generic requires both PLM and PSM firmware to be specified. They can | ||
53 | be specified as a path to a binary using PLM_FILE and PSM_FILE. Or they can | ||
54 | be generated by including meta-xilinx-standalone, the XSCT version by adding | ||
55 | meta-xilinx-tools or the DTB workflow version using | ||
56 | meta-xilinx-standalone-experimental. Additionally some configurations may | ||
57 | require you to specify the path to a PDI file using PDI_PATH. The XSCT | ||
58 | version will extract the PDI automatically. | ||
59 | |||
60 | |||
30 | Recipe Licenses | 61 | Recipe Licenses |
31 | =============== | 62 | =============== |
32 | 63 | ||
@@ -41,7 +72,7 @@ In order to use recipes that rely on restricted content the `xilinx` license | |||
41 | flag must be white-listed in the build configuration (e.g. `local.conf`). This | 72 | flag must be white-listed in the build configuration (e.g. `local.conf`). This |
42 | can be done on a per package basis: | 73 | can be done on a per package basis: |
43 | 74 | ||
44 | LICENSE_FLAGS_WHITELIST += "xilinx_pmu-rom" | 75 | LICENSE_FLAGS_WHITELIST += "xilinx_pmu-rom-native" |
45 | 76 | ||
46 | or generally: | 77 | or generally: |
47 | 78 | ||