Page MenuHomePhabricator

Open Tasks

Unbreak Now! (1)

Recent Activity

Fri, Sep 30

vwadekar edited the content of Long-term support (LTS) proposal.
Fri, Sep 30, 11:40 AM
vwadekar edited the content of Long-term support (LTS) proposal.
Fri, Sep 30, 11:39 AM

Tue, Sep 27

gyuri-szing updated subscribers of T993: Premature, forced OpenSSL 3.0 API upgrade..

it seems there are two existing workarounds related to OpenSSL3 available in different downstream projects.

Tue, Sep 27, 9:18 AM · TF-A Question, Trusted Firmware A
Luoject assigned T1003: TF-A: RPi4 fails to boot secondary core at second time by PSCI cpu_on to Andre-ARM.

Hi Andre-ARM, to fix the problem, here's the pull request: https://github.com/ARM-software/arm-trusted-firmware/pull/1988

Tue, Sep 27, 7:44 AM · Trusted Firmware A, TF-A Bug
Luoject added a comment to T1003: TF-A: RPi4 fails to boot secondary core at second time by PSCI cpu_on.

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 ;-)

Tue, Sep 27, 5:18 AM · Trusted Firmware A, TF-A Bug

Mon, Sep 26

vwadekar edited the content of Long-term support (LTS) proposal.
Mon, Sep 26, 9:05 PM
vwadekar edited the content of Long-term support (LTS) proposal.
Mon, Sep 26, 9:03 PM
Andre-ARM added a comment to T1003: TF-A: RPi4 fails to boot secondary core at second time by PSCI cpu_on.

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 ;-)

Mon, Sep 26, 1:18 PM · Trusted Firmware A, TF-A Bug
Luoject added a comment to T1003: TF-A: RPi4 fails to boot secondary core at second time by PSCI cpu_on.

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?

Mon, Sep 26, 12:09 PM · Trusted Firmware A, TF-A Bug
Andre-ARM added a comment to T1003: TF-A: RPi4 fails to boot secondary core at second time by PSCI cpu_on.

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?

Mon, Sep 26, 9:55 AM · Trusted Firmware A, TF-A Bug
Luoject updated the task description for T1003: TF-A: RPi4 fails to boot secondary core at second time by PSCI cpu_on.
Mon, Sep 26, 7:42 AM · Trusted Firmware A, TF-A Bug

Sun, Sep 25

felixsinger added a comment to T996: Compiling bl31.elf with binutils 2.39 warns/fails with “ LOAD segment with RWX permissions”.

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

Sun, Sep 25, 4:40 PM · Trusted Firmware A

Sat, Sep 24

joannafarley-arm updated subscribers of T1003: TF-A: RPi4 fails to boot secondary core at second time by PSCI cpu_on.

Pinging @Andre-ARM RPi4 platform code owner for comment.

Sat, Sep 24, 3:23 PM · Trusted Firmware A, TF-A Bug
Luoject added a project to T1003: TF-A: RPi4 fails to boot secondary core at second time by PSCI cpu_on: Trusted Firmware A.
Sat, Sep 24, 11:02 AM · Trusted Firmware A, TF-A Bug
Luoject created T1003: TF-A: RPi4 fails to boot secondary core at second time by PSCI cpu_on.
Sat, Sep 24, 11:01 AM · Trusted Firmware A, TF-A Bug

Thu, Sep 22

zandrey added a comment to T1000: imx8m does not start after EHF with S-EL2 SPMC change.

Hello Olivier,

Thu, Sep 22, 1:05 PM · Trusted Firmware A, TF-A Bug
odeprez added a comment to T1000: imx8m does not start after EHF with S-EL2 SPMC change.

Thanks for your reply. Looks like there is a fix under works:

Thu, Sep 22, 11:22 AM · Trusted Firmware A, TF-A Bug
mirschkyn added a comment to T996: Compiling bl31.elf with binutils 2.39 warns/fails with “ LOAD segment with RWX permissions”.

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.

Thu, Sep 22, 10:50 AM · Trusted Firmware A

Tue, Sep 20

odeprez created T1002: Revisit hypervisor page tables defragmentation.
Tue, Sep 20, 8:07 AM · Hafnium

Mon, Sep 19

eriders updated eriders.
Mon, Sep 19, 4:37 PM

Sat, Sep 17

zandrey added a comment to T1000: imx8m does not start after EHF with S-EL2 SPMC change.

Hello Olivier,

Sat, Sep 17, 7:34 PM · Trusted Firmware A, TF-A Bug

Tue, Sep 13

