diff options
author | Mark Hatle <mark.hatle@amd.com> | 2024-06-03 08:45:59 -0600 |
---|---|---|
committer | Mark Hatle <mark.hatle@amd.com> | 2024-06-03 08:45:59 -0600 |
commit | 955eaa968ab0ec0a4fc8d109f6eb0457844d6f00 (patch) | |
tree | 5d83dde7bc904c05e339f644c75aa44e66f1c977 | |
parent | cfd5ebb6b575530a48782a27cdf19a8b3974072d (diff) | |
download | meta-xilinx-955eaa968ab0ec0a4fc8d109f6eb0457844d6f00.tar.gz |
zynqmp-generic.conf: Fix qemu pmu firmware path
The path specified is the internal firmware path. This could be in a the
current deploy directory, a multiconfig deploy directory or some other place
directly specified by the user.
When using the sstate-cache, the build of the component in the a multiconfig
directory can be skipped, causing an error to find the component.
Instead we want to use OUR deploy directory, which will always have a copy
of the pmu firmware, no matter how it was constructed or packaged.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
-rw-r--r-- | meta-xilinx-core/conf/machine/zynqmp-generic.conf | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/meta-xilinx-core/conf/machine/zynqmp-generic.conf b/meta-xilinx-core/conf/machine/zynqmp-generic.conf index 055c7e5b..b5a2f832 100644 --- a/meta-xilinx-core/conf/machine/zynqmp-generic.conf +++ b/meta-xilinx-core/conf/machine/zynqmp-generic.conf | |||
@@ -150,7 +150,7 @@ QB_PMU_OPT = " \ | |||
150 | -display none \ | 150 | -display none \ |
151 | -hw-dtb ${QEMU_HW_DTB_PMU} \ | 151 | -hw-dtb ${QEMU_HW_DTB_PMU} \ |
152 | -kernel ${PMU_ROM} \ | 152 | -kernel ${PMU_ROM} \ |
153 | -device loader,file=${PMU_FIRMWARE_DEPLOY_DIR}/${PMU_FIRMWARE_IMAGE_NAME}.elf \ | 153 | -device loader,file=${DEPLOY_DIR_IMAGE}/${PMU_FIRMWARE_IMAGE_NAME}.elf \ |
154 | -device loader,addr=0xfd1a0074,data=0x1011003,data-len=4 \ | 154 | -device loader,addr=0xfd1a0074,data=0x1011003,data-len=4 \ |
155 | -device loader,addr=0xfd1a007C,data=0x1010f03,data-len=4 \ | 155 | -device loader,addr=0xfd1a007C,data=0x1010f03,data-len=4 \ |
156 | " | 156 | " |