stm32n6570-dk lwip support

[3mika3]

Hello,

Does the stm32n6570-dk has no support for lwip?

[ELABI.1]

Hi @3mika3,

First of all, please take a look at this article: How to write your question to maximize your chances of finding a solution.

LWIP is not included in the STM32CubeN6 firmware. However, the Azure NetXDuo networking stack is supported for the N6 series. You can find examples of its implementation our Cube firmware STM32CubeN6.

If you specifically want to use LWIP, you can port it yourself, and there is also a ported version available for this series on ST’s GitHub. Here is the link to the LWIP MCU Middleware.

Thanks.

ELABI.1

[STackPointer64]

Hello @3mika3,

Regarding support for LwIP on STM32N6, although it is no longer available in STM32CubeMX—having been replaced by NetXDuo—it is still supported and can be manually integrated into your project. A dedicated GitHub repository (first link) provides implementations for classic core middleware such as LwIP. There, you can find a ready-to-use example for the NUCLEO-N657X0-Q board, which you can adapt for the STM32N6570-Disco. Additionally, a modified implementation is available in the second repository for your convenience.

• stm32n6-classic-coremw-apps 
• LwIP_TCP_Echo_Server for STM32N6570-DK

Please let me know if you need further assistance. If this answers your question, kindly mark it as the accepted solution. Thank you!

Best regards,

[3mika3]

Thank you for the recommendations. The issue is that LwIP example is only using the memory of the bootloader....
I changed the Linkerscript so that it will use the bigger RAM, but I integrated Wolfssl and it can not allocate memory, if I do this:

g_tls.ssl = wolfSSL_new(g_ctx);

[3mika3]

I resolved the issue, was a problem with RNG, but I have the issue now, that Wolfssl_connect returns -1 
and 32 from wolfssl_get_error