Srdjan Veljkovic
Pubnub demo for AT&T IoT Starter Kit. Functionally similar to the Flow demo.
Dependencies: FXOS8700CQ MODSERIAL mbed
Pubnub demo for AT&T IoT Starter Kit
This demo is functionally similar to the Flow demo, so you can find general information here: https://developer.mbed.org/users/JMF/code/Avnet_ATT_Cellular_IOT/.
The only difference is that we use Pubnub to publish the measurements and subscribe to receiving the instructions to set the LED.
Settings
Pubnub related settings are:
Pubnub settings in `config_me.h`
PUBNUB_SUBSCRIBE_KEY PUBNUB_PUBLISH_KEY PUBNUB_CHANNEL
All are documented in their respective comments.
Pubnub context class
Similar to Pubnub SDKs, we provide a Pubnub context class. It is defined in pubnub.h header file and implemented in pubnub.cpp.
It provides only the fundamental "publish" and "subscribe" methods. They are documented in the header file.
This class is reusable in other code (it is not specific to this demo), it has a very narrow interface to the AT&T IoT cellular modem code. For example of use, you can look at the main() (in main.c).
Sample of published data
Published message w/measurement data
{"serial":"vstarterkit001","temp":89.61,"humidity":35,"accelX":0.97,"accelY":0.013,"accelZ":-0.038}
Don't worry, nobody got burnt, the temperature is in degrees Fahrenheit. :)
Publish a message (from, say, the Pubnub console http://pubnub.com/console) of the form {"LED":<name-of-the-color>} on the channel that this demo listens to (default is hello_world) to turn the LED to that color on the Starter Kit:
Turn LED to red
{"LED":"Red"}
Turn LED to green
{"LED":"Green"}
Turn LED to blue
{"LED":"Blue"}
Diff: itm_output.cpp
- Revision:
- 60:2aa16fd02dfd
- Child:
- 68:6e311c747045
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/itm_output.cpp Sat Jul 30 16:26:22 2016 +0000
@@ -0,0 +1,74 @@
+//Used for ULINK output only
+//
+
+/* ITM registers */
+#define ITM_PORT0_U8 (*((volatile unsigned int *)0xE0000000))
+#define ITM_PORT0_U32 (*((volatile unsigned long *)0xE0000000))
+#define ITM_TER (*((volatile unsigned long *)0xE0000E00))
+#define ITM_TCR (*((volatile unsigned long *)0xE0000E80))
+
+#define ITM_TCR_ITMENA_Msk (1UL << 0)
+
+/*!< Value identifying \ref ITM_RxBuffer is ready for next character. */
+#define ITM_RXBUFFER_EMPTY 0x5AA55AA5
+
+/*!< Variable to receive characters. */
+extern
+volatile int ITM_RxBuffer;
+volatile int ITM_RxBuffer = ITM_RXBUFFER_EMPTY;
+
+/** \brief ITM Send Character
+
+ The function transmits a character via the ITM channel 0, and
+ \li Just returns when no debugger is connected that has booked the output.
+ \li Is blocking when a debugger is connected, but the previous character
+ sent has not been transmitted.
+
+ \param [in] ch Character to transmit.
+
+ \returns Character to transmit.
+ */
+int ITM_putc (int ch) {
+ if ((ITM_TCR & ITM_TCR_ITMENA_Msk) && /* ITM enabled */
+ (ITM_TER & (1UL << 0) )) { /* ITM Port #0 enabled */
+ while (ITM_PORT0_U32 == 0);
+ ITM_PORT0_U8 = (int)ch;
+ }
+ return (ch);
+}
+
+/** \brief ITM Receive Character
+
+ The function inputs a character via the external variable \ref ITM_RxBuffer.
+ This variable is monitored and altered by the debugger to provide input.
+
+ \return Received character.
+ \return -1 No character pending.
+ */
+int ITM_getc (void) {
+ int ch = -1; /* no character available */
+
+ if (ITM_RxBuffer != ITM_RXBUFFER_EMPTY) {
+ ch = ITM_RxBuffer;
+ ITM_RxBuffer = ITM_RXBUFFER_EMPTY; /* ready for next character */
+ }
+
+ return (ch);
+}
+
+/** \brief ITM send string
+
+ The function sends a null terminated string via the external variable \ref ITM_RxBuffer.
+ This variable is monitored and altered by the debugger to provide input.
+
+ \return Received character.
+ \return -1 No character pending.
+ */
+int ITM_puts (char * str) {
+ int i=0;
+
+ while(str[i])
+ ITM_putc(str[i++]);
+ return i;
+}
+