[meta-xilinx] Build and boot zcu106 image

[Luca Ceresoli]

Hi Mike,

On 04/06/19 15:08, Mike Looijmans wrote:
> 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?
>>>
>>> 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?
>>
> 
> I tried to use the "enable all" config I also use on our custom boards.
> In theory, that should work on any board, right?

AFAIK there are boards (Ultra96 IIRC) that need to move some PMU-owned
GPIOs very early for proper voltage or clock, otherwise they won't boot.
But I've never used any. For those boards XSDK puts some code in the
pm_cfg_obj.c "GPO SECTION" to move those GPIOs. A "enable-all" config
won't have that code.

That said, I think zcu106 should not need that, thus perhaps this is not
your problem. But I always start from a XSDK-generate config object and
never had any issue with them.

> I also tried "whatever meta-xilinx delivers by default".

Does meta-xilinx provide any pm_cfg_obj.c file?

> 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. 

If you have a Vivado project open, it's rather simple:
 - in Vivado
   - file -> export -> hardware
   - file -> launch SDK
 - in XSDK
   - file -> new -> other
   - xilinx -> BSP -> next
   - finish
   - in "BSP settings" -> supported libraries -> enable "xilpm"
   - ok

Then use 'find' to, well, find your pm_cfg_obj.c.

> Do you think
> it'd make a difference?

As said, probably not in our case, but it's a safe starting point. If
that still fails, you have a different problem.

> 
> 
> 
>>>
>>>
>>>>
>>>> Thanks,
>>>> Manju
>>>>> Copied the usual files onto an SD card: atf-uboot.ub boot.bin Image
>>>>> system.dtb
>>>>> u-boot.bin uEnv.txt zynqmp-zcu106-revA.dtb
>>>>>
>>>>> Put the card in the board and switch it on. All I get is this:
>>>>>
>>>>> <debug_uart> Debug uart enabled
>>>>> "Synchronous Abort" handler, esr 0x96000040
>>>>> ELR:     fffc9e70
>>>>> LR:      fffc6c78
>>>>> x0 : fdfd00011dfdfe5d x1 : 0000000000000000
>>>>> x2 : 0202ffff020201a3 x3 : fdfd00011dfdfe5d
>>>>> x4 : 0000000000000000 x5 : 0000000000000000
>>>>> x6 : 00000000ffff7f20 x7 : 0000000000000005
>>>>> x8 : 00000000000000ad x9 : 0000000000000080
>>>>> x10: 000000000000fffd x11: 0000000000000064
>>>>> x12: 00000000fffffe6a x13: 60f8a90300b080a0
>>>>> x14: 8a10070a42650000 x15: a5cc22ca484081d9
>>>>> x16: 385a360321460003 x17: 9b800c890e560844
>>>>> x18: 00000000ffff7e90 x19: 0000000020000000
>>>>> x20: 0000000000000000 x21: fdfd00011dfdfe5d
>>>>> x22: 0000000000000000 x23: 0000000000000001
>>>>> x24: 00000000ffff7f20 x25: 00000000fffdae68
>>>>> x26: 00000000fffdae68 x27: 00000000fffdb000
>>>>> x28: 0000000000000000 x29: 00000000ffff7c10
>>>>>
>>>>> Resetting CPU ...
>>>>>
>>>>> ### ERROR ### Please RESET the board ###
>>>>>
>>>>>
>>>>> What does one have to do to actually boot that board with meta-xilinx?
>>>>> -- 
>>>>> _______________________________________________
>>>>> meta-xilinx mailing list
>>>>> meta-xilinx at yoctoproject.org
>>>>> https://lists.yoctoproject.org/listinfo/meta-xilinx
>>>
>>
> 

-- 
Luca