date:20161201

[meta-xilinx] [PATCH v2] machine-xilinx-default.inc: Add XSERVER

2016-12-01 Thread Manjukumar Matha

Add X org X server configurations, armsoc driver for zynqmp

Signed-off-by: Manjukumar Matha 
---
 conf/machine/include/machine-xilinx-default.inc | 14 ++
 1 file changed, 14 insertions(+)

diff --git a/conf/machine/include/machine-xilinx-default.inc 
b/conf/machine/include/machine-xilinx-default.inc
index 1dfef48..9b397ce 100644
--- a/conf/machine/include/machine-xilinx-default.inc
+++ b/conf/machine/include/machine-xilinx-default.inc
@@ -39,4 +39,18 @@ UBOOT_ELF_aarch64 ?= "u-boot.elf"
 MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS_append_zynqmp = " \
${@bb.utils.contains('MACHINE_FEATURES', 'mali', 
bb.utils.contains('PREFERRED_PROVIDER_virtual/kernel', 'linux-xlnx', 
'kernel-module-mali', '', d), '', d)} \
"
+XSERVER ?= " \
+   xserver-xorg \
+   xf86-input-evdev \
+   xf86-input-mouse \
+   xf86-input-keyboard \
+   xf86-video-fbdev \
+   ${XSERVER_EXT} \
+   "
+
+XSERVER_EXT ?= ""
+XSERVER_EXT_zynqmp ?= " \
+   ${@bb.utils.contains('MACHINE_FEATURES', 'mali', 
bb.utils.contains('DISTRO_FEATURES', 'opengl', 'xserver-xorg-extension-glx', 
'', d), '', d)} \
+   xf86-video-armsoc \
+   "
 
-- 
2.7.4

-- 
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx

[meta-xilinx] [PATCH] arm-trusted-firmware_git.bb: Fix out-of-tree build

2016-12-01 Thread Manjukumar Matha

This patch enabled out-of-tree build for arm-trusted-firmware. This also
enables EXTERNALSRC builds for ATF

Signed-off-by: Manjukumar Matha 
---
 recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_git.bb 
