Hi Adrian, I believe this is incorrect change as v11.0 indicates Microblaze IP version. And I don't think you can just go and change Hard IP Microblaze version.
I believe this should be set to v8.40 (if that is the real Hard IP Microblace version), Xilinx guys can probably tell what is the real Hard IP Microblace version used in PMU. Otherwise tooling might generate incorrect code for the PMU. Thanks, Vesa Jääskeläinen On 2020-02-05 14:41, Adrian Fiergolski wrote: > Hi Vesa, > > As I wrote in other threads, in order to fix this issue, you need to > cherry-pick a commit to the poky repo introducing the MB v11.0 feature > (3be6b045afabfb4d5cf137b3e93cb004067b71bb). > > Regards, > > Adrian > > On 04.02.2020 15:03, Vesa J??skel?inen wrote: >> Hi, >> >> I was trying to compile zeus branch for MPSoC and we are using >> multiconfig to also compile PMU firmware. >> >> Error I got was: >> -- >> ERROR: OE-core's config sanity checker detected a potential >> misconfiguration. >> Either fix the cause of this error or at your own risk disable the >> checker (see sanity.conf). >> Following is the list of potential problems / advisories: >> >> Toolchain tunings invalid: >> Tuning 'microblaze' has the following errors: >> Feature 'v11.0' is not defined. >> -- >> >> And when looking at poky/zeus: >> meta/conf/machine/include/microblaze/feature-microblaze-versions.inc >> >> # MicroBlaze versions >> TUNEVALID[v8.00] = "MicroBlaze version 8.00" >> TUNEVALID[v8.10] = "MicroBlaze version 8.10" >> TUNEVALID[v8.20] = "MicroBlaze version 8.20" >> TUNEVALID[v8.30] = "MicroBlaze version 8.30" >> TUNEVALID[v8.40] = "MicroBlaze version 8.40" >> ... >> TUNEVALID[v10.0] = "MicroBlaze version 10.0" >> >> Kinda indicates that there is no yet v11.0 defined for zeus. In Poky >> master it is already there. >> >> Now I started wondering why this is a problem. >> >> There was commit to upgrade PMU for newer microblaze (10.0->11.0): >> http://git.yoctoproject.org/cgit/cgit.cgi/meta-xilinx/commit/?h=zeus&id=de77bf7a8a9b1600f449ba42fa0da211c712fef0 >> >> If I revert that it seems to continue compiling nicely. >> >> However I believe this is not correct thing to do to change the >> microblaze version. In ZynqMPSoC the PMU block is hard IP and you cannot >> just upgrade that to newer microblaze version. I tried to find details >> of what microblaze version it is but it is kinda hidden well. >> >> If we trust Xilinx's QEMU device tree settings a bit then it might be >> 8.40 and that should then be set for PMU so that proper microblaze tunes >> and such are in use. >> >> https://github.com/Xilinx/qemu-devicetrees/blob/master/zynqmp-pmu.dts#L48 >> >> Thanks, >> Vesa Jääskeläinen >> >>
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#4650): https://lists.yoctoproject.org/g/meta-xilinx/message/4650 Mute This Topic: https://lists.yoctoproject.org/mt/70973014/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
