I will develop a device that must be monitored and controlled by remote through an IP connection over Ethernet interface. I'm not an expert of embedded TCP/IP and HTTP server, so I would prefer to separate the main MCU (Cortex-Mx that I already know) from the "remote MCU" (it is a block box at the moment). This separation could be useful if someone will decide to give the remote connection as an option.
The big question is how to design an embedded HTTP server, starting from the hw to the sw. The device is low-cost and the web pages will be simple.
I understood there's Microchip with its ready-to-use solutions (mainly16- and 32-bits PICs), including a free (even for commercial) open-source TCP/IP stack. I think it has a simple HTTP server too.
Many others (Atmel, NXP, ST), with their Cortex-Mx MCUs with integrated Ethernet controller (with external PHY), use lwip free open-source TCP/IP stack. Simple HTTP server implementation is included.
Is there a low-size low-cost embedded Linux solution? Maybe a cheap System On Module (with processor and some volatile and non-volatile memories)?
The link between the "remote CPU" and the "main MCU" could be a simple asyncronous serial link.