On Fri, Apr 26, 2024 at 07:58:00PM +0200, Tomek CEDRO wrote:
> Can you please elaborate more on why / how system hangs?
Nothing I can easily answer.
I have a complex codebase for a custom SAM4X board that I ported over to
a custom ESP32 board.
As part of that there is running HTTP code that I
Can you please elaborate more on why / how system hangs?
Do you know the cause?
Does that happen only with your firmware or clean examples too?
How often hangs happen?
Do you get any sort of traces or device just gets unresponsive?
What NuttX version do you work on?
I also experience random
On Fri, Apr 26, 2024 at 11:01:20AM -0300, Alan C. Assis wrote:
> Yes, Abdelatif is right, I think only Bluetooth requires a reserved area of
> the RAM.
>
> For WiFi the driver itself on the NuttX kernel is enough.
>
> Currently there is no support to direct boot on ESP32 (to avoid using the
>
Yes, Abdelatif is right, I think only Bluetooth requires a reserved area of
the RAM.
For WiFi the driver itself on the NuttX kernel is enough.
Currently there is no support to direct boot on ESP32 (to avoid using the
bootloader), only ESP32-C3 and newer chips have support for it.
Best Regards,
200KB should be the remaining SRAM size.
BLE uses 32KB of SRAM. I don't remember Wifi having a fixed carevout in
SRAM. Then there are other areas used by the ROM bootloader that can be
revoked once the system has fully booted.
On Fri, Apr 26, 2024 at 2:22 PM Nathan Hartman
wrote:
> I
I recommend to add a comment there, to explain that although the board has
320KB in total, ~200KB is used for WiFi and BLE.
On Thu, Apr 25, 2024 at 8:36 PM Alan C. Assis wrote:
> Hi Bernd,
>
> You can use 320KB only if you don't need to use WiFi and BLE.
>
> The memory is used but the WiFi/BLE
If I remember correctly CONFIG_RAM_SIZE is not used for ESP32. And it was
supposed to be set to 0 to avoid confusion.
For ESP32 only the heap is a bit messed up. Many agents poke holes inside
the SRAM space for their own use. You can check
