Simple Webserver example for wiznet W5500 (SPI Ethernet chip) mbed OS 5 - HTTP 1.1 and multi-threaded
Dependencies: W5500Interface easy-connect mbed-http
Fork of http-webserver-example by
mbed-os-example-http-server
This application demonstrates how to run an HTTP server on an mbed OS 5 device & WIZnet W5500 Ethernet components.
Request parsing is done through [nodejs/http-parser](https://github.com/nodejs/http-parser).
To build
- Open ``mbed_app.json`` and change the `network-interface` option to your connectivity method ([more info](https://github.com/ARMmbed/easy-connect)).
- Build the project in the online compiler or using mbed CLI.
- Flash the project to your development board.
- Attach a serial monitor to your board to see the debug messages.
Tested on
- NUCLEO_F411RE with W5500 Ethernet shield.
- For W5500, you need the following libraries.
Import libraryW5500Interface
W5500 driver for mbed OS 5
Import libraryeasy-connect
Modified version of easy-connect for W5500 Ethernet components
But every networking stack that supports the [mbed OS 5 NetworkInterface API](https://docs.mbed.com/docs/mbed-os-api-reference/en/latest/APIs/communication/network_sockets/) should work.
Test Result
README.md@0:41f820ea137a, 2017-07-31 (annotated)
- Committer:
- Jan Jongboom
- Date:
- Mon Jul 31 15:41:22 2017 +0200
- Revision:
- 0:41f820ea137a
- Child:
- 3:954c7d381623
Initial release
Who changed what in which revision?
User | Revision | Line number | New contents of line |
---|---|---|---|
Jan Jongboom |
0:41f820ea137a | 1 | # mbed-os-example-http-server |
Jan Jongboom |
0:41f820ea137a | 2 | |
Jan Jongboom |
0:41f820ea137a | 3 | This application demonstrates how to run an HTTP server on an mbed OS 5 device. |
Jan Jongboom |
0:41f820ea137a | 4 | |
Jan Jongboom |
0:41f820ea137a | 5 | Request parsing is done through [nodejs/http-parser](https://github.com/nodejs/http-parser). |
Jan Jongboom |
0:41f820ea137a | 6 | |
Jan Jongboom |
0:41f820ea137a | 7 | ## To build |
Jan Jongboom |
0:41f820ea137a | 8 | |
Jan Jongboom |
0:41f820ea137a | 9 | 1. Open ``mbed_app.json`` and change the `network-interface` option to your connectivity method ([more info](https://github.com/ARMmbed/easy-connect)). |
Jan Jongboom |
0:41f820ea137a | 10 | 2. Build the project in the online compiler or using mbed CLI. |
Jan Jongboom |
0:41f820ea137a | 11 | 3. Flash the project to your development board. |
Jan Jongboom |
0:41f820ea137a | 12 | 4. Attach a serial monitor to your board to see the debug messages. |
Jan Jongboom |
0:41f820ea137a | 13 | |
Jan Jongboom |
0:41f820ea137a | 14 | ## Tested on |
Jan Jongboom |
0:41f820ea137a | 15 | |
Jan Jongboom |
0:41f820ea137a | 16 | * K64F with Ethernet. |
Jan Jongboom |
0:41f820ea137a | 17 | * NUCLEO_F411RE with ESP8266. |
Jan Jongboom |
0:41f820ea137a | 18 | * For ESP8266, you need [this patch](https://github.com/ARMmbed/esp8266-driver/pull/41). |
Jan Jongboom |
0:41f820ea137a | 19 | |
Jan Jongboom |
0:41f820ea137a | 20 | But every networking stack that supports the [mbed OS 5 NetworkInterface API](https://docs.mbed.com/docs/mbed-os-api-reference/en/latest/APIs/communication/network_sockets/) should work. |