Hi guys,
This is buildbot speaking. I have finished a build of jallib-standard on jallib.
Buildslave for this Build: sebbot
Build Reason:
Build Source Stamp: HEAD
Blamelist: rob.jansen
Build succeeded!
Logs are attached.
sincerely,
-The Buildbot
--
You received this message because you are
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
Branch: refs/heads/master
Home: https://github.com/jallib/jallib
Commit: 66bb46a38b379a361d5abfff01c996463d984bc6
https://github.com/jallib/jallib/commit/66bb46a38b379a361d5abfff01c996463d984bc6
Author: Rob Jansen <12682653+robjanse...@users.noreply.github.com>
Date:
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.
