This does not seem like a technical issue but rather awkward
usage/naming that is prone to misuse.
Yes, free() should be called to release the memory allocated by strdup.
But applications cannot use the kernel heap and, for reasons of
protection, the kernel should not store anything in the use
So this post has been triggered by an issue I have just had using strdup in the
OS components of a protected mode build.
For clarity I will be using the term OS for the kernel part of the build and
application/app for the user part of the build.
The TLDR; is this design question:
Do we expect
Hello,
I have submitted issues with usage of GPIO and UART drivers with NuttX for
ESP32 in the apache/incubator-nuttx git repo. Please find the links to those
below
GPIO: https://github.com/apache/incubator-nuttx/issues/7152
UART: https://github.com/apache/incubator-nuttx/issues/7150
It would
Hello world :-)
I am slowly getting back to NuttX :-)
On FreeBSD all local packages are installed under /usr/local prefix
that does not seem to be added by tools/configure (or other) and this
results in missing includes build error, for instance:
CC: sim/up_x11framebuffer.c
sim/up_x11framebuff
Hi Prelude,
I think imxrt1176 is not available yet, did you get it?
Probably the peripherals will be the same.
BTW: did you test the W5500?
BR,
Alan
On Wednesday, September 21, 2022, prelude wrote:
> I want to ask my friends, is there anyone who supports imxrt1176 on
> Nuttx？At present, the
I want to ask my friends, is there anyone who supports imxrt1176 on Nuttx？At
present, there are only imxrt1020, imxrt1050, imxrt1060 and imxrt1064 in the
Nuttx code.
This article explains how we run the BASIC Interpreter on NuttX, to
experiment with the LEDs and GPIOs on Pine64's PinePhone...
https://lupyuen.github.io/articles/pio
Lup
