The MCR20A Wireless UART application functions as an wireless UART bridge between two (one-to-one) or several (one to many) boards. The application can be used with both a TERM, or with software that is capable of opening a serial port and writing to or reading from it. The characters sent or received are not necessarily ASCII printable characters.

Dependencies:   fsl_phy_mcr20a fsl_smac mbed-rtos mbed

Fork of mcr20_wireless_uart by Freescale

By default, the application uses broadcast addresses for OTA communication. This way, the application can be directly downloaded and run without any user intervention. The following use case assumes no changes have been done to the project.

  • Two (or more) MCR20A platforms (plugged into the FRDM-K64F Freescale Freedom Development platform) have to be connected to the PC using the mini/micro-USB cables.
  • The code must be downloaded on the platforms via CMSIS-DAP (or other means).
  • After that, two or more TERM applications must be opened, and the serial ports must be configured with the same baud rate as the one in the project (default baud rate is 115200). Other necessary serial configurations are 8 bit, no parity, and 1 stop bit.
  • To start the setup, each platform must be reset, and one of the (user) push buttons found on the MCR20A platform must be pressed. The user can press any of the non-reset buttons on the FRDM-K64F Freescale Freedom Development platform as well. *This initiates the state machine of the application so user can start.

Documentation

SMAC Demo Applications User Guide

Revision:
18:b02fc0e53df8
Parent:
17:52cfd7db8da3
Child:
19:71b793021c78
--- a/node_cfg.h	Wed Mar 18 18:52:47 2015 +0000
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,31 +0,0 @@
-#ifndef NODE_CFG_H_
-#define NODE_CFG_H_
-
-/************** NODE PROFILE SELECTION ***********************/
-#define     NODE_CONTROLLER             1       // only for FRDM-K64F platform (running from battery)
-
-/********  Optional Resources ***********/
-#define BATTERY         1
-
-
-/*************** NODE PROFILE CONFIGURATION  *****************/
-#if NODE_CONTROLLER
-#define NODE_SHORT_ADDRESS  2
-#define NODE_MAC_ADDRESS    {0,0,6,0x02,0x00,0x00,0x09,0x63}
-#define NODE_NAME           "mbed-controller"
-#define REMOTE_NODE         {0x20,0x02,0x0d,0xb4,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0xff,0xfe,0x00,0x00,0x01}
-#endif
-
-#define ENDPOINT_TYPE       {"mbed-device"}
-#define LIFE_TIME           {"600"}     //seconds, extra char needed to avoid truncation
-
-/************** REGISTRATION  PARAMETERS  ************************/
-#define RD_UPDATE_PERIOD    30000      // 30 seconds 
-#define NSP_IP_ADDRESS      {0x20, 0x02, 0x0d, 0xb4, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01, 0x00, 0x02, 0x01, 0x00}
-
-/************* ALARM APPLICATION PARAMETERS *********************/
-#define ALARM_IP_ADDRESS    NSP_IP_ADDRESS
-#define ALARM_CTRL_UDP_PORT 1010
-
-#endif  // NODE_CFG_H_
-