| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
device-tree, fsbl, plmfw, pmufw, psmfw do basic validation checks, when in
an eSDK skip these checks. Otherwise a partially configured system can't
generate an eSDK for the end user.
Sync Core and Standalone usages to be consistent.
Also cleanup the BB_DONT_CACHE to be consistent in all usages.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
| |
The dfx-mgr package depends on libdfx which is restricted to zynqmp and
versal and it follows that this package should have the same restriction
as it is not used on other platforms.
Signed-off-by: John Toomey <jtoomey@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
| |
Use ??= to define the default values. This ensures a ?= (or =) can be
used in a .bbappend, or a user can define a default value in the local.conf
or machine.conf file.
Also add a default config for versal that matches zynqmp and zynq.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
| |
Fix BIF_PARTITION_ATTR paths for fsbl and u-boot components. Also add
missing BIF_PARTITION_ATTR for device-tree.
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
| |
do_configure processes the BIF_PARTITION_ATTR based on python getVar. This
prevents the system from automatically discovering the variables needed for
hash calculations to determine if something has changed. Manually add in
the list of standard variables processed to ensure the hash updates.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
| |
Signed-off-by: John Toomey <jtoomey@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
| |
populate_sdk_ext step"
This reverts commit 51e48cc7acd766a6d84dbcc65d7b64de6f5d707e.
linux-firmware, linux-firmware-ti-bt, and petalinux-image-minimal
now build successfully.
Signed-off-by: Vishal Patel <vishal.patel@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Three bug fixes suggested by community member dednev@rambler.ru:
*elf*-microblaze-relaxation.patch short description:
The roots of invalid data offsets (pointer) after relaxation are in
internal symbol table cache handling. If symbol table was cached while
section processing for garbage collection, the elf_tdata
(abfd)->symtab_hdr pointer is not NULL, but (Elf_Internal_Sym *)
symtab_hdr->contents array contains data for local symbols only. But in
the repeated relocation processing there is no check whenever the symbol
index is local (ELF32_R_SYM (irelscan->r_info) < symtab_hdr->sh_info) or
global. This leads to the buffer overflow (global symbol index is out of
bounds) and following invalid relocation processing, especially in extra
relocation data modifications (f.e. irelscan->r_addend could be
decreased by arbitrary values).
*elf*-microblaze-no-keep-memory.patch short description:
There is incorrect newly allocated buffers handling if internal memory
caching is disabled (without --no-keep-memory ld switch). This leads to
possible double free(...) calls for such data and results in unexpected
ld termination with abort(). I've fixed this issue by implementing
similar to the elf32-avr.c data buffer handling.
*elf*-imm-check-for-relaxation.patch short description:
I've reverted Xilinx path to the original GNU binutils bfd code for
microblaze, because this patch incorrectly leaves some "imm -1"
instructions in resulting binary file after relaxation and increases
executable size. If you look at the IMM instruction argument processing
in binutils/gas/config/tc-microblaze.c you will see, that gas checks are
similar to the original bfd microblaze_elf_relax_section(...)
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
| |
We do not maintain support for hardknott so it is being removed
Signed-off-by: John Toomey <jtoomey@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
| |
We do not build, test or support gatesgarth in any of our layers so it
makes sense to remove this for the various layer.conf files
Signed-off-by: John Toomey <jtoomey@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
| |
Signed-off-by: John Toomey <jtoomey@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Move from the initial qemu-xilinx 6.1.0 version to the current development
version.
Changelog qemu-devicetrees:
versal-psm: Add psm err management module
versal: Add vitis variant for xcvc2802
versal: Add xcvc2802 & xcve2802 devices
versal: memmap: npi: Allow AIE2 NPI range to be overriden
versal: Make generic npi default for all boards
versal: remote-port: Add a PL to XRAM port
versal: lpd: Move the XRAM into a separate memory region
zynqmp: Fix DDR aliasing onto qemu_sysmem
versal-pmc-sys: Connect efuse-cache to sysmon
versal: smmu: Versal has 1 global + 32 context interrupts
vpk180: Add new board dts
xcvp1802: Add ssit property
board-versal-ps-virt: Add include guards
xcvp1802-virt: This virt board is for VPK180 emulation
versal: Add pmc error management node
vitis: versal: Prepare for NPI forwarding
versal: remote-port: Allocate device for NPI forwarding
versal: memmap: Add the AIE2 adress range
versal-ps-iou: Configure the number of interrupts an slots on usb_dwc3
zynqmp-iou: Configure the number of interrupts an slots on usb_dwc3
versal-pmc-sec: Improve the error message
board-versal-pmc-virt: Fix DDR size
Changelog qemu-xilinx:
versal-psm-error-mng: Fix the mask reg updates
versal-psm-error-mng: Add PSM error management module
versal-pmc-error-mng: Update MASK regs based on EN/DIS
versal: puf: Fix puf-id generation
versal: xram-slcr: Reflect XRAM power up/down status
versal: sysmon: Model secure efuse transfer
versal: pmc: efuse-cache: Implement sysmon data-source interface
xlnx-efuse: Introduce sysmon data-source interface
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
| |
Upgrade Qemu from 5.1.0 -> 6.1.0 for 2022 release
Signed-off-by: Sai Pavan Boddu <sai.pavan.boddu@xilinx.com>
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
| |
(dfx-mgr was moved from meta-xilinx-tools, the reverted patch was from before
the move)
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
| |
Fix override syntax in systemd variables.
Signed-off-by: Christian Kohn <christian.kohn@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
| |
The order is critical for the system to boot properly. Add a comment
explaing the requirements, making the various parts parameterized to
allow the optional parameters to be adjusted.
The bitstream element will typically be added by a bbappend in a layer
such as meta-xilinx-tools.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
| |
These machines are no longer necessary, as the regular "generic" machine with
an alterantive DEFAULTTUNE should be used instead.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
| |
support
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
| |
When the user uses a microblaze tune, we need to check if meta-microblaze is
part of their build. If not stop, and tell them they need to add it.
meta-microblaze is not a layers dependency as it is not needed for most
builds.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
| |
This prevents meta-microblaze from being required, and hash values changing
unless microblaze processor is enabled.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
| |
qemu-native requires pmu-rom-native when building for zynqmp based systems.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
| |
The default for virtual/boot-bin should be xilinx-bootbin.
The default UBOOT_SUFFIX should be 'bin'. Otherwise u-boot-xlnx may fail
being able to not find u-boot.img.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
fsbl, plmfw, pufw, and psmfw are reworked to provide earlier error messages,
and better handle multiconfig builds.
Also adjust MACHINE specific changes to use .* for compatibility based on the
SOC_FAMILY override. The system doesn't always set the SOC_FAMILY as
COMPATIBLE_MACHINE, so this avoids an error of incompatible machine.
Align all of the expected firmware filenames to be <firmware>-${MACHINE}.
The user can override as necessary.
The license moves to CLOSED as we don't know the license of the software being
provided by the user or other dependencies. It'll be up to the user to
reconcile it.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
| |
We need a method for regular building to specify a device tree. Since the
experimental flow already contained this, merge it in and connect to
the existing SYSTEM_DTFILE as a fall back.
Also enable addition 'early package failure' messages to alert the user as
soon as possible they need to pass in additional information.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
| |
Lopper comes from meta-virtualization, the python modules are required by
it and the related changes.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
| |
PACKAGE_ARCH is not relevant to native recipes, remove this
do_configure is not used as the package is simply loading in a binary. Skip
this as an optimization
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch will define the device-tree required memory and uart params.
Due to recent board/board_variant and machine changes in yocto caused
this issue.To work with these new changes we need this.
In plnxtool.conf we will define the default values but if we set board
value in that case due to the changes in new microblaze-generic.conf file
the plnxtool.conf changes will not work.
Signed-off-by: Varalaxmi Bingi <varalaxmi.bingi@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
| |
Enable SYSTEMD hooks by default as DISTRO_FEATURE is systemd.
Enable sysvinit hooks only if DISTRO_FEATURE is sysvinit.
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
| |
Signed-off-by: Neel Gandhi <neel.gandhi@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
| |
Move the pmu-rom to pmu-rom-native recipe. The ROM is only deployed in the
standard directory for qemu-xilinx usage when required by a zynqmp-generic
system.
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: 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>
|
|
|
|
|
|
| |
Change rootfs to cpio.gz, and runqemu will automatically load it as an initrd
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
| |
Use the MACHINEOVERRIDES to add the BOARD name so that overrides elsewhere
will work as expected. Eventually the overrides will need to be adjusted.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
| |
All machines are now capable of heterogenous configuration by selecting
the correct DEFAULTTUNE and other values.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
| |
PACKAGE_ARCH should not be MACHINE_ARCH, unless a specific override is
being used for compatibility.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Each inherited BSP must set a MACHINEOVERRIDES and PACKAGE_EXTRA_ARCHS to
ensure that various overrides can be set along the way. The general format
for this is (in the caller):
require conf/machine/<inherited machine>.conf
The callee is responsible for adding to the MACHINEOVERRIDES and
PACKAGE_EXTRA_ARCHS. It does this by setting the following at the beginning
and end of the file, respectively.
MACHINEOVERRIDES =. "${@['', '<machine>:']['<machine>' != '${MACHINE}']}"
...
...
PACKAGE_EXTRA_ARCHS_append = "${@['', ' <machine_arch>']['<machine>' != '${MACHINE}']}"
where <machine> is the <machine>.conf file the line appears in;
<machine_arch> is the <machine>.replace('-', '_') (matching MACHINE_ARCH) if
the machine file was used by itself.
The MACHINEOVERRIDES uses =. or .= everywhere in the Yocto Project. Doing it
via =. in the load order ensures in order evaluation.
PACKAGE_EXTRA_ARCHS is set via 'append', but needs to be the last operation
to ensure that we are always added AFTER anything we include along the way.
Effectively this is a late binding evaluation.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
| |
If the BOARD and/or BOARD_VARIANT is set, continue to allow this to
work, however warn the user it is deprecated.
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: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
| |
Cleanup some of the override syntax.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
| |
The board config matches the default config, it's not needed.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|