Fixed header input and typing

README.md

@@ -1,4 +1,4 @@
-# dwm1001-keil-examples
+# FORK OF dwm1001-examples
 ## Overview
 
 This project contains C simple examples for DWM1001 hardware and its derivatives, such as the DWM1001-DEV board.
@@ -12,7 +12,7 @@ The C simple examples allow user to discover the key functionalities offered by
 
 The project is built as follow : 
 ```
-dwm1001-keil-examples/
+Root
 ├── boards            // DWM1001-DEV board specific definitions
 ├── deca_driver       // DW1000 API software package 2.04 
 ├── examples          // C simple examples 
@@ -28,7 +28,6 @@ For more information about nrF52832 and nrF SDK, please visit http://infocenter.
 
 The examples are ready to use with the following IDE :
 * Segger Embedded Studio (SES)
-* Keil KEIL µVision
 
 ## Segger Embedded Studio
 
@@ -52,24 +51,6 @@ Nordic Semiconductor nRF CPU Support Package (version 1.06)
 
 They can be install from SES itself, through the package manager in the tools menu. 
 
-## KEIL µVision IDE
-
-Each example contains a µVision5 project file for Keil µVision IDE. The examples compile and load cleanly to the DWM1001.
-The project was created with the KEIL uVision version V5.24.2.0. 
-
-Keil µVision has a free license for project up to 32KB. For more information regarding Keil µVision, please visit http://www2.keil.com/mdk5/uvision/
-
-### µVision Error: Flash Download failed - "Cortex-M4"
-
-This error can be observed if there is a memory conflict between the binary to load and the current firmware on the target hardware. This issue can be easily fixed by fully erasing the target device 's flash memory. Keil µVision cannot perform a full erase and the following free tool can be used :
-
-* J-flash lite 
-* nrfjprog command line script
-
-For more information about the issue, please see :
-
-https://devzone.nordicsemi.com/f/nordic-q-a/18278/error-flash-download-failed---cortex---m4-while-flashing-softdevice-from-keil-uvision-5
-
 ## Example Details 
 
 The SS-TWR scheme can be implemented using two DWM1001 modules, the first one programmed as an initiator and the second one as a responder.
@@ -99,7 +80,7 @@ Calibration may be necessary in order to have an accurate measurement. It can be
 This example contains the source code for the responder. The receiver will receive a frame from the initiator and send the corresponding answer.
 
 ```
-dwm1001-keil-examples/examples/ss_twr_resp/
+dwm1001-examples/examples/ss_twr_resp/
 ├── config                    // Contains sdk_config.h file for nrF SDK 14.2 customization
 ├── main.c                    // Initialization and main program
 ├── ss_resp_main.c            // Single sided responder core program
@@ -118,7 +99,7 @@ This example implements a TWI between the LIS2DH12 and the nrF52832.
 The blue led will be on when a motion is detected by the LIS2DH12. It also reports the accelerometer state on the UART.
 
 ```
-dwm1001-keil-examples/examples/twi_accel/
+dwm1001-examples/examples/twi_accel/
 ├── config                    // Contains sdk_config.h file for nrF SDK 14.2 customization
 ├── LIS2DH12                  // LIS2DH12 (accelerometer) low level driver and api
 ├── main.c                    // Initialization and main program

examples/ss_twr_init/main.c

@@ -34,7 +34,7 @@
 #include "deca_param_types.h"
 #include "deca_regs.h"
 #include "deca_device_api.h"
-#include "uart.h"
+#include "UART.h"
 
 //-----------------dw1000----------------------------
 
@@ -200,7 +200,7 @@ int main(void)
  *    device should have its own antenna delay properly calibrated to get good precision when performing range measurements.
  * 3. This timeout is for complete reception of a frame, i.e. timeout duration must take into account the length of the expected frame. Here the value
  *    is arbitrary but chosen large enough to make sure that there is enough time to receive the complete response frame sent by the responder at the
- *    6.8M data rate used (around 200 �s).
+ *    6.8M data rate used (around 200 s).
  * 4. In a real application, for optimum performance within regulatory limits, it may be necessary to set TX pulse bandwidth and TX power, (using
  *    the dwt_configuretxrf API call) to per device calibrated values saved in the target system or the DW1000 OTP memory.
  * 5. The user is referred to DecaRanging ARM application (distributed with EVK1000 product) for additional practical example of usage, and to the

nRF5_SDK_14.2.0/components/libraries/uart/retarget.c

@@ -109,7 +109,7 @@ int __getchar(FILE * p_file)
         return ch;
     }
   #else
-    int __putchar(int ch, FILE *  p_file)
+    int __putchar(int ch, __printf_tag_ptr p_file)
     {
         UNUSED_PARAMETER(p_file);