From: Peter Korsgaard <peter@korsgaard.com>
To: Neal Frager <nealf@xilinx.com>
Cc: "luca@lucaceresoli.net" <luca@lucaceresoli.net>,
"giulio.benetti@benettiengineering.com"
<giulio.benetti@benettiengineering.com>,
"buildroot@buildroot.org" <buildroot@buildroot.org>,
Michal Simek <michals@xilinx.com>,
Neal Frager <neal.frager@amd.com>
Subject: Re: [Buildroot] [PATCH v1 2/2] configs/zynqmp_zcu106_defconfig: transition to tarballs
Date: Wed, 11 May 2022 17:54:00 +0200 [thread overview]
Message-ID: <875ymcawvb.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <SJ0PR02MB7758FE7F237530275606A745D7C89@SJ0PR02MB7758.namprd02.prod.outlook.com> (Neal Frager's message of "Wed, 11 May 2022 13:41:08 +0000")
>>>>> "Neal" == Neal Frager <nealf@xilinx.com> writes:
> Hi Luca,
> We may need your help on this one.
> Peter and I have both replaced the pmufw.bin generated by the zynqmp-pmufw-builder with the one generated
> by vitis or petalinux. When we build the boot.bin using the pmufw.bin from vitis or petalinux, reboot works
> as expected without changing anything else.
> So there appears to be something in the zynqmp-pmufw-builder which is incorrect for the pmufw 2022.1.
I believe it is an issue with (a different behaviour of) the
toolchain. I found a machine at $WORK with petalinux 2021.1 and rebuild
zynqmp-pmufw-builder with the following minor patch:
diff --git a/build.sh b/build.sh
index 6321733..f01194d 100755
--- a/build.sh
+++ b/build.sh
@@ -59,7 +59,7 @@ pmufw_build()
BSP_TARGETS_LIBDIR="${BSP_DIR}/psu_pmu_0/lib"
BSP_LIBXIL="${BSP_TARGETS_LIBDIR}/libxil.a"
- CROSS="${HOME}/x-tools/microblazeel-xilinx-elf/bin/microblazeel-xilinx-elf-"
+ CROSS="microblaze-xilinx-elf-"
CC=${CROSS}gcc
AR=${CROSS}ar
AS=${CROSS}as
@@ -92,7 +92,7 @@ pmufw_build()
AS="${AS}" \
COMPILER="${CC}" \
COMPILER_FLAGS="-O2 -c" \
- EXTRA_COMPILER_FLAGS="-g -Wall -Wextra -Os -flto -ffat-lto-objects" \
+ EXTRA_COMPILER_FLAGS="-g -Wall -Wextra -Os -flto -ffat-lto-objects -mlittle-endian -mxl-barrel-shift -mxl-pattern-compare -mcpu=v9.2 -mxl-soft-mul" \
ARCHIVER="${AR}" \
CFLAGS="${CFLAGS}" \
include libs
I had to also pass the -m* flags in EXTRA_COMPILER_FLAGS to get it to
link, presumably the petalinux toolchain has incompatible
defaults. Luca, any specific reasons to not pass CFLAGS there?
With this build I do NOT see the exception from the PMU during a reboot.
Notice that this is a gcc10 based toolchain:
microblaze-xilinx-elf-gcc -v
Using built-in specs.
COLLECT_GCC=/tools/Xilinx/Petalinux/2021.1/tools/xsct/gnu/microblaze/lin/bin/../x86_64-oesdk-linux/usr/bin/microblaze-xilinx-elf/microblaze-xilinx-elf-gcc.real
COLLECT_LTO_WRAPPER=/tools/Xilinx/Petalinux/2021.1/tools/xsct/gnu/microblaze/lin/x86_64-oesdk-linux/usr/bin/microblaze-xilinx-elf/../../libexec/microblaze-xilinx-elf/gcc/microblaze-xilinx-elf
Target: microblaze-xilinx-elf
Configured with: ../../../../../../work-shared/gcc-10.2.0-r0/gcc-10.2.0/configure --build=x86_64-linux --host=x86_64-oesdk-linux --target=microblaze-xilinx-elf --prefix=/usr/local/oecore-x86_re-x86_64/sysroots/x86_64-oesdk-linux/usr --bindir=/usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/bin/microblaze-xilinx-elf --sbindir=/usr/local/oecore-x86_64/sysroots/x86_64-oesdk-re-x86_64/sysroots/x86_64-oesdk-linux/usr/libexec/microblaze-xilinx-elf --datadir=/usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/share --sysconfdir=/usr/local/oecore-x86_64/sysroots4/sysroots/x86_64-oesdk-linux/com --localstatedir=/usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/var --libdir=/usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/lib/microblaze-xilsdk-linux/usr/include --oldincludedir=/usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/include --infodir=/usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/share/info --mandir=/n --disable-silent-rules --disable-dependen
cy-tracking --with-libtool-sysroot=/scratch/mhatle/git/internal/2021/build-tc/tmp/work/x86_64-nativesdk-oesdk-linux/gcc-cross-canadian-microblaze/10nguages=c,c++ --enable-threads=posix --enable-multilib --enable-c99 --enable-long-long --enable-libstdcxx-pch --program-prefix=microblaze-xilinx-elf- --without-local-prefix --disable-install-e-bootstrap --with-system-zlib --enable-linker-build-id --with-ppl=no --with-cloog=no --enable-checking=release --enable-cheaders=c_global --without-isl --with-gxx-include-dir=/not/exist/usr/nternal/2021/build-tc/tmp/work/x86_64-nativesdk-oesdk-linux/gcc-cross-canadian-microblaze/10.2.0-r0/recipe-sysroot-native/usr/microblaze-xilinx-elf/bin --with-build-sysroot=/scratch/mhatle/gicc-cross-canadian-microblaze/10.2.0-r0/recipe-sysroot --enable-poison-system-directories --enable-nls --with-glibc-version=2.28 --enable-initfini-array --without-headers --with-newlib --disab --with-newlib --disable-threads --enable-plugins --with-gnu-as --disable-libitm --en
able-target-optspace --without-long-double-128 --enable-multilib --with-sysroot=/not/exist
Thread model: single
Supported LTO compression algorithms: zlib
gcc version 10.2.0 (GCC)
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-05-11 15:54 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 15:24 [Buildroot] [PATCH v1 1/2] configs/zynqmp_zcu102_defconfig: transition to tarballs Neal Frager via buildroot
2022-05-03 15:24 ` [Buildroot] [PATCH v1 2/2] configs/zynqmp_zcu106_defconfig: " Neal Frager via buildroot
2022-05-04 6:49 ` Peter Korsgaard
[not found] ` <edddb58b-dee7-21aa-05b8-3a94c3e2c4d1@xilinx.com>
2022-05-04 7:18 ` Peter Korsgaard
[not found] ` <86b8666c-4427-32c6-c015-f9b67e963195@xilinx.com>
2022-05-04 7:39 ` Peter Korsgaard
2022-05-04 8:53 ` Neal Frager
2022-05-04 9:12 ` Luca Ceresoli
2022-05-04 9:24 ` Neal Frager
2022-05-04 9:34 ` Neal Frager
[not found] ` <a430617e-f535-75c5-a848-2384c774368d@xilinx.com>
2022-05-04 9:53 ` Luca Ceresoli
[not found] ` <5dd71ac6-35a1-1d34-0964-66390cbb94ba@xilinx.com>
2022-05-04 12:45 ` Neal Frager
[not found] ` <87d7438b-6b9d-a837-c6b9-0e2f6086b8c7@xilinx.com>
2022-05-04 13:09 ` Neal Frager
2022-05-11 9:10 ` Peter Korsgaard
[not found] ` <08d36a3f-8c9b-173d-f965-fa2aef9a8c77@xilinx.com>
2022-05-11 10:08 ` Peter Korsgaard
2022-05-11 11:06 ` Neal Frager
2022-05-11 13:41 ` Neal Frager
2022-05-11 15:54 ` Peter Korsgaard [this message]
2022-05-12 14:38 ` Luca Ceresoli
2022-05-12 16:09 ` Neal Frager
2022-05-12 19:32 ` Peter Korsgaard
2022-05-13 4:21 ` Neal Frager
2022-05-13 7:17 ` Luca Ceresoli
2022-05-13 8:40 ` Neal Frager
2022-05-13 9:06 ` Neal Frager
2022-05-13 10:48 ` Neal Frager
2022-05-17 7:42 ` Luca Ceresoli
2022-05-17 7:50 ` Neal Frager
2022-05-17 7:58 ` Peter Korsgaard
2022-08-01 13:59 ` Frager, Neal via buildroot
2022-08-02 15:01 ` Luca Ceresoli via buildroot
2022-08-02 15:06 ` Frager, Neal via buildroot
2022-08-17 17:23 ` Frager, Neal via buildroot
2022-08-18 16:13 ` Luca Ceresoli via buildroot
2022-05-28 8:37 ` Peter Korsgaard
2022-05-04 6:46 ` [Buildroot] [PATCH v1 1/2] configs/zynqmp_zcu102_defconfig: " Peter Korsgaard
2022-05-28 8:37 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875ymcawvb.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=luca@lucaceresoli.net \
--cc=michals@xilinx.com \
--cc=neal.frager@amd.com \
--cc=nealf@xilinx.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.