Re: [meta-xilinx] Support for PicoZed 7030 and FMC V2 Carrier
On 31.07.2018 23:30, Manjukumar Harthikote Matha wrote: > Can you submit the patch to u-boot mainline? I just sent out the patch email. - Andy -- ___ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
Re: [meta-xilinx] Support for PicoZed 7030 and FMC V2 Carrier
Hi Andy, > -Original Message- > From: meta-xilinx-boun...@yoctoproject.org [mailto:meta-xilinx- > boun...@yoctoproject.org] On Behalf Of Andreas Galauner > Sent: Tuesday, July 31, 2018 1:39 PM > To: meta-xilinx@yoctoproject.org; Thomas Goodwin > > Subject: Re: [meta-xilinx] Support for PicoZed 7030 and FMC V2 Carrier > > On 10.07.2018 17:05, Thomas Goodwin wrote: > > Hello, > > > > I'm attempting to build the picozed-zynq7 machine using meta-xilinx > > with Poky 2.4.2. I've tried using the /rocko/ branch as well as > > /rel-v2018.2/. For the latter, I had to patch the machine definition > > since it was missing /require > > /(PR: https://github.com/Xilinx/meta-xilinx/pull/9). My layer > > configuration is: > > > > BBLAYERS ?= " \ > > /ssd/yocto_projects/picozed/poky/meta \ > > /ssd/yocto_projects/picozed/poky/meta-poky \ > > /ssd/yocto_projects/picozed/poky/meta-xilinx/meta-xilinx-bsp \ > > " > > > > In each case, I can build /core-image-minimal/, however there is no > > console output on boot over the UART. The D10 and D11 PS LEDs on the > > FMC carrier card are flashing in sync. > > > > Has anyone else successfully built for this target recently? > > Yes, the u-boot device tree is broken for the Picozed. There is no console > defined > (the chosen/stdout-path node is missing) and because of that u-boot panics and > the board resets. That's why the LEDs are "blinking" > > I stepped through the code using JTAG and found out what's causing this after > a > longer debugging session. I fixed the device tree and it started to work. I > also > added some more stuff to it like USB, QSPI and the Ethernet MAC. In theory > that > should make them work as well, but I'm not sure if I ever tested that. Can you submit the patch to u-boot mainline? Thanks, Manju -- ___ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
Re: [meta-xilinx] Support for PicoZed 7030 and FMC V2 Carrier
Thanks for confirming. I ended up doing something similar to the kernel too. Hopefully Xilinx does upstream the patch! On Tue, Jul 31, 2018 at 4:38 PM Andreas Galauner wrote: > On 10.07.2018 17:05, Thomas Goodwin wrote: > > Hello, > > > > I'm attempting to build the picozed-zynq7 machine using meta-xilinx with > > Poky 2.4.2. I've tried using the /rocko/ branch as well as > > /rel-v2018.2/. For the latter, I had to patch the machine definition > > since it was missing /require > > /(PR: https://github.com/Xilinx/meta-xilinx/pull/9). My layer > > configuration is: > > > > BBLAYERS ?= " \ > > /ssd/yocto_projects/picozed/poky/meta \ > > /ssd/yocto_projects/picozed/poky/meta-poky \ > > /ssd/yocto_projects/picozed/poky/meta-xilinx/meta-xilinx-bsp \ > > " > > > > In each case, I can build /core-image-minimal/, however there is no > > console output on boot over the UART. The D10 and D11 PS LEDs on the > > FMC carrier card are flashing in sync. > > > > Has anyone else successfully built for this target recently? > > Yes, the u-boot device tree is broken for the Picozed. There is no > console defined (the chosen/stdout-path node is missing) and because of > that u-boot panics and the board resets. That's why the LEDs are "blinking" > > I stepped through the code using JTAG and found out what's causing this > after a longer debugging session. I fixed the device tree and it started > to work. I also added some more stuff to it like USB, QSPI and the > Ethernet MAC. In theory that should make them work as well, but I'm not > sure if I ever tested that. > > You find the patch attached. Maybe Xilinx should upstream that. The > u-boot is just broken on Picozeds without this. > > - Andy > -- ___ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
Re: [meta-xilinx] Support for PicoZed 7030 and FMC V2 Carrier
On 10.07.2018 17:05, Thomas Goodwin wrote:
> Hello,
>
> I'm attempting to build the picozed-zynq7 machine using meta-xilinx with
> Poky 2.4.2. I've tried using the /rocko/ branch as well as
> /rel-v2018.2/. For the latter, I had to patch the machine definition
> since it was missing /require
> /(PR: https://github.com/Xilinx/meta-xilinx/pull/9). My layer
> configuration is:
>
> BBLAYERS ?= " \
> /ssd/yocto_projects/picozed/poky/meta \
> /ssd/yocto_projects/picozed/poky/meta-poky \
> /ssd/yocto_projects/picozed/poky/meta-xilinx/meta-xilinx-bsp \
> "
>
> In each case, I can build /core-image-minimal/, however there is no
> console output on boot over the UART. The D10 and D11 PS LEDs on the
> FMC carrier card are flashing in sync.
>
> Has anyone else successfully built for this target recently?
Yes, the u-boot device tree is broken for the Picozed. There is no
console defined (the chosen/stdout-path node is missing) and because of
that u-boot panics and the board resets. That's why the LEDs are "blinking"
I stepped through the code using JTAG and found out what's causing this
after a longer debugging session. I fixed the device tree and it started
to work. I also added some more stuff to it like USB, QSPI and the
Ethernet MAC. In theory that should make them work as well, but I'm not
sure if I ever tested that.
You find the patch attached. Maybe Xilinx should upstream that. The
u-boot is just broken on Picozeds without this.
- Andy
commit 3115e00df2fc969becff15811c5ff5feb0ecd036
Author: Andreas Galauner
Date: Sat Nov 25 06:37:25 2017 +0100
Fix picozed device tree
diff --git a/arch/arm/dts/zynq-picozed.dts b/arch/arm/dts/zynq-picozed.dts
index e15667c108..73af38415e 100644
--- a/arch/arm/dts/zynq-picozed.dts
+++ b/arch/arm/dts/zynq-picozed.dts
@@ -15,13 +15,33 @@
aliases {
serial0 =
spi0 =
- mmc0 =
+ mmc0 =
+ mmc1 =
};
memory@0 {
device_type = "memory";
reg = <0 0x4000>;
};
+
+ chosen {
+ bootargs = "earlyprintk";
+ stdout-path = "serial0:115200n8";
+ };
+
+ usb_phy0: phy0 {
+ compatible = "usb-nop-xceiv";
+ #phy-cells = <0>;
+ };
+};
+
+ {
+ ps-clk-frequency = <>;
+};
+
+ {
+ u-boot,dm-pre-reloc;
+ status = "okay";
};
{
@@ -29,7 +49,17 @@
status = "okay";
};
- {
+ {
+ status = "okay";
+ phy-mode = "rgmii-id";
+ phy-handle = <_phy>;
+
+ ethernet_phy: ethernet-phy@0 {
+ reg = <0>;
+ };
+};
+
+ {
u-boot,dm-pre-reloc;
status = "okay";
};
@@ -38,3 +68,9 @@
u-boot,dm-pre-reloc;
status = "okay";
};
+
+ {
+ status = "okay";
+ dr_mode = "host";
+ usb-phy = <_phy0>;
+};
--
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx
