TF-A QuestionTag
ActivePublic

Members

  • This project does not have any members.

Recent Activity

Oct 2 2019

hzhuang1 added a comment to T498: Fail to configure email address in gerrit.

Hi Haojian,

I have the same problem.
Can you please share the solution you got from maintainer?

Oct 2 2019, 12:33 AM · TF-A Question

Oct 1 2019

semihalf-biernacki-radoslaw added a comment to T498: Fail to configure email address in gerrit.

Hi Haojian,

Oct 1 2019, 2:25 PM · TF-A Question

Sep 18 2019

hzhuang1 closed T498: Fail to configure email address in gerrit as Resolved.

Hi Sandrine,

Sep 18 2019, 12:16 PM · TF-A Question
sandrine-bailleux-arm added a watcher for TF-A Question: sandrine-bailleux-arm.
Sep 18 2019, 11:39 AM
sandrine-bailleux-arm added a comment to T498: Fail to configure email address in gerrit.

Could you please elaborate on your issue? How are you trying to configure your email address in Gerrit? Are you doing it from the user settings page? Do you have no email address registered on Gerrit at all or are you trying to add a secondary one? When is the error 422 showing?

Sep 18 2019, 11:16 AM · TF-A Question

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 created T498: Fail to configure email address in gerrit.
Sep 17 2019, 4:46 AM · TF-A Question
hzhuang1 claimed T388: Hikey960 problem reading FIP.

Hi David,

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

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

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

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

Jun 24 2019

joannafarley-arm placed T267: platform support up for grabs.
Jun 24 2019, 5:41 PM · Trusted Firmware A, TF-A Question
joannafarley-arm reopened T267: platform support as "Open".

Reopening so it can be answered

Jun 24 2019, 5:39 PM · Trusted Firmware A, TF-A Question
joannafarley-arm closed T267: platform support as Resolved.

It’s better to create a task from scratch than edit the example task. Added back in TF-A project so it is shown on the project workbook with your question.

Jun 24 2019, 5:37 PM · Trusted Firmware A, TF-A Question
amorfortune renamed T267: platform support from Example task/Issue 1 for TF-A to platform support.
Jun 24 2019, 3:32 AM · Trusted Firmware A, TF-A Question

Jun 16 2019

joannafarley-arm added a project to T388: Hikey960 problem reading FIP: TF-A Question.
Jun 16 2019, 1:01 PM · TF-A Question, Trusted Firmware A

May 31 2019

joannafarley-arm moved T334: Barrier in sprt_queue.c from Backlog to Closed on the Trusted Firmware A board.
May 31 2019, 7:07 AM · TF-A Question, Trusted Firmware A
joannafarley-arm added a project to T267: platform support: Restricted Project.
May 31 2019, 7:02 AM · Trusted Firmware A, TF-A Question

May 28 2019

soby-mathew closed T334: Barrier in sprt_queue.c as Resolved.
May 28 2019, 1:17 PM · TF-A Question, Trusted Firmware A

May 21 2019

raghuncstate added a comment to T334: Barrier in sprt_queue.c.

Thanks guys! The dmbish() is not a huge deal. Just get a little nervous when i see barriers and don't completely understand why it is there. :)

May 21 2019, 10:14 PM · TF-A Question, Trusted Firmware A
soby-mathew added a comment to T334: Barrier in sprt_queue.c.

Ah, You are right. Having taken a look at it again, yes, the SP-> SPM communication is register based and this spm_response_add() is invoked by SPM to push to a buffer within EL3 (its not a shared buffer between different ELs). I suspect the shared buffer primitives were written with shared buffer scenario in mind and the current prototype implementation does not optimize it for the case when the buffer is within EL3.

May 21 2019, 9:03 PM · TF-A Question, Trusted Firmware A
raghuncstate added a comment to T334: Barrier in sprt_queue.c.

