| e957c337 | 07-May-2025 |
Gabriel Fernandez <gabriel.fernandez@foss.st.com> |
feat(stm32mp25): add RCC register to display all IWDG flags
Add a new define RCC_C1BOOTRSTSCLRR_IWDGXSYSRSTF to check all IWDG flags.
Change-Id: Id48671ae935e3100d4c42bc341d770f702d661de Signed-off
feat(stm32mp25): add RCC register to display all IWDG flags
Add a new define RCC_C1BOOTRSTSCLRR_IWDGXSYSRSTF to check all IWDG flags.
Change-Id: Id48671ae935e3100d4c42bc341d770f702d661de Signed-off-by: Gabriel Fernandez <gabriel.fernandez@foss.st.com>
show more ...
|
| 2ec3cec5 | 24-Jan-2024 |
Nicolas Le Bayon <nicolas.le.bayon@st.com> |
feat(stm32mp21): add PWR registers file
Use the new file stm32mp21_pwr.h for STM32MP21 PWR peripheral registers definition. Update platform code for backup domain write protection disabling.
Change
feat(stm32mp21): add PWR registers file
Use the new file stm32mp21_pwr.h for STM32MP21 PWR peripheral registers definition. Update platform code for backup domain write protection disabling.
Change-Id: Iedfa764529bcd5119be8e94da7f7b84699e86086 Signed-off-by: Yann Gautier <yann.gautier@foss.st.com> Signed-off-by: Nicolas Le Bayon <nicolas.le.bayon@st.com>
show more ...
|
| 701178dc | 01-Aug-2024 |
Maxime Méré <maxime.mere@foss.st.com> |
feat(st): introduce SoC family compilation switch
add STM32MP1X and STM3MP2X compilation switch to replace #if STM32MP21 || STM32MP23 || STM32MP25 for MP2 SoCs and #if STM32MP13 || STM32MP15 for MP1
feat(st): introduce SoC family compilation switch
add STM32MP1X and STM3MP2X compilation switch to replace #if STM32MP21 || STM32MP23 || STM32MP25 for MP2 SoCs and #if STM32MP13 || STM32MP15 for MP1 SoCs.
This will avoid to forget to modify all these files when a new SoC is introduced.
Change-Id: Ib984b22a19e08af5bc1b62fe2032f10240ec9122 Signed-off-by: Maxime Méré <maxime.mere@foss.st.com>
show more ...
|
| f83afc9d | 23-Nov-2023 |
Yann Gautier <yann.gautier@st.com> |
docs(changelog): add subsections for STM32MP2
Now that STM32MP2 family has different types of SoCs, add relative subsections for STM32MP2. The same is done for FDTS scopes.
Change-Id: I374215c44ce9
docs(changelog): add subsections for STM32MP2
Now that STM32MP2 family has different types of SoCs, add relative subsections for STM32MP2. The same is done for FDTS scopes.
Change-Id: I374215c44ce9515ca33b5882058a71db4886b80a Signed-off-by: Yann Gautier <yann.gautier@st.com> Signed-off-by: Nicolas Le Bayon <nicolas.le.bayon@st.com>
show more ...
|
| e577ca36 | 02-Feb-2024 |
Nicolas Le Bayon <nicolas.le.bayon@st.com> |
docs(stm32mp2): introduce new STM32MP23 family
STM32MP23 is a derivative from STM32MP25. It comes in 3 different lines: - STM32MP235: Dual Cortex-A35 + Cortex-M33 - 2x Ethernet - 2x CAN FD
docs(stm32mp2): introduce new STM32MP23 family
STM32MP23 is a derivative from STM32MP25. It comes in 3 different lines: - STM32MP235: Dual Cortex-A35 + Cortex-M33 - 2x Ethernet - 2x CAN FD H264 - 3D GPU - AI / NN - LVDS / DSI - STM32MP233: Dual Cortex-A35 + Cortex-M33 - 2x Ethernet - 2x CAN FD - STM32MP231: Single Cortex-A35 + Cortex-M33 - 1x Ethernet
Change-Id: Iaf3dd7e0c1eda055063361af3c98855b1272d4c6 Signed-off-by: Nicolas Le Bayon <nicolas.le.bayon@st.com>
show more ...
|
| 07759f2b | 20-Apr-2023 |
Yann Gautier <yann.gautier@foss.st.com> |
docs(stm32mp2): introduce new STM32MP21 family
STM32MP21 is a derivative from STM32MP25. It comes in 3 different lines: - STM32MP215: Single Cortex-A35 + Cortex-M33 - 2x Ethernet - 2x CAN FD
docs(stm32mp2): introduce new STM32MP21 family
STM32MP21 is a derivative from STM32MP25. It comes in 3 different lines: - STM32MP215: Single Cortex-A35 + Cortex-M33 - 2x Ethernet - 2x CAN FD CSI - LTDC - STM32MP213: Single Cortex-A35 + Cortex-M33 - 2x Ethernet - 2x CAN FD - STM32MP211: Single Cortex-A35 + Cortex-M33 - 1x Ethernet
Change-Id: Ie3db430bedd86c3b444bec647792be24b20a0cba Signed-off-by: Yann Gautier <yann.gautier@foss.st.com> Signed-off-by: Nicolas Le Bayon <nicolas.le.bayon@st.com>
show more ...
|
| f3fec61f | 28-May-2025 |
Manish V Badarkhe <Manish.Badarkhe@arm.com> |
fix(drtm): measure and record the DLME EP offset instead of absolute address
Update the DLME measurement logic to record only the DLME image entry point offset (`dlme_img_ep_off`) rather than the fu
fix(drtm): measure and record the DLME EP offset instead of absolute address
Update the DLME measurement logic to record only the DLME image entry point offset (`dlme_img_ep_off`) rather than the fully resolved physical address. This aligns with the DRTM specification v1.1.
Signed-off-by: Manish V Badarkhe <Manish.Badarkhe@arm.com> Change-Id: I3093282a1cb0fef0aafa48aeec34770f574fa34a
show more ...
|
| 3b6e5947 | 27-May-2025 |
Manish V Badarkhe <Manish.Badarkhe@arm.com> |
fix(drtm): set correct max region mask for DMA protection to 0xFFFF
Update `ARM_DRTM_DMA_PROT_FEATURES_MAX_REGIONS_MASK` from `0xF` to `0xFFFF` to correctly reflect the maximum number of supported D
fix(drtm): set correct max region mask for DMA protection to 0xFFFF
Update `ARM_DRTM_DMA_PROT_FEATURES_MAX_REGIONS_MASK` from `0xF` to `0xFFFF` to correctly reflect the maximum number of supported DMA protection regions, as per the expected DRTM capability encoding.
The previous 4-bit mask limited the range to 16 regions, which is insufficient and incorrect based on the spec's intention. This fix extends the bitmask to 16 bits, allowing up to 65,535 regions if supported in future implementations.
Signed-off-by: Manish V Badarkhe <Manish.Badarkhe@arm.com> Change-Id: I2531706f4b75125b510413870dfd4b1804e5adb6
show more ...
|
| 65f6936e | 27-May-2025 |
Manish V Badarkhe <Manish.Badarkhe@arm.com> |
fix(drtm): correct PROTECT_MEM_REGION value as per DRTM specification
The value of `PROTECT_MEM_REGION` was incorrectly set to 2. This patch updates it to 1, which aligns with the DRTM specification
fix(drtm): correct PROTECT_MEM_REGION value as per DRTM specification
The value of `PROTECT_MEM_REGION` was incorrectly set to 2. This patch updates it to 1, which aligns with the DRTM specification v1.1 for DMA protection modes.
Note: Although the DRTM implementation does not currently handle `PROTECT_MEM_REGION`, this fix ensures future compatibility and avoids misleading definitions.
Signed-off-by: Manish V Badarkhe <Manish.Badarkhe@arm.com> Change-Id: I6811be8241aa4c0801352e2b9bd4872dc475ca78
show more ...
|
| 94aa3d27 | 27-May-2025 |
Manish V Badarkhe <Manish.Badarkhe@arm.com> |
fix(drtm): add event name data for separator event entries
Update the DRTM measurement logging to include `drtm_event_arm_sep_data` as the event name for separator events recorded in PCR-17 and PCR-
fix(drtm): add event name data for separator event entries
Update the DRTM measurement logging to include `drtm_event_arm_sep_data` as the event name for separator events recorded in PCR-17 and PCR-18.
Previously, the event name parameter was set to `NULL`, resulting in incomplete event records. This fix ensures that separator events are correctly labeled in the event log with meaningful context and it aligns with DRTM specification v1.1.
Signed-off-by: Manish V Badarkhe <Manish.Badarkhe@arm.com> Change-Id: I2803d0f2e113352116d7894c2a89dfc48ed0fd85
show more ...
|
| c61c9a31 | 15-May-2025 |
Harrison Mutai <harrison.mutai@arm.com> |
build(poetry): wrap docs build in poetry
Simplify building documentation by wrapping the Sphinx command inside a Poetry environment. Previously, the developer had to manually activate Poetry and in
build(poetry): wrap docs build in poetry
Simplify building documentation by wrapping the Sphinx command inside a Poetry environment. Previously, the developer had to manually activate Poetry and install the docs group. This change makes the process consistent with other build targets and reduces user error. Falls back gracefully if Poetry is not installed.
Change-Id: I1dfea58314253773bec5e2c70d27e2216e3143d9 Signed-off-by: Harrison Mutai <harrison.mutai@arm.com>
show more ...
|
| 388cb2f4 | 29-May-2025 |
Harrison Mutai <harrison.mutai@arm.com> |
docs(fconf): streamline TB_FW_CONFIG bindings
This change simplifies the documentation for TB_FW_CONFIG by removing outdated or platform-specific bindings and introducing a clear section referencing
docs(fconf): streamline TB_FW_CONFIG bindings
This change simplifies the documentation for TB_FW_CONFIG by removing outdated or platform-specific bindings and introducing a clear section referencing the standardized Chain of Trust (CoT) bindings.
Change-Id: I3f3f96ed333a57153bde929fa35863655c30e8ed Signed-off-by: Harrison Mutai <harrison.mutai@arm.com>
show more ...
|
| ddb4aee5 | 29-May-2025 |
Harrison Mutai <harrison.mutai@arm.com> |
refactor(fconf): use macro to set image info
Use the provided macro to set the image_info_t header rather than doing it manually.
Change-Id: I45fd62c3947c9a23c2cb0df542ce2424955e2f8b Signed-off-by:
refactor(fconf): use macro to set image info
Use the provided macro to set the image_info_t header rather than doing it manually.
Change-Id: I45fd62c3947c9a23c2cb0df542ce2424955e2f8b Signed-off-by: Harrison Mutai <harrison.mutai@arm.com>
show more ...
|
| adbcd85e | 29-May-2025 |
Joanna Farley <joanna.farley@arm.com> |
Merge changes from topic "xlnx_versal_custom_sip" into integration
* changes: feat(versal): add hooks for mmap and early setup refactor(zynqmp): refactor custom sip service |
| a0aec939 | 28-May-2025 |
Madhukar Pappireddy <madhukar.pappireddy@arm.com> |
Merge "fix(qemu): fix variable may be used uninitialized error" into integration |
| 8daebefe | 15-Apr-2025 |
Chris Kay <chris.kay@arm.com> |
refactor(memmap)!: change behavioural flags to commands
This change factors out the following memory map tool flags into independent commands:
- `--footprint` (becomes `memory footprint`) - `--tree
refactor(memmap)!: change behavioural flags to commands
This change factors out the following memory map tool flags into independent commands:
- `--footprint` (becomes `memory footprint`) - `--tree` (becomes `memory tree`) - `--symbol` (becomes `memory symbol`)
So, for example, where previously you would generate the memory footprint of a build with:
memory --tree
You would now instead use:
memory footprint
Any flags specific to a command (e.g. `--depth` for `tree`) must be specified after the command, e.g.
memory tree --depth 1
... instead of:
memory --depth 1 tree
BREAKING-CHANGE: The image memory map visualization tool now uses commands, rather than arguments, to determine the behaviour of the script. See the commit message for further details.
Change-Id: I11d54d1f6276b8447bdfb8496544ab80399459ac Signed-off-by: Chris Kay <chris.kay@arm.com>
show more ...
|
| 6acd79ab | 17-Apr-2025 |
Chris Kay <chris.kay@arm.com> |
refactor(memmap): fix typing-related issues
This change introduces Pyright - a static type checker for Python - and resolves a large number of the errors that it reports. Some errors have not been r
refactor(memmap): fix typing-related issues
This change introduces Pyright - a static type checker for Python - and resolves a large number of the errors that it reports. Some errors have not been resolved as they require larger refactors, so these will be done in later patches.
Change-Id: I2ed9b1cc729bf44a1fa8e69882af34657cc30b38 Signed-off-by: Chris Kay <chris.kay@arm.com>
show more ...
|
| bc74cfc7 | 15-Apr-2025 |
Chris Kay <chris.kay@arm.com> |
refactor(memmap): create common image parser interface
This is another non-functional change, which factors the memory footprint and symbol listing interfaces shared by the two image parsing backend
refactor(memmap): create common image parser interface
This is another non-functional change, which factors the memory footprint and symbol listing interfaces shared by the two image parsing backends into a common `Image` interface.
Change-Id: I625a8e5ca77e38155b6ed545a33a8ae4c2cf133a Signed-off-by: Chris Kay <chris.kay@arm.com>
show more ...
|
| b658ccd7 | 22-Apr-2025 |
Chris Kay <chris.kay@arm.com> |
refactor(memmap): represent image symbols with key-value map
The symbols defined by an image are currently returned as a list of tuple pairs, which is a fairly unintuitive way of representing what i
refactor(memmap): represent image symbols with key-value map
The symbols defined by an image are currently returned as a list of tuple pairs, which is a fairly unintuitive way of representing what is essentially a map.
This commit changes the return type to the appropriate map type, and moves the heavy-lifting required to turn it into a list of tuples into the printer, which is the only place where this representation is necessary.
Change-Id: I87d047608b390e1e0cdf93eb6af5aeb103b1d69e Signed-off-by: Chris Kay <chris.kay@arm.com>
show more ...
|
| 5bce4e60 | 14-Apr-2025 |
Chris Kay <chris.kay@arm.com> |
refactor(memmap): factor memory regions into their own structure
This is a non-functional change to clean up how we represent memory regions in the memory map tool.
This introduces the `Region` dat
refactor(memmap): factor memory regions into their own structure
This is a non-functional change to clean up how we represent memory regions in the memory map tool.
This introduces the `Region` data-class, which does little more than store the region data exposed by the linker scripts, and provides some additional helper methods which re-produce what was already being done by both the ELF parser and the map file parser.
Change-Id: Idf45b71bd460f7312498b97b9e4743f4dc482411 Signed-off-by: Chris Kay <chris.kay@arm.com>
show more ...
|
| 205248e8 | 28-Apr-2025 |
Chris Kay <chris.kay@arm.com> |
refactor(memmap): apply additional type hints
This is a non-functional change which adds type hints wherever they might be helpful. Outside of human readability, this can also help static analysis t
refactor(memmap): apply additional type hints
This is a non-functional change which adds type hints wherever they might be helpful. Outside of human readability, this can also help static analysis tools and IDEs identify additional errors.
Change-Id: Ie63e7f1cdeb893ca7d8a703aff56361eaa4e8f1b Signed-off-by: Chris Kay <chris.kay@arm.com>
show more ...
|
| f59b6fb5 | 01-May-2025 |
Chris Kay <chris.kay@arm.com> |
refactor(memmap): check ELF object type rather than flag
This is a small functional change which removes the need to pass the type of the ELF object given to `memory.elfparser.tfa_mem_obj_factory` b
refactor(memmap): check ELF object type rather than flag
This is a small functional change which removes the need to pass the type of the ELF object given to `memory.elfparser.tfa_mem_obj_factory` by instead checking its type.
Change-Id: I653e71345e41bcbae87a3a7475d7a1dd69614b5d Signed-off-by: Chris Kay <chris.kay@arm.com>
show more ...
|
| 015a8fd1 | 17-Apr-2025 |
Chris Kay <chris.kay@arm.com> |
refactor(memmap): remove unused functionality
The functionality removed by this patch is currently unused, and there are currently no plans to expose it to users.
Change-Id: I277fce51e0f34cd9608b4b
refactor(memmap): remove unused functionality
The functionality removed by this patch is currently unused, and there are currently no plans to expose it to users.
Change-Id: I277fce51e0f34cd9608b4bc1258c78af208897fa Signed-off-by: Chris Kay <chris.kay@arm.com>
show more ...
|
| 8ab677b9 | 17-Apr-2025 |
Chris Kay <chris.kay@arm.com> |
fix(memmap): ensure terminal width is respected
Python, for one reason or another, doesn't always get access to the terminal columns environment variable (`COLUMNS`). Instead, switch out this logic
fix(memmap): ensure terminal width is respected
Python, for one reason or another, doesn't always get access to the terminal columns environment variable (`COLUMNS`). Instead, switch out this logic with the Python-recommended way to get the terminal width, via the `shutil` import.
Change-Id: I3956f10e91b286404c4d9e802d94592a00c746fb Signed-off-by: Chris Kay <chris.kay@arm.com>
show more ...
|
| 1bed7707 | 01-Apr-2025 |
Chris Kay <chris.kay@arm.com> |
style(memmap): format with Ruff
This change adds the Python formatter and linter Ruff to the Poetry development dependencies for the memory map script, and formats the entire project using it.
Chan
style(memmap): format with Ruff
This change adds the Python formatter and linter Ruff to the Poetry development dependencies for the memory map script, and formats the entire project using it.
Change-Id: I7c5898bd8ee364e3b72476014ef6b4b11947ae18 Signed-off-by: Chris Kay <chris.kay@arm.com>
show more ...
|