[meta-xilinx] Build and boot zcu106 image

[Mike Looijmans]

On 04-06-19 15:26, Manjukumar Harthikote Matha wrote:
> Hi Mike,
> 
>> -----Original Message-----
>> From: meta-xilinx-bounces at yoctoproject.org <meta-xilinx-
>> bounces at yoctoproject.org> On Behalf Of Mike Looijmans
>> Sent: Tuesday, June 4, 2019 6:09 AM
>> To: Luca Ceresoli <luca at lucaceresoli.net>; Manjukumar Harthikote Matha
>> <MANJUKUM at xilinx.com>; meta-xilinx at yoctoproject.org
>> Subject: Re: [meta-xilinx] Build and boot zcu106 image
>>
>> On 04-06-19 14:58, Luca Ceresoli wrote:
>>> Hi Mike,
>>>
>>> On 04/06/19 07:41, Mike Looijmans wrote:
>>>> On 03-06-19 16:25, Manjukumar Harthikote Matha wrote:
>>>>> Hi Mike,
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: meta-xilinx-bounces at yoctoproject.org <meta-xilinx-
>>>>>> bounces at yoctoproject.org> On Behalf Of Mike Looijmans
>>>>>> Sent: Monday, June 3, 2019 7:01 AM
>>>>>> To: meta-xilinx at yoctoproject.org
>>>>>> Subject: [meta-xilinx] Build and boot zcu106 image
>>>>>>
>>>>>> Got a zcu106 board here to experiment with. With pre-built stuff,
>>>>>> the board boots okay.
>>>>>>
>>>>>> I cloned OpenEmbedded and meta-xilinx "thud" branches, made no
>> changes.
>>>>>>
>>>>>> Built the PMU firmware and core-image-minimal for machine zcu106-
>> zynqmp.
>>>>>>
>>>>>
>>>>> I had similar issue! I think the PMU default config objects in SPL
>>>>> flow does not work.
>>>>> Luca had config object which worked for him.
>>>>
>>>>
>>>> And what is the solution?
>>>>
>>>>
>>>> There's nothing "machine" dependent in the PMU recipe, so all ZynqMP
>>>> machines will build the exact same binary. Right?
>>>>
> 
> I am not sure about this, because Ultra96 needed different PMU cfg to work.
> I will check once I am back from vacay
> 
>>>> My first attempt was actually to use my "standard" PMU stuff (patched
>>>> PMU with built-in config object) for the image, but that also
>>>> delivered the same error.
>>>
>>> My SPL patch is just moving the cfg loading in a different place. It
>>> would not solve your problem.
>>>
>>> Just guessing, are you using the pm_cfg_obj.c produced by XDSK for
>>> your FPGA design or an "enable-all" config?
>>>
> 
> The pmu configs generated from XSDK works, meaning I don’t see the issue while using meta-xilinx-tools
> 
>>
>> I tried to use the "enable all" config I also use on our custom boards. In theory,
>> that should work on any board, right?
>>
>> I also tried "whatever meta-xilinx delivers by default".
>>
>> As for "pm_cfg_obj.c produced by XDSK", I have no clue as to how to do that,
>> but I'm guessing Google can help me out with that. Do you think it'd make a
>> difference?
> 
> meta-xilinx-tools can help generate that file, maybe comparing that with SPL generated flow might provide some insights why it is breaking
> 
> 
> Thanks,
> Manju
> 


I patched pmu-firmware to also include the mysterious GPIO mapping for the 
zcu106 board. No change, still only get that crash.