Thanks Paul, Soby.
spm_response_*() currently cannot invoked by any secure partition since the responses[] array is in EL3 space. Is this not the case ? or is it the expectation that the responses array will be mapped to secure EL0 some time in the future? I don't see how a secure partition can invoke spm_response_* other than through an SMC, in which case we are already in EL3 context and dont require the dmbish(), as Paul pointed. I understand your argument for sprt_queue_*, since they are invoked by EL3 and the secure partition.

May 21 2019, 4:33 PM · TF-A Question, Trusted Firmware A
soby-mathew added a comment to T334: Barrier in sprt_queue.c.

Who is the lockless reader for spm_response_add() and spm_response_get()?

May 21 2019, 3:23 PM · TF-A Question, Trusted Firmware A
pbeesley-arm added a comment to T334: Barrier in sprt_queue.c.

Apologies for the delay. I've had a look into the spm_buffers.c file and I understand your query is around the dmbish() that's performed shortly before releasing the lock in both spm_response_add() and spm_response_get().

May 21 2019, 1:57 PM · TF-A Question, Trusted Firmware A
pbeesley-arm updated subscribers of T334: Barrier in sprt_queue.c.
May 21 2019, 12:40 PM · TF-A Question, Trusted Firmware A

May 13 2019

raghuncstate added a comment to T334: Barrier in sprt_queue.c.

anything ?

May 13 2019, 6:58 PM · TF-A Question, Trusted Firmware A

May 8 2019

raghuncstate added a comment to T334: Barrier in sprt_queue.c.

Thanks. Missed the lockless reader of the queue. Who is the lockless reader for spm_response_add() and spm_response_get()?

May 8 2019, 11:40 PM · TF-A Question, Trusted Firmware A
antonio-nino-diaz-arm added a comment to T334: Barrier in sprt_queue.c.

A secure partition may be reading from the queue from CPU1 at the same time as CPU0 pushes a new request. If this happens, it is needed that the stores are seen in the same order by all observers of the system.

May 8 2019, 2:54 PM · TF-A Question, Trusted Firmware A
soby-mathew assigned T334: Barrier in sprt_queue.c to pbeesley-arm.
May 8 2019, 9:50 AM · TF-A Question, Trusted Firmware A

May 5 2019

raghuncstate updated the task description for T334: Barrier in sprt_queue.c.
May 5 2019, 9:09 PM · TF-A Question, Trusted Firmware A
raghuncstate triaged T334: Barrier in sprt_queue.c as Normal priority.
May 5 2019, 9:07 PM · TF-A Question, Trusted Firmware A

Mar 22 2019

joannafarley-arm changed the visibility for TF-A Question.
Mar 22 2019, 6:15 PM
joannafarley-arm renamed T267: platform support from Example task/Issue for TF-A to Example task/Issue 1 for TF-A.
Mar 22 2019, 4:00 PM · Trusted Firmware A, TF-A Question
joannafarley-arm updated the task description for T267: platform support.
Mar 22 2019, 1:46 PM · Trusted Firmware A, TF-A Question
joannafarley-arm updated the task description for T267: platform support.
Mar 22 2019, 1:41 PM · Trusted Firmware A, TF-A Question
joannafarley-arm renamed T267: platform support from Test task/Issue for TF-A to Example task/Issue for TF-A.
Mar 22 2019, 12:11 PM · Trusted Firmware A, TF-A Question
joannafarley-arm renamed T267: platform support from Test task for TF-A to Test task/Issue for TF-A.
Mar 22 2019, 12:01 PM · Trusted Firmware A, TF-A Question
joannafarley-arm added projects to T267: platform support: TF-A Bug, TF-A Question.
Mar 22 2019, 11:58 AM · Trusted Firmware A, TF-A Question
joannafarley-arm renamed TF-A Question from Question to TF-A Question.
Mar 22 2019, 11:44 AM
joannafarley-arm set the color for TF-A Question to Violet.
Mar 22 2019, 11:42 AM