Projet files

Session6/Project_Two_Feedback/.gitignore

@@ -0,0 +1,5 @@
+.pio
+.vscode/.browse.c_cpp.db*
+.vscode/c_cpp_properties.json
+.vscode/launch.json
+.vscode/ipch

Session6/Project_Two_Feedback/.mbedignore

@@ -0,0 +1,83 @@
+/* Bootloader */
+mbed-os/features/FEATURE_BOOTLOADER/*
+
+/* BLE */
+mbed-os/connectivity/drivers/ble/*
+mbed-os/connectivity/FEATURE_BLE/*
+
+/* Cellular */
+mbed-os/connectivity/cellular/*
+mbed-os/connectivity/drivers/cellular/*
+mbed-os/connectivity/netsocket/source/Cellular*.*
+
+/* Device Key */
+mbed-os/drivers/device_key/*
+
+/* Experimental */
+mbed-os/platform/FEATURE_EXPERIMENTAL_API/*
+
+/* FPGA */
+mbed-os/features/frameworks/COMPONENT_FPGA_CI_TEST_SHIELD/*
+
+/* Greentea client */
+mbed-os/features/frameworks/greentea-client/*
+
+/* LORAWAN */
+mbed-os/connectivity/drivers/lora/*
+mbed-os/connectivity/lorawan/*
+
+/* LWIP */
+mbed-os/connectivity/drivers/emac/*
+mbed-os/connectivity/lwipstack/*
+
+/* Mbed-client-cli */
+mbed-os/features/frameworks/mbed-client-cli/*
+
+/* MBED TLS */
+mbed-os/connectivity/drivers/mbedtls/*
+mbed-os/connectivity/mbedtls/*
+
+/* Nanostack */
+mbed-os/connectivity/drivers/emac/*
+mbed-os/connectivity/libraries/mbed-coap/*
+mbed-os/connectivity/libraries/nanostack-libservice/*
+mbed-os/connectivity/libraries/ppp/*
+mbed-os/connectivity/nanostack/*
+
+/* Netsocket */
+mbed-os/connectivity/drivers/emac/*
+mbed-os/connectivity/netsocket/*
+mbed-os/connectivity/libraries/mbed-coap/*
+mbed-os/connectivity/libraries/ppp/*
+
+/* NFC */
+mbed-os/connectivity/drivers/nfc/*
+mbed-os/connectivity/nfc/*
+
+/* RF */
+/*mbed-os/connectivity/drivers/802.15.4_RF/* */
+
+/* Storage */
+mbed-os/storage/filesystem/*
+mbed-os/storage/kvstore/*
+mbed-os/storage/platform/*
+
+/* Tests */
+mbed-os/platform/tests/*
+mbed-os/TEST_APPS/*
+mbed-os/TESTS/*
+mbed-os/UNITTESTS/*
+
+/* Unity */
+mbed-os/features/frameworks/unity/*
+
+/* Utest */
+mbed-os/features/frameworks/utest/*
+
+/* USB */
+mbed-os/drivers/usb/source/*
+mbed-os/hal/usb/source/*
+mbed-os/hal/usb/TARGET_Templates/*
+
+/* WiFi */
+mbed-os/connectivity/drivers/wifi/*

Session6/Project_Two_Feedback/.vscode/extensions.json

@@ -0,0 +1,10 @@
+{
+    // See http://go.microsoft.com/fwlink/?LinkId=827846
+    // for the documentation about the extensions.json format
+    "recommendations": [
+        "platformio.platformio-ide"
+    ],
+    "unwantedRecommendations": [
+        "ms-vscode.cpptools-extension-pack"
+    ]
+}

Session6/Project_Two_Feedback/include/README

@@ -0,0 +1,39 @@
+
+This directory is intended for project header files.
+
+A header file is a file containing C declarations and macro definitions
+to be shared between several project source files. You request the use of a
+header file in your project source file (C, C++, etc) located in `src` folder
+by including it, with the C preprocessing directive `#include'.
+
+```src/main.c
+
+#include "header.h"
+
+int main (void)
+{
+ ...
+}
+```
+
+Including a header file produces the same results as copying the header file
+into each source file that needs it. Such copying would be time-consuming
+and error-prone. With a header file, the related declarations appear
+in only one place. If they need to be changed, they can be changed in one
+place, and programs that include the header file will automatically use the
+new version when next recompiled. The header file eliminates the labor of
+finding and changing all the copies as well as the risk that a failure to
+find one copy will result in inconsistencies within a program.
+
+In C, the usual convention is to give header files names that end with `.h'.
+It is most portable to use only letters, digits, dashes, and underscores in
+header file names, and at most one dot.
+
+Read more about using header files in official GCC documentation:
+
+* Include Syntax
+* Include Operation
+* Once-Only Headers
+* Computed Includes
+
+https://gcc.gnu.org/onlinedocs/cpp/Header-Files.html

Session6/Project_Two_Feedback/lib/README

@@ -0,0 +1,46 @@
+
+This directory is intended for project specific (private) libraries.
+PlatformIO will compile them to static libraries and link into executable file.
+
+The source code of each library should be placed in a an own separate directory
+("lib/your_library_name/[here are source files]").
+
+For example, see a structure of the following two libraries `Foo` and `Bar`:
+
+|--lib
+|  |
+|  |--Bar
+|  |  |--docs
+|  |  |--examples
+|  |  |--src
+|  |     |- Bar.c
+|  |     |- Bar.h
+|  |  |- library.json (optional, custom build options, etc) https://docs.platformio.org/page/librarymanager/config.html
+|  |
+|  |--Foo
+|  |  |- Foo.c
+|  |  |- Foo.h
+|  |
+|  |- README --> THIS FILE
+|
+|- platformio.ini
+|--src
+   |- main.c
+
+and a contents of `src/main.c`:
+```
+#include <Foo.h>
+#include <Bar.h>
+
+int main (void)
+{
+  ...
+}
+
+```
+
+PlatformIO Library Dependency Finder will find automatically dependent
+libraries scanning project source files.
+
+More information about PlatformIO Library Dependency Finder
+- https://docs.platformio.org/page/librarymanager/ldf.html

Session6/Project_Two_Feedback/platformio.ini

@@ -0,0 +1,22 @@
+; PlatformIO Project Configuration File
+;
+;   Build options: build flags, source filter
+;   Upload options: custom upload port, speed and extra flags
+;   Library options: dependencies, extra library storages
+;   Advanced options: extra scripting
+;
+; Please visit documentation for the other options and examples
+; https://docs.platformio.org/page/projectconf.html
+
+; --- UNCOMMENT THIS FOR KPIT BOARDS
+;[env:nucleo_f401re]
+;platform = ststm32
+;board = nucleo_f401re
+;framework = mbed
+
+; ----- DANS DEV BOARD
+[env:nucleo_f746zg]
+platform = ststm32
+board = nucleo_f746zg
+framework = mbed
+

Session6/Project_Two_Feedback/src/main.cpp

@@ -0,0 +1,131 @@
+#include "mbed.h"
+
+int MAX_SPEED = 120;
+
+//Lets have LED blink to show its working
+DigitalOut statusLED(LED1);
+
+// Use Analog 0 to represent speed
+AnalogIn speedSensor(A0);
+AnalogIn selectSensor(A1);
+
+// Struct to hold messages
+typedef struct{
+    int speed;
+    int user_speed;
+    float distance;
+    } sensing_t;
+
+// Our Message Box
+Mail<sensing_t, 4> message_queue;
+
+// For Speed Output
+BusOut driver_led(D5,D7,D10);
+
+
+// Create a queue that can hold a maximum of 32 events
+EventQueue queue(32 * EVENTS_EVENT_SIZE);
+
+// Threads
+Thread event_thread;  //Needs to be global so all elements can post to it
+//Thread for sensing
+Thread sensing_thread; 
+// Thread for Conrol
+Thread control_thread;
+
+void driver_led_feedback(int bitmask){
+  driver_led = bitmask;
+}
+
+
+void handle_sensing(){
+  int speed = 0;
+  int selected_speed = 0;
+
+  while (true){
+    //Read from our speed potentiometer Remeber Value here is 0-1
+    float speed_pot = speedSensor.read();
+    // Convert to speed range
+    int speed = round(speed_pot * MAX_SPEED);
+
+    float select_pot = selectSensor.read();
+    int selected_speed = round(select_pot * MAX_SPEED);
+    //And Print It for the moment
+    queue.call(printf, "Current Speed is %d\n", speed);
+    queue.call(printf, "Selected Speed is %d\n", selected_speed);
+
+    // Ceate a sensor message
+    if (!message_queue.full()){
+      //Block if there is no space
+      sensing_t *sensor_msg = message_queue.try_alloc_for(Kernel::wait_for_u32_forever);
+      sensor_msg->speed = speed;
+      sensor_msg->user_speed = selected_speed;
+      sensor_msg->distance = 0.0;
+
+    //And Send it
+    message_queue.put(sensor_msg);
+    }
+
+    ThisThread::sleep_for(1000ms);
+  }
+}
+
+void handle_control(){
+  int speed_delta;
+
+  while (true){
+    // Get the message in blocking mode
+    queue.call(printf, "Read from Queue\n");
+    sensing_t *the_msg = message_queue.try_get_for(Kernel::wait_for_u32_forever);
+    queue.call(printf, "Read from Queue Complete\n");  
+
+    queue.call(printf, "HANDLE:  Speed %d User %d\n", the_msg->speed, the_msg->user_speed);
+    // Do the processing
+    speed_delta = the_msg->user_speed - the_msg->speed;
+    queue.call(printf,"--> Speed Delta is %d\n", speed_delta);
+
+    if (speed_delta > 5){  //Low Speed
+      queue.call(printf,"--> speed INCREASE needed\n");
+      queue.call(driver_led_feedback, 1); //Bitmask 001 (But Endianess)
+    }
+    else if (speed_delta < -5){ //High Speed
+      queue.call(printf,"--> speed DECREASE needed\n");
+      queue.call(driver_led_feedback, 4); 
+    }
+    else { //Speed OK
+      queue.call(driver_led_feedback, 2);
+      int foo=0;
+    }
+
+    message_queue.free(the_msg); //Important, Free space in the queue
+    // For the moment have a break to avoid thrashig processor
+    ThisThread::sleep_for(1000ms);
+
+    //Release the queue
+
+
+  }
+}
+
+
+int main() {
+
+  // put your setup code here, to run once:
+
+  // Start the Event Thread
+  event_thread.start(callback(&queue, &EventQueue::dispatch_forever));
+  sensing_thread.start(handle_sensing);
+  control_thread.start(handle_control);
+
+  while(1) {
+    // put your main code here, to run repeatedly:
+
+
+    // Blink to let us know things are working
+    statusLED = !statusLED;
+
+    // Temporary Print Callbak so we we know event queue is working
+    queue.call(printf, "Tick\n"); 
+    ThisThread::sleep_for(5000ms);
+  }
+}

Session6/Project_Two_Feedback/test/README

@@ -0,0 +1,11 @@
+
+This directory is intended for PlatformIO Test Runner and project tests.
+
+Unit Testing is a software testing method by which individual units of
+source code, sets of one or more MCU program modules together with associated
+control data, usage procedures, and operating procedures, are tested to
+determine whether they are fit for use. Unit testing finds problems early
+in the development cycle.
+
+More information about PlatformIO Unit Testing:
+- https://docs.platformio.org/en/latest/advanced/unit-testing/index.html