All of lore.kernel.org
 help / color / mirror / Atom feed
From: Neal Frager <nealf@xilinx.com>
To: Luca Ceresoli <luca@lucaceresoli.net>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>,
	Michal Simek <michals@xilinx.com>,
	"giulio.benetti@benettiengineering.com"
	<giulio.benetti@benettiengineering.com>,
	Neal Frager <neal.frager@amd.com>
Subject: Re: [Buildroot] [PATCH v1 2/2] configs/zynqmp_zcu106_defconfig: transition to tarballs
Date: Thu, 12 May 2022 16:09:42 +0000	[thread overview]
Message-ID: <D9EEAC86-D8CB-46E0-A019-B0F792B0511C@xilinx.com> (raw)
In-Reply-To: <56c3feaa-cbd2-eaa9-7800-cd2102fa8545@lucaceresoli.net>

Hi Luca,


> Le 12 mai 2022 à 16:38, Luca Ceresoli <luca@lucaceresoli.net> a écrit :
> 
> CAUTION: This message has originated from an External Source. Please use proper judgment and caution when opening attachments, clicking links, or responding to this email.
> 
> 
> Hi Peter,
> 
> On 11/05/22 17:54, Peter Korsgaard wrote:
>>>>>>> "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?
> 
> I'm afraid I have no real answer. :( When I initially wrote the script I
> did it to have the same logic as petalinux. Later I didn't watch for its
> changes. I would love to be helpful but I have no access to a zynqmp
> board now.
> 
> --
> Luca

Would it be possible for you to just implement the changes that Peter has proposed?  Peter appears to have already identified a solution.  

Both Peter and I have zcu106 boards, so we can both test and verify the update works.

Thanks for any help!

Best regards,
Neal Frager
AMD

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-05-12 16:09 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
2022-05-12 14:38               ` Luca Ceresoli
2022-05-12 16:09                 ` Neal Frager [this message]
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=D9EEAC86-D8CB-46E0-A019-B0F792B0511C@xilinx.com \
    --to=nealf@xilinx.com \
    --cc=buildroot@buildroot.org \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=luca@lucaceresoli.net \
    --cc=michals@xilinx.com \
    --cc=neal.frager@amd.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.