Fix failing FW update integ test (2.1) #702
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mlvisaya
requested review from
helloxiling,
mhatrevi,
parvathib,
swenson and
vsonims
helloxiling
reviewed
Jan 6, 2026
helloxiling
reviewed
Jan 6, 2026
mlvisaya
force-pushed
the
mlvisaya/fix-failing-fw-update-tests-2.1
branch
from
ad0f077 to
ba97faf
Compare
mlvisaya
commented
Jan 7, 2026
mlvisaya
force-pushed
the
mlvisaya/fix-failing-fw-update-tests-2.1
branch
2 times, most recently
from
10031de to
2788fb7
Compare
- Due to the reduced mailbox size, the Caliptra FW and manifest should use an external staging area instead of mailbox fifo. To do this, the mailbox driver now wraps all mailbox commands in an ExternalMailboxReq. - The mailbox driver will use, as much as possible, DMA to transfer data from the application buffer to the external staging area. For this, the DMA HIL is passed to the mailbox driver. DMA HIL file is now moved to the runtime code instead of emulator - The external staging area to be used is 0xb00c_0000 mapped to the same FPGA memory address for the staging memory. - Also fixed the unnecessary endianess swap when reading from the emulator's external test sram peripheral - Speed up MboxSram read/write in the emulator by using block read/write instead of word read/writes. Note that fw update integ test is using MboxSram1 to stage MCU FW (this is different from Mailbox payload staging area) - Due to upgrade in Caliptra-sw dependency, some of the crypto APIs have changed and also updated here.
mlvisaya
force-pushed
the
mlvisaya/fix-failing-fw-update-tests-2.1
branch
from
2788fb7 to
1e7db10
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Due to the reduced mailbox size, the Caliptra FW and manifest should use an external staging area instead of mailbox fifo. To do this, the mailbox driver now wraps all mailbox commands in an ExternalMailboxReq.
The mailbox driver will use, as much as possible, DMA to transfer data from the application buffer to the external staging area. For this, the DMA HIL is passed to the mailbox driver. DMA HIL file is now moved to the runtime code instead of emulator
The external staging area to be used is 0xb00c_0000 mapped to the same FPGA memory address for the staging memory.
Also fixed the unnecessary endianess swap when reading from the emulator's external test sram peripheral
Speed up MboxSram read/write in the emulator by using block read/write instead of word read/writes. Note that fw update integ test is using MboxSram1 to stage MCU FW (this is different from Mailbox payload staging area)
Due to upgrade in Caliptra-sw dependency, some of the crypto APIs have changed and also updated here. The example-app stack has been increased to accommodate increase certificate size.