4 ms·
These are the same reasons you should opt for an SoC that can run Linux over a "wifi microcontroller" if your embedded project needs networking and has the cost
by ohazi 6y ago
These are the same reasons you should opt for an SoC that can run Linux over a "wifi microcontroller" if your embedded project needs networking and has the cost and power budget to support it. The Linux community has spent the last 25 years finding and fixing bugs that you absolutely will encounter if you use the Microchip or Espressif or SiLabs networking stack.
- monocasa 6y agoEh, those almost always use lwip, which is probably the only stack that can rival the Linux and BSD stacks in man hours spent fixing bugs and adding support for different envs. I don't think any of those companies are writing their own stacks.
- Matthias247 6y agolwip is indeed decent. At least as decent as all the C based work is which lacks any decent unit-tests to make sure it keeps working (the linux kernel is not better). The problem with those embedded solutions is often not lwip but that the integration and requirements between lwip, the OS and it's task system (e.g. FreeRTOS), and the actual hardware is not properly understood. Which can e.g. lead to function calls being made from the wrong context - which could work in the beginning - might lead to weird errors later on. For this reason I would also recommend people who want to build connected devices to build on top of a more mature and streamlined stack - like the Linux TCP/IP stack plus associated drivers.