On Wed, Jul 9, 2025 at 12:38 PM Gregory Nutt wrote:
> The time delay that you are concerned about is simply the context
> switching time and this is necessary to instantiate the thread's stack and
> other operating context. As a general rule this restoration of thread
> context cannot really be
The time delay that you are concerned about is simply the context switching
time and this is necessary to instantiate the thread's stack and other
operating context. As a general rule this restoration of thread context cannot
really be omitted.
From: Gregory Nut
In general, callbacks from the OS to application code is not possible in NuttX.
That will not work at all in PROTECTED or KERNAL builds due to address space
conflicts between the OS and the application. In some FLAT build cases it
could work, provided that there is no dependency on the properti
Hi Sebastien,
For now it will depend on GPIO IRQ, just like the
digital joystick (ref.: lpc17_40_djoystick.c)
But probably someone could extend it in the future to support polling mode.
BR,
Alan
On Wed, Jul 9, 2025 at 11:22 AM Sebastien Lorquet
wrote:
> Hello,
>
> Can this be wired in the GP
Hi Tomek,
I think the Single Button Actions will be a good name (maybe in future it
could have a dual click function, like used in mouses).
Yes, the idea is to use some generic system timer to get it working on all
MCUs.
BR,
Alan
On Wed, Jul 9, 2025 at 11:03 AM Tomek CEDRO wrote:
> Hey there
I believe the GPIO system does in fact trigger a signal event. I've used
this for a project before.
However, I think it would be nice to be able to register a callback instead
of blocking for a signal, since that introduced A LOT more delay. This
would probably need to be done with the low priorit
Hello,
Can this be wired in the GPIO system?
There are gpio interrupts iirc. these could be used to trigger a signal.
If a system does not have gpio interrupts, polling can do the same trick.
Just my two cents!
Sebastien
On 09/07/2025 15:16, Alan C. Assis wrote:
Hi Everyone,
Some years ag
Hey there Alan :-)
Very cool and useful idea! I did something like this long time ago in
pure assembly and C but it was returning press time and based on that
actions were performed by the handling routine.
In NuttX this would work on various platforms where different
capabilities (i.e. irq, time
Hi Everyone,
Some years ago a customer asked me to develop a project with NuttX for this
board that used a small OLED display and a single button.
That button should be used to navigate in the menu, as a side note:
initially he suggested: quick press and release will work as a ENTER and
long press
On 2025-07-09 01:20, Tomek CEDRO wrote:
Thank you Kerogit :-)
How about ARCH_HAVE_AVR_FLMAP? This would align with existing
nomenclature and enable easy filtering / sorting?
Thanks :-)
Tomek
Xiaoxiang781216 was faster on GitHub so I will be echoing a bit - I
don't think ARCH_HAVE is a good
10 matches
Mail list logo
