Hello,
I am not entirely clear how to participate in the release vote, I will have
to review the linked information again, but I have noticed that the Pico W
is not able to connect to a wireless network because of an issue that was
previously encountered a few releases ago. I am investigating this
Hello world :-)
There goes -1 from me, sorry :-P :-P
1. There are memory leak problems reported that I tried to confirm on
STM32F769. Is it ostest problem only or more general memory management
issue?
before ostest total/used: 483056 / 10112.
after ostest total/used: 483056 / 10200.
2. There ar
This is a +1 from me.
(Assuming that LVGL does not run due to hardware issues / that we won't
stop the release due to external lib problems).
Build on Linux (Fedora 40), using:
arm-none-eabi-gcc --version
arm-none-eabi-gcc (Arm GNU Toolchain 12.2.Rel1 (Build arm-12.24)) 12.2.1
20221205
Copyright
Hi all,
I'm busy trying to get the PX4 running on the ESP32. I think it can be
quite a nice payload controller with the wireless comms it provides. I have
PX4 running, with the hrt driver implemented, and now busy with saving the
parameters to the external flash using the spi flash via mtd. Howeve
Hello Tim,
I have identical problems with nx graphics and previous configurations
known to work.
This is why I suspect a broken board.
Troubleshooting with my current setup is not easy, so I would appreciate it
if anyone can either test this config on this board,
or alternatively provide me anoth
I have had lots of issues with LVGL 9.1 as used in NuttX, but on SAMA5D2. The
framebuffer was being rendered to directly causing tearing. I have also seen
LVGL repo issues relating to STM32, I think. LVGL V9.2 fixes my issues.
Don’t necessarily assume it’s a board fault!
Regards,
Time
> On 4
I am running some tests on actual STM32 hardware for this release.
I am stuck with stm32f746g-disco:lvgl configuration on a Discovery
STM32F746 board, the screen displays garbage.
I start to suspect that this may be an issue with my board, rather than
NuttX.
Does anyone have this board to test th
Issue seen with rv-virt:knsh64 as well. After first ostest run the memory usage
rises by ~500 bytes, but the consequent runs do not increase it further.
Something is allocated once from kheap that is never freed again.
nsh> free
total used freemaxusedmaxfree
