The example above this in the documentation states
```
// semantically, the monotonic timer is frozen at time "zero" during `init`
// NOTE do *not* call `Instant::now` in this context; it will return a nonsense value
let now = cx.start; // the start time of the system
```
It results in weird scheduling issues, but still eventually works. `cx.start` is much more reliable.
Relates to https://github.com/rtfm-rs/cortex-m-rtfm/issues/196
306: Retain cfg-attributes on resources r=korken89 a=AfoHT
When rust 1.43 lands as stable this will resolve#301 and allow for the kind of conditional compilation exemplified in the issue.
Tested on beta and nightly.
Co-authored-by: Henrik Tjäder <henrik@tjaders.com>
307: Use build.rs for conditional compilation r=korken89 a=AfoHT
Extend the current test suite to allow for running tests on newer rustc-versions than current MSRV.
Required by #306 to add special tests for future MSRV.
To exclude an example from the regular non-nightly testing:
```
#![no_main]
#![no_std]
#[cfg(rustc_is_nightly)]
mod example {
use panic_halt as _;
#[rtfm::app(device = lm3s6965)]
const APP: () = {
<more code>
}
}
```
Co-authored-by: Henrik Tjäder <henrik@tjaders.com>
305: Updated dead links to SLEEPONEXIT reference on developer.arm.com r=korken89 a=FluenTech
Co-authored-by: Peter Taylor <40178570+FluenTech@users.noreply.github.com>
284: book, Russian lang: fix "idle not defined" typo r=burbull a=kolen
Fix typo in Russian translation of book, was "When idle function is declared", should be "When no idle function is declared"
"не" means "not".
Corresponding text in English:
```markdown
When no `idle` function is declared, the runtime sets the [SLEEPONEXIT] bit and
then sends the microcontroller to sleep after running `init`.
```
Co-authored-by: Konstantin Mochalov <incredible.angst@gmail.com>
283: Include DWT enable in migration guide r=korken89 a=MabezDev
Makes note of the fact the DWT has to be enabled manually in rtfm 0.5.0; an easy one to miss considering debuggers generally enable the DWT automatically.
Co-authored-by: Scott Mabin <scott@mabez.dev>
277: TimerQueue.dequeue: don't set SYST reload to 0 r=korken89 a=mpasternacki
ARM Architecture Reference Manual says: "Setting SYST_RVR to zero has the effect of disabling the SysTick counter independently of the counter enable bit."
If Monotonic's ratio is less than one, the timeout calculations
can compute zero if next task is scheduled after current instant, but
before next timer tick. This results in disabling SYST and freezing the
timer queue.
The division by ratio's denominator rounds downward and the dequeue
condition is `if instant < now`. If ratio is small enough, this results
in unnecessary interrupts:
Let's say `instant - now` is 99 and ratio is 1/25. Then, `dur` will
equal 3 and the next tick will happen at `now + 75`. In the next
interrupt, `instant > now` and additional tick needs to be scheduled
(which doesn't happen, because now `instant - now` is less than 25, so
reload will be set to 0 and timer queue will stop). Adding one to
computed duration will prevent both freezing and additional interrupts.
When ratio is 1 or close, timer queue code overhead will prevent this
from happening. I am working with a chip where CPU is clocked at 600MHz
and SysTick is 100kHz and the freeze happens quite often.
Co-authored-by: Maciej Pasternacki <maciej@3ofcoins.net>
ARM Architecture Reference Manual says: "Setting SYST_RVR to zero has the effect of disabling the SysTick counter independently of the counter enable bit."
If Monotonic's ratio is less than one, the timeout calculations
can compute zero if next task is scheduled after current instant, but
before next timer tick. This results in disabling SYST and freezing the
timer queue.
278: Cyccnt r=texitoi a=perlindgren
The subtractions in `elapsed` and `duration` may cause an overflow panic in debug mode. This is solved by using wrapping arithmetics.
Co-authored-by: Per Lindgren <per.lindgren@ltu.se>
275: fix CI r=perlindgren a=japaric
after caching was enabled binary install through the trust/install.sh script
stopped working (due to permissions?). This updates crate installation to use
`cargo-install` iff the requested version of a crate is not already installed
Co-authored-by: Jorge Aparicio <jorge@japaric.io>
after caching was enabled binary install through the trust/install.sh script
stopped working (due to permissions?). This updates crate installation to use
`cargo-install` iff the requested version of a crate is not already installed
268: CI: replace compiletest-rs with trybuild r=japaric a=japaric
We use compiletest to run compile-fail tests but compiletest depends on compiler
internals so it breaks every now and then and requires nightly. With trybuild we
can also run compile-fail tests but it works on stable and it already has
reached version 1.0
270: Added struct de-structure-ing example in tips & tricks r=japaric a=korken89
As per last meeting, a bare-bones added that we can improve
Co-authored-by: Jorge Aparicio <jorge@japaric.io>
Co-authored-by: Emil Fresk <emil.fresk@gmail.com>
this version is more or less fixed so new releases of Rust (stable or nightly
channel) are unlikely to break to build due to changes in diagnostic messages
We use compiletest to run compile-fail tests but compiletest depends on compiler
internals so it breaks every now and then and requires nightly. With trybuild we
can also run compile-fail tests but it works on stable and it already has
reached version 1.0
266: CI: build 0.4 docs from the v0.4.x branch r=korken89 a=japaric
instead of using a specific tag; this way documentation changes done to the
v0.4.x branch will show up on the site as soon as they land -- right now they
require publishing a new v0.4.x release on crates.io
Co-authored-by: Jorge Aparicio <jorge@japaric.io>