b/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_git.bb
index 4cd9cf3..0a4e55a 100644
--- a/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_git.bb
+++ b/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_git.bb
@@ -36,7 +36,7 @@ do_configure() {
 }
 
 do_compile() {
-   oe_runmake PLAT=${PLATFORM} RESET_TO_BL31=1 bl31
+   oe_runmake -C ${S} PLAT=${PLATFORM} RESET_TO_BL31=1 bl31
 }
 
 do_install() {
-- 
2.7.4

-- 
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx

[meta-xilinx] [PATCH 1/2] kc705-microblazeel: Update to 2016.3 Xilinx design

2016-12-01 Thread Manjukumar Matha

Change kc705-microblazeel to reflect v2016.3 Xilinx tools.

Signed-off-by: Manjukumar Matha 
---
 recipes-bsp/device-tree/files/kc705/pl.dtsi|  51 +-
 .../device-tree/files/kc705/system-conf.dtsi   |  21 +-
 ...aze-kc705-Convert-microblaze-generic-to-k.patch | 641 +
 .../bsp/kc705-microblazeel/kc705-microblazeel.cfg  |   4 +
 4 files changed, 335 insertions(+), 382 deletions(-)

diff --git a/recipes-bsp/device-tree/files/kc705/pl.dtsi 
b/recipes-bsp/device-tree/files/kc705/pl.dtsi
index e80b99b..8f06467 100644
--- a/recipes-bsp/device-tree/files/kc705/pl.dtsi
+++ b/recipes-bsp/device-tree/files/kc705/pl.dtsi
@@ -1,7 +1,7 @@
 /*
  * CAUTION: This file is automatically generated by Xilinx.
- * Version: HSI 2016.1
- * Today is: Tue Apr 19 17:57:03 2016
+ * Version: HSI 2016.3
+ * Today is: Tue Sep 13 19:30:07 2016
 */
 
 
@@ -60,6 +60,7 @@
xlnx,debug-enabled = <0x1>;
xlnx,debug-event-counters = <0x5>;
xlnx,debug-external-trace = <0x0>;
+   xlnx,debug-interface = <0x0>;
xlnx,debug-latency-counters = <0x1>;
xlnx,debug-profile-size = <0x0>;
xlnx,debug-trace-size = <0x2000>;
@@ -93,6 +94,7 @@
xlnx,interrupt-is-edge = <0x0>;
xlnx,interrupt-mon = <0x0>;
xlnx,ip-axi-mon = <0x0>;
+   xlnx,lockstep-master = <0x0>;
xlnx,lockstep-select = <0x0>;
xlnx,lockstep-slave = <0x0>;
xlnx,mmu-dtlb-size = <0x4>;
@@ -114,6 +116,12 @@
xlnx,pvr-user1 = <0x00>;
xlnx,pvr-user2 = <0x>;
xlnx,reset-msr = <0x>;
+   xlnx,reset-msr-bip = <0x0>;
+   xlnx,reset-msr-dce = <0x0>;
+   xlnx,reset-msr-ee = <0x0>;
+   xlnx,reset-msr-eip = <0x0>;
+   xlnx,reset-msr-ice = <0x0>;
+   xlnx,reset-msr-ie = <0x0>;
xlnx,sco = <0x0>;
xlnx,trace = <0x0>;
xlnx,unaligned-exceptions = <0x1>;
@@ -173,7 +181,11 @@
xlnx = <0x0>;
xlnx,axiliteclkrate = <0x0>;
xlnx,axisclkrate = <0x0>;
+   xlnx,enableasyncsgmii = <0x0>;
xlnx,gt-type = <0x0>;
+   xlnx,gtinex = <0x0>;
+   xlnx,gtlocation = <0x0>;
+   xlnx,gtrefclksrc = <0x0>;
xlnx,phy-type = <0x1>;
xlnx,phyaddr = <0x1>;
xlnx,rable = <0x0>;
@@ -195,7 +207,10 @@
#dma-cells = <1>;
axistream-connected = <&axi_ethernet>;
axistream-control-connected = <&axi_ethernet>;
-   compatible = "xlnx,axi-dma-1.00.a";
+   clock-frequency = <2>;
+   clock-names = "s_axi_lite_aclk";
+   clocks = <&clk_bus_0>;
+   compatible = "xlnx,eth-dma";
interrupt-parent = <µblaze_0_axi_intc>;
interrupts = <3 2 2 2>;
reg = <0x41e0 0x1>;
@@ -214,7 +229,7 @@
xlnx,trig0-assert = <0x1>;
xlnx,trig1-assert = <0x1>;
};
-   dip_switches_4bits: gpio@4001 {
+   calib_complete_gpio: gpio@4001 {
#gpio-cells = <2>;
compatible = "xlnx,xps-gpio-1.00.a";
gpio-controller ;
@@ -225,6 +240,24 @@
xlnx,all-outputs-2 = <0x0>;
xlnx,dout-default = <0x>;
xlnx,dout-default-2 = <0x>;
+   xlnx,gpio-width = <0x1>;
+   xlnx,gpio2-width = <0x20>;
+   xlnx,interrupt-present = <0x0>;
+   xlnx,is-dual = <0x0>;
+   xlnx,tri-default = <0x>;
+   xlnx,tri-default-2 = <0x>;
+   };
+   dip_switches_4bits: gpio@4002 {
+   #gpio-cells = <2>;
+   compatible = "xlnx,xps-gpio-1.00.a";
+   gpio-controller ;
+   reg = <0x4002 0x1>;
+   xlnx,all-inputs = <0x1>;
+   xlnx,all-inputs-2 = <0x0>;
+   xlnx,all-outputs = <0x0>;
+   xlnx,all-outputs-2 = <0x0>;
+   xlnx,dout-default = <0x>;
+   xlnx,dout-default-2 = <0x>;
xlnx

[meta-xilinx] [PATCH 2/2] u-boot-xlnx_2016.07.bb: Add kc705 patch

2016-12-01 Thread Manjukumar Matha

Add kc705-microblazeel patch for u-boot

Signed-off-by: Manjukumar Matha 
---
 recipes-bsp/u-boot/u-boot-xlnx_2016.07.bb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/recipes-bsp/u-boot/u-boot-xlnx_2016.07.bb 
b/recipes-bsp/u-boot/u-boot-xlnx_2016.07.bb
index 118fed8..7a15154 100644
--- a/recipes-bsp/u-boot/u-boot-xlnx_2016.07.bb
+++ b/recipes-bsp/u-boot/u-boot-xlnx_2016.07.bb
@@ -10,6 +10,8 @@ FILESEXTRAPATHS_prepend := "${THISDIR}/u-boot-xlnx:"
 
 SRC_URI_append = " file://0001-compiler-gcc6.h-Fix-u-boot-issue-for-gcc6.patch"
 
+SRC_URI_append_kc705-microblazeel = " 
file://microblaze-kc705-Convert-microblaze-generic-to-k.patch"
+
 LICENSE = "GPLv2+"
 LIC_FILES_CHKSUM = 
"file://README;beginline=1;endline=6;md5=157ab8408beab40cd8ce1dc69f702a6c"
 
-- 
2.7.4

-- 
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx

[meta-xilinx] [PATCH 0/2] Update kc705 design

2016-12-01 Thread Manjukumar Matha

Update kc705-microblazeel machine for 2016.3 tool release

Manjukumar Matha (2):
  kc705-microblazeel: Update to 2016.3 Xilinx design
  u-boot-xlnx_2016.07.bb: Add kc705 patch

 recipes-bsp/device-tree/files/kc705/pl.dtsi|  51 +-
 .../device-tree/files/kc705/system-conf.dtsi   |  21 +-
 ...aze-kc705-Convert-microblaze-generic-to-k.patch | 641 +
 recipes-bsp/u-boot/u-boot-xlnx_2016.07.bb  |   2 +
 .../bsp/kc705-microblazeel/kc705-microblazeel.cfg  |   4 +
 5 files changed, 337 insertions(+), 382 deletions(-)

-- 
2.7.4

-- 
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx

[meta-xilinx] [PATCH 2/2] u-boot-xlnx_2016.01.bb: Remove older u-boot

2016-12-01 Thread Manjukumar Matha

Remove older u-boot version

Signed-off-by: Manjukumar Matha 
---
 recipes-bsp/u-boot/u-boot-xlnx_2016.01.bb | 31 ---
 1 file changed, 31 deletions(-)
 delete mode 100644 recipes-bsp/u-boot/u-boot-xlnx_2016.01.bb

diff --git a/recipes-bsp/u-boot/u-boot-xlnx_2016.01.bb 
b/recipes-bsp/u-boot/u-boot-xlnx_2016.01.bb
deleted file mode 100644
index a6b243d..000
--- a/recipes-bsp/u-boot/u-boot-xlnx_2016.01.bb
+++ /dev/null
@@ -1,31 +0,0 @@
-include u-boot-xlnx.inc
-include u-boot-spl-zynq-init.inc
-
-XILINX_RELEASE_VERSION = "v2016.2"
-SRCREV = "0daf88c7f8c9085a81336a0ad2dd3bcc84c7a18a"
-PV = "v2016.01-xilinx-${XILINX_RELEASE_VERSION}+git${SRCPV}"
-
-FILESEXTRAPATHS_prepend := "${THISDIR}/u-boot-xlnx:"
-
-SRC_URI_append = " file://0001-compiler-gcc6.h-Fix-u-boot-issue-for-gcc6.patch"
-
-SRC_URI_append_kc705-microblazeel = " 
file://microblaze-kc705-Convert-microblaze-generic-to-k.patch"
-
-LICENSE = "GPLv2+"
-LIC_FILES_CHKSUM = 
"file://README;beginline=1;endline=6;md5=157ab8408beab40cd8ce1dc69f702a6c"
-
-UBOOT_ENV_zc702-zynq7 = "uEnv"
-UBOOT_ENV_zedboard-zynq7 = "uEnv"
-
-SRC_URI_append_zc702-zynq7 = " file://uEnv.txt"
-SRC_URI_append_zedboard-zynq7 = " file://uEnv.txt"
-
-# u-boot 2016.01 has support for these
-HAS_PS7INIT ?= " \
-   zynq_microzed_config \
-   zynq_zed_config \
-   zynq_zc702_config \
-   zynq_zc706_config \
-   zynq_zybo_config \
-   "
-
-- 
2.7.4

-- 
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx

[meta-xilinx] [PATCH 0/2] Update u-boot-xlnx version

2016-12-01 Thread Manjukumar Matha

Update u-boot-xlnx version

Manjukumar Matha (2):
  u-boot-xlnx_2016.07.bb: Update u-boot version
  u-boot-xlnx_2016.01.bb: Remove older u-boot

 recipes-bsp/u-boot/u-boot-xlnx_2016.01.bb | 31 ---
 recipes-bsp/u-boot/u-boot-xlnx_2016.07.bb | 30 ++
 2 files changed, 30 insertions(+), 31 deletions(-)
 delete mode 100644 recipes-bsp/u-boot/u-boot-xlnx_2016.01.bb
 create mode 100644 recipes-bsp/u-boot/u-boot-xlnx_2016.07.bb

-- 
2.7.4

-- 
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx

[meta-xilinx] [PATCH 1/2] u-boot-xlnx_2016.07.bb: Update u-boot version

2016-12-01 Thread Manjukumar Matha

Upgrade u-boot to supported 2016.07 version

Signed-off-by: Manjukumar Matha 
---
 recipes-bsp/u-boot/u-boot-xlnx_2016.07.bb | 30 ++
 1 file changed, 30 insertions(+)
 create mode 100644 recipes-bsp/u-boot/u-boot-xlnx_2016.07.bb

diff --git a/recipes-bsp/u-boot/u-boot-xlnx_2016.07.bb 
b/recipes-bsp/u-boot/u-boot-xlnx_2016.07.bb
new file mode 100644
index 000..118fed8
--- /dev/null
+++ b/recipes-bsp/u-boot/u-boot-xlnx_2016.07.bb
@@ -0,0 +1,30 @@
+include u-boot-xlnx.inc
+include u-boot-spl-zynq-init.inc
+
+XILINX_RELEASE_VERSION = "v2016.3"
+# this matches u-boot-xlnx 'xilinx-v2016.3' release tag
+SRCREV = "95e11f6eb4bc07bbee12a4217c58146bddac61b2"
+PV = "v2016.07-xilinx-${XILINX_RELEASE_VERSION}+git${SRCPV}"
+
+FILESEXTRAPATHS_prepend := "${THISDIR}/u-boot-xlnx:"
+
+SRC_URI_append = " file://0001-compiler-gcc6.h-Fix-u-boot-issue-for-gcc6.patch"
+
+LICENSE = "GPLv2+"
+LIC_FILES_CHKSUM = 
"file://README;beginline=1;endline=6;md5=157ab8408beab40cd8ce1dc69f702a6c"
+
+UBOOT_ENV_zc702-zynq7 = "uEnv"
+UBOOT_ENV_zedboard-zynq7 = "uEnv"
+
+SRC_URI_append_zc702-zynq7 = " file://uEnv.txt"
+SRC_URI_append_zedboard-zynq7 = " file://uEnv.txt"
+
+# u-boot 2016.07 has support for these
+HAS_PS7INIT ?= " \
+   zynq_microzed_config \
+   zynq_zed_config \
+   zynq_zc702_config \
+   zynq_zc706_config \
+   zynq_zybo_config \
+   "
+
-- 
2.7.4

-- 
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx

Re: [meta-xilinx] [PATCH] glibc: Fix up MicroBlaze pt-vfork compat symbols

2016-12-01 Thread Nathan Rossi

Merged.

Regards,
Nathan

On 24 November 2016 at 21:38, Nathan Rossi  wrote:
> A bug has been present in glibc for a while where a symbol is emitted in
> libpthread.so which is corrupt. Whilst previously this has not been an
> issue due to how binutils has handled it, recent binutils behaviour has
> changed enough to make this bug surface as a linker error.
>
> Depending on the host (behaviour and native dependencies) the cross
> binutils that is built may emit different values for the corrupt symbol.
> This appears as an error similar to the following when linking against
> libpthread.so (e.g. librt links against libpthread in glibc):
>
> invalid string offset 1843814912 >= 4913 for section `.dynstr'
>
> This patch fixes up the symbols emitted for libpthread.so without
> breaking any libpthread or libc ABI. See the glibc patch for more
> specifics.
>
> Signed-off-by: Nathan Rossi 
> ---
>  ...oBlaze-fix-up-pt-vfork-symbol-definitions.patch | 105 
> +
>  .../glibc/glibc-initial_2.24.bbappend  |   4 +
>  recipes-microblaze/glibc/glibc_2.24.bbappend   |   4 +
>  3 files changed, 113 insertions(+)
>  create mode 100644 
> recipes-microblaze/glibc/files/MicroBlaze-fix-up-pt-vfork-symbol-definitions.patch
>  create mode 100644 recipes-microblaze/glibc/glibc-initial_2.24.bbappend
>  create mode 100644 recipes-microblaze/glibc/glibc_2.24.bbappend
>
> diff --git 
> a/recipes-microblaze/glibc/files/MicroBlaze-fix-up-pt-vfork-symbol-definitions.patch
>  
> b/recipes-microblaze/glibc/files/MicroBlaze-fix-up-pt-vfork-symbol-definitions.patch
> new file mode 100644
> index 00..ed37d6349f
> --- /dev/null
> +++ 
> b/recipes-microblaze/glibc/files/MicroBlaze-fix-up-pt-vfork-symbol-definitions.patch
> @@ -0,0 +1,105 @@
> +From 873fc4bf58d6cc8d579a65224350ce3adddc6c2a Mon Sep 17 00:00:00 2001
> +From: Nathan Rossi 
> +Date: Wed, 23 Nov 2016 22:30:29 +1000
> +Subject: [PATCH] MicroBlaze: fix up pt-vfork symbol definitions
> +
> +Due to the reuse of the alpha/pt-vfork.S implementation additional
> +symbols are emitted for libpthread which are invalid due to the
> +non-existence of a '__libc_vfork' symbol/implementation. A symbol is
> +emitted which references __libc_vfork and is invalid which causes the
> +linker to emit a corrupt symbol entry:
> +
> +180:  0x24a91 NOTYPE  LOCAL  DEFAULT  UND 
> +
> +Depending on the internals of the linker this corrupt symbol is either a
> +valid symbol as above or an completely invalid symbol that causes issues
> +when linking against libpthread.so:
> +
> +179: 564b 0x825fd688 : 11 : 4 HIDDEN
> +[: 54]   UND 
> +
> +In both cases this is the 'vfork@GLIBC_2.18' compat_symbol which is
> +aliased as the local '__libc_vfork'. (in libpthread.so)
> +
> +12:  0 NOTYPE  GLOBAL DEFAULT  UND vfork@GLIBC_2.18
> +
> +Due to how MicroBlaze differs from other architectures, it is special in
> +that it only implements '__vfork' and due to the weak_alias in vfork.S
> +also defines 'vfork' for both libc and libpthread. No other symbols
> +(e.g. '__vfork_compat') are part of the ABI.
> +
> +This change removes the compatible symbol generation provided by
> +alpha/pt-vfork.S and sets up the 'vfork' and '__vfork' symbols to be
> +provided in libpthread based on SHLIB_COMPAT. This avoids the generation
> +of invalid symbols but maintains the expected libc and libpthread vfork
> +ABIs.
> +
> +Signed-off-by: Nathan Rossi 
> +Upstream-Status: Pending
> +---
> + sysdeps/unix/sysv/linux/microblaze/pt-vfork.S | 40 
> ++-
> + sysdeps/unix/sysv/linux/microblaze/vfork.S|  4 ++-
> + 2 files changed, 42 insertions(+), 2 deletions(-)
> +
> +diff --git a/sysdeps/unix/sysv/linux/microblaze/pt-vfork.S 
> b/sysdeps/unix/sysv/linux/microblaze/pt-vfork.S
> +index 65cc3823ac..82bc36eecc 100644
> +--- a/sysdeps/unix/sysv/linux/microblaze/pt-vfork.S
>  b/sysdeps/unix/sysv/linux/microblaze/pt-vfork.S
> +@@ -1 +1,39 @@
> +-#include 
> ++/* vfork ABI-compatibility entry points for libpthread.
> ++   Copyright (C) 2014-2016 Free Software Foundation, Inc.
> ++   This file is part of the GNU C Library.
> ++
> ++   The GNU C Library is free software; you can redistribute it and/or
> ++   modify it under the terms of the GNU Lesser General Public
> ++   License as published by the Free Software Foundation; either
> ++   version 2.1 of the License, or (at your option) any later version.
> ++
> ++   The GNU C Library is distributed in the hope that it will be useful,
> ++   but WITHOUT ANY WARRANTY; without even the implied warranty of
> ++   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
> ++   Lesser General Public License for more details.
> ++
> ++   You should have received a copy of the GNU Lesser General Public
> ++   License along with the GNU C Library; if not, see
> ++   .  */
> ++
> ++#include 
> ++
> ++/* libpthread used to have its own vfork implementation th

Re: [meta-xilinx] [PATCH 0/4] Embed Xilinx Release Versions into recipe PV

2016-12-01 Thread Nathan Rossi

Merged.

Regards,
Nathan

On 23 November 2016 at 18:52, Nathan Rossi  wrote:
> Currently all the Xilinx specific forks of certain components
> (linux-xlnx, u-boot-xlnx, arm-trusted-firmware, qemu-xilinx) have a PV
> that only contains the git abbrev commit id of the respective Xilinx
> release.  This series sets the Xilinx Release Version for each
> respective recipe as well as embedding it into the PV after the base
> version of the component (e.g. 4.6-xilinx-v2016.3).
>
> Nathan Rossi (4):
>   linux-xlnx: Embed Xilinx Release Version in PV and EXTENSION
>   u-boot-xlnx: Embed Xilinx Release Version into PV
>   arm-trusted-firmware: Embed Xilinx Release Version into PV
>   qemu-xilinx: Embed Xilinx Release Version into PV
>
>  recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_git.bb | 4 ++--
>  recipes-bsp/u-boot/u-boot-xlnx-dev.bb| 2 +-
>  recipes-bsp/u-boot/u-boot-xlnx.inc   | 2 --
>  recipes-bsp/u-boot/u-boot-xlnx_2016.01.bb| 4 ++--
>  recipes-devtools/qemu/qemu-xilinx_2.2.5.bb   | 4 ++--
>  recipes-kernel/linux/linux-xlnx.inc  | 3 ++-
>  recipes-kernel/linux/linux-xlnx_4.6.bb   | 2 +-
>  7 files changed, 10 insertions(+), 11 deletions(-)
>
> --
> 2.10.2
-- 
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx

Re: [meta-xilinx] uboot CONFIG_SYS_SDRAM_SIZE allocation error

2016-12-01 Thread Nathan Rossi

On 1 December 2016 at 20:28, Arno Steffens  wrote:
> Thanks Mike and Nathan for feedback.
> As this is really effort to test if uboot fails (I have to flash (slow) via 
> xilinx jtag the hole qspi) I am asking once again:

You shouldn't need to write to QSPI to test if you have JTAG access to
the Zynq. Have a read of the JTAG loading section in the
README.booting.

http://git.yoctoproject.org/cgit/cgit.cgi/meta-xilinx/tree/README.booting.md#n26

(You can substitute fsbl.elf in place of u-boot-spl.bin if you are using FSBL).

You can also use this as a potentially faster way to write to your
QSPI, using u-boot to load the images via TFTP and then writing them
to QSPI from ram.

>
> So I will delete (or better said not add) CONFIG_SYS_SDRAM_SIZE?
> My devicetree aready looks like this, so I expected this works
>
>   memory {
> device_type = "memory";
> reg = <0x0 0x1f00>;

This should define your entire memory. Aka 0x0 - 0x2000.

>   };
>
> I add than (is this optional or required?)
> reserved-memory {

Don't forget 'ranges;' and '#*-cells'.

>   buffer_fpga: buffer_fpga@1f00 {
>   reg = <0x1f00 0x100>;

You may want to also consider 'no-map;' here depending on how you use
this region, have a look at the documentation linked below.

> };
>
> (what meaning does have the name as here "buffer_fpga" - is it free to chose 
> ?)

The node name is not particularly important, what you have is fine.

Full documentation on how the reserved-memory node works:

https://www.kernel.org/doc/Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt

However it is worth noting that u-boot does not handle
'reserved-memory' nodes (at least at the moment). So if your fpga
buffer is needed during u-boot execution (aka you load the fpga with
FSBL or U-Boot and it immediately accesses the memory segment), then
the 'reserved-memory' options will not work for you and you will have
to do as you have done previously and reduce the memory size.

>
> Than you mentions fdt_high. Honestly, not fully understand what this means.
> Do I get it right, that with the default it is load to beyond my physical 
> memory (0x2000.)?
> But which address I have to chose - any inbetween 0 and 0x1e00. - so that 
> devicetree fits into the 0x1f00. range for linux?
>
> set fdt_high 0x1e00  ?

>From the u-boot readme:

  fdt_high - if set this restricts the maximum address that the
 flattened device tree will be copied into upon boot.
 For example, if you have a system with 1 GB memory
 at physical address 0x1000, while Linux kernel
 only recognizes the first 704 MB as low memory, you
 may need to set fdt_high as 0x3C00 to have the
 device tree blob be copied to the maximum address
 of the 704 MB low memory, so that Linux kernel can
 access it during the boot procedure.

The kernel does not handle relocating the dtb, so make sure fdt_high
(and initrd_high) is below the reserved region.

Regards,
Nathan

>
> Thanks,
> Arno
>
>
>> Gesendet: Donnerstag, 01. Dezember 2016 um 09:44 Uhr
>> Von: "Nathan Rossi" 
>> An: "Arno Steffens" 
>> Cc: meta-xilinx@yoctoproject.org
>> Betreff: Re: [meta-xilinx] uboot CONFIG_SYS_SDRAM_SIZE allocation error
>>
>> On 1 December 2016 at 17:39, Arno Steffens  wrote:
>> >
>> > I switched from an older yocto u-boot (2015.01) to recent one (2016.01). 
>> > Now I can't boot anymore:
>> >
>> > Zynq> boot
>> > QSPI: Kernel/Devicetree - NFS: rootfs
>> > SF: Detected S25FL128S_64K with page size 256 Bytes, erase size 64 KiB, 
>> > total 16 MiB
>> > device 0 offset 0x4b, size 0x1
>> > SF: 65536 bytes @ 0x4b Read: OK
>> > device 0 offset 0x4c, size 0x38
>> > SF: 3670016 bytes @ 0x4c Read: OK
>> > ## Booting kernel from Legacy Image at 0208 ...
>> >Image Name:   Linux-4.4.0-xilinx
>> >Image Type:   ARM Linux Kernel Image (uncompressed)
>> >Data Size:3513736 Bytes = 3.4 MiB
>> >Load Address: 8000
>> >Entry Point:  8000
>> >Verifying Checksum ... OK
>> > ## Flattened Device Tree blob at 0200
>> >Booting using the fdt blob at 0x200
>> >Loading Kernel Image ... OK
>> > ERROR: Failed to allocate 0x82a5 bytes below 0x0.
>> > device tree - allocation error
>> > FDT creation failed! hanging...### ERROR ### Please RESET the board ###
>> >
>> > 
>> > My guess for reason of that is following, but I can't solve it.
>> >
>> > My board (based on MicroZed) has 512MB Ram, but 16MB are used for FPGA.
>> >
>> > I managed that before with
>> >  #ifndef __CONFIG_ZYNQ_MICROZED_H
>> >  #define __CONFIG_ZYNQ_MICROZED_H
>> >
>> > -#define CONFIG_SYS_SDRAM_SIZE  (1024 * 1024 * 1024)
>> > +#define CONFIG_SYS_SDRAM_SIZE  (496 * 1024 * 1024)
>> >
>> > In newer Uboot I can't find this definition not in that way. Nevertheless 
>> > I added this line.
>> > (If not, that my last message is "Starting kernel ...")
>> >
>> > Although digging around, I couldn't find how nowadays this is handled.

Re: [meta-xilinx] uboot CONFIG_SYS_SDRAM_SIZE allocation error

2016-12-01 Thread Arno Steffens

Thanks Mike and Nathan for feedback.
As this is really effort to test if uboot fails (I have to flash (slow) via 
xilinx jtag the hole qspi) I am asking once again:

So I will delete (or better said not add) CONFIG_SYS_SDRAM_SIZE?
My devicetree aready looks like this, so I expected this works

  memory {
device_type = "memory";
reg = <0x0 0x1f00>;
  };

I add than (is this optional or required?)
reserved-memory {
  buffer_fpga: buffer_fpga@1f00 {
  reg = <0x1f00 0x100>;
};

(what meaning does have the name as here "buffer_fpga" - is it free to chose ?)

Than you mentions fdt_high. Honestly, not fully understand what this means.
Do I get it right, that with the default it is load to beyond my physical 
memory (0x2000.)? 
But which address I have to chose - any inbetween 0 and 0x1e00. - so that 
devicetree fits into the 0x1f00. range for linux?

set fdt_high 0x1e00  ?

Thanks,
Arno
 

> Gesendet: Donnerstag, 01. Dezember 2016 um 09:44 Uhr
> Von: "Nathan Rossi" 
> An: "Arno Steffens" 
> Cc: meta-xilinx@yoctoproject.org
> Betreff: Re: [meta-xilinx] uboot CONFIG_SYS_SDRAM_SIZE allocation error
>
> On 1 December 2016 at 17:39, Arno Steffens  wrote:
> >
> > I switched from an older yocto u-boot (2015.01) to recent one (2016.01). 
> > Now I can't boot anymore:
> >
> > Zynq> boot
> > QSPI: Kernel/Devicetree - NFS: rootfs
> > SF: Detected S25FL128S_64K with page size 256 Bytes, erase size 64 KiB, 
> > total 16 MiB
> > device 0 offset 0x4b, size 0x1
> > SF: 65536 bytes @ 0x4b Read: OK
> > device 0 offset 0x4c, size 0x38
> > SF: 3670016 bytes @ 0x4c Read: OK
> > ## Booting kernel from Legacy Image at 0208 ...
> >Image Name:   Linux-4.4.0-xilinx
> >Image Type:   ARM Linux Kernel Image (uncompressed)
> >Data Size:3513736 Bytes = 3.4 MiB
> >Load Address: 8000
> >Entry Point:  8000
> >Verifying Checksum ... OK
> > ## Flattened Device Tree blob at 0200
> >Booting using the fdt blob at 0x200
> >Loading Kernel Image ... OK
> > ERROR: Failed to allocate 0x82a5 bytes below 0x0.
> > device tree - allocation error
> > FDT creation failed! hanging...### ERROR ### Please RESET the board ###
> >
> > 
> > My guess for reason of that is following, but I can't solve it.
> >
> > My board (based on MicroZed) has 512MB Ram, but 16MB are used for FPGA.
> >
> > I managed that before with
> >  #ifndef __CONFIG_ZYNQ_MICROZED_H
> >  #define __CONFIG_ZYNQ_MICROZED_H
> >
> > -#define CONFIG_SYS_SDRAM_SIZE  (1024 * 1024 * 1024)
> > +#define CONFIG_SYS_SDRAM_SIZE  (496 * 1024 * 1024)
> >
> > In newer Uboot I can't find this definition not in that way. Nevertheless I 
> > added this line.
> > (If not, that my last message is "Starting kernel ...")
> >
> > Although digging around, I couldn't find how nowadays this is handled. This 
> > seems memory size is not board-specific anymore. How it is handled?
> 
> Current versions of u-boot use the memory size which is provided by
> device trees now (for zynq), so make sure you update the value in your
> u-boot device tree. (you can used 'reserved-memory' for the 16MB FPGA
> segment)
> 
> Also it is additionally worth noting to make sure "fdt_high" is set in
> your environment such that you can load at 0x0200_ or above (the
> default is normally set to 0x2000_).
> 
> Regards,
> Nathan
> 
> >
> > Thanks
> > --
> > ___
> > meta-xilinx mailing list
> > meta-xilinx@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/meta-xilinx
> 
-- 
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx

Re: [meta-xilinx] uboot CONFIG_SYS_SDRAM_SIZE allocation error

2016-12-01 Thread Mike Looijmans

The RAM config in current u-boot is taken from the devicetree. Modify the 
"memory" node.


You should make a "reserved" RAM region instead of reducing the size.

On 01-12-16 08:39, Arno Steffens wrote:

I switched from an older yocto u-boot (2015.01) to recent one (2016.01). Now I 
can't boot anymore:

Zynq> boot
QSPI: Kernel/Devicetree - NFS: rootfs
SF: Detected S25FL128S_64K with page size 256 Bytes, erase size 64 KiB, total 
16 MiB
device 0 offset 0x4b, size 0x1
SF: 65536 bytes @ 0x4b Read: OK
device 0 offset 0x4c, size 0x38
SF: 3670016 bytes @ 0x4c Read: OK
## Booting kernel from Legacy Image at 0208 ...
   Image Name:   Linux-4.4.0-xilinx
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:3513736 Bytes = 3.4 MiB
   Load Address: 8000
   Entry Point:  8000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 0200
   Booting using the fdt blob at 0x200
   Loading Kernel Image ... OK
ERROR: Failed to allocate 0x82a5 bytes below 0x0.
device tree - allocation error
FDT creation failed! hanging...### ERROR ### Please RESET the board ###


My guess for reason of that is following, but I can't solve it.

My board (based on MicroZed) has 512MB Ram, but 16MB are used for FPGA.

I managed that before with
 #ifndef __CONFIG_ZYNQ_MICROZED_H
 #define __CONFIG_ZYNQ_MICROZED_H

-#define CONFIG_SYS_SDRAM_SIZE  (1024 * 1024 * 1024)
+#define CONFIG_SYS_SDRAM_SIZE  (496 * 1024 * 1024)

In newer Uboot I can't find this definition not in that way. Nevertheless I 
added this line.
(If not, that my last message is "Starting kernel ...")

Although digging around, I couldn't find how nowadays this is handled. This 
seems memory size is not board-specific anymore. How it is handled?

Thanks





Kind regards,

Mike Looijmans
System Expert

TOPIC Products
Materiaalweg 4, NL-5681 RJ Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
E-mail: mike.looijm...@topicproducts.com
Website: www.topicproducts.com

Please consider the environment before printing this e-mail





--
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx

Re: [meta-xilinx] uboot CONFIG_SYS_SDRAM_SIZE allocation error

2016-12-01 Thread Nathan Rossi

On 1 December 2016 at 17:39, Arno Steffens  wrote:
>
> I switched from an older yocto u-boot (2015.01) to recent one (2016.01). Now 
> I can't boot anymore:
>
> Zynq> boot
> QSPI: Kernel/Devicetree - NFS: rootfs
> SF: Detected S25FL128S_64K with page size 256 Bytes, erase size 64 KiB, total 
> 16 MiB
> device 0 offset 0x4b, size 0x1
> SF: 65536 bytes @ 0x4b Read: OK
> device 0 offset 0x4c, size 0x38
> SF: 3670016 bytes @ 0x4c Read: OK
> ## Booting kernel from Legacy Image at 0208 ...
>Image Name:   Linux-4.4.0-xilinx
>Image Type:   ARM Linux Kernel Image (uncompressed)
>Data Size:3513736 Bytes = 3.4 MiB
>Load Address: 8000
>Entry Point:  8000
>Verifying Checksum ... OK
> ## Flattened Device Tree blob at 0200
>Booting using the fdt blob at 0x200
>Loading Kernel Image ... OK
> ERROR: Failed to allocate 0x82a5 bytes below 0x0.
> device tree - allocation error
> FDT creation failed! hanging...### ERROR ### Please RESET the board ###
>
> 
> My guess for reason of that is following, but I can't solve it.
>
> My board (based on MicroZed) has 512MB Ram, but 16MB are used for FPGA.
>
> I managed that before with
>  #ifndef __CONFIG_ZYNQ_MICROZED_H
>  #define __CONFIG_ZYNQ_MICROZED_H
>
> -#define CONFIG_SYS_SDRAM_SIZE  (1024 * 1024 * 1024)
> +#define CONFIG_SYS_SDRAM_SIZE  (496 * 1024 * 1024)
>
> In newer Uboot I can't find this definition not in that way. Nevertheless I 
> added this line.
> (If not, that my last message is "Starting kernel ...")
>
> Although digging around, I couldn't find how nowadays this is handled. This 
> seems memory size is not board-specific anymore. How it is handled?

Current versions of u-boot use the memory size which is provided by
device trees now (for zynq), so make sure you update the value in your
u-boot device tree. (you can used 'reserved-memory' for the 16MB FPGA
segment)

Also it is additionally worth noting to make sure "fdt_high" is set in
your environment such that you can load at 0x0200_ or above (the
default is normally set to 0x2000_).

Regards,
Nathan

>
> Thanks
> --
> ___
> meta-xilinx mailing list
> meta-xilinx@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-xilinx
-- 
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx

[meta-xilinx] [PATCH v2] machine-xilinx-default.inc: Add XSERVER

[meta-xilinx] [PATCH] arm-trusted-firmware_git.bb: Fix out-of-tree build

[meta-xilinx] [PATCH 1/2] kc705-microblazeel: Update to 2016.3 Xilinx design

[meta-xilinx] [PATCH 2/2] u-boot-xlnx_2016.07.bb: Add kc705 patch

[meta-xilinx] [PATCH 0/2] Update kc705 design

[meta-xilinx] [PATCH 2/2] u-boot-xlnx_2016.01.bb: Remove older u-boot

[meta-xilinx] [PATCH 0/2] Update u-boot-xlnx version

[meta-xilinx] [PATCH 1/2] u-boot-xlnx_2016.07.bb: Update u-boot version

Re: [meta-xilinx] [PATCH] glibc: Fix up MicroBlaze pt-vfork compat symbols

Re: [meta-xilinx] [PATCH 0/4] Embed Xilinx Release Versions into recipe PV

Re: [meta-xilinx] uboot CONFIG_SYS_SDRAM_SIZE allocation error

Re: [meta-xilinx] uboot CONFIG_SYS_SDRAM_SIZE allocation error

Re: [meta-xilinx] uboot CONFIG_SYS_SDRAM_SIZE allocation error

Re: [meta-xilinx] uboot CONFIG_SYS_SDRAM_SIZE allocation error

14 matches

Site Navigation

Mail list logo

Footer information