summaryrefslogtreecommitdiffstats
path: root/meta-xilinx-bsp/recipes-bsp/embeddedsw
Commit message (Collapse)AuthorAgeFilesLines
* fsbl-firmware_%.bbappend: Add generation of pmu-confJohn Vicky Vykuntapu2024-10-231-7/+3
| | | | | | | | | In SDT flow pmu-conf.bin is missing and observing qemu boot failure on kria SOM. Therefore, removed the SYSTEM_DTFILE flag check so, this way it generates for both xsct and sdt Signed-off-by: John Vicky Vykuntapu <johnvicky.vykuntapu@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* fsbl-firmware: Update integrationMark Hatle2023-04-101-4/+8
| | | | | | | | Set COMPATIBLE_HOST more loosely to allow for baremetal builds. Update processing to use OBJCOPY and add additional deploy names. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* meta-xilinx-bsp: recipes-bsp: embeddedsw: fsbl-firmware: Fix compilation ↵Appana Durga Kedareswara rao2023-04-071-2/+6
| | | | | | | | | error in system device-tree flow Update checks for system device-tree flow. Signed-off-by: Appana Durga Kedareswara rao <appana.durga.kedareswara.rao@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* embeddedsw:add the pmu-conf extraction from fsblSwagath Gadde2022-11-101-0/+12
| | | | | | | | QEMU for all zynqmp platforms requires pmu-conf from fsbl binary section. Signed-off-by: Swagath Gadde <swagath.gadde@amd.com> Signed-off-by: Shubhangi Mahalle <shubhangi.shrikrushna-mahalle@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* Initial restructure/split of meta-xilinx-bspMark Hatle2022-01-144-241/+0
| | | | | | | | | | Create a new meta-xilinx-core, move core functionality to the core, keeping board specific files in the bsp layer. zynqmp-generic changed from require <board> to include, so if meta-xilinx-bsp is not available it will not fail. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* Convert to new override syntaxSai Hari Chandana Kalluri2021-09-284-17/+17
| | | | | | | | | | This is the result of automated script (0.9.0) conversion: oe-core/scripts/contrib/convert-overrides.py . converting the metadata to use ":" as the override character instead of "_". Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* Enabling bootbin wiring for decoupling flow for zynqmp and versalJaewon Lee2021-09-274-52/+20
| | | | Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
* fsbl/pmufw/plmfw/psmfw: Switch to BOARDVARIANT_ARCHMark Hatle2021-07-144-8/+12
| | | | | | | | | Issue: CR-1099768 Each of these are really board specific, as each can be configured in many different ways. Switch this to be board specific to avoid conflicts. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* Various: Fix eSDK hash changesMark Hatle2021-07-143-0/+3
| | | | | | | | | | | | The various *fw.bb Linux recipes need to exclude the PLM_DEPLOY_DIR from hash calculations. This location can change, but the actual value does not matter. Move plm-firmware, psm-firmware, pmu-firmware to use IMAGE_VERSION_SUFFIX (and the associate image-artifact-names class) by default. This matches how modern deployed components should work. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* fsbl/fsbl-firmware: Split the packaging and building of the fsblMark Hatle2021-07-141-0/+67
| | | | | | | | | | | | | | | | | | | | | Following the example of the psm, pmu and plm, we split the FSBL into both a packaging component (fsbl) and the build of the firmware (fsbl-firmware). This also adds an additional multilib, fsbl-fw, that is used to handle the multiconfig version, as the Linux and baremetal builds are done differently. Typical build approach is: Add to local.conf: BBMULTICONFIG += "fsbl-fw" then build using: MACHINE=zynqmp-generic bitbake fsbl Note, while 'zynq' is implemented, it does not currently function. To build the fsbl for zynq, you must use the meta-xilinx-tools version. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* plmfw/psmfw: Fix missing do_deploy addtask, and local checkMark Hatle2021-07-142-2/+9
| | | | | | | | If the fw is pulling from the same config, we don't want to re-deploy the firmware (it will fail.) Otherwise copy it from the other config into our config, as other tools may look for it. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* embeddedsw; Fixups for missed plm and psm issuesMark Hatle2021-07-141-1/+1
| | | | Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* embeddedsw: Rework plm/pmu/psm firmware and Linux packagingMark Hatle2021-07-143-0/+192
In order to allow standalone (meta-xilinx-standalone), XSCT (meta-xilinx-tools), and future items to work in the same way the recipes have been restructured. A *-firmware recipe will generate the firmware and stage it to do_deploy. A *fw recipe will take the deployed version and package it for the Linux side of things. This allows the firmware generation to be easily extended without requiring packaging knowledge. Similarly packaging can be extended for alternative boot/upgrade mechanisms as required. In all cases, the MACHINE configuration will specify the default way the components are to be built, along with the names of the item in the deploy directory. The PLM/PSM/PMU_IMAGE_NAME is the name for the generated firmware. PLM/PSM/PMU_DEPLOY_DIR is the path to the constructed firmware. This along with the IMAGE_NAME above can be used to specify the location of an externally generated set of firmware. Addtionally the dependencies for building the plmfw/psmfw/pmufw can be changed easily using PLM/PSM/PMU_DEPENDS and PLM/PSM/PMU_MCDEPENDS. The former specifies dependencies in the same multiconfig, while the later allows the component to require another multiconfig to have finihed. The system has a referenced default, if multiconfig is enabled it will automatically use it, otherwise it will try to use the recipe in the main configuration. (This will fail unless meta-xilinx-tools is available.) Also two multiconfigs hve been implemented: versal-fw and zynqmp-pmufw They can be enabled using BBMULITCONFIG += "zynqmp-pmufw" or versal-fw. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-07-19 22:33:51 +0000