Re: [meta-xilinx] Zynqmp QSPI boot: FSBL or SPL?
> -Original Message- > From: meta-xilinx-boun...@yoctoproject.org [mailto:meta-xilinx- > boun...@yoctoproject.org] On Behalf Of Magne Munkejord > Sent: Monday, June 11, 2018 8:42 AM > To: meta-xilinx@yoctoproject.org > Subject: [meta-xilinx] Zynqmp QSPI boot: FSBL or SPL? > > Hi > > I'm trying to generate boot images for QSPI for a custom board in Yocto but > ran > into some issues. > I use meta-xilinx-bsp and meta-xilinx-tools 2018.1 branches and I have added > u- > boot and linux machines + DTS pathces. > > Can the files generated by Yocto be used to boot from QSPI? > I did not find it in any readme but a patch in u-boot-xlnx suggested I need to > follow a special QSPI partition layout and a special atf-spi.ub: > https://github.com/Xilinx/u-boot- > xlnx/commit/378a437a49dd3d17a9a544768051b2336e5ed874 > Is there an easy way to make Yocto generate this special atf-spi.ub? > You can add a bbappend, see the existing recipe which generates atf-uboot.ub. On similar line you can create atf-spi.ub > > I tried an alternate approach by setting PREFERRED_PROVIDER_virtual/boot-bin = > xilinx-bootbin to use FSBL and generate a BOOT.bin for QSPI. But the FSBL > seems > to require PMUFW version 1.0. I got around this by cherry-picking a commit > from > master branch to get a newer pmu-firmware recipe. But now I also need a newer > kernel recipe. So I am not sure this is a reasonable path forward. > Pin PREFERRED_PROVIDER_virtual/pmu-firmware = "pmu-firmware" from meta-xilinx-tools Being on 2018.1 branches, it will build all the components including v4.14 kernel. > In general which boot method would you recommend for QSPI? SPL or FSBL. Flow depends on what you need. If you are sticking with SPL, then use Yocto release branches like master, rocko, morty etc If you using SPL flow, see Mikes input here https://lists.yoctoproject.org/pipermail/meta-xilinx/2017-November/003343.html Also check on Xilinx forum for any solution on FSBL flow. Thanks, Manju -- ___ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
Re: [meta-xilinx] [meta-xilinx-contrib][PATCH 3/3 v3] minized-zynq7: Add wireless support
Hi Clement,
> -Original Message-
> From: meta-xilinx-boun...@yoctoproject.org [mailto:meta-xilinx-
> boun...@yoctoproject.org] On Behalf Of Clement Laigle
> Sent: Sunday, June 10, 2018 3:23 PM
> To: meta-xil...@lists.yoctoproject.org
> Subject: [meta-xilinx] [meta-xilinx-contrib][PATCH 3/3 v3] minized-zynq7: Add
> wireless support
>
> The Minized has a wireless connectivity (WiFi / Bluetooth). This recipes add
> drivers to use the murata wireless module.
>
> Signed-off-by: Clement Laigle
> ---
>
> Changes in v2:
> - split patch
>
> Changes in v3:
> - Modify partition QSPI
> - Remove unnecessary recipes
> - Fix Licence
>
> ---
> .../minized-wireless/minized-wireless.bb | 43
> ++
> .../linux/linux-xlnx/v2018.1/wifi-bluetooth.cfg| 33
> ++
> .../linux/linux-xlnx_2018.1.bbappend | 1 +
> 3 file changed, 77 insertions(+)
> create mode 100644 meta-xilinx-contrib/recipes-bsp/minized-wireless/minized-
> wireless.bb
> create mode 100644 meta-xilinx-contrib/recipes-kernel/linux/linux-
> xlnx/v2018.1/wifi-bluetooth.cfg
>
> diff --git
> a/meta-xilinx-contrib/recipes-bsp/minized-wireless/minized-wireless.bb
> b/meta-xilinx-contrib/recipes-bsp/minized-wireless/minized-wireless.bb
> new file mode 100644
> index 000..78e618b
> --- /dev/null
> +++ b/meta-xilinx-contrib/recipes-bsp/minized-wireless/minized-wireless.bb
> @@ -0,0 +1,43 @@
> +SUMMARY = "minized-wireless: Wi-Fi/BT drivers and firmware for the Murata
> 1DX module"
> +LICENSE = "Proprietary"
> +LIC_FILES_CHKSUM = "file://cyw-fmac-
> fw/LICENCE.cypress;md5=cbc5f665d04f741f1e006d2096236ba7"
> +
> +SRC_URI = " \
> + git://github.com/murata-wireless/cyw-fmac-
> fw;protocol=git;branch=orga;destsuffix=cyw-fmac-fw;name=cyw-fmac-fw \
> + git://github.com/murata-wireless/cyw-fmac-
> nvram;protocol=git;branch=orga;destsuffix=cyw-fmac-nvram;name=cyw-fmac-
> nvram \
> + git://github.com/murata-wireless/cyw-bt-
> patch;protocol=git;branch=morty-orga;destsuffix=cyw-bt-patch;name=cyw-bt-
> patch \
> + git://github.com/murata-wireless/cyw-fmac-utils-
> imx32;protocol=git;branch=orga;destsuffix=cyw-fmac-utils-imx32;name=cyw-
> fmac-utils-imx32 \
> +"
> +
> +SRCREV_cyw-fmac-fw = "2242fd3f67a913fbfff8678cc8f7761629dca8ca"
> +SRCREV_cyw-fmac-nvram = "d12c2ac1b93941eaa03063bb7cb3c1ee1aa1b7d0"
> +SRCREV_cyw-bt-patch = "9216e0d9f778009b5667d032886dfd49174c4b3a"
> +SRCREV_cyw-fmac-utils-imx32 =
> "060688dfe76df98751207c8146268ce7fd80b6ab"
> +
> +DEPENDS = "libnl virtual/kernel"
> +
> +S = "${WORKDIR}"
> +
> +do_install() {
> + install -d ${D}/lib/firmware/brcm
> + install -d ${D}${sysconfdir}/firmware
> + install -d ${D}${bindir}
> +
> + install -m 644 ${S}/cyw-fmac-fw/brcmfmac43430-sdio.bin
> ${D}/lib/firmware/brcm/brcmfmac43430-sdio.bin
> + install -m 644 ${S}/cyw-fmac-nvram/brcmfmac43430-sdio.txt
> ${D}/lib/firmware/brcm/brcmfmac43430-sdio.txt
> + install -m 644 ${S}/cyw-bt-patch/CYW43430A1.1DX.hcd
> ${D}${sysconfdir}/firmware/BCM43430A1.1DX.hcd
> + install -m 755 ${S}/cyw-fmac-utils-imx32/wl ${D}${bindir}/wl
> +}
> +
> +PACKAGES =+ "${PN}-mfgtest"
> +
> +FILES_${PN} = " \
> + /lib/firmware/brcm/brcmfmac43430-sdio.bin \
> + /lib/firmware/brcm/brcmfmac43430-sdio.txt \
> + ${sysconfdir}/firmware/BCM43430A1.1DX.hcd \
> +"
> +
> +FILES_${PN}-mfgtest = " \
> + ${bindir}/wl \
> +"
> +
See the firmware here:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/brcm
I think the above recipe would be a bbappend to this instead of a new recipe:
https://git.yoctoproject.org/cgit.cgi/poky/plain/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb
Thanks,
Manju
--
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx
[meta-xilinx] Zynqmp QSPI boot: FSBL or SPL?
Hi I'm trying to generate boot images for QSPI for a custom board in Yocto but ran into some issues. I use meta-xilinx-bsp and meta-xilinx-tools 2018.1 branches and I have added u-boot and linux machines + DTS pathces. Can the files generated by Yocto be used to boot from QSPI? I did not find it in any readme but a patch in u-boot-xlnx suggested I need to follow a special QSPI partition layout and a special atf-spi.ub: https://github.com/Xilinx/u-boot-xlnx/commit/378a437a49dd3d17a9a544768051b2336e5ed874 Is there an easy way to make Yocto generate this special atf-spi.ub? I tried an alternate approach by setting PREFERRED_PROVIDER_virtual/boot-bin = xilinx-bootbin to use FSBL and generate a BOOT.bin for QSPI. But the FSBL seems to require PMUFW version 1.0. I got around this by cherry-picking a commit from master branch to get a newer pmu-firmware recipe. But now I also need a newer kernel recipe. So I am not sure this is a reasonable path forward. In general which boot method would you recommend for QSPI? SPL or FSBL. -- ___ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
