Hello,
+1
Tested 13.0.0 RC0 from git, AVR architecture, breadxavr:nsh - works out
of the box.
Register: nsh
Register: sh
LD: nuttx
Memory region Used Size Region Size %age Used
flash: 55211 B 128 KB 42.12%
sram: 780 B 16 KB 4.76%
eeprom: 0 B 512 B 0.00%
rodata: 602 B 4 KB 14.70%
However, when testing, I spotted some Kconfig warnings:
CP: arch/dummy/Kconfig to .../nuttx.git/arch/dummy/dummy_kconfig
CP: boards/dummy/Kconfig to .../nuttx.git/boards/dummy/dummy_kconfig
LN: platform/board to .../apps/platform/dummy
LN: include/arch to arch/avr/include
LN: include/arch/board to
.../nuttx.git/boards/avr/avrdx/breadxavr/include
LN: drivers/platform to .../nuttx.git/drivers/dummy
LN: include/arch/chip to .../nuttx.git/arch/avr/include/avrdx
LN: arch/avr/src/chip to .../nuttx.git/arch/avr/src/avrdx
LN: arch/avr/src/board to .../nuttx.git/boards/avr/avrdx/breadxavr/src
arch/arm/Kconfig:56:error: recursive dependency detected!
For a resolution refer to Documentation/kbuild/kconfig-language.txt
subsection "Kconfig recursive dependency limitations"
arch/arm/Kconfig:56: choice <choice> contains symbol ARCH_CHIP_STM32
For a resolution refer to Documentation/kbuild/kconfig-language.txt
subsection "Kconfig recursive dependency limitations"
arch/arm/Kconfig:492: symbol ARCH_CHIP_STM32 is part of choice
ARCH_CHIP_STM32F0
For a resolution refer to Documentation/kbuild/kconfig-language.txt
subsection "Kconfig recursive dependency limitations"
arch/arm/Kconfig:508: symbol ARCH_CHIP_STM32F0 is part of choice
<choice>
configuration written to .config
Is this is something that does not manifest for non-AVR build?
Cheers
On 2026-06-27 02:01, Alin Jerpelea wrote:
Hello all,
Apache NuttX 13.0.0 RC0 has been staged under [1] and it's
time to vote on accepting it for release. Voting will be open for 72hr.
A minimum of 3 binding +1 votes and more binding +1 than binding -1 are
required to pass.
The Apache requirements for approving a release can be found here [3]
"Before voting +1 PMC members are required to download the signed
source code package, compile it as provided, and test the resulting
executable on their own platform, along with also verifying that the
package meets the requirements of the ASF policy on releases."
A document to walk through some of this process has been published on
our project wiki and can be found here [4].
[ ] +1 accept (indicate what you validated - e.g. performed the non-RM
items in [4])
[ ] -1 reject (explanation required)
Thank you all,
Alin Jerpelea
SCM Information:
Release tag: nuttx-13.0.0-RC0
Hash for the release nuttx tag:
2c18ee90cd3dd7d53cc2d3e6500c0597ddd4620c
Hash for the release nuttx-apps tag:
b8cb8d1a4a3c6aa7b86b593f409380a07b4f61eb
[1] https://dist.apache.org/repos/dist/dev/nuttx/13.0.0-RC0/
[2]
https://raw.githubusercontent.com/apache/nuttx/nuttx-13.0.0-RC0/ReleaseNotes
[3] https://www.apache.org/dev/release.html#approving-a-release
[4]
https://cwiki.apache.org/confluence/display/NUTTX/Validating+a+staged+Release
