arm-bsp: add recipes to support cortex-a5 designstart
cover arm-bsp: add recipes to support cortex-a5 designstart
Add necessary recipes to feature equivalent to the actual releases for the sw stack for the Cortex-A5 Designstart [0] platform.
Cheers,
Rui
[0]: https://developer.arm.com/ip-products/designstart/pro/cortex-a5
Rui Silva (3):
arm-bsp: add upstream kernel inc and v5.3 recipe
arm-bsp: u-boot: move machine patches
arm-bsp: add support to cortex-a5 designstart
meta-arm-bsp/conf/machine/a5ds.conf | 25 ++
meta-arm-bsp/documentation/a5ds.md | 24 ++
...t-arm-a5ds-move-dtb-to-a-new-address.patch | 31 ++
.../trusted-firmware-a-a5ds.inc | 22 ++
.../trusted-firmware-a_git.bbappend | 7 +
.../a5ds/0001-armv7-add-mmio-timer.patch | 105 ++++++
...-arm-add-designstart-cortex-a5-board.patch | 309 ++++++++++++++++++
.../{ => juno}/u-boot_vexpress_uenv.patch | 0
.../recipes-bsp/u-boot/u-boot_%.bbappend | 8 +
.../recipes-bsp/u-boot/u-boot_2019.%.bbappend | 2 +-
.../linux/linux-upstream-arm-platforms.inc | 24 ++
.../linux/linux-upstream-arm_5.3.bb | 8 +
12 files changed, 564 insertions(+), 1 deletion(-)
create mode 100644 meta-arm-bsp/conf/machine/a5ds.conf
create mode 100644 meta-arm-bsp/documentation/a5ds.md
create mode 100644 meta-arm-bsp/recipes-bsp/trusted-firmware-a/files/a5ds/0001-plat-arm-a5ds-move-dtb-to-a-new-address.patch
create mode 100644 meta-arm-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a-a5ds.inc
create mode 100644 meta-arm-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a_git.bbappend
create mode 100644 meta-arm-bsp/recipes-bsp/u-boot/files/a5ds/0001-armv7-add-mmio-timer.patch
create mode 100644 meta-arm-bsp/recipes-bsp/u-boot/files/a5ds/0002-board-arm-add-designstart-cortex-a5-board.patch
rename meta-arm-bsp/recipes-bsp/u-boot/files/{ => juno}/u-boot_vexpress_uenv.patch (100%)
create mode 100644 meta-arm-bsp/recipes-bsp/u-boot/u-boot_%.bbappend
create mode 100644 meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm-platforms.inc
create mode 100644 meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm_5.3.bb--
2.25.1
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
PATCH 1/3 arm-bsp: add upstream kernel inc and v5.3 recipe
From: Rui Silva <[email protected]>
Add support to build using the upstream (Linus tree) and as first user add recipe for v5.3, which will be later.
--- .../linux/linux-upstream-arm-platforms.inc | 24 +++++++++++++++++++ .../linux/linux-upstream-arm_5.3.bb | 8 +++++++ 2 files changed, 32 insertions(+) create mode 100644 meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm-platforms.inc create mode 100644 meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm_5.3.bb
meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm-platforms.inc new file +24 -0
@@ -0,0 +1,24 @@ +DESCRIPTION = "Linux Kernel based on upstream tree" +SECTION = "kernel" +LICENSE = "GPLv2" +SRCREV_FORMAT = "kernel" + +require recipes-kernel/linux/linux-yocto.inc + +KERNEL_VERSION_SANITY_SKIP = "1" + +S = "${WORKDIR}/git" + +# Override do_kernel_configme to avoid kernel being assembled into a linux-yocto +# style kernel +# https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#ref-tasks-kernel_configme +do_kernel_configme[noexec] = "1" + +# Make sure no branch is defined since here we track a specific version +KBRANCH = "" + +LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814" + +SRC_URI = "\ + git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux;protocol=https;nobranch=1 \ + "
meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm_5.3.bb new file +8 -0
@@ -0,0 +1,8 @@ +# Add support for Upstream Kernel for Arm Platforms (boards or simulators) + +SUMMARY = "Linux Kernel Upstream, supported by Arm/Linaro" + +require recipes-kernel/linux/linux-upstream-arm-platforms.inc + +SRCREV = "v${PV}" +LINUX_VERSION ?= "${PV}"
--
2.25.1
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Re: [meta-arm] [PATCH 1/3] arm-bsp: add upstream kernel inc and v5.3 recipe
Quoted 39 lines · Rui Miguel Silva
From: Rui Silva <[email protected]>
Add support to build using the upstream (Linus tree) and as first user add recipe for v5.3, which will be later.
Change-Id I0f30a45002adca7c0b95a0421e0291a6852295ebSigned-off-by Rui Miguel Silva <[email protected]>--- .../linux/linux-upstream-arm-platforms.inc | 24 +++++++++++++++++++ .../linux/linux-upstream-arm_5.3.bb | 8 +++++++ 2 files changed, 32 insertions(+) create mode 100644 meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm-platforms.inc create mode 100644 meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm_5.3.bb
diff --git a/meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm-platforms.inc b/meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm-platforms.inc new file mode 100644
index 000000000000..7b73e7536d19meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm-platforms.inc new file +12
-0@@ -0,0 +1,24 @@ +DESCRIPTION = "Linux Kernel based on upstream tree" +SECTION = "kernel" +LICENSE = "GPLv2" +SRCREV_FORMAT = "kernel" + +require recipes-kernel/linux/linux-yocto.inc + +KERNEL_VERSION_SANITY_SKIP = "1" + +S = "${WORKDIR}/git" + +# Override do_kernel_configme to avoid kernel being assembled into alinux-yocto
meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm-platforms.inc new file +2
-0+# style kernel +#
Quoted 3 lines
https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#ref-tasks-kernel_configme
+do_kernel_configme[noexec] = "1"
What are the benefits of using linux-yocto when building an upstream kernel? Most BSP typically define their own linux.inc file and do_configure task. I am curious about your approach here, since I haven't seen that before.
+
Quoted 35 lines
meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm-platforms.inc new file +7
-0+# Make sure no branch is defined since here we track a specific version +KBRANCH = "" + +LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814" + +SRC_URI = "\ + git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux;protocol=https;nobranch=1 \
meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm-platforms.inc new file +1
-0+ "meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm_5.3.bb new file +8
-1@@ -0,0 +1,8 @@ +# Add support for Upstream Kernel for Arm Platforms (boards or simulators) + +SUMMARY = "Linux Kernel Upstream, supported by Arm/Linaro" + +require recipes-kernel/linux/linux-upstream-arm-platforms.inc + +SRCREV = "v${PV}" +LINUX_VERSION ?= "${PV}" --2.25.1
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Re: [meta-arm] [PATCH 1/3] arm-bsp: add upstream kernel inc and v5.3 recipe
Hi Nicho,
thanks for the review.
On Wed, Mar 11, 2020 at 12:06:34PM +0100, Nicolas Dechesne wrote: [--
Type: text/plain; charset=UTF-8, Encoding: 7bit, Size: 3.3K --]
Quoted 30 lines
Quoted 27 lines · Rui Miguel Silva
From: Rui Silva <[email protected]>
Add support to build using the upstream (Linus tree) and as first user add recipe for v5.3, which will be later.
Change-Id I0f30a45002adca7c0b95a0421e0291a6852295ebSigned-off-by Rui Miguel Silva <[email protected]> ---.../linux/linux-upstream-arm-platforms.inc | 24
+++++++++++++++++++ .../linux/linux-upstream-arm_5.3.bb | 8 +++++++2 files changed, 32 insertions(+) create mode 100644meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm-platforms.inc create mode 100644 meta-arm-bsp/recipes-kernel/linux/ linux-upstream-arm_5.3.bb
diff --git a/meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm-platforms.inc b/meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm-platforms.inc new file mode 100644 index 000000000000..7b73e7536d19 ---
/dev/null+++ b/meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm-platforms.inc(quoted diff) +0
-0@@ -0,0 +1,24 @@ +DESCRIPTION = "Linux Kernel based on upstreamtree" +SECTION = "kernel" +LICENSE = "GPLv2" +SRCREV_FORMAT = "kernel" + +require recipes-kernel/linux/linux-yocto.inc + +KERNEL_VERSION_SANITY_SKIP = "1" + +S = "${WORKDIR}/git" + +# Override
do_kernel_configmeto avoid kernel being assembled into a linux-yocto +# style kernel +#
Quoted 8 lines
Quoted 3 lines
https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#ref-tasks-kernel_configme
+do_kernel_configme[noexec] = "1"What are the benefits of using linux-yocto when building an upstream kernel? Most BSP typically define their own linux.inc file and
do_configuretask. I am curious about your approach here, since I haven't seen that before.
The original idea was to use as much as possible the linux-yocto existing infrastructure and disable what we did not needed, but your approach also makes sense.
For you this is a shipstoper? or can we go like this and change this in a follow up patch? What I really want is to have as much as possible with sync with the existing recipes, and when we swap to the ones in this meta-arm then cleanup any notes.
------ Cheers, Rui
Quoted 19 lines
+
Quoted 17 lines
+# Make sure no branch is defined since here we track a specific version +KBRANCH = "" + +LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814" + +SRC_URI =
"\ +git://
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux;protocol=https;nobranch=1
\ + " diff --git
a/meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm_5.3.bb b/meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm_5.3.bb new file mode 100644 index 000000000000..88a06c4bb3c0 ---/dev/null
+++ b/meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm_5.3.bb(quoted diff) +0
-0@@ -0,0 +1,8 @@ +# Add support for Upstream Kernel for ArmPlatforms (boards or simulators) + +SUMMARY = "Linux Kernel Upstream, supported by Arm/Linaro" + +require recipes-kernel/linux/linux-upstream-arm-platforms.inc + +SRCREV = "v${PV}" +LINUX_VERSION ?= "${PV}" --
2.25.1
Quoted 7 lines
Quoted 7 lines
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Re: [meta-arm] [PATCH 1/3] arm-bsp: add upstream kernel inc and v5.3 recipe
Quoted 45 lines · Rui Miguel Silva
Hi Nicho,
thanks for the review.On Wed, Mar 11, 2020 at 12:06:34PM +0100, Nicolas Dechesne wrote: [--
Type: text/plain; charset=UTF-8, Encoding: 7bit, Size: 3.3K --]Quoted 18 lines
Quoted 15 lines · Rui Miguel Silva
From: Rui Silva <[email protected]>
Add support to build using the upstream (Linus tree) and as first user add recipe for v5.3, which will be later.
Change-Id I0f30a45002adca7c0b95a0421e0291a6852295ebSigned-off-by Rui Miguel Silva <[email protected]> ---.../linux/linux-upstream-arm-platforms.inc | 24
+++++++++++++++++++ .../linux/linux-upstream-arm_5.3.bb | 8 +++++++2 files changed, 32 insertions(+) create mode 100644meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm-platforms.inc create mode 100644 meta-arm-bsp/recipes-kernel/linux/ linux-upstream-arm_5.3.bb
Quoted 13 lines
Quoted 7 lines
diff --git a/meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm-platforms.inc b/meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm-platforms.inc new file mode 100644 index 000000000000..7b73e7536d19 ---
/dev/null+++ b/meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm-platforms.inc(quoted diff) +0
-0@@ -0,0 +1,24 @@ +DESCRIPTION = "Linux Kernel based on upstreamQuoted 6 lines
tree" +SECTION = "kernel" +LICENSE = "GPLv2" +SRCREV_FORMAT = "kernel" + +require recipes-kernel/linux/linux-yocto.inc + +KERNEL_VERSION_SANITY_SKIP = "1" + +S = "${WORKDIR}/git" + +# Override
do_kernel_configmeto avoid kernel being assembled into a linux-yocto +# style kernel +#https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#ref-tasks-kernel_configme
Quoted 7 lines
Quoted 2 lines
+do_kernel_configme[noexec] = "1"
What are the benefits of using linux-yocto when building an upstream kernel? Most BSP typically define their own linux.inc file and
do_configuretask. I am curious about your approach here, since I haven't seen that before.
Quoted 9 lines
The original idea was to use as much as possible the linux-yocto existing infrastructure and disable what we did not needed, but your approach also makes sense.
For you this is a shipstoper? or can we go like this and change this in a follow up patch? What I really want is to have as much as possible with sync with the existing recipes, and when we swap to the ones in this meta-arm then cleanup any notes.
again.. it's just my thoughts on this, and what came to my mind when I looked at your patch. But to me, we should either use linux-yocto (e.g. kernel-yocto.bbclass) and in which case we have to provide a kernel SRC_URI that implements the kernel-yocto mechanisms (for configure) like it's done in the other kernel recipe in meta-rm, or we should use kernel.bbclass only otherwise. I am worried about potential issues, since i think this is pretty much an unsupported combo.. but if you tested it and it worked, it might be fine for now..
Quoted 36 lines
------ Cheers, Rui
Quoted 7 lines
+
Quoted 5 lines
+# Make sure no branch is defined since here we track a specific version +KBRANCH = "" + +LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814" + +SRC_URI =
"\ +git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux;protocol=https;nobranch=1
Quoted 12 lines
Quoted 12 lines
\ + " diff --git
a/meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm_5.3.bb b/meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm_5.3.bb new file mode 100644 index 000000000000..88a06c4bb3c0 ---/dev/null+++ b/meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm_5.3.bb(quoted diff) +0
-0@@ -0,0 +1,8 @@ +# Add support for Upstream Kernel for ArmPlatforms (boards or simulators) + +SUMMARY = "Linux Kernel Upstream, supported by Arm/Linaro" + +require recipes-kernel/linux/linux-upstream-arm-platforms.inc + +SRCREV = "v${PV}" +LINUX_VERSION ?= "${PV}" --
2.25.1Quoted 7 lines
Quoted 7 lines
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Re: [meta-arm] [PATCH 1/3] arm-bsp: add upstream kernel inc and v5.3 recipe
Hi Nicolas,
On Thu, Mar 12, 2020 at 09:11:49AM +0100, Nicolas Dechesne wrote:
[-- Type: text/plain; charset=UTF-8, Encoding: 7bit, Size: 5.1K --]
Quoted 57 lines · Rui Miguel Silva
Quoted 46 lines
Hi Nicho,
thanks for the review.On Wed, Mar 11, 2020 at 12:06:34PM +0100, Nicolas Dechesne wrote: [--
Type: text/plain; charset=UTF-8, Encoding: 7bit, Size: 3.3K --]Quoted 18 lines
Quoted 15 lines · Rui Miguel Silva
From: Rui Silva <[email protected]>
Add support to build using the upstream (Linus tree) and as first user add recipe for v5.3, which will be later.
Change-Id I0f30a45002adca7c0b95a0421e0291a6852295ebSigned-off-by Rui Miguel Silva <[email protected]> ---.../linux/linux-upstream-arm-platforms.inc | 24
+++++++++++++++++++ .../linux/linux-upstream-arm_5.3.bb | 8 +++++++2 files changed, 32 insertions(+) create mode 100644meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm-platforms.inc create mode 100644 meta-arm-bsp/recipes-kernel/linux/ linux-upstream-arm_5.3.bb
Quoted 13 lines
Quoted 7 lines
diff --git a/meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm-platforms.inc b/meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm-platforms.inc new file mode 100644 index 000000000000..7b73e7536d19 ---
/dev/null+++ b/meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm-platforms.inc(quoted diff) +0
-0@@ -0,0 +1,24 @@ +DESCRIPTION = "Linux Kernel based on upstreamQuoted 6 lines
tree" +SECTION = "kernel" +LICENSE = "GPLv2" +SRCREV_FORMAT = "kernel" + +require recipes-kernel/linux/linux-yocto.inc + +KERNEL_VERSION_SANITY_SKIP = "1" + +S = "${WORKDIR}/git" + +# Override
do_kernel_configmeto avoid kernel being assembled into a linux-yocto +# style kernel +#https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#ref-tasks-kernel_configme
Quoted 7 lines
Quoted 2 lines
+do_kernel_configme[noexec] = "1"
What are the benefits of using linux-yocto when building an upstream kernel? Most BSP typically define their own linux.inc file and
do_configuretask. I am curious about your approach here, since I haven't seen that before.Quoted 9 lines
The original idea was to use as much as possible the linux-yocto existing infrastructure and disable what we did not needed, but your approach also makes sense.
For you this is a shipstoper? or can we go like this and change this in a follow up patch? What I really want is to have as much as possible with sync with the existing recipes, and when we swap to the ones in this meta-arm then cleanup any notes.
Quoted 8 lines
again.. it's just my thoughts on this, and what came to my mind when I looked at your patch. But to me, we should either use linux-yocto (e.g. kernel-yocto.bbclass) and in which case we have to provide a kernel
SRC_URIthat implements the kernel-yocto mechanisms (for configure) like it's done in the other kernel recipe in meta-rm, or we should use kernel.bbclass only otherwise. I am worried about potential issues, since i think this is pretty much an unsupported combo.. but if you tested it and it worked, it might be fine for now..
Sorry for the late reply, it works for us, and we can/should get back to this afterwards in a follow up series.
------
Cheers,
Rui
Quoted 25 lines
Quoted 25 lines
------ Cheers, Rui
Quoted 7 lines
+
Quoted 5 lines
+# Make sure no branch is defined since here we track a specific version +KBRANCH = "" + +LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814" + +SRC_URI =
"\ +git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux;protocol=https;nobranch=1
Quoted 12 lines
Quoted 12 lines
\ + " diff --git
a/meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm_5.3.bb b/meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm_5.3.bb new file mode 100644 index 000000000000..88a06c4bb3c0 ---/dev/null+++ b/meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm_5.3.bb(quoted diff) +0
-0@@ -0,0 +1,8 @@ +# Add support for Upstream Kernel for ArmPlatforms (boards or simulators) + +SUMMARY = "Linux Kernel Upstream, supported by Arm/Linaro" + +require recipes-kernel/linux/linux-upstream-arm-platforms.inc + +SRCREV = "v${PV}" +LINUX_VERSION ?= "${PV}" --
2.25.1
Quoted 14 lines
Quoted 8 lines
Quoted 7 lines
Quoted 7 lines
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Quoted 6 lines
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
[-- Alternative Type #1: text/html; charset=UTF-8, Encoding: quoted-printable, Size: 8.3K --]
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
PATCH 2/3 arm-bsp: u-boot: move machine patches
In reply to [email protected]From: Rui Silva <[email protected]>
Move Juno patches to machine specific directory. This will allow to add others machines related patches later on.
---
.../u-boot/files/{ => juno}/u-boot_vexpress_uenv.patch | 0
meta-arm-bsp/recipes-bsp/u-boot/u-boot_2019.%.bbappend | 2 +-
2 files changed, 1 insertion(+), 1 deletion(-)
rename meta-arm-bsp/recipes-bsp/u-boot/files/{ => juno}/u-boot_vexpress_uenv.patch (100%)meta-arm-bsp/recipes-bsp/u-boot/files/juno/u-boot_vexpress_uenv.patch renamed from meta-arm-bsp/recipes-bsp/u-boot/files/u-boot_vexpress_uenv.patch +0 -0
meta-arm-bsp/recipes-bsp/u-boot/u-boot_2019.%.bbappend +1 -1
@@ -4,6 +4,6 @@ # Patch u-boot to add environment variables from Flash # -FILESEXTRAPATHS_prepend := "${THISDIR}/files:" +FILESEXTRAPATHS_prepend := "${THISDIR}/files/${MACHINE}:" SRC_URI_append_juno = " file://u-boot_vexpress_uenv.patch"
--
2.25.1
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
PATCH 3/3 arm-bsp: add support to cortex-a5 designstart
In reply to [email protected]From: Rui Silva <[email protected]>
Add tf-a recipes, u-boot, machine configuration, and documentation to support Arm Cortex-A5 Designstart.
The output of this build is compatible to run on the FVP and the FPGA implementation of the package.
For more information see:
https://community.arm.com/developer/ip-products/processors/\
designstart/b/blog/posts/\
pre-silicon-software-development-with-arm-models-for-cortex-a5-designstart
--- meta-arm-bsp/conf/machine/a5ds.conf | 25 ++ meta-arm-bsp/documentation/a5ds.md | 24 ++ ...t-arm-a5ds-move-dtb-to-a-new-address.patch | 31 ++ .../trusted-firmware-a-a5ds.inc | 22 ++ .../trusted-firmware-a_git.bbappend | 7 + .../a5ds/0001-armv7-add-mmio-timer.patch | 105 ++++++ ...-arm-add-designstart-cortex-a5-board.patch | 309 ++++++++++++++++++ .../recipes-bsp/u-boot/u-boot_%.bbappend | 8 + 8 files changed, 531 insertions(+) create mode 100644 meta-arm-bsp/conf/machine/a5ds.conf create mode 100644 meta-arm-bsp/documentation/a5ds.md create mode 100644 meta-arm-bsp/recipes-bsp/trusted-firmware-a/files/a5ds/0001-plat-arm-a5ds-move-dtb-to-a-new-address.patch create mode 100644 meta-arm-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a-a5ds.inc create mode 100644 meta-arm-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a_git.bbappend create mode 100644 meta-arm-bsp/recipes-bsp/u-boot/files/a5ds/0001-armv7-add-mmio-timer.patch create mode 100644 meta-arm-bsp/recipes-bsp/u-boot/files/a5ds/0002-board-arm-add-designstart-cortex-a5-board.patch create mode 100644 meta-arm-bsp/recipes-bsp/u-boot/u-boot_%.bbappend
meta-arm-bsp/conf/machine/a5ds.conf new file +25 -0
@@ -0,0 +1,25 @@ +# Configuration for Cortex-A5 DesignStart development board + +#@TYPE: Machine +#@NAME: a5ds machine +#@DESCRIPTION: Machine configuration for Cortex-A5 DesignStart + +require conf/machine/include/tune-cortexa5.inc + +PREFERRED_PROVIDER_virtual/kernel = "linux-upstream-arm" +PREFERRED_VERSION_linux-upstream-arm ?= "5.3%" +KBUILD_DEFCONFIG = "multi_v7_defconfig" + +EXTRA_IMAGEDEPENDS += "virtual/trusted-firmware-a u-boot" + +SERIAL_CONSOLES = "115200;ttyAMA0" + +IMAGE_FSTYPES += "tar.bz2 wic wic.nopt cpio.gz" + +EXTRA_IMAGEDEPENDS += "u-boot" + +# Cortex-a5 u-boot configuration +UBOOT_MACHINE = "designstart_ca5_defconfig" +UBOOT_IMAGE_ENTRYPOINT = "0x84000000" +UBOOT_IMAGE_LOADADDRESS = "0x84000000" +
meta-arm-bsp/documentation/a5ds.md new file +24 -0
@@ -0,0 +1,24 @@ +# Cortex-A5 DesignStart A5DS Platform Support in meta-arm-platforms + +## Howto Build and Run + +### Configuration: +In the local.conf file, MACHINE should be set as follow: +MACHINE ?= "a5ds" +DISTRO ?= "iota-tiny" + +Or set environment variables with that values: + +MACHINE "a5ds" +DISTRO "iota-tiny" + +### Build: +``bash$ bitbake iota-tiny-image``` + +### Run: +To run the result in a Fixed Virtual Platform please get: +https://git.linaro.org/landing-teams/working/arm/model-scripts + +and follow the instructions in the readme.txt file in that +repository. +
meta-arm-bsp/recipes-bsp/trusted-firmware-a/files/a5ds/0001-plat-arm-a5ds-move-dtb-to-a-new-address.patch new file +31 -0
@@ -0,0 +1,31 @@ +From d3cadbc6f1060020960dc05af0465db919bbbe2b Mon Sep 17 00:00:00 2001 +From: Rui Miguel Silva <[email protected]> +Date: Fri, 30 Aug 2019 13:38:44 +0100 +Subject: [PATCH] plat/arm: a5ds: move dtb to a new address + +When Using bigger kernel images (>8.4MB compressed zImage) and at +decompress and final location init stage of kernel start makes it +override dtb at this address, to avoid this move the dtb a little +higher in address related. + +Signed-off-by: Rui Miguel Silva <[email protected]> +--- + plat/arm/board/a5ds/fdts/a5ds_tb_fw_config.dts | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/plat/arm/board/a5ds/fdts/a5ds_tb_fw_config.dts b/plat/arm/board/a5ds/fdts/a5ds_tb_fw_config.dts +index 9ab2d9656600..c616ff772237 100644 +--- a/plat/arm/board/a5ds/fdts/a5ds_tb_fw_config.dts ++++ b/plat/arm/board/a5ds/fdts/a5ds_tb_fw_config.dts +@@ -10,7 +10,7 @@ + /* Platform Config */ + plat_arm_bl2 { + compatible = "arm,tb_fw"; +- hw_config_addr = <0x0 0x82000000>; ++ hw_config_addr = <0x0 0x83000000>; + hw_config_max_size = <0x01000000>; + /* Disable authentication for development */ + disable_auth = <0x0>; +-- +2.22.1 +
meta-arm-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a-a5ds.inc new file +22 -0
@@ -0,0 +1,22 @@ +# Cortex-A5 Designstart specific TFA support + +COMPATIBLE_MACHINE = "a5ds" +TFA_PLATFORM = "a5ds" +TFA_DEBUG = "1" +TFA_UBOOT = "1" +TFA_BUILD_TARGET = "all fip" +TFA_INSTALL_TARGET = "bl1.bin fip.bin" + +SRCREV = "5d3ee0764b03567bf3501edf47d67d72daff0cb3" +LIC_FILES_CHKSUM = "file://license.rst;md5=1dd070c98a281d18d9eefd938729b031" + +EXTRA_OEMAKE_append = " \ + ARCH=aarch32 \ + FVP_HW_CONFIG_DTS=fdts/a5ds.dts \ + ARM_ARCH_MAJOR=7 \ + AARCH32_SP=sp_min \ + ARM_CORTEX_A5=yes \ + ARM_XLAT_TABLES_LIB_V1=1 \ + " + +
meta-arm-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a_git.bbappend new file +7 -0
@@ -0,0 +1,7 @@ +# Machine specific TFAs + +MACHINE_TFA_REQUIRE ?= "" + +MACHINE_TFA_REQUIRE_a5ds = "trusted-firmware-a-a5ds.inc" + +require ${MACHINE_TFA_REQUIRE}
meta-arm-bsp/recipes-bsp/u-boot/files/a5ds/0001-armv7-add-mmio-timer.patch new file +105 -0
105 lines not on this page · raw message
meta-arm-bsp/recipes-bsp/u-boot/files/a5ds/0002-board-arm-add-designstart-cortex-a5-board.patch new file +309 -0
309 lines not on this page · raw message
meta-arm-bsp/recipes-bsp/u-boot/u-boot_%.bbappend new file +8 -0
@@ -0,0 +1,8 @@ +# Machine specific u-boot + +FILESEXTRAPATHS_prepend := "${THISDIR}/files/${MACHINE}:" + +SRC_URI_append_a5ds = " file://0001-armv7-add-mmio-timer.patch \ + file://0002-board-arm-add-designstart-cortex-a5-board.patch" + +
--
2.25.1
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Quoted 6 lines · Rui Miguel Silva
Add necessary recipes to feature equivalent to the actual releases for the sw stack for the Cortex-A5 Designstart [0] platform.
Cheers,
Rui
Series applied to the master branch of meta-arm.
Thanks,
Jon
Quoted 39 lines
[0]: https://developer.arm.com/ip-products/designstart/pro/cortex-a5
Rui Silva (3):
arm-bsp: add upstream kernel inc and v5.3 recipe
arm-bsp: u-boot: move machine patches
arm-bsp: add support to cortex-a5 designstartmeta-arm-bsp/conf/machine/a5ds.conf | 25 ++ meta-arm-bsp/documentation/a5ds.md | 24 ++ ...t-arm-a5ds-move-dtb-to-a-new-address.patch | 31 ++ .../trusted-firmware-a-a5ds.inc | 22 ++ .../trusted-firmware-a_git.bbappend | 7 + .../a5ds/0001-armv7-add-mmio-timer.patch | 105 ++++++ ...-arm-add-designstart-cortex-a5-board.patch | 309 ++++++++++++++++++ .../{ => juno}/u-boot_vexpress_uenv.patch | 0 .../recipes-bsp/u-boot/u-boot_%.bbappend | 8 + .../recipes-bsp/u-boot/u-boot_2019.%.bbappend | 2 +- .../linux/linux-upstream-arm-platforms.inc | 24 ++ .../linux/linux-upstream-arm_5.3.bb | 8 + 12 files changed, 564 insertions(+), 1 deletion(-) create mode 100644 meta-arm-bsp/conf/machine/a5ds.conf create mode 100644 meta-arm-bsp/documentation/a5ds.md create mode 100644 meta-arm-bsp/recipes-bsp/trusted-firmware-a/files/a5ds/0001-plat-arm-a5ds-move-dtb-to-a-new-address.patch create mode 100644 meta-arm-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a-a5ds.inc create mode 100644 meta-arm-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a_git.bbappend create mode 100644 meta-arm-bsp/recipes-bsp/u-boot/files/a5ds/0001-armv7-add-mmio-timer.patch create mode 100644 meta-arm-bsp/recipes-bsp/u-boot/files/a5ds/0002-board-arm-add-designstart-cortex-a5-board.patch rename meta-arm-bsp/recipes-bsp/u-boot/files/{ => juno}/u-boot_vexpress_uenv.patch (100%) create mode 100644 meta-arm-bsp/recipes-bsp/u-boot/u-boot_%.bbappend create mode 100644 meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm-platforms.inc create mode 100644 meta-arm-bsp/recipes-kernel/linux/linux-upstream-arm_5.3.bb--
2.25.1IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.