I'll try to experiment with this, but as I mentioned I'm not sure if it will be
useful for this
case since I need to interact with the OS.
You would perform the time critical portion in the interrupt handler
then schedule the OS interaction via PendSV.
We might want to look at the docs and see if what Greg just explained a few
minutes ago is documented there.
Also worth remembering that this is only an ARMv7-M and ARMv8-M feature
because it depends on (1) having true prioritized interrupts (ARMv6-M
does not) and (2) the ability to execute
On Wed, Oct 28, 2020 at 1:10 PM Matias N. wrote:
> I'm okay with ns jitter. I need to satisfy a 150uS timing response, so
> that is OK.
>
> Outside the context of RTOSs, isn't this just defining your own interrupt
> handler? Maybe
> it should be called "custom interrupt handler"?
>
Well I think
I'm okay with ns jitter. I need to satisfy a 150uS timing response, so that is
OK.
Outside the context of RTOSs, isn't this just defining your own interrupt
handler? Maybe
it should be called "custom interrupt handler"?
I'll try to experiment with this, but as I mentioned I'm not sure if it wil
On 10/28/2020 10:41 AM, Nathan Hartman wrote:
On Tue, Oct 27, 2020 at 10:21 AM Alan Carvalho de Assis
wrote:
Hi Nathan,
I totally agree! Zero Jitter Interrupt is a better name.
We don't have zero latency, we have zero jitter.
BR,
Alan
The latency is pretty close to zero too, because it
On Tue, Oct 27, 2020 at 10:21 AM Alan Carvalho de Assis
wrote:
> Hi Nathan,
>
> I totally agree! Zero Jitter Interrupt is a better name.
>
> We don't have zero latency, we have zero jitter.
>
> BR,
>
> Alan
The latency is pretty close to zero too, because it interrupts whatever
else is happenin
Hi,
Alan and I became interested in this smartwatch, which has an nRF52832 inside
and a nice transflective color LCD.
There's quite a bit of data already on how to hack it and I'm slowly making
progress towards having NuttX run on it.
I just created this page on HaD to document the progress of th
