Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.arch.embedded > #25817

Re: Suggestions on solutions to develop an embedded web server over Ethernet interface

From Don Y <blockedofcourse@foo.invalid>
Newsgroups comp.arch.embedded
Subject Re: Suggestions on solutions to develop an embedded web server over Ethernet interface
Date 2017-02-10 12:59 -0700
Organization A noiseless patient Spider
Message-ID <o7l5v0$6n9$1@dont-email.me> (permalink)
References <o7kt2p$36s$1@dont-email.me>

Show all headers | View raw


On 2/10/2017 10:27 AM, pozz wrote:
> 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

I seem to have missed the step where you jumped from "IP" to "TCP/IP & HTTPd".

> 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 (mainly 16- 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.

Back to comp.arch.embedded | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Suggestions on solutions to develop an embedded web server over Ethernet interface pozz <pozzugno@gmail.com> - 2017-02-10 18:27 +0100
  Re: Suggestions on solutions to develop an embedded web server over Ethernet interface Theo Markettos <theom+news@chiark.greenend.org.uk> - 2017-02-10 18:28 +0000
    Re: Suggestions on solutions to develop an embedded web server over Ethernet interface pozz <pozzugno@gmail.com> - 2017-02-13 00:36 +0100
    Re: Suggestions on solutions to develop an embedded web server over Ethernet interface pozz <pozzugno@gmail.com> - 2017-02-13 00:36 +0100
      Re: Suggestions on solutions to develop an embedded web server over Ethernet interface Theo Markettos <theom+news@chiark.greenend.org.uk> - 2017-02-13 08:04 +0000
  Re: Suggestions on solutions to develop an embedded web server over Ethernet interface Joe Chisolm <jchisolm6@earthlink.net> - 2017-02-10 13:52 -0600
    Re: Suggestions on solutions to develop an embedded web server over Ethernet interface Uwe Bonnes <bon@hertz.ikp.physik.tu-darmstadt.de> - 2017-02-13 11:43 +0000
  Re: Suggestions on solutions to develop an embedded web server over Ethernet interface Don Y <blockedofcourse@foo.invalid> - 2017-02-10 12:59 -0700
  Re: Suggestions on solutions to develop an embedded web server over Ethernet interface Tim Wescott <seemywebsite@myfooter.really> - 2017-02-10 14:13 -0600
  Re: Suggestions on solutions to develop an embedded web server over Ethernet interface aquaverde <svaquaverde@yahoo.com> - 2017-02-10 17:09 -0800
  Re: Suggestions on solutions to develop an embedded web server over Ethernet interface Paul Rubin <no.email@nospam.invalid> - 2017-02-13 01:02 -0800

csiph-web