Hi,
Theoretically, this is possible. But only for a single netconn. And the
implementation is probably not as easy as you think it is: you have to ensure
that timers are running, i.e. what the tcpip_thread does in an OS has to be
executed somewhere. Plus there are certain netconn calls that can make the
calling task block. These need to be either handled by implementing a delay or
you need to abort such calls (e.g. only allow nonblocking RX) but then the
question is: why do you need the netconn API without an OS? It all depends on
what else your system should do...
Regards,
Simon
Am 9. Dezember 2025 09:56:24 MEZ schrieb "轻风" <[email protected]>:
>Hello everyone，
>I am using the Raw API of LWIP2.1.2. I hope to use a sequential API to
>complete my task. The Netconn API is a sequential API, but it requires support
>from the RTOS system. May I ask if it is possible to use the Netconn API on
>non RTOS operating systems? I plan to set the semaphore of the operating
>system simulation layer to an empty implementation. If possible, what other
>modifications do I need to make?
>Thank you！
_______________________________________________
lwip-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/lwip-users
