Aksal/nuttx
3
1
Fork 1
mirror of https://github.com/apache/nuttx.git synced 2026-10-03 20:27:53 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 2
nuttx/tools/ci/testlist/arm-06.dat

8 lines
200 B
Text
Raw Normal View History

CI: Split the Build Job arm-05 into multiple smaller jobs CI Build Job `arm-05` (runtime 2 hours) has become the Performance Bottleneck for CI Workflow. That's because `arm-05` builds too many targets for nRF, RP2040, SAM 3, SAM A and SAM D. This PR splits `arm-05` into multiple smaller jobs, to reduce the CI Build Duration. Before the PR: `arm-05` is overloaded, build requires 2 hours - `arm-05` (2 hours): nRF, RP2040, SAM 3, SAM A, SAM D - `arm-06` (56 mins): STM32 [a-m]* After the PR: `arm-05` is offloaded (to `arm-06` and `arm-07`), completes within 1 hour - `arm-05` (47 mins): nRF - `arm-06` (1 hour): Reserve for RP2040 exclusively - `arm-07` (1 hour 15 mins): SAM 3, SAM A, SAM D, STM32 [a-m]* Build Jobs are sorted by Target Name. So we cascade the changes and rename the Build Jobs: `arm-07` becomes `arm-08`, `arm-08` becomes `arm-09` etc. Then `arm-13` becomes a new job `arm-14`. (Which we added to `build.yml`) Performance of `arm-05` is discussed in https://github.com/apache/nuttx/issues/13775 and https://github.com/apache/nuttx/issues/12773
2024-10-09 09:37:07 +08:00
/arm/r*,CONFIG_ARM_TOOLCHAIN_GNU_EABI
Documentation, tools/ci: Say where the NXFLAT tools actually come from. The download link is dead: bitbucket.org/nuttx/buildroot is gone, and the buildroot that still carries ldnxflat is github.com/patacongo/buildroot. The instructions were also more than is needed. mknxflat came in tree with PR #19600, so only ldnxflat has to be built, and an ordinary arm-none-eabi GCC compiles and links NXFLAT modules: a board does not have to select CONFIG_ARM_TOOLCHAIN_BUILDROOT to use them. What ldnxflat does need is a binutils source and build tree, because it reads its input through libbfd. The CI test list said mknxflat is what the container lacks. It is in tree now; ldnxflat is the one that is missing. Assisted-by: Claude Opus 5 (1M context) <noreply@anthropic.com> Signed-off-by: Marco Casaroli <marco.casaroli@gmail.com>
2026-09-08 22:53:11 +02:00
# ldnxflat is not available in the CI container. mknxflat is in tree.
boards/rp23xx: Split the xipfs configuration into xipfs and xipfs-nxflat. The xipfs configuration enabled CONFIG_NXFLAT and the nxflatxip example, whose build runs mknxflat to generate the module thunk. The NXFLAT tools are not installed in the CI container, so every CI build of this configuration failed with "mknxflat: command not found". * xipfs keeps the file system, the xipfs command and the test suite. It builds with a plain toolchain, so CI still covers the file system code. * xipfs-nxflat adds CONFIG_NXFLAT and CONFIG_EXAMPLES_NXFLATXIP and is excluded from the CI build list, the same treatment the other NXFLAT configurations already get (eagle100:nxflat, lm3s6965-ek:qemu-nxflat, olimex-lpc1766stk:thttpd-nxflat). Impact: CI and board configurations only. No source or runtime change. Assisted-by: Claude Code:claude-opus-5 Signed-off-by: Marco Casaroli <marco.casaroli@gmail.com>
2026-07-28 16:28:36 +02:00
-pimoroni-pico-2-plus:xipfs-nxflat
arm/rp2040: CMake build for Raspberry Pi RP2040 implemented - CMake added board Raspberry Pi Pico - Added the entry: CMake,raspberrypi-pico:bmp280 to the file arm-06.dat. - Moved the search for the Python 3 interpreter to the root CMakefile to avoid unnecessary repetition. Signed-off-by: simbit18 <simbit18@gmail.com>
2025-09-22 16:28:20 +02:00
# Boards build by CMake
CMake,raspberrypi-pico:bmp280
Reference in a new issue Copy permalink