On 22-07-16 16:03, Nathan Rossi wrote:
> On Fri, Jul 22, 2016 at 11:44 PM, Mike Looijmans
> <[email protected]> wrote:
>>
>> On 22-07-16 15:31, Nathan Rossi wrote:
>>> On Fri, Jul 22, 2016 at 3:25 PM, Mike Looijmans <[email protected]> wrote:
>>>>
>>>> If I modify the devicetree and disable the 'psci' part, the system boots fine
>>>> but doesn't wake the other three cores.
>>>
>>> By default ZynqMP machines are setup to use PSCI for cpu bringup (QEMU
>>> has a PSCI implementation in-built), which means you will have to load
>>> some firmware before the kernel to handle PSCI calls, etc. ARM Trusted
>>> Firmware is what Xilinx recommends and they provide support for.
>>>
>>> The u-boot post regarding SPL
>>> (http://lists.denx.de/pipermail/u-boot/2016-May/254902.html) has info
>>> for booting atf. By default meta-xilinx will build an ATF binary for
>>> ZynqMP targets.
>>
>>
>> Please explain, it seems to build a package "arm-trusted-firmware" but it
>> doesn't seem to make its way into the image or deployment area?
>
> It deploys (or it at least should deploy) the
> "bl31-<machine>.bin"/"bl31-<machine>.elf" binaries. This is a piece of
> ATF, specifically stage 3 - 1 (the el3 runtime). You can read more
> info here https://github.com/ARM-software/arm-trusted-firmware/blob/master/docs/firmware-design.md.
Okay, thanks, got it figured out now.
I sent a patch to automate that "mkimage" step. Will save other people a lot
of headaches.
M.
> On Fri, Jul 22, 2016 at 11:44 PM, Mike Looijmans
> <[email protected]> wrote:
>>
>> On 22-07-16 15:31, Nathan Rossi wrote:
>>> On Fri, Jul 22, 2016 at 3:25 PM, Mike Looijmans <[email protected]> wrote:
>>>>
>>>> If I modify the devicetree and disable the 'psci' part, the system boots fine
>>>> but doesn't wake the other three cores.
>>>
>>> By default ZynqMP machines are setup to use PSCI for cpu bringup (QEMU
>>> has a PSCI implementation in-built), which means you will have to load
>>> some firmware before the kernel to handle PSCI calls, etc. ARM Trusted
>>> Firmware is what Xilinx recommends and they provide support for.
>>>
>>> The u-boot post regarding SPL
>>> (http://lists.denx.de/pipermail/u-boot/2016-May/254902.html) has info
>>> for booting atf. By default meta-xilinx will build an ATF binary for
>>> ZynqMP targets.
>>
>>
>> Please explain, it seems to build a package "arm-trusted-firmware" but it
>> doesn't seem to make its way into the image or deployment area?
>
> It deploys (or it at least should deploy) the
> "bl31-<machine>.bin"/"bl31-<machine>.elf" binaries. This is a piece of
> ATF, specifically stage 3 - 1 (the el3 runtime). You can read more
> info here https://github.com/ARM-software/arm-trusted-firmware/blob/master/docs/firmware-design.md.
Okay, thanks, got it figured out now.
I sent a patch to automate that "mkimage" step. Will save other people a lot
of headaches.
M.
Kind regards,
Mike Looijmans
System Expert
|
TOPIC Products |
|
| |
|
Materiaalweg 4 |
|
| |
|
5681 RJ Best |
T: |
+31 (0) 499 33 69 69 | |
|
Postbus 440 |
E: |
||
|
5680 AK Best |
W: |
||
| The Netherlands |
Please consider the
environment before printing this e-mail
Topic zoekt gedreven (embedded) software specialisten!
-- _______________________________________________ meta-xilinx mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-xilinx
