Multiple interrupts as handled by libraries right know are generating
incontrolled jitter to any timing sensitive applications. Unfortunately
almost nothing can be doneexcept grouping everything in one interrupt
carefully controlled.
On Sun 20 Feb 2022, 5:27 PM Rob CJ Hi Kiste,
>
> Thanks
Hi Kiste,
Thanks for your reply. I thought that it would work when disabling the
interrupt but I did not think of what you said about variable reuse. That could
have been the problem. The current I2C procedures wait for a transfer to be
completed and the PIC is always the master so that should
Hi Rob,
it is possible to call a procedure from both the main program and from an
interrupt alternately, but I would try to avoid that, it's... I'd call it
dangerous.
As jal is not reentrant, you have to make absolutely sure, that no single part
of any procedure is running twice in any case.
Hello all,
Some time ago I made a library for the clock IC DS3231. This library is
part of Jallib release 1.7.0.
This IC has an I2C interface and is capable of handling two alarms. When an
alarm is activated an interrupt is generated.
Reading the alarm flag from the IC also uses - of course-
