Example program running mbedClient over UbloxATCellularInterface or OnboardCellularInterface for the C030 platform.

Dependencies:   ublox-cellular-base ublox-at-cellular-interface ublox-ppp-cellular-interface ublox-at-cellular-interface-n2xx ublox-cellular-base-n2xx

Revision:
5:d81fdd2c89f2
Parent:
3:5b8623c17906
Child:
8:f341bfe37797
--- a/main.cpp	Thu Jun 15 17:34:15 2017 +0100
+++ b/main.cpp	Mon Jun 19 09:57:23 2017 +0100
@@ -32,9 +32,8 @@
 // If you wish to use LWIP and the PPP cellular interface, select
 // the line UbloxPPPCellularInterface, otherwise select the line
 // UbloxATCellularInterface.  Using the AT cellular interface does not
-// require LWIP and hence uses less RAM (significant on C027).  It also
-// allows other AT command operations (e.g. sending an SMS) to happen
-// during a data transfer.
+// require LWIP and hence uses less RAM.  It also allows other AT command
+// operations (e.g. sending an SMS) to happen during a data transfer.
 #define INTERFACE_CLASS  UbloxATCellularInterface
 //#define INTERFACE_CLASS  UbloxPPPCellularInterface
 
@@ -133,14 +132,17 @@
     pulseEvent();
 }
 
-/* This example program for the u-blox C030 and C027 boards instantiates
- * the mbedClient and runs it over a UbloxATCellularInterface connection to
+/* This example program for the u-blox C030 board instantiates mbedClient
+ * and runs it over a UbloxATCellularInterface or a UbloxPPPCellularInterface to
  * the mbed connector.
  * Progress may be monitored with a serial terminal running at 9600 baud.
  * The LED on the C030 board will turn green when this program is
  * operating correctly, pulse blue when an mbedClient operation is completed
  * and turn red if there is a failure.
  *
+ * Note: mbedClient malloc's around 34 kbytes of RAM, more than is available on
+ * the C027 platform, hence this example will not run on the C027 platform.
+ *
  * IMPORTANT to use this example you must first register with the mbed Connector:
  *
  * https://connector.mbed.com/