> No directory at /home/micha/nuttxspace/nuttx//src
It looks like you are trying to use a custom board but didn't set the
options and the path correctly.
On Thu, Jun 16, 2022 at 8:43 AM wrote:
>
> Dear all,
>
> I am new to Nuttx, and I try to port Nuttx to our ESP32 board. I
> followed this arti
>From your .config file:
CONFIG_ARCH_BOARD_CUSTOM_NAME=""
CONFIG_ARCH_BOARD_CUSTOM_DIR=""
Please set these to their correct values.
On Thu, Jun 16, 2022 at 9:43 AM Abdelatif Guettouche
wrote:
>
> > No directory at /home/micha/nuttxspace/nuttx//src
>
> It looks like you are trying to use a custo
Alternately you can create a new board, it is not difficult.
You can start copying some board from boards/xtensa/esp32/ i.e.:
$ cd boards/xtensa/esp32/
$ cp -a esp32-devkitc esp32-new-board-name
Then inside your new board src/ rename esp32-devkitc.h to your
esp32-new-board-name.h and update all
Hi Alan,
thank you, I managed to create a new board, and can compile it now. I am
diving into the code, and all the possibilities of Nuttx.
Am 2022-06-16 14:46, schrieb Alan Carvalho de Assis:
Alternately you can create a new board, it is not difficult.
You can start copying some board fro
Dear Abdelatif,
I finally managed to make a new board definition, and made this to
compile well. Thanks for your support.
Am 2022-06-16 09:45, schrieb Abdelatif Guettouche:
From your .config file:
CONFIG_ARCH_BOARD_CUSTOM_NAME=""
CONFIG_ARCH_BOARD_CUSTOM_DIR=""
Please set these to their cor
Alan,
If you still have the config, that would be helpful!
I have tried going into the device's low-power modes both using the
tickless OS, and using the normal scheduler.
When I use the debugger, I can see that the line of code in stm32_idle.c
that puts the device into the low-power modes is bein
Ok, just sent to you private email.
BR,
Alan
On 6/16/22, Jesse Jensen wrote:
> Alan,
>
> If you still have the config, that would be helpful!
> I have tried going into the device's low-power modes both using the
> tickless OS, and using the normal scheduler.
> When I use the debugger, I can see
