Hello all,
My issue is related to testing the SIGKILL in Nuttx and not making it work
correctly.
Description:
=
I am using a ESP32 DevKitC Board using default NSH configuration.
1) Enabled CONFIG_SIG_DEFAULT=y and CONFIG_SCHED_HAVE_PARENT=y
2) After starting the board, type "sh" + 3 tim
I think a benefit from renaming many of those "up_something" to
"stm32_something", "esp32_something", etc is now it is easy for
software find the right function.
I think many IDEs cannot handle functions search correctly for NuttX
because they don't have heuristics to know that IF I'm searching a
Yes, I think seamless Nordic BLE support is important for NuttX.
I will try to release some time for this, I´ve got nrf52832, nrf52833 and
nrf52840 boards/products at my disposal.
Med vänlig hälsning
Erik Englund
Innoware Development AB
Hyttvägen 13
73338 SALA
Org.nr. 556790-2977
www.innoware.s
I sill wonder what is the purpose of this variable rename. Sorry to say,
but it just looks cosmetic while critically breaking everything that was
made before, and this kind of thing is a nightmare for migration when
you cant follow the project day to day. Boards can be external to the
project,
Boom, that was the extrastuff. The board now boots. We're going to run a
lot of functional tests to make sure everything is okay, but I dont have
this strange hardfault at boot.
Thank you.
I did not find this page despite searching through a lot of
documentation, mainly the "official" ReadThe
Code was working perfectly before the nuttx upgrade so I tend to think
that stack is sufficient.
Sebastien
Le 26/05/2021 à 21:49, David Sidrane a écrit :
Hi Sebastien,
Stack crashing into heap?
Have you upped the stack sizes across the board?
David
-Original Message-
From: Sebasti
