
This is an example based on mbed-os cellular APIs that demonstrates a TCP or UDP echo transaction with a public echo server.
Revision 16:bf6ed28b4d08, committed 2018-08-08
- Comitter:
- mbed_official
- Date:
- Wed Aug 08 08:30:20 2018 +0100
- Parent:
- 15:e3541a4bca76
- Child:
- 17:25a08e26e894
- Commit message:
- Merge pull request #94 from ARMmbed/update_readme_boardsupports
Updated readme supported boards as a list.
.
Commit copied from https://github.com/ARMmbed/mbed-os-example-cellular
Changed in this revision
README.md | Show annotated file Show diff for this revision Revisions of this file |
--- a/README.md Thu Jul 19 09:30:22 2018 +0100 +++ b/README.md Wed Aug 08 08:30:20 2018 +0100 @@ -90,7 +90,11 @@ The [generic cellular modem driver](https://github.com/ARMmbed/mbed-os/tree/master/features/netsocket/cellular/generic_modem_driver) this application uses was written using only a standard AT command set. It uses PPP with an Mbed-supported external IP stack. These abilities make the driver essentially generic, or nonvendor specific. However, this particular driver is for onboard-modem types. In other words, the modem exists on the Mbed Enabled target as opposed to plug-in modules (shields). For more details, please see our [Mbed OS cellular documentation](https://os.mbed.com/docs/latest/reference/cellular-api.html). -Examples of Mbed Enabled boards with onboard modem chips include [u-blox C027](https://os.mbed.com/platforms/u-blox-C027/) and [MultiTech MTS Dragonfly](https://os.mbed.com/platforms/MTS-Dragonfly/). +Currently supported boards with onboard modem chips are: + +[u-blox C027](https://os.mbed.com/platforms/u-blox-C027/) +[MultiTech MTS Dragonfly](https://os.mbed.com/platforms/MTS-Dragonfly/) + ## Compiling the application