| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
This recipe did not provide anything useful for the target, so adjust to only
run native and nativesdk.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Generic machines no longer depend on firmware (ESW) components. Thus they
will now build a full Linux system, where possible, without XSCT or SDT
modes.
It is up to the specific machine.conf files to enable the correct build
flow and that will enable the necessary firmware dependencies for the SoC.
This also means HDF_MACHINES is no longer required.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Zynq-7000 SDT and XSCT runqemu doesn't come up due to conditional
assignment in both machine-xilinx-qemu.inc and zynq-generic.conf file.
With that said the value set in machine-xilinx-qemu.inc will be used
during pre-expansion value. To fix this issue set weak assignment for
QB_XILINX_SERIAL so that variable can be override from machine conf
file or local.conf.
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Generic machines no longer depend on firmware (ESW) components. Thus they
will now build a full Linux system, where possible, without XSCT or SDT
modes. (Default, if XILINX_WITH_ESW is set to xsct, still builds firmware.)
It is up to the specific machine.conf files to enable the correct build
flow and that will enable the necessary firmware dependencies for the SoC.
This also means HDF_MACHINES is no longer required. Set HDF_MACHINES = ""
to produce a firmware-less build.
Also correct QEMU settings so they can be overridden.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
| |
This reverts commit da77c918db698d7912b6a2c6807720e9e2c522c8.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
| |
Remove soft assignment in IMAGE_FSTYPES variable due to this cpio file
are not generated for poky distro and this is required for devtool
boot-jtag feature.
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
| |
Remove FSBL recipe variables from soc-zynq.inc as this is already set
in fsbl recipes and no more required in machine inclusion file.
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
| |
Add cortexa9 DEFAULTTUNE which is required for zynq-7000 multiconfig
builds.
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
|
| |
By default upstream qemu sets CDROM, Floppy drive and use eMMC
as secondary boot device the drive index doesn't work as expected.
Hence add -nodefaults option to qemu all device this fix this issue.
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
|
|
| |
The generic machine configurations should not have a direct dependency
on specific firmware components as these dependencies should be
associated with boot.bin (or similar).
This change also removes WIC_DEPENDS as it is no longer required
Signed-off-by: John Toomey <john.toomey@amd.com>
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>
|
|
|
|
|
|
| |
These files are already part of scarthgap, remove the local copies.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
| |
Create a new layer containing all code related to the Mali400 graphics
stack and software. This includes the Mali kernel module / patches,
libglu/libgles code, mesa, wayland, kernel recipe and udev rules. This
layer also includes a dynamic layer for the qt5 bbappends and patches.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|\
| |
| |
| | |
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
Building libmetal and openamp using poky core-image-minimal requires
providers, Hence set default libmetal and openamp provider.
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|\|
| |
| |
| | |
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
For microblaze u-boot not booting on qemu or hw after moving to
u-boot 2024.1 rebase branch.
Reason explained below:
u-boot will provide output files as u-boot.elf, u-boot,
u-boot.bin, u-boot-nodtb.bin etc..
For Microblaze and Zynq we are using u-boot output file
For aarch64 family we are using u-boot.elf
u-boot: which has no relocation inside, then we apply relocation
(rela section) over binary. and then copying as u-boot.elf and using it.
u-boot.elf: It will relocation inside it and without debug symbols.
After recent relocation changes in u-boot
we should use u-boot.elf only for all platforms.
Signed-off-by: Varalaxmi Bingi <varalaxmi.bingi@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
| |
| |
| |
| | |
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Backport the tune files from poky master as of commit:
dd4c941e9fe9e0f1b73a934d9ecd0d165ee85474
This adds support for cortex-r5 and cortexr-r52 hard float ABI, as well
as cortex-a78.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
| |
| |
| |
| |
| |
| |
| | |
Enable tune files for Cortex-R52 processor.
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
| |
| |
| |
| | |
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
| |
This reverts commit 6ad9836940fa9c3541b5339c84d6d86e36734e24.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
| |
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
Switch the machine files to use the new 'xilinx-default-sd.wks' file.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
| |
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>
|
|\
| |
| |
| | |
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
| |
| |
| |
| | |
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| |
| |
| |
| |
| | |
We need the mali400 and vcu overrides to override the SOC and SOC_FAMILY
overrides. So adjust the order so they are higher priority, just under
the machine name itself.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
| |
| |
| |
| | |
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|/
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|\
| |
| |
| | |
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|