Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[feat] Firmware image download from Recovery Interface #1867

Merged
merged 1 commit into from
Jan 23, 2025

Conversation

mhatrevi
Copy link
Collaborator

This change adds the ROM flow to download the firmware image from the recovery interface.

swenson
swenson previously approved these changes Jan 6, 2025
Copy link
Contributor

@swenson swenson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

rom/dev/src/flow/cold_reset/fw_processor.rs Show resolved Hide resolved
@mhatrevi mhatrevi force-pushed the vmhatre/recovery-interface-fw-download-final branch 3 times, most recently from fbec406 to b302283 Compare January 15, 2025 00:14
swenson added a commit that referenced this pull request Jan 23, 2025
This stubs out the recovery flow in the runtime.

We also update the DMA peripheral so that it can be used as a
`ureg::Mmio`, which will allow us to use the autogenerated I3C recovery
register interface instead of hardcoding offsets.

We also had to modify `ureg` slightly to remove the unused `impl Uint`
for `u64` (because we don't don't support 64-bit AXI transfers) and add
a `from_u32()` method for the (unused) `u8` and `u16` implementations.

This builds on #1867 and rewrites it to use the updated DMA interface.
swenson added a commit that referenced this pull request Jan 23, 2025
This stubs out the recovery flow in the runtime.

We also update the DMA peripheral so that it can be used as a
`ureg::Mmio`, which will allow us to use the autogenerated I3C recovery
register interface instead of hardcoding offsets.

We also had to modify `ureg` slightly to remove the unused `impl Uint`
for `u64` (because we don't don't support 64-bit AXI transfers) and add
a `from_u32()` method for the (unused) `u8` and `u16` implementations.

This builds on #1867 and rewrites it to use the updated DMA interface.
@mhatrevi mhatrevi force-pushed the vmhatre/recovery-interface-fw-download-final branch from b302283 to 226130e Compare January 23, 2025 02:53
This change adds the ROM flow to download the firmware image from the recovery interface.
@mhatrevi mhatrevi force-pushed the vmhatre/recovery-interface-fw-download-final branch from 226130e to 3afb7e7 Compare January 23, 2025 03:03
Copy link
Contributor

@swenson swenson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mhatrevi mhatrevi merged commit b764d0a into main-2.x Jan 23, 2025
5 checks passed
swenson added a commit that referenced this pull request Jan 23, 2025
This stubs out the recovery flow in the runtime.

We also update the DMA peripheral so that it can be used as a
`ureg::Mmio`, which will allow us to use the autogenerated I3C recovery
register interface instead of hardcoding offsets.

We also had to modify `ureg` slightly to remove the unused `impl Uint`
for `u64` (because we don't don't support 64-bit AXI transfers) and add
a `from_u32()` method for the (unused) `u8` and `u16` implementations.

This builds on #1867 and rewrites it to use the updated DMA interface.
swenson added a commit that referenced this pull request Jan 23, 2025
This stubs out the recovery flow in the runtime.

We also update the DMA peripheral so that it can be used as a
`ureg::Mmio`, which will allow us to use the autogenerated I3C recovery
register interface instead of hardcoding offsets.

We also had to modify `ureg` slightly to remove the unused `impl Uint`
for `u64` (because we don't don't support 64-bit AXI transfers) and add
a `from_u32()` method for the (unused) `u8` and `u16` implementations.

This builds on #1867 and rewrites it to use the updated DMA interface.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Caliptra v2.0 Items to be considered for v2.0 Release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants