TEN MBED OS Course events lab

Files at this revision

API Documentation at this revision

Comitter:
uLipe
Date:
Sun Jan 29 20:40:45 2017 +0000
Commit message:
first

Changed in this revision

.gitignore Show annotated file Show diff for this revision Revisions of this file
README.md Show annotated file Show diff for this revision Revisions of this file
img/uvision.png Show annotated file Show diff for this revision Revisions of this file
main.cpp Show annotated file Show diff for this revision Revisions of this file
mbed-os.lib Show annotated file Show diff for this revision Revisions of this file
diff -r 000000000000 -r 4303da3c75bf .gitignore
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/.gitignore	Sun Jan 29 20:40:45 2017 +0000
@@ -0,0 +1,4 @@
+.build
+.mbed
+projectfiles
+*.py*
diff -r 000000000000 -r 4303da3c75bf README.md
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/README.md	Sun Jan 29 20:40:45 2017 +0000
@@ -0,0 +1,89 @@
+# Getting started with Blinky on mbed OS
+
+This is a very simple guide, reviewing the steps required to get Blinky working on an mbed OS platform.
+
+Please install [mbed CLI](https://github.com/ARMmbed/mbed-cli#installing-mbed-cli).
+
+## Get the example application!
+
+From the command line, import the example:
+
+```
+mbed import mbed-os-example-blinky
+cd mbed-os-example-blinky
+```
+
+### Now compile
+
+Invoke `mbed compile` specifying the name of your platform and your favorite toolchain (`GCC_ARM`, `ARM`, `IAR`). For example, for the ARM Compiler 5:
+
+```
+mbed compile -m K64F -t ARM
+```
+
+Your PC may take a few minutes to compile your code. At the end you should get the following result:
+
+```
+[snip]
++----------------------------+-------+-------+------+
+| Module                     | .text | .data | .bss |
++----------------------------+-------+-------+------+
+| Misc                       | 13939 |    24 | 1372 |
+| core/hal                   | 16993 |    96 |  296 |
+| core/rtos                  |  7384 |    92 | 4204 |
+| features/FEATURE_IPV4      |    80 |     0 |  176 |
+| frameworks/greentea-client |  1830 |    60 |   44 |
+| frameworks/utest           |  2392 |   512 |  292 |
+| Subtotals                  | 42618 |   784 | 6384 |
++----------------------------+-------+-------+------+
+Allocated Heap: unknown
+Allocated Stack: unknown
+Total Static RAM memory (data + bss): 7168 bytes
+Total RAM memory (data + bss + heap + stack): 7168 bytes
+Total Flash memory (text + data + misc): 43402 bytes
+Image: .\.build\K64F\ARM\mbed-os-example-blinky.bin
+```
+
+### Program your board
+
+1. Connect your mbed device to the computer over USB.
+1. Copy the binary file to the mbed device .
+1. Press the reset button to start the program.
+
+You should see the LED of your platform turning on and off.
+
+Congratulations if you managed to complete this test!
+
+## Export the project to Keil MDK and debug your application
+
+From the command line, run the following command:
+
+```
+mbed export -m K64F -i uvision
+```
+
+To debug the application:
+
+1. Start uVision.
+1. Import the uVision project generated earlier.
+1. Compile your application and generate an `.axf` file.
+1. Make sure uVision is configured to debug over CMSIS-DAP (From the Project menu > Options for Target '...' > Debug tab > Use CMSIS-DAP Debugger).
+1. Set breakpoints and start a debug session.
+
+![Image of uVision](img/uvision.png)
+
+## Troubleshooting
+
+1. Make sure `mbed-cli` is working correctly and its version is greater than `0.8.9`
+
+ ```
+ mbed --version
+ ```
+
+ If not, you can update it easily:
+
+ ```
+ pip install mbed-cli --upgrade
+ ```
+
+2. If using Keil MDK, make sure you have a license installed. [MDK-Lite](http://www.keil.com/arm/mdk.asp) has a 32KB restriction on code size.
diff -r 000000000000 -r 4303da3c75bf img/uvision.png
Binary file img/uvision.png has changed
diff -r 000000000000 -r 4303da3c75bf main.cpp
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/main.cpp	Sun Jan 29 20:40:45 2017 +0000
@@ -0,0 +1,66 @@
+/**
+ * @brief first event control program with  MBED OS
+ */
+#include "mbed.h"
+#include "rtos.h"
+#include "mbed_events.h"
+
+/* declares threads for this demo: */
+const size_t a_stk_size = 1024;
+uint8_t a_stk[a_stk_size];
+Thread a_thread(osPriorityNormal, a_stk_size, &a_stk[0]);
+
+/* thread b is used as event loop thread*/
+Thread b_thread;
+
+/* queue used to handle events */
+EventQueue ev_queue(32 * EVENTS_EVENT_SIZE);
+
+/* reserve the debbuger uart to shell interface */
+Serial pc_serial(USBTX,USBRX);
+
+/* allocate HW for button with interrupt */
+InterruptIn sw(SW2);
+
+
+/**
+ * @brief thread a function 
+ */
+static void thread_a(void)
+{
+    int pressed = 0;
+    for(;;) {
+        /* halt thread until a signal is received */
+        a_thread.signal_wait(1, osWaitForever);
+        pressed++;
+        pc_serial.printf("## button press woke up this thread, noof presses: %d !##\n\r", pressed);
+        pc_serial.printf("## now this thread will wait for a new press !##\n\r");        
+    }
+}
+
+
+/**
+ * @brief event callback called from thread context 
+ */
+static void button_callback(void) 
+{
+    /* button callback is used to assert a signal, 
+     * this is the advantage of event loop, signals are not allowed
+     * to use in ISR, but this callback is executed from thread
+     * context
+     */
+     a_thread.signal_set(1);
+}
+
+
+/**
+ * @brief main application loop
+ */
+int main(void) 
+{  
+    pc_serial.baud(115200);
+    a_thread.start(thread_a);
+    b_thread.start(callback(&ev_queue, &EventQueue::dispatch_forever));
+    sw.rise(ev_queue.event(button_callback));
+    return 0;
+}
\ No newline at end of file
diff -r 000000000000 -r 4303da3c75bf mbed-os.lib
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/mbed-os.lib	Sun Jan 29 20:40:45 2017 +0000
@@ -0,0 +1,1 @@
+https://github.com/ARMmbed/mbed-os/#34c1facf42a174f47fdf9002cd8c6bf10ac41744