| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Add bc-native as build time dependency
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These recipes were primarily kept to make the transition for ZynqMP from
Non PMU Firmware to PMU Firmware easier for users. However these
releases are now outdated (by at least a year) and users should have
already transitioned or sorted out a long term strategy if not.
This change also drops any patches that were only used/available for
these recipes.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Acked-by: Alistair Francis <alistair.francis@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Make the pmu-firmware recipe provide a non-prefixed
virtual/pmu-firmware. Due to the common use of a class extender the
PROVIDES variable will be remapped with the 'zynqmp-pmu-' prefix. In
order to ensure the provider is always without a prefix modify the
PROVIDES after the recipe has been parsed (and any class extender
mapping is already processed).
Additionally set the zcu102-zynqmp machine to use the
virtual/pmu-firmware target and set the zynqmp-pmu-pmu-firmware recipe
as the default provider.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add a recipe that extracts the pmu-rom.elf from the PetaLinux ZCU102
BSP. This recipe cannot fetch the BSP, but uses the
xilinx-fetch-restricted class to handle error cases and providing
information on how to manually fetch.
This recipe is marked with the 'xilinx' license flag due to its use of
content that has licensing/legal requirements.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Tested-by: Alistair Francis <alistair.francis@xilinx.com>
Acked-by: Alistair Francis <alistair.francis@xilinx.com>
Acked-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This recipe was never updated when the rest of the configuration was
updated to be built for the PetaLinux v2016.3 BSP. This was due to
download access issues which were not resolved.
Instead of pointing at the old bitstream point at the download path on
Xilinx's servers which is restricted by account access, and using the
xilinx-fetch-restricted class to handle erroring properly and providing
user instructions for fetching the BSP file.
This recipe now also manually extracts the 'download.bit' from the BSP
and populates it into a package as well as the deploy directory.
The recipe is now marked with the 'xilinx' license flag due to its use
of content that has licensing/legal requirements.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Tested-by: Alistair Francis <alistair.francis@xilinx.com>
Acked-by: Alistair Francis <alistair.francis@xilinx.com>
Acked-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
|
|
|
|
|
|
|
|
| |
Update the patches that we are holding in Yocto to reflect the commits
that have been accepted by the mainline ATF project.
Signed-off-by: Alistair Francis <alistair.francis@xilinx.com>
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
The SPL based flow needs a raw firmware image instead of an ELF executable. Though
probably any objcopy version can perform this, it's better to have the actual
microblaze tool do the conversion, hence its inclusion in this recipe.
With this addition, it is possible to create a bootloader for the zynqmp
platforms based op opensource tools.
Signed-off-by: Mike Looijmans <mike.looijmans@topic.nl>
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This error is received while building
services/std_svc/psci/psci_common.c: In function 'psci_do_state_coordination':
services/std_svc/psci/psci_common.c:220:27: error: array subscript is above
array bounds [-Werror=array-bounds]
psci_req_local_pwr_states[pwrlvl - 1][cpu_idx] = req_pwr_state;
Patch 555ebb34db8f3424c1b394df2f10ecf9c1f70901 explains why the error
is seen and supposibly includes a fix. As the fix appears not to work,
let's disable the error checking.
Signed-off-by: Alistair Francis <alistair.francis@xilinx.com>
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
|
| |
Backport a mainline ATF patch to the Xilinx tree in order to fix the ATF
build.
Signed-off-by: Alistair Francis <alistair.francis@xilinx.com>
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
|
|
|
| |
There is differences in the value of *_load_address environment
variables between U-Boot versions (u-boot/u-boot-xlnx) as well as any
environment stored in spi flash. Instead of relying on correct
configuration being set, set the expected values in uEnv.txt to avoid
issues.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
|
|
| |
Change the device tree for the gem0 phy to match that of the kernel
device tree for ZYBO. This removes the compatible string and uses the
phy address of 0 (broadcast). This lets the kernel auto detect the phy
since there are no other devices on the MDIO bus for gem0.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
|
| |
PACKAGE_ARCH = "${MACHINE_ARCH}" is defined in u-boot.inc. Remove the
package arch here to be consistent with upstream
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
Reviewed-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Create a recipe for the PMU firmware for the ZynqMP PMU. This firmware
is provided by the embeddedsw repo, and specifically uses the
'zynqmp_pmufw' application of the repo.
This build requires a MicroBlaze compiler with newlib, libgloss and
libgcc.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Tested-by: Alistair Francis <alistair.francis@xilinx.com>
Tested-by: Koteswararao Nayudu <kotin@xilinx.com>
|
|
|
|
|
|
|
|
|
| |
This patch modifies the deployed content to use versioned image
names,while retaining unversioned symlinks.
Signed-off-by: Cyril Chemparathy <cyril.chemparathy@xilinx.com>
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
Reviewed-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
|
| |
Make arm-trusted-firmware machine independent
Signed-off-by: Cyril Chemparathy <cyril.chemparathy@xilinx.com>
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
Reviewed-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
|
| |
Add a recipe for the xilinx-v2017.1 release of the Xilinx fork of
arm-trusted-firmware. This release is based on 1.3 of ARM Trusted
Firmware.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
| |
Rename the arm-trusted-firmware recipe so that the filename matches the
release version of the recipe.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
|
| |
Split the common build/config/description/etc. of the recipe into an
include file so that multiple versions can use the include instead of
copying the recipe content.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Add a recipe for the u-boot-xlnx xilinx-v2017.1 release, this release is
based on v2017.01 of U-Boot. Also add an updated version of the patches.
This patch also moves the FILESEXTRAPATHS prepend to the u-boot-xlnx.inc
due to common use. And a u-boot-xlnx/${XILINX_RELEASE_VERSION} subdir is
added to the list for version specific patches.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
| |
Add the configs that have platform-init files already available in the
u-boot-xlnx source.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add a recipe to generate uEnv.txt environments for SD boot of Zynq
targets. This replaces the existing uEnv.txt for zc702/zedboard that
were manually created and populated only for u-boot-xlnx builds.
The generated uEnv.txt files also support auto loading of the fpga
bitstream before the kernel.
Also enable the use of this recipe for all *-zynq7 machines that use
U-Boot and have SD/eMMC available. And additionally setup
IMAGE_BOOT_FILES for these machines.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update to using the xilinx-platform-init.bbclass and depending on the
'virtual/xilinx-platform-init' provider. This allows for more generic
support of platform-init (between Zynq7, ZynqMP and any future targets).
This change also renames some of the variables used for defining the
source of the platform-init files for SPL. Specifically HAS_PS7INIT is
renamed to HAS_PLATFORM_INIT, and FORCE_PS7INIT is renamed to
FORCE_PLATFORM_INIT. However for compatibility the existing variables
still function as expected.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update to use xilinx-platform-init.bbclass. And change to providing the
generic 'virtual/xilinx-platform-init' as opposed to a zynq7 specific
one.
Remove the 'zynq7-platform-init.inc' this include was only useful for
recipes that provide/package only platform-init files. Which means it is
no more useful that the platform-init.bb recipe itself. Layers that want
to provide additional platform-init files can bbappend to the
platform-init recipe.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
|
|
|
| |
Update this recipe to use the new class, and change the virtual provider
to the more generic 'virtual/xilinx-platform-init'.
Additionally simplify the FILES_${PN}-platform-init paths, and take
advantage of the PLATFORM_INIT_FILES variable.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change improves and does a number of clean up to the device-tree
recipe. This includes adding support for building overlays, default
inclusion of kernel device tree sources, updated license value and
general clean ups to the logic.
This change also removes the support for MACHINE_DEVICETREE, and
additionally the now unused xilinx-utils.bbclass.
Note: In order to support overlays dtc version 1.4.3 or newer is needed,
currently in oe-core only 1.4.2 is available.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove the use of MACHINE_DEVICETREE for providing sources to
device-tree, instead provide the device tree sources as SRC_URI entires.
Whilst this was already being done automatically by the
MACHINE_DEVICETREE logic it also created a non-standard way of providing
the device tree sources to the recipe.
The setup of SRC_URI is done via the use of a device-tree.bbappend
instead of directly in the device-tree.bb recipe itself. This is for two
reason, separation of the source from the build logic as well as to
provide an example for how a user can extend the device-tree recipe to
provide custom device tree sources in their layer.
This change also moves the paths to the sources around, this is to align
the names of the directories to match the OVERRIDES so that when
expanding the file paths it will search the subdirs based on the
OVERRIDES or machine names.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
|
|
| |
This recipe uses unzip, however it was depending on the targets unzip as
opposed to unzip-native. Because of this it was using the hosts unzip
during the build which is no longer valid with newer oe-core.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Reviewed-by: Alistair Francis <alistair.francis@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Replace the existing device tree content with the content of the
zynq-microzed.dts from the kernel source. Specifically based on commit
df2f3c48b9cd51e2612a1598342769d09d849f39.
This resolves the issues with the ethernet phy as well as adding pinctrl
for USB.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently the jtagboot cmd fails when jtagmemboot failed. This is
because the jtagmemboot returns false when it fail the itest.w or the
booti failed. Thus the network based jtagboot cmd never gets triggered.
The jtagboot can't be purely base on the itest.w because sometimes
the dhcp command triggers the Image download which has valid image
in the ram. This passes the itest.w and iminfo test but fail the
booti.
This patch triggers the network based jtagboot cmd if jtagmemboot
failed.
Signed-off-by: Jason Wu <jason.hy.wu@gmail.com>
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When booting a ZynqMP machine configured to boot from JTAG, setup U-Boot
to attempt to automatically load the kernel, rootfs and device tree from
default memory locations.
This enables auto-booting for QEMU allowing for a completely automated
boot up when using qemu-xilinx.
Note the patch in this change is not acceptable for upstreaming in its
current form. The upstream maintainer would however accept a similar
change that uses FIT instead of individual components.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Reviewed-by: Alistair Francis <alistair.francis@xilinx.com>
|
|
|
|
|
|
|
|
|
| |
Update the u-boot-xlnx recipe to the xilinx-v2016.04 release.
Note that this changes the naming convention for the .bb file, this has
no affect on the value of PV since it is specified in the recipe itself.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
|
| |
This append no longer provides patches and only includes the platform
init injection support. As such this append can apply generally to
'u-boot' versions.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
|
|
| |
This include has been deprecated for two releases. It is now completely
obsolete and being removed.
Remove the deprecation warning message as well.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
|
|
| |
Backport the dram_init* memory corruption fix, this resolves issues with
some configurations where the dram_init function for zynq/zynqmp would
trash non-relocated locations in memory due to the use of static
variables before bss initialization.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
|
| |
Update the appends for the u-boot 2016.11 recipe. Remove unneeded
patches, and drop the SPL bitstream patch as it does not apply cleanly
(and newer features are available in 2016.11 for FPGA loading from FIT).
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
| |
Add kc705-microblazeel patch for u-boot
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
| |
Change kc705-microblazeel to reflect v2016.3 Xilinx tools.
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
|
|
|
| |
Handle building where B != S, allowing for the source and build
artefacts to be separated. This allows for out-of-tree building, and
enabling use of EXTERNALSRC such that the build artefacts are not
written into the EXTERNALSRC directory.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
|
|
|
|
|
|
|
| |
This patch is unused, and not required as U-Boot has updated to handle
newer GCC compilers without the need for a separate header.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
| |
Remove older u-boot version
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
| |
Upgrade u-boot to supported 2016.07 version
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Embed the Xilinx Release Version (aka the 'xilinx-vYYYY.X' tag) into the
PV of the recipe, this makes it easier to determine which version of
Xilinx's ATF is being used.
Additionally change the version string to extend instead of extra data
(switch the '+' to a '-' before 'xilinx...').
This removes the need for the comment on what the SRCREV points at,
instead this is replaced with a XILINX_RELEASE_VERSION variable which
contains the 'vYYYY.X' release string.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Embed the Xilinx Release Version into the PV of the u-boot-xlnx recipes.
This allows for easier determination of which version of u-boot-xlnx is
in use and avoid any ambiguity when one or more Xilinx Release uses the
same upstream u-boot version.
This removes the need for the comment on what the SRCREV points at,
instead this is replaced with a XILINX_RELEASE_VERSION variable which
contains the 'vYYYY.X' release string.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
|
|
| |
There are cases where we want different providers for ATF depending on
development methodology. Having provides will enable easier switch for
ATF development.
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
|
|
| |
The bl31 name doesn't mean much, and we're unlikely to support other
payload types on ZU+. We therefore use a more human name for the
deployed images
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
| |
Update ATF to release tag xilinx-v2016.3 tag
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
| |
ATF Package architecture can be ARCH specific not machine specific
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
|
| |
Update the bindings where required for the v4.6 linux-xlnx kernel. These
changes are incompatible with older linux-xlnx kernels due to changes in
the Xilinx DRM bindings.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
|
|
|
|
|
|
|
| |
The LICENSE field is no longer provided by u-boot.inc, so for the
u-boot-xlnx recipes provide the expected value which matches the source.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Acked-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rename the QEMU machines to match the <board>-<design>-<arch>
convention. QEMU only machines no longer need to be named qemu*.
Note for qemuzynq it is special in that it does not model a board, as
such it has no board in the name being just 'qemu-zynq7'.
This updates the README.md to match the new machine names.
Additional update all occurrences of the qemu* machines
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Reviewed-by: Alistair Francis <alistair.francis@xilinx.com>
|