Embeded System Software: Freescale K22F, KDS2.0, KSDK1.2, MQX

BACKGROUND: We’re developing a product that uses a WiFi & Bluetooth via UART, Serial Data Flash (SPI) and RTC (I2C) and some other stuff. I am using a FRDM-K22F (with a MK22FN512VLH12) as our dev platform while the target hardware is being completed. I need someone experienced with Freescale Tools to create a sample project that we can use a template to develop our project. We can use the FRDM-K22F as a common platform for us to verify the deliverables) SPEC: 1. Project that builds using KDS2.0 using KSDS 1.2 & MQX 4.x and run on a FRDM-K22F using mbed OpenSDA debugger Essential that all required project files are able to be checked into a VCS.(It is acceptable that just the Freescale libraries are separately built and the prebuilt libraries are version controlled Acceptance Criteria: Install Freescale tools on a ‘clean’ machine. Unzip project to (separate) file hierarchy (including pre-built libraries) build without errors and runs on target Intent: Currently I can only make a working project if it’s located at C:\Freescale\KSDK_1.2.0\rtos\mqx\mqx\examples\... this is unacceptable as the file dependencies are not clear and it is not clear which files are required to checked into a VCS. I am happy to take advice as to how to best manages the Freescale code base, at this stage it is acceptable that just the prebuilt libraries are version controlled by the project. I want to be able to put the entire project on any dev machine that has the Freescale toolchain on it and be able to build. 2. Create Several Tasks. Each implementing the required feature (to me detailed later) This project will serve as a template to our actual project. As such it does not need to be complete. Minimum error checking is all that is required – it would be appreciated that any ‘gotchas’ as highlighted for our considerations (via comments, in the code) 3. UART TX Task. Transmit strings of varying lengths and contents via UART1 every 500msec. String would be ‘commands’ to the receive task. To simplify decoding they will be ‘framed by “[ ]” (or similar) (Eg “[CMD1]”, “[A2]”, “[DEFG3]”, “[XY3Z]”,…) 4. UART Rx Task Receive a string via UART2. Able to accept each character at a time to decode the ‘command’. Each command will result is a message being send to a command processing tasks. Intent: To demonstrate ability to send and receive UART data using MQX tasks. To show how to accept variable length data, decode it and transform it by sending to other tasks. Acceptance Criteria: printf() diagnostic in Rx Task to print the received and decoded ‘command’. 5. Command Processing Task & transmit via SPI Wait on message being send by UART RX task and depending on Intent: To demonstrate ability to receive MQX messages and confirm SPI peripheral setup as SPI master (Mode 0) and transmit data via SPI Acceptance Criteria: printf() diagnostic upon reception of the message from the Uart RX Task. Data transmission via SPI to be verifiable by oscilloscope. 6. I2C task (Inertial Sensor) Tasks Poll the inertial sensor every 500msec and display values via printf() diagnostics Intent: To demonstrate ability to configure I2C peripheral and communicate with a device running as an MQX task. It is not important to develop and interface to the inertial sensor. The point of this requirement is to demonstrate working I2C. So a minimal interface (eg read on register in the Inertial sensor) is acceptable Acceptance Criteria: printf() diagnostic of data received from I2C device