On 2/16/23 12:24 AM, Martin Siegumfeldt wrote:
There have to be dependencies on "fsbl" in your configuration. "fsbl" will
depend (by default) on fsbl-firmware, which is the normal provider usually
via meta-xilinx-tools.
There is no dependency from our machine towards fsbl-firmware - simply deleting
fsbl-firmware_%.bbappend from the BSP layer enables the build to succeed.
When BB parses the recipes of the BSP layer it finds fsbl-firmware_%.bbappend
but not the equivalent .bb file (as it resides in the standalone layer which is
not added to the index). I believe this is the basics of the Yocto layers
concept and is the root cause of the error:
ERROR: No recipes in default available for:
/tmp/distro-gomspace/meta-xilinx/meta-xilinx-bsp/recipes-bsp/embeddedsw/fsbl-firmware_%.bbappend
The above is a bug then. The fsbl-firmware should only be appended to if you
have either standalone as part of your configuration.
I believe we already have plans to remove this bbappend in the near future from
that layer. If not, it belongs in a dynamic-layer where it only loads if
meta-xilinx-standlone is part of your build.
And see the behavior of the system change. If that does work, capture it in
some notes and send them to me. As I said, up to this point nobody has
provided me with instructions on actually doing an SPL boot without
hand-stitching everything outside of the build system. So I don't know where
to begin to try to make this work and to be testable.
We are not using wks files and I do not expect any difference. Unfortunately I
can't share our layer publicly, but I'd be glad to send it to just you if you
would like insights to the build flow (which I believe i quite common for a lot
of other Zynq 7000 boards)?
I don't need your layers or XSA file. What I'm looking for it the specific
changes to your local.conf, or other files (including in these layers) that you
did to make SPL work. And then how did you know it actually works? What are
the expected outputs. This is the part that nobody has shared with me, I just
keep being pointed at out of date documentation or hand stitched files with no
real description of what I'm looking at. I do integration, I'm not an expert
in u-boot, so I really do need some hand holding to know what is expected and
how to accomplish it.
SKIP_RECIPE[fsbl] = "FSBL is disabled"
SKIP_RECIPE[fsbl-firmware] = "fsbl-firmware is disabled"
I tried this and it results in the same error, which I believe backs the point
of it being a basic inter-layer recipe resolution issue.
The error above (bbappend) won't be resolved by the skip recipe, that is only
for when the recipe (.bb) is available. Dangling bbappends are bugs that I need
to fix.
We have intentionally designed the system so that meta-xilinx-standalone is
optional and not required, assuming you provide the binaries that would have
otherwise been built -- or use an alternative approach that does not require
baremetal binaries to be generated.
I appreciate this design and we have efficiently utilized it so far, but as
previously stated, the mentioned commit breaks this approach.
If this doesn't work, the only way I can fix this is get help from users as
to how to change the workflow and how to test the alternative workflows
work. So far I've gotten very little help for anything related to u-boot SPL
flow, thus it's in the state it is in.
As mentioned previously I can share our layer with you in a private manner.
I'm happy to do this. I will send you an email from my work account. (This
account is my maintainer/mailing list account.)
Thanks!
--Mark
Thanks,
Martin
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5161):
https://lists.yoctoproject.org/g/meta-xilinx/message/5161
Mute This Topic: https://lists.yoctoproject.org/mt/96982329/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