madhukar-Arm updated the task description for T1001: Improvements to secure interrupt handling, partition runtime models and scheduling modes in Hafnium.
Tue, Sep 13, 5:39 PM · Hafnium
madhukar-Arm updated the task description for T1001: Improvements to secure interrupt handling, partition runtime models and scheduling modes in Hafnium.
Tue, Sep 13, 5:39 PM · Hafnium
madhukar-Arm updated the task description for T1001: Improvements to secure interrupt handling, partition runtime models and scheduling modes in Hafnium.
Tue, Sep 13, 5:37 PM · Hafnium
madhukar-Arm updated the task description for T1001: Improvements to secure interrupt handling, partition runtime models and scheduling modes in Hafnium.
Tue, Sep 13, 5:37 PM · Hafnium
madhukar-Arm updated the task description for T1001: Improvements to secure interrupt handling, partition runtime models and scheduling modes in Hafnium.
Tue, Sep 13, 5:36 PM · Hafnium
madhukar-Arm triaged T1001: Improvements to secure interrupt handling, partition runtime models and scheduling modes in Hafnium as Normal priority.
Tue, Sep 13, 5:34 PM · Hafnium
odeprez added a comment to T1000: imx8m does not start after EHF with S-EL2 SPMC change.

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.

Tue, Sep 13, 7:54 AM · Trusted Firmware A, TF-A Bug

Sun, Sep 11

joannafarley-arm updated subscribers of T1000: imx8m does not start after EHF with S-EL2 SPMC change.

Ping @raghuncstate for comment https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/commit/?id=7c2fe62f1347bb94d82e9fdd3bc5eaebedaf0bc7

Sun, Sep 11, 10:20 AM · Trusted Firmware A, TF-A Bug

Sat, Sep 10

zandrey added projects to T1000: imx8m does not start after EHF with S-EL2 SPMC change: TF-A Bug, Trusted Firmware A.
Sat, Sep 10, 8:21 PM · Trusted Firmware A, TF-A Bug

Fri, Sep 9

zandrey created T1000: imx8m does not start after EHF with S-EL2 SPMC change.
Fri, Sep 9, 2:58 PM · Trusted Firmware A, TF-A Bug

Thu, Sep 8

joannafarley-arm added a comment to T996: Compiling bl31.elf with binutils 2.39 warns/fails with “ LOAD segment with RWX permissions”.

Hey Chris, I may have raised the bug wrong we are tracking internally as its binutils-2.39, sorry!

Thu, Sep 8, 4:33 PM · Trusted Firmware A
CJKay added a comment to T996: Compiling bl31.elf with binutils 2.39 warns/fails with “ LOAD segment with RWX permissions”.

Hi Heitbaum, could you tell me which toolchain you're using to build TF-A? The latest Arm GNU AArch64 toolchain is 11.3.Rel1, which packages binutils-2.38 and therefore compiles successfully, so I'm currently unable to reproduce this error.

Thu, Sep 8, 3:53 PM · Trusted Firmware A

Aug 29 2022

hramrach renamed T999: TF-A does not build with GCC 7 for some platforms from TF-A doe not build with GCC 7 for some platforms to TF-A does not build with GCC 7 for some platforms.
Aug 29 2022, 12:46 PM · TF-A Bug
hramrach added a comment to T999: TF-A does not build with GCC 7 for some platforms.

Aug 29 2022, 12:45 PM · TF-A Bug
hramrach created T999: TF-A does not build with GCC 7 for some platforms.
Aug 29 2022, 12:44 PM · TF-A Bug

Aug 19 2022

joannafarley-arm closed T998: dtc warns when compiling TF-A with FVP_HW_CONFIG_DTS=fdts/fvp-base-gicv3-psci-1t.dts as Resolved.
Aug 19 2022, 1:16 PM · Trusted Firmware A
nadlertz added a comment to T998: dtc warns when compiling TF-A with FVP_HW_CONFIG_DTS=fdts/fvp-base-gicv3-psci-1t.dts.

I see. Thanks for the replies. Feel free to close this task then.

Aug 19 2022, 11:34 AM · Trusted Firmware A
joannafarley-arm added a comment to T998: dtc warns when compiling TF-A with FVP_HW_CONFIG_DTS=fdts/fvp-base-gicv3-psci-1t.dts.

Regarding this web page reporting system its mainly now being used for Bug reporting. There is now a TF-A mailing list https://lists.trustedfirmware.org/mailman3/lists/tf-a.lists.trustedfirmware.org/ where many more people can help with questions.

Aug 19 2022, 11:21 AM · Trusted Firmware A
Andre-ARM added a comment to T998: dtc warns when compiling TF-A with FVP_HW_CONFIG_DTS=fdts/fvp-base-gicv3-psci-1t.dts.

Yes, this is a known issue. The DTs for the base FVP model were once imported from the Linux tree, but haven't been updated since. Meanwhile both DTC and the DT schema compliance tooling in the kernel tree got stricter, so the old files trigger warnings now.
One could go ahead and just fix each of those warnings, but I am actually working on rearranging the FVP DT files, so we can sync them from the kernel tree. That should fix those messages automatically.

Aug 19 2022, 11:03 AM · Trusted Firmware A