...
Security Issues Fixed In This Release
Compatibility Concerns
| Markdown |
|---|
* [#10605](https://github.com/apache/nuttx/pull/10605) Implement ticket spinlock |
...
A proposal to slove #1488 |
...
Implement ticket spinlock. |
...
* [#10861](https://github.com/apache/nuttx/pull/10861) spinlock: Add spin_lock_init and spin_is_locked macro |
...
align with Linux api naming. |
...
* [#11102](https://github.com/apache/nuttx/pull/11102) sched: explicitly select the cpuload clock source configuration |
...
Different configurations require different dependencies. |
...
Explicitly select dependencies to avoid automatically selecting |
...
inappropriate configurations. |
...
* [#11334](https://github.com/apache/nuttx/pull/11334) stm32h7_adc: Dynamically set clock prescaler and BOOST |
...
First commit is aligning naming and is a breaking change. |
...
* [#10827](https://github.com/apache/nuttx/pull/10827) Improve adjtime() functionality |
...
Prior pull request #9084 and issue #8858 added basic adjtime() |
...
support for the SAMv7 platform. |
...
This pull request adds support for STM32 platform. |
...
In addition I have made a few changes to the adjtime() configuration |
...
options: |
...
1) Previously adjustments less than 1 microsecond per tick would be |
...
completely ignored. Now they are applied over a shorter period at |
...
a rate of 1 us per tick. |
...
2) Previously CLOCK_ADJTIME_PERIOD was in units of 1/100th of second. |
...
Change to milliseconds to be more generally useful unit. |
...
Change setting name to CLOCK_ADJTIME_PERIOD_MS to make the unit change |
...
easier to notice. |
...
3) Previously CLOCK_ADJTIME_SLEWLIMIT was in percentage. |
...
Most clock crystals have better accuracy than 1%, so the minimum slew |
...
rate was excessive. Change to CLOCK_ADJTIME_SLEWLIMIT_PPM with setting |
...
value in parts per million. |
...
4) No need to use floating point math in |
...
clock_adjtime.c.
Impact
Users who have used CLOCK_ADJTIME_PERIOD and CLOCK_ADJTIME_SLEWLIMIT
settings should update their configuration. New CLOCK_ADJTIME_PERIOD_MS is
10x the old period value, and new CLOCK_ADJTIME_SLEWLIMIT_PPM is 10000 times
the old slewlimit. |
Known Problems In This Release
NuttX on Ox64: getprime + hello crashes
| Markdown |
|---|
NuttShell (NSH) NuttX-12.4.0
nsh> uname -a
NuttX 12.4.0 96c2707737 Jan 15 2024 10:35:29 risc-v ox64
nsh>
nsh> getprime
Set thread priority to 10
Set thread policy to SCHED_RR
Start thread #0
thread #0 started, looking for primes < 10000, doing 10 run(s)
thread #0 finished, found 1230 primes, last one was 9973
Done
getprime took 0 msec
nsh>
nsh> hello
riscv_exception: EXCEPTION: Store/AMO page fault. MCAUSE: 000000000000000f, EPC: 0000000050208fcc, MTVAL: 0000000080200000
riscv_exception: PANIC!!! Exception = 000000000000000f |
Impact
Users who have used CLOCK_ADJTIME_PERIOD and CLOCK_ADJTIME_SLEWLIMIT
settings should update their configuration. New CLOCK_ADJTIME_PERIOD_MS is
10x the old period value, and new CLOCK_ADJTIME_SLEWLIMIT_PPM is 10000 times
the old slewlimit.
Known Problems In This Release
More Information
How to Download
...
The main "Single Source of Truth" repositories are hosted by the ASF:
- https://gitbox.apache.org/repos/asf?p=incubator-nuttx.git
- https://gitbox.apache.org/repos/asf?p=incubator-nuttx-apps.git
These are synchronized with repositories hosted at GitHub:
- https://github.com/apache/incubator-nuttx/
- https://github.com/apache/incubator-nuttx-apps/
How to Contact the Community
...