Trusted Firmware AProject
ActivePublic

Recent Activity

Wed, Nov 20

raghuncstate updated the task description for T589: Insufficient ordering guarantees in bakery_lock_get() and bakery_lock_release() in bakery_lock_coherent.c.
Wed, Nov 20, 12:03 AM · Trusted Firmware A

Tue, Nov 19

raghuncstate updated the task description for T589: Insufficient ordering guarantees in bakery_lock_get() and bakery_lock_release() in bakery_lock_coherent.c.
Tue, Nov 19, 11:59 PM · Trusted Firmware A
raghuncstate created T589: Insufficient ordering guarantees in bakery_lock_get() and bakery_lock_release() in bakery_lock_coherent.c.
Tue, Nov 19, 11:56 PM · Trusted Firmware A

Mon, Nov 18

anarsoul added a comment to T582: rk3399: rockchip_soc_system_off() and rockchip_soc_soft_reset() are broken if board doesn't have poweroff and reset GPIOs.

Review request is here: https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/2512

Mon, Nov 18, 5:49 AM · Trusted Firmware A
anarsoul added a comment to T582: rk3399: rockchip_soc_system_off() and rockchip_soc_soft_reset() are broken if board doesn't have poweroff and reset GPIOs.

Looks like it fixed itself, I was able to confirm my email.

Mon, Nov 18, 5:42 AM · Trusted Firmware A

Sun, Nov 17

joannafarley-arm added a comment to T582: rk3399: rockchip_soc_system_off() and rockchip_soc_soft_reset() are broken if board doesn't have poweroff and reset GPIOs.

Hi Vasily,

Sun, Nov 17, 9:20 PM · Trusted Firmware A
anarsoul added a comment to T582: rk3399: rockchip_soc_system_off() and rockchip_soc_soft_reset() are broken if board doesn't have poweroff and reset GPIOs.

Sorry guys, your gerrit infrastructure is broken. I can't register my email at review.trustedfirmware.org it complains "Error 422 (Unprocessable Entity): invalid token" when I'm trying to confirm my email.

Sun, Nov 17, 9:07 PM · Trusted Firmware A
anarsoul created T582: rk3399: rockchip_soc_system_off() and rockchip_soc_soft_reset() are broken if board doesn't have poweroff and reset GPIOs.
Sun, Nov 17, 8:33 PM · Trusted Firmware A

Fri, Nov 8

Deepika added a watcher for Trusted Firmware A: Deepika.
Fri, Nov 8, 4:28 PM
madhukar-Arm added a member for Trusted Firmware A: madhukar-Arm.
Fri, Nov 8, 3:28 PM
laurenw-arm added a member for Trusted Firmware A: laurenw-arm.
Fri, Nov 8, 3:28 PM
balintdobszay added a member for Trusted Firmware A: balintdobszay.
Fri, Nov 8, 1:38 PM

Tue, Nov 5

joannafarley-arm closed T570: Git tag for 2.2 release has not been applied to GitHub mirror as Resolved.
Tue, Nov 5, 3:10 PM · Trusted Firmware A
joannafarley-arm added a comment to T570: Git tag for 2.2 release has not been applied to GitHub mirror.

Issue has been addressed with an update to the syncing scripts.

Tue, Nov 5, 3:10 PM · Trusted Firmware A

Sat, Nov 2

joannafarley-arm added a comment to T570: Git tag for 2.2 release has not been applied to GitHub mirror.

Hi Pete, thanks for your message.

Sat, Nov 2, 2:11 PM · Trusted Firmware A
pbatard created T570: Git tag for 2.2 release has not been applied to GitHub mirror.
Sat, Nov 2, 12:43 PM · Trusted Firmware A

Thu, Oct 24

