Found them, thanks for that. Although on ReadTheDocs it does say that "A more comprehensive view is available in the Security Center."
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Dec 6 2022
Dec 5 2022
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.
Nov 9 2022
Nov 8 2022
Nov 2 2022
Oct 31 2022
Added LTS patch automation doc: https://developer.trustedfirmware.org/w/tf_a/tf-a_lts_meeting_minutes/tf-a_lts_patch_automation/
Oct 28 2022
Oct 26 2022
Oct 25 2022
Oct 18 2022
Oct 17 2022
Oct 13 2022
Oct 12 2022
Oct 6 2022
Oct 4 2022
Oct 3 2022
Further improvement to tf-a-tests added to this ticket
added more improvement suggestions
Sep 30 2022
Sep 28 2022
Sep 27 2022
Hi Andre-ARM, to fix the problem, here's the pull request: https://github.com/ARM-software/arm-trusted-firmware/pull/1988
In T1003#11851, @Andre-ARM wrote:Hi,
thanks for the info, I will have a look at this, though probably only later this week.
As for rebuilding: I assume you are using the firmware drops from the pftf github?
This is deeply hidden in the EDK2 build system, but it will effectively use a precompiled version of bl31.bin checked into the edk2-non-osi.git repository. This will be placed into the first 128KB of RPI_EFI.fd file, filled up with 0xff.
So to replace just bl31.bin, you simply overwrite the first part of that file, with your compiled version.
To get bl31.bin from source, you just need an aarch64 (cross-)compiler, then:
$ CROSS_COMPILE=aarch64-linux-gnu- make PLAT=rpi4 DEBUG=0
This should be described in docs/plat/rpi4.rst. If you find something missing, let me know, or even better: send a patch ;-)
Sep 26 2022
Hi,
thanks for the info, I will have a look at this, though probably only later this week.
As for rebuilding: I assume you are using the firmware drops from the pftf github?
This is deeply hidden in the EDK2 build system, but it will effectively use a precompiled version of bl31.bin checked into the edk2-non-osi.git repository. This will be placed into the first 128KB of RPI_EFI.fd file, filled up with 0xff.
So to replace just bl31.bin, you simply overwrite the first part of that file, with your compiled version.
To get bl31.bin from source, you just need an aarch64 (cross-)compiler, then:
$ CROSS_COMPILE=aarch64-linux-gnu- make PLAT=rpi4 DEBUG=0
This should be described in docs/plat/rpi4.rst. If you find something missing, let me know, or even better: send a patch ;-)
In T1003#11849, @Andre-ARM wrote:So that's a lot of details (thanks for that!), but what is the actual problem? That secondaries cannot be taken offline? Or that they don't came back online? And did that work before the commit you mentioned?
So that's a lot of details (thanks for that!), but what is the actual problem? That secondaries cannot be taken offline? Or that they don't came back online? And did that work before the commit you mentioned?
Sep 25 2022
I can confirm this occurs with binutils 2.39. We (coreboot) are trying to update binutils from our toolchain and we are about to adjust our build system. --no-warn-rwx-segment fixes the issue. https://review.coreboot.org/c/coreboot/+/66920
Sep 24 2022
Pinging @Andre-ARM RPi4 platform code owner for comment.
Sep 22 2022
Hello Olivier,
Thanks for your reply. Looks like there is a fix under works:
Adding that the linking warns about both rwx-sections and execstack for bl2 too.
So both are needed or the linking needs to be fixed.
I think the no-warn flags are only available to newer tools, so defaulting to them will probably break things.
Sep 20 2022
Sep 19 2022
Sep 17 2022
Hello Olivier,
Sep 13 2022
Hi,
From the logs I understand BL31 is started by U-Boot SPL rather than TF-A's BL1/BL2, correct?
Would it be possible to gather more verbose logs (build with DEBUG=1 LOG_LEVEL=50) ?
Can you share the TF-A command line used to build this platform?
In particular what's the state of EL3_EXCEPTION_HANDLING, SPD, SPMD_SPM_AT_SEL2 toggles?
Thanks, Olivier.