| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
SOC_VARIANT has been remove, we are now only using the YP standard SOC_FAMILY
configuration. The defined families are: zynq, zynqmp, versal and versal-net.
Our decision of breaking up versal-net from versal, is based on the SoC CPU
changes from cortexa72/r5 to cortexa78/r52, thus we're treating it as a
different SoC family.
In order to capture the individual capabilities that we used to handle via
SOC_VARIANT, we have defined the following features (some may have been
previously defined):
- mali400 (zynqmp eg and ev)
- vcu (zynqmp ev)
- rfsoc (zynqmp dr RF capabiltiies)
- aie - (versal ai & premium)
- vdu - (versal ai)
SOC_VARIANT_ARCH and SOC_FAMILY_ARCH are now obsolete and replaced by
MACHINE_ARCH. This is based on the guideline that any recipes that use
MACHINE_FEATURES should be MACHINE_ARCH specific.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
| |
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| |
|
|
|
|
| |
Add the override expected by device-tree and other recipes to each machine.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| |
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| |
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| |
|
|
| |
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
| |
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
| |
Using weaker assingnment for UBOOT_MACHINE to update this value in
petalinux without _forcevariable.
Signed-off-by: Raju Kumar Pothuraju <raju.kumar-pothuraju@xilinx.com>
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
|
| |
zynqmp machines
Update UBOOT MACHINE defconfig to xilinx_zynqmp_virt_defconfig instead of using
custom machine specifc defconfigs.
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
| |
|
|
|
|
|
|
| |
Adding boot.scr to IMAGE_BOOT_FILES so boot.scr is included in the wic
sd card generation, if wic image generation is enabled
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Separating out sample boot.cmd file for the three supported arch (zynq,
zynqmp, versal), Updating devicetree, kernel, ramdisk load addresses for
zynq, and dynamically setting DEVICE_TREE_NAME to either system.dtb or
kernel dtb, depending on if dtg is used or not.
This u-boot-zynq-scr implementation is put in to set the default boot
and boot quicker than having to wait for the distro_bootcmd to cycle to
the correct boot medium. For example, zynq arch has boot_targets set to
"mmc mmc0 qspi usb0 pxe dhcp xilinx" and it takes about 30 seconds to
try the 'xilinx' target which will run the correct bootargs.
To use the boot.scr file, zynqmp boards must have BOOT.bin, Image,
system.dtb, and boot.scr in the boot partition and a rootfs extracted in
the second partition. Zynq boards must have BOOT.bin, uImage,
system.dtb, boot.scr, and uramdisk.image.gz in the boot partition.
(uramdisk.image.gz is the ${IMAGE}.cpio.gz.u-boot in deploy directory)
Adding u-boot-zynq-scr dependency to all zynq and zynqmp machine confs.
Conditionally adding system.dtb to IMAGE_BOOT_FILES for zcu102 to
support boot.scr in qemu flow.
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
|
|
|
Add initial support for the zc1254 evaluation board which has the
following main features:
* RFSoC XCZU28DR-FFVE1156
* Samtec BullsEye cable access to:
* 8 high speed analog-to-digital converters (HSADC)
* 8 high speed digital-to-analog converters (HSDAC)
* 8 GTY transceivers
* 4 GTR transceivers
This patch adds machine configuration file for ZC1254 Evaluation Kit
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 which will also generate SPL
boot.bin
While using SPL flow, you may need to provide additional hack to pass
the PMU config object. This is similar to all ZU+ boards, due to gap in
SPL flow unable to load PMU config object.
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
|