joannafarley-arm added a project to T553: plat/arm: use Aff3 bits also to validate mpidr: Trusted Firmware A.
Thu, Oct 24, 9:58 AM · Trusted Firmware A
joannafarley-arm added a project to T562: [N1SDP] Dual Chip support: Trusted Firmware A.
Thu, Oct 24, 9:57 AM · Trusted Firmware A
joannafarley-arm added a project to T564: [GIC600] multichip support: Trusted Firmware A.
Thu, Oct 24, 9:57 AM · Trusted Firmware A
sandeepbrcm added a project to T566: psci system shutdown and system reset to follow graceful shutdown sequence: Trusted Firmware A.
Thu, Oct 24, 3:48 AM · Trusted Firmware A

Oct 21 2019

simonsouth added a comment to T554: Build can fail on systems with stack protection enabled by default.

I'm using gcc 9.2.0 and GNU binutils 2.32 for AArch64, from Void Linux's cross-aarch64-linux-gnu-0.32_1 package.

Oct 21 2019, 1:12 PM · Trusted Firmware A
soby-mathew closed T547: Correct UART PL011 initialization code as Resolved.
Oct 21 2019, 9:07 AM · Trusted Firmware A
sandrine-bailleux-arm added a comment to T554: Build can fail on systems with stack protection enabled by default.

Hi Simon,

Oct 21 2019, 6:46 AM · Trusted Firmware A

Oct 20 2019

simonsouth added a comment to T555: Rockchip RK3328: Enable workaround for Cortex-A53 erratum 855873.

Patch available for review at
https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/2303

Oct 20 2019, 8:02 PM · Trusted Firmware A
simonsouth created T555: Rockchip RK3328: Enable workaround for Cortex-A53 erratum 855873.
Oct 20 2019, 8:00 PM · Trusted Firmware A
simonsouth updated the task description for T554: Build can fail on systems with stack protection enabled by default.
Oct 20 2019, 7:17 PM · Trusted Firmware A
simonsouth added a comment to T554: Build can fail on systems with stack protection enabled by default.

Patch available for review at
https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/2302

Oct 20 2019, 7:11 PM · Trusted Firmware A
simonsouth created T554: Build can fail on systems with stack protection enabled by default.
Oct 20 2019, 6:58 PM · Trusted Firmware A

Oct 9 2019

ADIsdouthit added a comment to T548: mvebu_a3700_comphy_usb3_power_on hangs when running on lane 2.

My patch was a duplicate of https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/2198, so I dropped #2205.

Oct 9 2019, 7:00 PM · Trusted Firmware A
ADIsdouthit added a comment to T548: mvebu_a3700_comphy_usb3_power_on hangs when running on lane 2.

Fix pushed to https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/2205

Oct 9 2019, 3:30 PM · Trusted Firmware A
ADIsdouthit triaged T548: mvebu_a3700_comphy_usb3_power_on hangs when running on lane 2 as Normal priority.
Oct 9 2019, 3:06 PM · Trusted Firmware A

Oct 8 2019

avinashmehtadelhi added a comment to T547: Correct UART PL011 initialization code.

code review : https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/2197

Oct 8 2019, 2:24 PM · Trusted Firmware A
avinashmehtadelhi created T547: Correct UART PL011 initialization code.
Oct 8 2019, 1:15 PM · Trusted Firmware A

Sep 17 2019

hzhuang1 added a comment to T388: Hikey960 problem reading FIP.

Hi David,

Sep 17 2019, 8:41 AM · TF-A Question, Trusted Firmware A
DavidMCerdeira added a comment to T388: Hikey960 problem reading FIP.

Hi there!

Sep 17 2019, 8:37 AM · TF-A Question, Trusted Firmware A
hzhuang1 claimed T388: Hikey960 problem reading FIP.

Hi David,

Sep 17 2019, 4:42 AM · TF-A Question, Trusted Firmware A

Sep 11 2019

petretudor-arm added a comment to T463: Using ROM Lib.

I don't know what options you tried to build with, but I managed to build with the ROMLIB feature for the FVP platform. I will post everything I did here, hoping it will be of some use to you.
I used the following command to build:

