summaryrefslogtreecommitdiffstats
path: root/meta-xilinx-core/conf/machine
Commit message (Collapse)AuthorAgeFilesLines
* soc-tune-include: Add cortex-r5{,2}hf and cortex-a78 supportMark Hatle2024-03-181-0/+4
| | | | Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* meta-xilinx-core: zynqmp-generic.conf: Use default QB_XILINX_SERIALMark Hatle2023-12-121-1/+3
| | | | | | | A default (blank) QB_XILINX_SERIAL will fall back to the runqemu default which works correctly for this board. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* versal-generic.conf: Remove obsolete DTBsMark Hatle2023-10-261-3/+0
| | | | Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* various machines: Change qemu serial port configuration for nanbieldMark Hatle2023-10-266-7/+58
| | | | | | | | | | | | | | | | | As of Yocto Project nanbield, if a -serial is pass in QB_OPT_APPEND the runqemu may add additional null entries (padding) or simply skip further setup. Due to this, emulated platforms where the first hardware serial port is not used in Linux need specific "-serial null" settings, but with the new rules also need the real serial port defined (this can no longer be assumed.) The downside of this new approach is all consoles must be defined, so we can not rely on runqemu adding "-serial mon:<device>", as now assume the primary usage is stdio (nographic/serial port) settings. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* meta-xilinx-core: zynq-generic: Remove gdb port usageMark Hatle2023-10-251-1/+0
| | | | | | | | | While including a default gdb in the QEMU configuration might be useful, it does require a static port that will prevent multiple QEMU sessions from running in parallel. If the user wants GDB support, they will need to manually add this on the runqemu command line. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* zynqmp-generic: Ensure qemu-devicetrees is install for qemu usageMark Hatle2023-10-251-1/+1
| | | | | | | | testimage requires qemu, qemu requires qemu-devicetrees:do_deploy. Adjust the dependencies to specifically list do_deploy and not the authomatic do_install. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* versal-generic: Fix testimageMark Hatle2023-10-251-2/+2
| | | | | | | | qemu-devicetrees and the extracted cdo are required for QEMU booting. These are only populated after do_deploy, so make sure our dependency clearly depends on do_deploy and not the (automatic) do_install. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* README: Update README on using ATF_CONSOLESandeep Gundlupet Raju2023-08-311-1/+1
| | | | | | | Update README on using ATF_CONSOLE instead of ATF_CONSOLE_DEFAULT. Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* versal-net-generic: Make it clear versal-net is not supported in 2023.2Mark Hatle2023-08-311-0/+2
| | | | Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* machine-xilinx-default.inc: use installed IMAGE_BOOT_FILESTrevor Woerner2023-08-181-22/+27
| | | | | | | | | | | IMAGE_BOOT_FILES is a whitespace-separated list of entries specifying files to be installed into the boot partition. Entries can change the installed filename by specifying the destination name after a semicolon (e.g. u-boot.img;uboot). Make sure to use the installed filename when scanning IMAGE_BOOT_FILES if one is provided, otherwise use the specified file as-is. Signed-off-by: Trevor Woerner <trevor.woerner@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* README: Update the docs on variablesSandeep Gundlupet Raju2023-07-201-6/+69
| | | | | | | | | | Update READE docs on list of variables used in machine conf. Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com> Fixed a couple of typos Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* microblaze-generic: Update machine conf file using gen-machineconf toolSandeep Gundlupet Raju2023-07-201-10/+11
| | | | | | | | | | 1. Update machine conf file using gen-machineconf tool by parsing latest kcu105 xsa and reorder the variables to match the gen-machineconf tool output. 2. Add axi-quad-spi as kcu105 reference xsa has this ip enabled. Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* machine: Add SERIAL_CONSOLES_CHECK for sysvinit onlySandeep Gundlupet Raju2023-07-205-4/+3
| | | | | | | | | | SERIAL_CONSOLES_CHECK is supported only for sysvinit and default INIT Manager is systemd, hence move this variable from machine conf files to machine-xilinx-default inclusion and set only if DISTRO_FEATURES is sysvinit. Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* microblaze-generic: Add target fpu hard TUNE FEATURESSandeep Gundlupet Raju2023-07-191-1/+1
| | | | | | | | Since microblaze-generic machine conf file uses kcu105 xsa, target fpu hard TUNE_FEATURES were missing hence add it. Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* *-generic.conf: Fix hardcoded dependencies in the generic machinesMark Hatle2023-05-174-6/+4
| | | | | | | | Each of these dependencies need to be based on preferred_provider. A hard dependency on u-boot-xlnx-uenv is not required to use qemu. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* zynqmp-generic: Emulate FSBL hand-off for qemu bootMark Hatle2023-03-161-0/+28
| | | | | | | | | | | | | | | Qemu boots by loading ATF and jumping to it directory. A recent change adds a verification that the data structure passed by the FSBL is correct in a 'mode 5' (SD card) boot. If it's not valid ATF will fail to continue to boot. (JTAG, 'mode 0' boot will proceed but other system behavior changes.) In order to emulate the FSBL handoff to ATF, we need to populate a data structure in fffc0000, and tell ATF to look at that address. See the comments for more information. This also ends up hard-coding the u-boot address. If it changes booting will fail. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* machine-xilinx-default.inc: Set FIT_CONF_DEFAULT_DTB only for SDT flowRaju Kumar Pothuraju2023-03-031-1/+1
| | | | | | | | | | | | | system.dtb is symlink to actual dtb file which is not present in linux sysroot path. If specified dtb name for FIT_CONF_DEFAULT_DTB not present fitimage.bbclass will not set default configuration variable. To fix this, setting FIT_CONF_DEFAULT_DTB to empty if CONFIG_DTFILE not set(xsct flow) so that which dtb comes first that will be the default configuration in fitimage creation. Signed-off-by: Raju Kumar Pothuraju <rajukumar.pothuraju@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* machine-xilinx-default.inc: defining default dtb for fitimageVaralaxmi Bingi2023-02-231-0/+4
| | | | | | | | | | | | When we tried to create fitimage it will pick the dtb from linux recipe-sysroot path. There are multiple dtb files in linux sysroot in sdt case and we did not specified any default dtb file to package in fitimage and it was picking baremetal dtb file which is leading to kernel panic. There is a variable in yocto to specify the default dtb file to pick for fitimage FIT_CONF_DEFAULT_DTB. If we specify the above then the fitimage is generated properly and able to boot successfully. Signed-off-by: Mark Hatle <mark.hatle@amd.com> Signed-off-by: Varalaxmi Bingi <varalaxmi.bingi@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* Revert "machine-xilinx-default: Implement default FIT_CONF_DEFAULT_DTB"Mark Hatle2023-02-221-7/+0
| | | | This reverts commit 6ad9836940fa9c3541b5339c84d6d86e36734e24.
* machine-xilinx-default: Implement default FIT_CONF_DEFAULT_DTBMark Hatle2023-02-221-0/+7
| | | | | | | | | | | | | When using a system device tree build there will be more then one device-tree that is constructed. If a fit image is constructed, then an DTB needs to be selected. We use the CONFIG_DTFILE as the default, which should inherit from the SYSTEM_DTFILE. The default for SYSTEM_DTFILE is empty as a fallback which should restore the default behavior of first DTB found is the one used. This also has ramifications for other recipes that use DTB files and unifies everything. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* machine-xilinx-qemu.inc: Disable qemu-xilinx, prefer Yocto qemu on targetSandeep Gundlupet Raju2023-02-011-1/+0
| | | | | Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* zynqmp-generic: Set variables for QEMU HW PS and PMU DTBSandeep Gundlupet Raju2023-01-251-2/+8
| | | | | | | | Set variables for QEMU DTB PATH, PS DTB and PMU DTB for zynqmp_generic, this allows user to use different QEMU HW DTB to match their board. Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* qemu-xilinx-system-native: Move pmu-rom enablement to recipeMark Hatle2023-01-161-3/+0
| | | | | | | | | | | | Setting the pmu-rom being required by QEMU within the machine.conf will cause the recipe's hash to change, which can cause a ripple effect causing other things to rebuild. Moving this to the recipe, and switching it on based on what licenses the user allows will avoid this conflict. Additionally add a warning message to the xilinx-vars.bbclass if the user has not enabled the license. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* machine-xilinx-default.inc: Set default virtual/dtb providerMark Hatle2023-01-111-0/+3
| | | | Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* u-boot-xlnx: Update 2023.1 versionMark Hatle2023-01-111-0/+3
| | | | | | | | | | | Add u-boot-tools-xlnx as well. Update the PREFERRED VERSION to select the new u-boot version, add preferred provider for u-boot-tools to be u-boot-tools-xlnx. Needed to split the microblaze configs to older and newer versions as well. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* microblaze-generic: Make it clear it uses 2GB of memoryMark Hatle2023-01-111-0/+1
| | | | Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* zynqmp-generic: Add a comment explaining network configMark Hatle2023-01-111-0/+1
| | | | Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* versal-generic: Fix network device configurationMark Hatle2023-01-111-2/+2
| | | | Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* machines: Remove LOADADDR from kernel argsMark Hatle2023-01-103-6/+0
| | | | | | | The arguments will be added by gen-machine-conf, if the user requires them. The default configurations do not use these. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* xilinx-deprecated: Remove support for BOARD and BOARD VARIANTMark Hatle2023-01-065-50/+0
| | | | | | | | | | | We still warn the user. This will likely be moved to fatal in the near future, but this would impact some automated test cases so preserve it as a warning for now. Also remove all of the support infrastructure for the BOARD/BOARD_VARIANT values. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* microblaze-generic: Update machine conf file using gen-machineconf toolSandeep Gundlupet Raju2023-01-061-17/+21
| | | | | | | | | | | 1. Update machine conf file using gen-machineconf tool by parsing kcu105 xsa. 2. Move variables which changes based on xsa before required inclusion file to handle pre-expansion values. 3. Use UIMAGE_LOADADDR in KERNEL_EXTRA_ARGS instead of LOADADDR. Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* versal-net-generic: Update machine conf file using gen-machineconf toolSandeep Gundlupet Raju2023-01-061-2/+13
| | | | | | | | | | 1. Update machine conf file using gen-machineconf tool by parsing versal-net static xsa. 2. Move variables which changes based on xsa before required inclusion file to handle pre-expansion values. Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* versal-generic: Update machine conf file using gen-machineconf toolSandeep Gundlupet Raju2023-01-061-11/+41
| | | | | | | | | | | 1. Update machine conf file using gen-machineconf tool by parsing vck190 xsa. 2. Use TFA_BL33_LOAD for TF-A preloadded bl33 base address. 3. Move variables which changes based on xsa before required inclusion file to handle pre-expansion values. Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* zynq-generic: Update machine conf file using gen-machineconf toolSandeep Gundlupet Raju2023-01-061-18/+50
| | | | | | | | | | | | 1. Update machine conf file using gen-machineconf tool by parsing zc702 xsa. 2. Add UIMAGE_LOADADDR to KERNEL_EXTRA_ARGS. 3. Move variables which changes based on xsa before required inclusion file to handle pre-expansion values. 4. Add uImage to IMAGE_BOOT_FILES. Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* zynqmp-generic: Update machine conf file using gen-machineconf toolSandeep Gundlupet Raju2023-01-061-44/+85
| | | | | | | | | | | | | | 1. Update machine conf file using gen-machineconf tool by parsing zcu102 xsa. 2. Use TFA_BL33_LOAD for TF-A preloadded bl33 base address. 3. Move variables which changes based on xsa before required inclusion file to handle pre-expansion values. 4. Remove uEnv.txt from IMAGE_BOOT_FILES. 5. Disable U-boot SPL boot by default. User has to set explicitly to use it. Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* soc-tune-include.inc: Make crypto tune availableChristian Kohn2022-12-211-0/+1
| | | | | | | | Make cortexa72-cortexa53-crypto tune available so it can be easily turned on by the user. Signed-off-by: Christian Kohn <chris.kohn@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* machine: Refactor mali400 supportMark Hatle2022-12-162-12/+22
| | | | | | | | | | | | | | | Define a new MACHINE_FEATURE called mali400 that is used to determine if the hardware has a mali400. Define a new DISTRO_FEATURE called libmali, as well as one called lima to indicated which configuration to build. Both the MACHINE_FEATURE and DISTRO_FEATURE must be enabled to activate the new code. This means any recipe that gets libmali-xlnx is expected to be: PACKAGE_ARCH = "${MACHINE_ARCH}" Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* soc-zynqmp: Move from vcu override to MACHINE_FEATURESMark Hatle2022-12-161-5/+6
| | | | | | | | | | The override was not being used anywhere, this was just acting as a potential tigger for recipes. Instead, we define the MACHINE_FEATURES vcu and will use that to determine if VCU functionality is enabled. By default the zynqmp-ev has VCU feature present. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* u-boot-xlnx-scr: Load openamp.dtbo if presentMark Hatle2022-12-051-0/+1
| | | | | | | Loading the devicetree/openamp.dtbo if present and merge into the loaded system dtb. (Note, not all boot modes support this behavior.) Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* xilinx-default-sd.wks: Enable a new rootfs based sd/mmc imageMark Hatle2022-12-024-5/+3
| | | | | | Switch the machine files to use the new 'xilinx-default-sd.wks' file. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* machine-xilinx-default.inc: Enable both bootimg and rootfs image /bootMark Hatle2022-12-021-6/+30
| | | | | | | | | | | | | | IMAGE_BOOT_FILES and WKS_FILE_DEPENDS are used in the bootimg technique. THis ensures that an bootimg will continue to work in the future. The MACHINE_ESSENTIAL_EXTRA_RDEPENDS is also filled out based on the same IMAGE_BOOT_FILES. This ensures that the packages used to generate the filesystem's /boot partition is matching and full. The end result of both approaches is slightly different, but the rootfs method must be used for on-target package upgrade to work properly. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* machine-xilinx-default.inc: Update the IMAGE_BOOT_FILES devicetree/*.dtbMark Hatle2022-12-021-1/+1
| | | | | | | | | | Previously the system was copying the boot files directly to the /boot partition. This does not match the package behavior, where dtbs exist in /boot/devicetree. Adjust the configuration to keep them in the subdirectory. This also adjust uEnv.txt and or other users of the image-wic-utils functions. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* meta-xilinx-core: Rename u-boot scripts and uenv packagesSandeep Gundlupet Raju2022-12-025-16/+24
| | | | | | | | | In meta-xilinx-core u-boot-zynq-scr and u-boot-zynq-uenv recipes are renamed to u-boot-xlnx-scr and u-boot-xlnx-uenv. Hence change these in all the configuraiton and inclusion files. Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* microblaze-generic: Switch default machine to kcu105Sandeep Gundlupet Raju2022-11-241-12/+46
| | | | | | | | | | 1. Switch default machine from kc705 to kcu105. 2. Move YAML configs to microblaze-generic file with weak assignments. 3. Add bitstream, bootloader and u-boot-zynq-scr to EXTRA_IMAGEDEPENDS. 4. Use QB_KERNEL_CMDLINE_APPEND to pass bootargs to QEMU. Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* qemu-xilinx-helper-native: Remove, replace with standard upstream versionMark Hatle2022-11-241-1/+0
| | | | | | | | | qemu-system-helper contains support for general system items, there is no reason for us to provide our own version. We can then add a dependency for the specific xilinx multiarch component as needed to the system-native versions. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* Merge remote-tracking branch 'langdale' into 2023Mark Hatle2022-11-1515-21/+206
|\ | | | | | | Signed-off-by: Mark Hatle <mark.hatle@amd.com>
| * zynqmp-generic: Move default soc variant to cg to match zynqmp-genericMark Hatle2022-11-102-5/+2
| | | | | | | | Signed-off-by: Mark Hatle <mark.hatle@amd.com>
| * conf/machine: Add all of the zynqmp and versal variantsMark Hatle2022-11-1010-2/+110
| | | | | | | | Signed-off-by: Mark Hatle <mark.hatle@amd.com>
| * versal-net-generic: Cleanup overridesMark Hatle2022-11-101-6/+0
| | | | | | | | Signed-off-by: Mark Hatle <mark.hatle@amd.com>
| * conf/machine: Better document inheritence expectationsMark Hatle2022-11-103-9/+95
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | See the README files for specific requirements, but we have designed the machine configurations into an inheritance model. This module can be further broken into 3 distinct categories of variables: 1 - Variables that MUST be declared BEFORE inheriting the base machine 2 - Variables that SHOULD be declared BEFORE inheriting the base machine, as they are commonly overridden. (This will need continual review.) 3 - All remaining variables that should only be declared in the machine .conf file, and MUST be declared AFTER inheriting the base machine. Signed-off-by: Mark Hatle <mark.hatle@amd.com>