On 07-03-19 21:54, Manjukumar Harthikote Matha wrote: > Hi Mike, > >> -----Original Message----- >> From: meta-xilinx-boun...@yoctoproject.org [mailto:meta-xilinx- >> boun...@yoctoproject.org] On Behalf Of Mike Looijmans >> Sent: Friday, February 01, 2019 12:19 AM >> To: meta-xilinx@yoctoproject.org >> Subject: Re: [meta-xilinx] ZCU102 boot issue >> >> On 30-01-19 14:13, Jean-Francois Dagenais wrote: >>> Hi guys, >>> >>>> On Jan 28, 2019, at 14:39, Manjukumar Harthikote Matha >>>> <manju...@xilinx.com <mailto:manju...@xilinx.com>> wrote: >>>> >>>> Hi Alex, >>>> You need additional patches on pmu-firmware >>>> See:https://lists.yoctoproject.org/pipermail/meta-xilinx/2019-January >>>> /004198.html >>> >>> Manju, thanks for your patience and diligence in answering this yet another >>> time. >>> >>> In my experience, when such an issue is raised again and again, it >>> means it will not go away and it costs a lot in loss of time, money >>> and most importantly, spirit ;) >>> >>> I know it's been discussed before too but if I may add my 2 cents: Am >>> I missing something or without manually patching pmu-firmware, the >>> boards in the meta-xilinx-bsp will not function because of the missing >>> config object? (I still use meta-xilinx-tools so I actually don't >>> know.) Doesn't this mean Xilinx doesn't fully support the open-source >>> workflow? Or is just the word "support" that should be replaced with >>> "participates"? (In which case it is indeed directly responsible for >>> it) >>> >>> I remember problems with the licensing, but there has to be a >>> solution. Even if not elegant, once automated in yocto recipes, it's >>> better than nothing and a broken board after 5 hours of building! >>> >>> And if this is still not possible, to help people find the very >>> un-obvious source of their issues, perhaps PMU firmware could suffix >>> "(no cfg obj)" to its version? Or anything else printed early which >>> will help people find a xilinx wiki page explaining the problem and the >>> solutions >> available. >>> >> >> Simplest solution here would be to just integrate that "default config" >> patch into the >> standard PMU firmware and then all boards will just boot. It won't prevent >> the FSBL >> changing the config, so that flow isn't affected negatively. >> > > Please do send a patch if you have for pmu-firmware "default config". We will > take a look at having them integrated.
It's where it's always been: https://github.com/topic-embedded-products/meta-topic/tree/master/recipes-bsp/pmu-firmware/pmu-firmware -- _______________________________________________ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
