Repository navigation
This release is about making a board target something you can copy rather than something you have to invent. A generic BSP framework replaces the per-board scaffolding, four targets are built on it, and every toolchain and SDK the builds depend on is now pinned and cached rather than fetched from whatever the network offers that day.
Much of that work came from Google Summer of Code. @alieissa contributed the NXP i.MX RT1064-EVK target with its three demos and Renode CI, and the STM32F767ZI BSP refactor that brought a NetX Duo echo demo with it. @AmmarOkla12772 contributed the ThreadX monitor and primitives showcase for the NUCLEO-F401RE, and the network-connected environmental station demo. Between them that is half the targets in this release and two of its demos. We thank them both, and we are grateful to Google for supporting their work through the programme.
We also thank the independent contributors @divyanshisingh987456321 and @Jaxc for their valuable contributions to this release.
The SampleX user guide is attached to this release as a PDF, in A4 and US Letter.
Vulnerabilities addressed
No vulnerabilities were addressed in this release. You can access advisories for previously addressed vulnerabilities here.
Highlights
A generic BSP framework, and four targets on it
Board support was per-target and copied by hand. There is now a generic BSP framework, with the startup self-tests and RAM sizing behind interfaces a target implements rather than duplicates, and the demo application moved into apps/ so more than one target builds it. (#49, #56, #57, @fdesbiens)
Four targets are built on that framework:
- PolarFire SoC Icicle Kit, added with the framework itself (#49, @fdesbiens)
- NUCLEO-F401RE, relocated into
targets/and adopted onto it, with Renode regression tests and a ThreadX monitor and primitives showcase (#50, #51, #45, @fdesbiens, @AmmarOkla12772 for the showcase) - NXP i.MX RT1064-EVK, with three demos and Renode CI (@alieissa, Google Summer of Code)
- STM32 NUCLEO-F429ZI, derived from the F767ZI target and moved onto STM32F4 peripherals (#47, @Jaxc)
The STM32F767ZI target also gained a NetX Duo echo demo and a BSP refactor (#39, @alieissa), and a network-connected environmental station demo (#44, @AmmarOkla12772). Both were Google Summer of Code contributions.
Builds that fetch the same thing twice
The toolchains and SDKs the targets build against were fetched unpinned, so two runs a week apart could compile against different compilers. The Arm toolchain is pinned to 14.3.Rel1 and adopts the ThreadX install pattern, the RISC-V toolchain to xPack GCC 14.3.0, the NUCLEO Renode download is pinned, and every toolchain fetch is cached. (#53, #54, #55, @fdesbiens)
The STM32F429 SVD follows the same rule: it is fetched from ST's CMSIS device family pack with the pack version pinned and its digest checked, rather than carried in the tree, and declared in that target's NOTICE alongside the HAL and CMSIS components. (#47)
Host tests for the CORE-V CLI
The CORE-V-MCU CLI host tests did not build. Mocks for the CLI core, GPIO, UART and hardware accessors let them link without the target, and they now pass. (#64, @divyanshisingh987456321)
Other Changes
- Documented the MXChip Newlib runtime glue (#68, @fdesbiens)
- Corrected the target template to describe how the framework actually works (#52, @fdesbiens)
- Updated the contribution guide for board workflows (#75, @fdesbiens)
- Normalized the AI disclosure comment to one fixed line per file (#69, #71, @fdesbiens)
- Updated the security policy (#43, @fdesbiens)
- Fixed the CORE-V-MCU deploy scripts (#32, @fdesbiens)
New Contributors
- @Jaxc made their first contribution in #47
- @divyanshisingh987456321 made their first contribution in #64
Full Changelog: v6.5.1.202602a_rel...v6.5.2.202603_rel
