Skip to content

Tags: chipsalliance/caliptra-sw

Tags

release_v20250301_0

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Release artifacts for main-2.x (#1945)

Scheduled actions can only be done on the main branch, which is why a workflow_dispatch is used.

release_v20250301_0-2.x

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Updating to the latest RTL (#1988)

release_v20250228_0

Respect the no-cfi feature in the drivers crate.

release_v20250227_0

Respect the no-cfi feature in the drivers crate.

release_v20250227_0-2.x

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Fix runtime integration test (#1978)

Remove the fw_image argument from BootParams.

release_v20250226_0

Put CFI behind a feature flag in caliptra-lms-types and caliptra-imag…

…e-types.

release_v20250225_0

[fix] Skip nightly release if caliptra-rtl submodule is stale

Last night, the release workflow made a release, even though the
caliptra-rtl submodule was not up-to-date:

https://github.com/chipsalliance/caliptra-sw/actions/runs/6875915531

The syntax !"$CHECK_RELEASE_SYNC" does not work as intended; we should
use -z instead.

release_v20250222_0

Update to zerocopy 0.8.17

Also updates DPE submodule to pull in the same zerocopy.

Zerocopy's derive macro for KnownLayout has changed. Compiling DPE in caliptra-sw fails because public interfaces are leaking these private types.

The solution is to mark them as a public field. There may be another workaround, but since these types are being serialized to and from raw bytes, it makes sense that these private fields should be visible to callers.

release_v20250221_0

Add libcaliptra APIs to check if ready for certain boot milestones.

Previously the only APIs blocked until it reached those milestones. Now they can be checked asynchronously. This is also how `caliptra_is_csr_ready` works.

release_v20250220_0

Add libcaliptra APIs to check if ready for certain boot milestones.

Previously the only APIs blocked until it reached those milestones. Now they can be checked asynchronously. This is also how `caliptra_is_csr_ready` works.