-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
attrflags is not expanded #15
Comments
Is this new on master or warrior branch? |
On both, if "warrior" is rel-v2019.1 |
rel-v2019.1 is on thud and we dont see the issue |
Ok. Try to add a "xilinx-bootbin_%.bbappend":
And you will find the issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If "attrflags" contains some environment variable, result.bif file will contain something like
"[destination_cpu=a53-0, offset=${DTB_OFFSET}] /mnt/ext/bla/blabla/build/tmp/deploy/images/blablabla/blablabla-system.dtb " instead of
"[destination_cpu=a53-0, offset=0x1c80000] /mnt/ext/bla/blabla/build/tmp/deploy/images/blablabla/blablabla-system.dtb "
To prevent it, attrflags should be expanded.
meta-xilinx-tools/recipes-bsp/bootbin/xilinx-bootbin_1.0.bb
Line 46 in 881132b
Change to
cfgval = d.expand(attrflags[cfg]).split(',')
meta-xilinx-tools/recipes-bsp/bootbin/xilinx-bootbin_1.0.bb
Line 57 in 881132b
Change to
cfgval = d.expand(attrflags[cfg]).split(',')
The text was updated successfully, but these errors were encountered: