Ah, and meta-xilinx-tools is not part of meta-xilinx, but in a separate repo: 
https://github.com/Xilinx/meta-xilinx-tools.git

Okay, this seems to build, but that can't be the case. It appears to be using 
some random defaults for DDR timing and such... So next is to figure out where 
to put that information...




Met vriendelijke groet / kind regards,

Mike Looijmans
System Expert

[cid:thumb_topiclogoemail_24628bdd-be1f-488e-8e50-d9c8e7ca4bb7.gif]
TOPIC Embedded Products B.V.
Materiaalweg 4
5681 RJ Best    T:      +31 (0) 499 33 69 69
The Netherlands E:      
[email protected]<mailto:[email protected]>
       W:      www.topic.nl<http://www.topic.nl>
       L:      LinkedIn<https://www.linkedin.com/company/topic-embedded-systems>

Please consider the environment before printing this e-mail

On 06-04-2023 11:49, Michał Fita wrote:
As I'm around this topic ATM, the both pmu-firmware and fsbl-firmware recipes 
are in meta-xilinx-tools, so you have to have this layer configured. I don't 
understand the full role of zynqmp-pmwfw and fsbl-fw yet, but they're tied to 
these proper recipes.

Hope this hint helps.


On Thu, 6 Apr 2023 at 10:17, Mike Looijmans 
<[email protected]<mailto:[email protected]>> wrote:
Okay, got langdale to build with my old SPL configuration.

Because Xilinx doesn't support SPL, I'll move to FSBL for the ZynqMP boards.

But now I'm getting lost. There's apparently a bunch of ways to do this,
and I have no idea where to start.

I removed the SPL selection from the machine config, which results in
this build error:

ERROR: Nothing PROVIDES 'fsbl' (but
/.../meta-xilinx/meta-xilinx-core/recipes-bsp/bootbin/xilinx-bootbin_1.0.bb<http://xilinx-bootbin_1.0.bb>
DEPENDS on or otherwise requires it)
fsbl was skipped: The expect file
/.../build/tmp-glibc/deploy/images/tdpzu9/fsbl-tdpzu9.elf is not available.
Set FSBL_FILE to the path with a precompiled FSBL binary or you may need
to enable BBMULTICONFIG += 'fsbl-fw' to generate it.
ERROR: Required build target 'my-image' has no buildable providers.
Missing or unbuildable dependency chain was: ['my-image',
'u-boot-zynq-uenv', 'virtual/boot-bin', 'fsbl']

In "meta-xilinx-standalone/README.md" there are two solutions, both
don't work.

One is to use:
BBMULTICONFIG += "fsbl-fw zynqmp-pmufw"

This results in parse errors in
meta-xilinx/meta-xilinx-standalone/recipes-bsp/embeddedsw/fsbl-firmware_git.bb<http://fsbl-firmware_git.bb>.
Which I can work around by simply removing that recipe.

Then I get this:
ERROR: Nothing PROVIDES 'pmu-firmware'
pmu-firmware was skipped: incompatible with host aarch64-oe-linux (not
in COMPATIBLE_HOST)
pmu-firmware was skipped: incompatible with host aarch64-oe-linux (not
in COMPATIBLE_HOST)
pmu-firmware was skipped: incompatible with host aarch64-xilinx-elf (not
in COMPATIBLE_HOST)


So far for that...


In "meta-xilinx-standalone/README.md" it also mentions:

To build you should use a command similar to:
MACHINE=<machine> DISTRO=xilinx-standalone bitbake <recipe>

I'm fine with that, in the paragraph above it states that:

  cortexa53-zynqmp - ZynqMP based Cortex-A53 target
    Valid Targets: fsbl-firmware, meta-toolchain

But there's no "cortexa53-zynqmp" to be found anywhere.


Please help, how is this supposed to work?





--
Mike Looijmans


Met vriendelijke groet / kind regards,

Mike Looijmans
System Expert


TOPIC Embedded Products B.V.
Materiaalweg 4, 5681 RJ Best
The Netherlands

T: +31 (0) 499 33 69 69
E: [email protected]<mailto:[email protected]>
W: www.topic.nl<http://www.topic.nl>

Please consider the environment before printing this e-mail





--
Mike Looijmans
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5196): 
https://lists.yoctoproject.org/g/meta-xilinx/message/5196
Mute This Topic: https://lists.yoctoproject.org/mt/98101406/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to