| c87df00f | 03-Sep-2025 |
dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> |
chore(dev-deps): bump the pip group across 2 directories with 1 update
Bumps the pip group with 1 update in the /tools/tlc directory: [requests](https://github.com/psf/requests).
Bumps the pip group
chore(dev-deps): bump the pip group across 2 directories with 1 update
Bumps the pip group with 1 update in the /tools/tlc directory: [requests](https://github.com/psf/requests).
Bumps the pip group with 1 update in the / directory: [requests](https://github.com/psf/requests).
Updates `requests` from 2.32.3 to 2.32.4
- [Release notes](https://github.com/psf/requests/releases)
- [Changelog](https://github.com/psf/requests/blob/main/HISTORY.md)
- [Commits](https://github.com/psf/requests/compare/v2.32.3...v2.32.4)
Updates `requests` from 2.32.3 to 2.32.4
- [Release notes](https://github.com/psf/requests/releases)
- [Changelog](https://github.com/psf/requests/blob/main/HISTORY.md)
- [Commits](https://github.com/psf/requests/compare/v2.32.3...v2.32.4)
---
updated-dependencies:
- dependency-name: requests
dependency-version: 2.32.4
dependency-type: indirect
dependency-group: pip
- dependency-name: requests
dependency-version: 2.32.4
dependency-type: indirect
dependency-group: pip
...
Change-Id: Ia260450e46a6c4bd3f9fcaf3f99bbbfb04877093
Signed-off-by: dependabot[bot] <support@github.com>
show more ...
|
| 0b4722cf | 08-Jul-2025 |
Yann Gautier <yann.gautier@st.com> |
feat(st): put stm32image tool in build directory
Following the series moving common tools compilation to the build
directory[1], do the same for stm32image tool.
[1]: cbd6cec3c3 feat(build): put fi
feat(st): put stm32image tool in build directory
Following the series moving common tools compilation to the build
directory[1], do the same for stm32image tool.
[1]: cbd6cec3c3 feat(build): put fiptool in the build directory
Signed-off-by: Yann Gautier <yann.gautier@st.com>
Change-Id: If33556e98c4788350a29c8ad96dc574584b67abd
show more ...
|
| 96fbe884 | 02-May-2025 |
Boyan Karatotev <boyan.karatotev@arm.com> |
feat(build): put enctool in the build directory
Same as fiptool. Move all artefacts to the platform build directory and
convert to the standard build macro to make things more generic. Only
differen
feat(build): put enctool in the build directory
Same as fiptool. Move all artefacts to the platform build directory and
convert to the standard build macro to make things more generic. Only
difference is that there is no symlink as the tool is only used
internally and is not exported.
Change-Id: I7570f13505ed9c5d91b3582d9981177df4d5d04c
Signed-off-by: Boyan Karatotev <boyan.karatotev@arm.com>
show more ...
|
| cbd6cec3 | 02-May-2025 |
Boyan Karatotev <boyan.karatotev@arm.com> |
feat(build): put fiptool in the build directory
For some reason, tools are not built in the build directory, but rather
in the source directory, regardless of what BUILD_BASE might say. This
is espe
feat(build): put fiptool in the build directory
For some reason, tools are not built in the build directory, but rather
in the source directory, regardless of what BUILD_BASE might say. This
is especially annoying when trying to have a few builds going at the
same time (like in a CI). For example, run A may check if a file X
exists. Seeing that it does not, it will start building the file. At the
same time, run B may also check if file X exists but before A has
written it, starting a build again. Then it is possible for A to use the
file it believes to have built right at the moment B begins writing to
it (and truncating it beforehand). This results in gcc failing to read a
fail and a failed build. The more parallel runs there are, the more
likely this is to happen, and this is virtually guaranteed to happen
with just a handful onwards.
So move fiptool and all of its build artefacts to the build directory.
Since there are platform differences between the various fiptool
incarnations, this goes in the plat build rather than a more top-level
location.
This patch adds the build macro MAKE_TOOL to do this generically for any
kind of tool since the other tools suffer from the same shortfall. This
macro takes care to use unique names for every type of argument that
building a tool might need. The fiptool makefile and platform add-ons
are updated accordingly.
This should have never been allowed in the first place, but downstream
scripts almost certainly depend on this behaviour now. So add a symlink
in the place of the old fiptool so these continue working. With any
luck, this will be removed in the future.
Change-Id: I3d4d87dab0f53deab5b43fbc6652146f0e4e7e81
Signed-off-by: Boyan Karatotev <boyan.karatotev@arm.com>
show more ...
|
| a98d4661 | 16-Sep-2024 |
Jimmy Brisson <jimmy.brisson@arm.com> |
feat(memmap): add summary command to memory map script
This patch adds a `summary` command, invoked with:
poetry run memory summary <map-file>
This command is capable of producing a summary tabl
feat(memmap): add summary command to memory map script
This patch adds a `summary` command, invoked with:
poetry run memory summary <map-file>
This command is capable of producing a summary table, similar to the
footprint command, or an HTML flame-graph representing the size of ELF
image sections.
When specified with `-o` (`--old`), an old GNU map file is used as a
past state and subtracted from the GNU map file specified by
`<map-file>` to annotate printed information with additional size
deltas.
Note that many bootloaders include alignment padding and will align to
a page size. To exclude this alignment-padding from the summary, use the
`-e` switch.
For example:
$ poetry run memory summary bl1.map -e -d 1
| Module | .text | .data | .bss |
|-----------|--------------|----------|-----------|
| bl1 | 32616(+24) | 2217(+0) | 11175(+0) |
| lib | 55932(+2060) | 40(+0) | 10628(+0) |
| Subtotals | 88548(+2084) | 2257(+0) | 21803(+0) |
Total Static RAM memory (data + bss): 24060(+0) bytes
Total Flash memory (text + data): 90805(+2084) bytes
Change-Id: Id0bc157d09e654f89730dfbe318fa5f820e9f18d
Co-authored-by: Chris Kay <chris.kay@arm.com>
Signed-off-by: Chris Kay <chris.kay@arm.com>
Signed-off-by: Jimmy Brisson <jimmy.brisson@arm.com>
show more ...
|