A fix has been made available through the patch https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/18679. It is now merged. Thanks to Sylwester Garncarek.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Feb 28 2023
Feb 27 2023
Feb 26 2023
Feb 21 2023
Please see https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/19401 which should fix this for all targets.
Feb 16 2023
Feb 11 2023
Feb 10 2023
The recipe I am following.
Feb 9 2023
Feb 7 2023
Feb 6 2023
Feb 4 2023
Feb 3 2023
Feb 2 2023
Feb 1 2023
Jan 31 2023
Jan 30 2023
Jan 25 2023
Jan 24 2023
Jan 20 2023
Jan 19 2023
Jan 18 2023
Jan 13 2023
Jan 12 2023
Jan 9 2023
Jan 8 2023
The patch stack is still a work in progress so BL1 is the only fixed image so far, but BL2 and BL31 need the same treatment. Your best bet until I get around to applying these fixes to the remaining images is the current workaround (TF_LDFLAGS="--no-warn-rwx-segment").
Thanks, good to know. So, 2.9 will likely carry a fix? Is there a better patch I can use already (the one referenced does not directly appear to solve the issue)?
Hi Jan, sorry for the delay. This is currently in progress under the mixed-rwx topic: https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/18661/5
What's the status of this? Currently trying to build TF-A against the bookworm toolchain, and there the warning is even fatal. For now I'm working around it with this patch:
Jan 6 2023
Jan 4 2023
Jan 3 2023
I want to find a way to clean a memory region in TF-A firmware.
Dec 30 2022
Dec 19 2022
I want to find a way to clean a memory region in TF-A firmware.
Can you elaborate what you mean by "clean" ?
From the description it seems to be a simple memset, in which case data may remain in caches.
Does the requested operation need to complete to memory e.g. involving cache clean?
Dec 13 2022
Dec 7 2022
Found a fix in atf master which seems to touch on exactly this issue: https://github.com/ARM-software/arm-trusted-firmware/commit/fa7fdfabf07d91439b0869ffd8e805f0166294bf
Dec 6 2022
Dec 5 2022
Found them, thanks for that. Although on ReadTheDocs it does say that "A more comprehensive view is available in the Security Center."
Nov 28 2022
Nov 19 2022
Nov 17 2022
Nov 16 2022
There may be something wrong with my network that I can't visit https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a. I will follow up this issue after my network is fixed.
Nov 15 2022
fix submitted
Nov 14 2022
Patch from Bug submitter also raised https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/17768
Nov 10 2022
I agree with the idea and its a good capability to have. I don't thing there will be many TF-A build flags which has chance of name collision with environment variables. we can add TF-A prefix to them.