MBEDTLS_DIR=<path_to_mbedtls> make ARM_ROTPK_LOCATION=devel_rsa CROSS_COMPILE=<path_to_cross_compiler(aarch64)> GENERATE_COT=1 PLAT=fvp ROT_KEY=plat/arm/board/common/rotpk/arm_rotprivk_rsa.pem TRUSTED_BOARD_BOOT=1 USE_ROMLIB=1  DEBUG=1 fiptool all

The cross-compiler I used is GCC 8.3 for AArch64 ELF bare-metal target. You can get it from here:
https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-a/downloads

Sep 11 2019, 3:02 PM · Trusted Firmware A, TF-A Bug

Sep 10 2019

sandrine-bailleux-arm added a comment to T464: TF-A artifacts.

So, just to be clear: Imagine a scenario with two devices - one I made (I know the keys and code on BL1) and another one that some malicious user cloned (he signed with his own keys). My device will have a Root of Trust in BL1 based on my hardware and the keys I own. The second device also has a BL1 but that image was signed by someone I don't trust. In the end, both devices will boot up successfully because they are based on each individual Chain of Trust but there's no way a third party (i.e. remote attestation server) can know the difference between the malicious device and my device solely relying on Verified Boot, right?

Sep 10 2019, 7:31 AM · TF-A Question, Trusted Firmware A

Sep 9 2019

vivinamartins16 added a comment to T464: TF-A artifacts.

Verified boot in itself already proves the boot integrity of all firmware images from BL1 up to BL33.

BL1 is the root of trust and cannot be tampered with, as it is hardware-protected. All other BL image are signed and their signature is verified before they get executed: BL1 verifies the signature of BL2, and BL2 does the same for all subsequent BL3x images. If one of the signatures is invalid then TF-A refuses to execute the corresponding image. This is treated as a fatal error that the firmware cannot recover from and the platform will typically panic in this case.

Sep 9 2019, 4:42 PM · TF-A Question, Trusted Firmware A
sandrine-bailleux-arm added a comment to T464: TF-A artifacts.

Sorry, I completely missed your point at first!

Sep 9 2019, 3:08 PM · TF-A Question, Trusted Firmware A

Sep 6 2019

vivinamartins16 added a comment to T464: TF-A artifacts.

Hi vivina,

Hi @soby-mathew !

Sep 6 2019, 5:46 PM · TF-A Question, Trusted Firmware A
akshaynkulkarni added a member for Trusted Firmware A: akshaynkulkarni.
Sep 6 2019, 1:07 PM

Sep 5 2019

soby-mathew added a comment to T464: TF-A artifacts.

Hi vivina,
Are you thinking something similar to measured boot ?
The TF-A implements what is called verified boot. Found a good description for difference between verified and measured boot here:
https://forums.juniper.net/t5/Security/What-s-the-Difference-between-Secure-Boot-and-Measured-Boot/ba-p/281251

Sep 5 2019, 2:20 PM · TF-A Question, Trusted Firmware A

Sep 3 2019

sandrine-bailleux-arm edited the content of Getting started: Contributing TF-A patches on www.trustedfirmware.org.
Sep 3 2019, 6:31 AM · Trusted Firmware A

Aug 13 2019

joannafarley-arm moved T290: Example task/Issue 2 from In Progress to Closed on the Trusted Firmware A board.
Aug 13 2019, 8:32 AM · TF-A General, Trusted Firmware A
joannafarley-arm closed T290: Example task/Issue 2 as Resolved.
Aug 13 2019, 8:32 AM · TF-A General, Trusted Firmware A

Aug 7 2019

vivinamartins16 added a comment to T464: TF-A artifacts.

Thanks Sandrine!

Aug 7 2019, 6:05 PM · TF-A Question, Trusted Firmware A
sandrine-bailleux-arm added a comment to T464: TF-A artifacts.

Hi Viviane,

Aug 7 2019, 2:57 PM · TF-A Question, Trusted Firmware A
vivinamartins16 created T464: TF-A artifacts.
Aug 7 2019, 12:33 PM · TF-A Question, Trusted Firmware A
neil-jones-work removed a project from T463: Using ROM Lib: TF-A General.
Aug 7 2019, 11:44 AM · Trusted Firmware A, TF-A Bug