On 4/7/23 12:40 AM, Mike Looijmans wrote:
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]
W: www.topic.nl
Please consider the environment before printing this e-mail
On 06-04-2023 17:02, Mark Hatle via lists.yoctoproject.org wrote:
On 4/6/23 7:28 AM, Mike Looijmans wrote:
Nope, wrote that too soon.
Added the meta-xilinx-tools overlay, enabled multiconfig, but after a while,
You don't use multiconfigs with meta-xilinx-tools, there is an internal (xsct)
provided toolchain.
If you do enable multiconfigs, that toolchain is disabled and the Yocto
Project compiled one will be used. This is a test configuration and not
supported for deployment. (It was designed so we could test new Yocto Project
toolchains, as well as give people who wanted to replace the toolchain a
method for doing it. But we don't support this for production purposes. For
instance, gcc 12.2 won't build the 2022.2 firmware for a variety of reasons.)
I enabled multiconfig because one of the READMEs told me to do so. Without it,
I got build errors about binaries not being where they were supposed to be.
Hence my confusion - there's a dozen READMEs, they each provide some pieces of
the puzzle, but it isn't always the same puzzle apparently.
We're in the process of updating the README files. Hopefully this will help in
the future.
Isn't there some description somewhere that explains how to build the zynqmp
bootloader in Yocto, and that actually works?
Sandeep has added a new 'docs' directory that covers various booting methods. I
don't know if this directly answers your question.
But (once the update I'm working on is ready), at least from a qemu perspective,
downloading and enabling meta-xilinx (and it's layers), and meta-xilinx-tools
should provide a working (bootable) system for all of the included machine.conf
files.
A new tool, we're going to be releasing soon, 'gen-machine-conf' will help
generate machine.conf files from an XSA for creation of custom boards/layers.
In the end you should never have to manually build anything to boot a default
"getitng started" configuration. The intention is once you have the getting
started going, you will be able to tailor it using standard bbappend (or
replacement recipes) for u-boot configuration, scripting, etc. The FSBL, PMUFW
should be automatic, if you are building it -- or (eventually) you will be able
to provide pre-built versions.
(The later is to enable vendor boards, where the vendor is not willing to
provide the XSA to their end user. If they provide the FSBL and PMUFW binary
and some other configuration artifacts -- the user should still be able to do
development. We're not yet there, but moving closer to enabling this type of
development.)
--Mark
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5210):
https://lists.yoctoproject.org/g/meta-xilinx/message/5210
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]]
-=-=-=-=-=-=-=-=-=-=-=-
