| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adding base required dependencies to do_image_wic[depends] to make sure
the common files required to boot.bin have been deployed in DEPLOYDIR
before the do_image_wic task tries to use them.
zynqmp/versal will add virtual/kernel, virtual/boot-bin,
virtual/bootloader, and virtual/arm-trusted-firmware
zynq will add everything but virtual/arm-trusted-firmware
If you want to add other files to IMAGE_BOOT_FILES, aside from files
deployed from virtual/kernel, virtual/boot-bin, virtual/bootloader, you
may need to manually add the dependency to do_image_wic[depends]
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
provider
Python3 package from OE-core depends on qemu-helper-native, to meet this
dependency use qemu-xilinx-helper-native as preferred provider. In
addition this helps the sstate-cache to be similar across generic
machines and evaluation boards.
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
|
| |
|
|
|
|
| |
Deploy u-boot.elf for Versal devices
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
While enabling PIE does not produce build time errors AFAIC, for
example: bash fails to return/exit properly when PIE is enabled.
Given the fact that init code relies on bash to source scripts at boot
time and such, booting hangs at init on microblaze targets.
Disable PIE on SECURITY_CFLAGS/SECURITY_LDFLAGS for MB architecture
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Introduce FPGA_MNGR_RECONFIG_ENABLE to enable overlay configuration for
fpga-manager support in kernel.
To enable, set FPGA_MNGR_RECONFIG_ENABLE = "1" in local.conf or other
bitbake configuration files.
For backward compatibility, set FPGA_MNGR_RECONFIG_ENABLE based on
IMAGE_FEATURES.
In future release, the option of fpga-manager in IMAGE_FEATURES will be
deprecated.
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
CONFIG_REMAKE_ELF is enabled for all zynq boards. Also, using
CONFIG_OF_SEPERATE is recommeneded by u-boot release v2019.01. So,
Deploy u-boot.elf instead of u-boot as u-boot.elf contains dtb. This
would solve the following boot issue:
No valid device tree binary found - please append one to U-Boot binary,
use u-boot-dtb.bin or define CONFIG_OF_EMBED. For sandbox, use -d
<file.dtb> initcall sequence 00461b18 failed at call 004582e0 (err=-1)
Signed-off-by: Sreeja Vadakattu <svadakat@xilinx.com>
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add all available dtb sources to the IMAGE_BOOT_FILES variable. For
device-tree recipe generated dtbs the files available are only known
after they files are deployed, so a wildcard pattern is used for these
files. Note that this pattern appears before the kernel device trees due
to the preference to use custom non-kernel device trees where available.
This ordering is needed so that recipes like u-boot-zynq-uenv can pick
the first device tree to select as the default.
The kernel device trees are specifically selected based on the value of
KERNEL_DEVICETREE, this avoid the duplication of kernel image type
prefixed files along side having the actual files that the kernel
builds.
Additionally remove all instances of "${MACHINE}.dtb" as they no longer
need to be specified and are incorrect due to the nesting of the files
in the `devicetree` directory.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Replace the definition of IMAGE_BOOT_FILES in machine-xilinx-board.inc
with the use of a function which automatically selects available images
that should be included. This includes the existing implementation of
`get_dtb_list` and replaces it with a function that covers all image
files including the existing default for KERNEL_IMAGETYPE(S) and
UBOOT_BINARY.
Also remove the use of `get_dtb_list` from individual machines which is
replaced by the default value.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
IMAGE_BOOT_FILES
Replaced the hard-coded devicetree files in IMAGE_BOOT_FILES with a function,
which formats the KERNEL_DEVICETREE list properly.
Signed-off-by: Franz Forstmayr <f.forstmayr@gmail.com>
Reviewed-by: Nathan Rossi <nathan@nathanrossi.com>
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
|
| |
|
|
|
|
|
|
| |
zynqmpeg and zynqmpev devices has Mali400, overrides extended with
mali400.This patch sets preferred providers to libmali-xlnx.
Signed-off-by: Vineeth Chowdary Karumanchi <vineethchowz.chowdary@xilinx.com>
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With the perspective removal of tune-microblaze.inc, the following
preferred GDB version configuration for MicroBlaze needs to be
relocated.
This change also drops the setting of gdb-cross* targets as they were
not setup properly since "gdb-cross-${TARGET_ARCH}" was not specified
correctly. This is also preferred as newer GDB (e.g. 8.0) does support
gdb-cross for debugging (just not gdbserver/gdb).
Ideally the MicroBlaze GDB patches should be updated to support the
newest GDB and or upstreamed. However this setup continues to be
available until that occurs.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
With prelink-rtld support available for MicroBlaze and toolchain fixes
for atomic CAS bugs it is functional to generate gobject introspection
data for MicroBlaze binaries. This does still require the meta-xilinx
append for qemu which enables the architecture such that qemu linux user
is available.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
|
|
|
As discussed previously on mailing list, we are proceeding with layer
restructuring. For rocko release we will have the following layers
meta-xilinx
->meta-xilinx-bsp (current meta-xilinx)
->meta-xilinx-contrib
In the subsequent releases we will add other layers from Xilinx
meta-xilinx
->meta-xilinx-bsp (current meta-xilinx)
->meta-petalinux
->meta-xilinx-tools
->meta-xilinx-contrib
This will provide one clone to get all the required meta layers from
Xilinx for a complete solution, and the users can blacklist any layer
which they don't want to use using bblayer.conf.
This will enables us to help our vendors/partners to add their reference
designs, board definitions etc.
Recipe changes :
* Move reference design zybo-linux-bd.bb to meta-xilinx-contrib
* Move kernel patches realted to zybo-linux-bd-zynq7 board to
meta-xilinx-contrib
* Update README
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
|
