Re: [meta-xilinx] PicoZed 7030 again
The device tree in U-Boot and U-Boot-XLNX (which is different than the one
from that recipe) do not have the SD card set as the boot device (mmc0
points to sdhci1 vs. sdhci0) and then the block for sdhci0 needs to be
enabled (status = "okay") vs. disabling sdhci1. I recall someone has put a
patch into the U-Boot mainline, but that's the gist. The built-in one
seems to be eyeing if you were planning to boot from eMMC.
As I recall, the device tree is also missing a "chosen" block, like this:
chosen {
bootargs = "earlycon";
stdout-path = "serial0:115200n8";
}
However I do not recall if that block is required or not.
Cheers,
Thomas
On Wed, Oct 3, 2018 at 2:35 PM Artjom Rjabov wrote:
> For some reason, I can't boot the picozed-zynq7 image from an SD card on
> PicoZed+FMC Carrier Card Gen2. I worked with Zedboard previously and
> everything worked perfectly.
> I've read all the threads about Picozed here but didn't find anything
> helpful. Devicetree in "meta-xilinx-bsp/recipes-bsp/device-tree" looks fine
> at the moment.
> It has a console definition (chosen/stdout-path) in it and serial0 is
> enabled. I decompiled it to make sure that everything is there.
>
> Here what I did:
>
> 1. Compiled everything without my own recipes and bbappends. Uploaded
> boot.bin, uImage, picozed-zynq7.dtb, uEnv.txt, u-boot.img, and rootfs on
> the SD card and tried to boot.
> It didn't work. The D10 and D11 PS LEDs on the FMC carrier were blinking
> in sync indefinitely.
>
> 2. I generated my own ps7_init_gpl files in vivado (SD0 and SD1 enabled,
> UART1 on MIO48 and 49), created my own platform-init.bbappend file for
> replacing the init files. Enabled SD0 in the device tree. Bitbaked
> everything. Same result.
>
> 3. FSBL approach that worked with Zedboard. I copied u-boot.elf from the
> generated image folder, created FSBL in SDK and generated BOOT.bin with
> these two files. The result was different. The D10 and D11 blinked only
> once, but still no console output over the UART. It looks like it doesn't
> even get to the device tree because the result is the same even if there is
> no dtb file on the SD card.
>
> What am I missing here?
> --
> ___
> 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] 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
[meta-xilinx] Support for PicoZed 7030 and FMC V2 Carrier
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? Regards, Thomas -- ___ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
