summaryrefslogtreecommitdiffstats
path: root/meta-xilinx-bsp/conf/machine/vck190-versal.conf
Commit message (Collapse)AuthorAgeFilesLines
* meta-xilinx-bsp: Move XSCT bsps to meta-xilinx-toolsMark Hatle2024-09-041-45/+0
| | | | Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* meta-xilinx-bsp:machine: Use ATF_CONSOLE instead of ATF_CONSOLE_DEFAULTSandeep Gundlupet Raju2023-08-311-1/+1
| | | | | | | | | | | In arm-trusted-firmware recipe, ATF_CONSOLE_DEFAULT variable has override and setting this variable value from local.conf and machine.conf will not be effective during variable pre-expansion values. Hence use ATF_CONSOLE instead of ATF_CONSOLE_DEFAULT in machine conf files. Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* machine: Update machine conf file using gen-machineconf toolSandeep Gundlupet Raju2023-07-201-1/+1
| | | | | | | | | | | | | 1. Add missing space to append operation for machine files generated by gen-machineconf tool. 2. Update all machine conf file using gen-machineconf tool by parsing latest xsa. a. Reorder the variables to match the gen-machineconf tool output. b. Add any missing or new variables. 3. Remove machine overrides for XSCTH_PROC variable. Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* machine: Remove BOARD overrides from xilinx bsp layerSandeep Gundlupet Raju2023-06-231-4/+0
| | | | | | | | Using BOARD variable are deprecated, hence remove it. Machine conf files using BOARD overrides now will be replaced with machineoverrides. Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* versal: Update machine conf file using gen-machineconf toolSandeep Gundlupet Raju2023-01-131-6/+45
| | | | | | | | | | | | | | 1. Update below versal eval board machine conf file using gen-machineconf tool by parsing respective xsa. - vck190-versal - vck5000-versal - vmk180-versal 2. Move variables which changes based on xsa before required inclusion file to handle pre-expansion values. 3. Use use soc variant based generic machine inclusion. Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* meta-xilinx-bsps: Add board-style overrides to select correct componentsMark Hatle2022-01-141-0/+3
| | | | | | Add the override expected by device-tree and other recipes to each machine. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* meta-xilinx-bsp: Remove extra entries, already set by the included defaultsMark Hatle2022-01-141-64/+0
| | | | Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* meta-xilinx-bsp: Convert all BSPs to use the generic configsMark Hatle2022-01-141-4/+2
| | | | Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* Initial restructure/split of meta-xilinx-bspMark Hatle2022-01-141-5/+5
| | | | | | | | | | 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>
* manual changes for overrides syntax fixesSai Hari Chandana Kalluri2021-09-281-1/+1
| | | | Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* Convert to new override syntaxSai Hari Chandana Kalluri2021-09-281-4/+4
| | | | | | | | | | 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>
* embeddedsw: Rework plm/pmu/psm firmware and Linux packagingMark Hatle2021-07-141-5/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* SOC_VARIANT versal: removing previously required prepended '-'Jaewon Lee2021-07-141-1/+1
| | | | | | | Removing the need to prepend a '-' to SOC_VARIANT for versal variants for ex. '-ai-core' Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
* Cleanup QB_MACHINE for xilinx machinesSai Hari Chandana Kalluri2020-12-221-1/+0
| | | | | | | Pick correct QB_MACHINE name for each of the machine from qemuboot-xilinx.bbclass. Remove QB_MACHINE from machine.conf Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* vck190-versal.conf: Setting SOC_VARIANT to ai-coreJaewon Lee2020-09-081-0/+2
| | | | | | Setting vck190-versal board's SOC_VARIANT to ai-core Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
* versal confs: cleaning up unnecessary file loading in runqemu commandJaewon Lee2020-05-081-3/+0
| | | | | | | | | | | | | | | | Removing dtb fatload in boot.scr and removing unnecessary image, dtb, rootfs loading in runqemu command dtb is being loaded through boot.bin for versal so fatload through boot.scr and loading into memory through runqemu commands are not necessary (before this change dtb was essentially being loaded three times) image will be fatloaded through boot.scr (provided in sd image) rootfs is provided through sd image Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
* versal confs: Upping RAM in runqemu command to 8G for versal boardsJaewon Lee2020-05-081-1/+1
| | | | | | | | Recent requirement for Versal has changed, we now we need to supply 8G so changing QB_MEM to 8G from 4096. This will fix issue of runqemu hanging at 'Starting Kernel' Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
* machines: Remove default SERIAL_CONSOLES_CHECKMark Hatle2020-04-031-1/+0
| | | | | | | | | | | | | | | | | | By default the machines should not check and remove declared consoles that are not available on first boot. It's up to the user to add this to their build configuration. The recommended user behavior is: SERIAL_CONSOLES_CHECK = ${SERIAL_CONSOLES} but the side effect of this is that if the device configuration changes after the first boot, the additional devices will not be available. (Note, this may result in warning messages with getty unable to connect to certain devices.) Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* machines: Allow the user to override SERIAL_CONSOLESMark Hatle2020-04-031-1/+1
| | | | Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* machines: Move from SERIAL_CONSOLE (deprecated) to SERIAL_CONSOLESMark Hatle2020-04-031-1/+1
| | | | | | | Usage of 'SERIAL_CONSOLE' was deprecarted in late 2013. Move to the using 'SERIAL_CONSOLES', where the format is slightly different. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* xilinx-qemu: Move -multiarch extension to the machine-xilinx-qemuMark Hatle2020-03-171-3/+0
| | | | | | | | All xilinx BSPs that support qemu should use the machine-xilinx-qemu.inc file. So move all references to the -multiarch extension into that location. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* meta-xilinx-bsp: cleanup qemu referencesMark Hatle2020-03-171-3/+0
| | | | | | | | | | Move IMAGE_CLASSES setting to common machine-xilinx-qemu.inc, also add preferred provider for the xilinx specific qemu components. Adjust the various BSPs to remove duplicate references to these and non-Xilinx versions of qemu. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* meta-xilinx-bsp: remove redundant PREFERRED_PROVIDERMark Hatle2020-03-131-2/+0
| | | | | | | PREFERRED_PROVIDER_virtual/kernel and PREFERRED_PROVIDER_virtual/bootloader are normally set by machine-xilinx-default.inc. Only set these if necessary. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* meta-xilinx-bsp: rename machine-xilinx-override to xilinx-soc-family.incMark Hatle2020-03-131-1/+0
| | | | | | | | | | The machine-xilinx-override is really just an extension to the standard soc-family.inc file. So rename this, move the include of soc-family.inc to this file, move the include to the soc includes to each soc file, and finally adjust the machines to remove machine-xilinx-override as it's no longer necessary. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* meta-xilinx-bsp: Remove default valuesMark Hatle2020-03-131-2/+0
| | | | | | Remove the default values, as they are already set by the soc include. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* meta-xilinx-bsp: Rename soc configuration masquerading as a tune fileMark Hatle2020-03-131-1/+1
| | | | | | | The tune files were really soc configuration files. Tune files should only specify toolchain flags that affect optimiation and abi. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* vck190-versal.conf: Add deploy dir for psm and plm firmwareSai Hari Chandana Kalluri2019-12-091-0/+3
| | | | | | Add deploy dir path for plm and psm to support multiconfig builds. Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* plm_2019.2.bb: recipe to build plm standaloneSai Hari Chandana Kalluri2019-12-091-0/+3
| | | | | | | | Add recipe to build plm as standalone component. plm is platform loader and manager for versal devices.It performs boot and configuration of the Versal ACAP device. Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* vc-p-a2197-00-versal.conf:Add versal Tenzing +SE1 board configurationManjukumar Matha2019-12-091-0/+86
Add support to build images for vc-p-a2197-00-versal Tenzing board + SE1 board configuration vck190-versal.conf: Rename vc-e-a2197-00-versal to vck190-versal Rename vc-e-a2197-00-versal machine configuration to vck190-versal with required setting of board specific yocto variables needed for compilation of bootloader, kernel and device-tree. - linux-xlnx is the kernel provider - u-boot-xlnx is the u-boot provider Signed-off-by: Swagath Gadde <swagathg@xilinx.com> Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-08-07 11:50:41 +0000