If you are interested in a PPP connection between your PC and your board using Win 7 OS you may find the attached document useful. This project (ATTACHED) starts PPP service and waits for a Windows connection. ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- If you are interested in getting started with MQX for KSDK please see the following document: How To: Create a New MQX RTOS for KSDK Project in KDS If you are interested in using RTCS with Processor Expert please see the following document: How to add RTCS to a Processor Expert Project Using KDS and KSDK Regards, Carlos

CREATE MQX FOR KSDK PROJECT FROM SCRATCH IN IAR IDE Note: ${KSDK_PATH} is used in this guide line to instead of path of KSDK source (Example: C:/Freescale/KSDK_1.2.0/). This procedure was created for TWR-K64f120M 1     Create new workspace                 Open IAR  --> File  --> New  --> Workspace                 2     Create new project Project --> Create New Project  --> C  -> main --> OK                    Select project directory                              3    Add project lib to workspace         Project  -->  Add Existing Project … then select projects: {SDK_PATH}/lib/ksdk_mqx_lib/iar/K64F12/ksdk_mqx_lib.ewp {SDK_PATH}/rtos/mqx/mqx/build/iar/mqx_twrk64f120m/mqx_twrk64f120m.ewp {SDK_PATH}/rtos/mqx/mqx_stdlib/build/iar/mqx_stdlib_twrk64f120m/mqx_stdlib_twrk64f120m.ewp                        4    Build All Lib project                   5    Setting Project On the left workspace pane, right click on Mqx Project and select Options. Setting General Options         Select device:                       Setting C/C++ Compiler          Add include file and define symbols for project at Preprocessor tab: Additional include directories: {SDK_PATH}/rtos/mqx/lib/twrk64f120m.iar/debug {SDK_PATH}/rtos/mqx/lib/twrk64f120m.iar/debug/config {SDK_PATH}/rtos/mqx/lib/twrk64f120m.iar/debug/mqx {SDK_PATH}/rtos/mqx/lib/twrk64f120m.iar/debug/mqx_stdlib {SDK_PATH}/platform/osa/inc {SDK_PATH}/platform/CMSIS/Include {SDK_PATH}/platform/devices {SDK_PATH}/platform/hal/inc {SDK_PATH}/platform/drivers/inc {SDK_PATH}/platform/system/inc {SDK_PATH}/platform/devices/MK64F12/include {SDK_PATH}/platform/devices/MK64F12/startup {SDK_PATH}/platform/system/inc {SDK_PATH}/platform/hal/inc {SDK_PATH}/platform/drivers/inc {SDK_PATH}/platform/startup {SDK_PATH}/platform/utilities/inc {SDK_PATH}/examples/twrk64f120m {SDK_PATH}/rtos/mqx/config {SDK_PATH}/rtos/mqx/mqx/source/include Defined symbols: CPU_MK64FN1M0VMD12 TWR_K64F120M FSL_RTOS_MQX                         Setting Linker option           Use linker file in KSDK source:             {KSDK_PATH}/platform/devices/MK64F12/linker/iar/MK64FN1M0xxx12_flash.icf           Set stack/heap size and define __ram_vector_table__ __stack_size__=0x400 __heap_size__=0x400 __ram_vector_table__=1                           The project request three librarys: lib_mqx.a, lib_mqx_stdlib.a, libksdk_platform_mqx.a {KSDK_PATH}/lib/ksdk_mqx_lib/iar/K64F12/Debug/libksdk_platform_mqx.a {KSDK_PATH}/rtos/mqx/lib/twrk64f120m.iar/debug/mqx/lib_mqx.a {KSDK_PATH}/rtos/mqx/lib/twrk64f120m.iar/debug/mqx_stdlib/lib_mqx_stdlib.a              MQX uses owner’s startup-code (boot.S), We need to override default program entry                        6     Create project template Project structure and create group:          Specific file for board in: {KSDK_PATH}\examples\twrk64f120m\board.c {KSDK_PATH}\examples\twrk64f120m\board.h {KSDK_PATH}\examples\twrk64f120m\gpio_pins.c {KSDK_PATH}\examples\twrk64f120m\gpio_pins.h {KSDK_PATH}\examples\twrk64f120m\pin_mux.c {KSDK_PATH}\examples\twrk64f120m\pin_mux.h          BSP file in: {KSDK_PATH}\rtos\mqx\mqx\source\bsp\bsp.h {KSDK_PATH}\rtos\mqx\mqx\source\bsp\bsp_config.h {KSDK_PATH}\rtos\mqx\mqx\source\bsp\init_bsp.c {KSDK_PATH}\rtos\mqx\mqx\source\bsp\mqx_main.c {KSDK_PATH}\rtos\mqx\mqx\source\include\mqx.h          Config files in: {KSDK_PATH}\rtos\mqx\config\common\small_ram_config.h {KSDK_PATH}\rtos\mqx\config\common\verif_enabled_config.h {KSDK_PATH}\rtos\mqx\config\board\twrk64f120m\user_config.h {KSDK_PATH}\rtos\mqx\config\mcu\MK64F12\mqx_sdk_config.h           Utilities files in: {KSDK_PATH}\platform\utilities\src\print_scan.c {KSDK_PATH}\platform\utilities\src\print_scan.h {KSDK_PATH}\platform\utilities\src\fsl_debug_console.c {KSDK_PATH}\platform\utilities\inc\fsl_debug_console.h                                                                7    Write code The code below is used to turn on the LED and print out “hello world”. #include "stdio.h" #include "fsl_os_abstraction.h" #include "board.h" #include "fsl_debug_console.h" #define MAIN_TASK        8 void main_task(uint32_t param); const TASK_TEMPLATE_STRUCT  MQX_template_list[] = {    { MAIN_TASK, main_task, 0xC00, 20, "main_task", MQX_AUTO_START_TASK},    { 0L, 0L,        0L,    0L, 0L,         0L } }; void main_task(uint32_t param) {     LED1_EN;     LED1_ON;     PRINTF("Hello World\r\n");     while(1)     {} } 8    Run example: Build project:                   Select debug target                     - Set serial console 115200 baud rate, no parity, 8 data bits, 1 stop bit, without flow control - Set project as active prior we run project Run project                         See Led1 is On status and string “Hello World” is printed to screen                           

Hello All, Next document lists the steps needed to install a basic NIO driver in MQX for KSDK 1.3. In this document, a basic SPI driver for FRDM-K64F was created in order to serve as guidance for any user's driver. Source and header file for this NIO SPI are attached as well as hello.c source files that was taken from hello_world example in order to test this driver. I hope you can find it helpful! Best Regards, Isaac Avila

It's a note to configre and use Flexbus interface in MQX platform .

A new MQX Flash File System (FFS) add-on is available for Freescale MQX™ 4.0.2.   See MQX Downloads.  FFS provides wear-leveling support required for mapping MFS on top of NAND flash. Files available # Name Description 1 FSL_MQX__FFS_RELEASE_NOTES_4_0_2 Freescale   MQX™ FFS package 4.0.2 Release Notes 2 Freescale   MQX RTOS 4.0.2 FFS package NAND   Flash File System solution for MQX™ 4.0.2

If anybody meets an issue with MQX 3.8 (also 3.8.1, 4.0 and 4.0.1) writing to a Compact flash (/mfs/examples/cfcard), there is an error in the cfcard io driver. Compact flash can be read, but writing doesn't work. Fix for this is in the source file: c:\Freescale\Freescale MQX 3.8\mqx\source\io\pcflash\apcflash.c in function _io_apcflash_write() on line 452, change from: results = _io_apcflash_read_write_blocks(fd_ptr, info_ptr, data_ptr, num, FALSE); change to: results = _io_apcflash_read_write_blocks(fd_ptr, info_ptr, data_ptr, num, TRUE); Tested on M5329EVB and MQX 3.8.1.

This blog shares several issues reported by China customers when they use NAND FFS in MQX4.1.1. NAND FFS open failure issue Customer reported they can use a pressure test code to continuously open file, write file and close file, each time write about 20 bytes with append and they will find after running for a while, file open will fail and it returns error code 0x3067 (MFS_EOF). Each time file open failed, file has been written with 20480 bytes. This is a typical use case at customer side for data logging. The test code is attached named as "nand_pressure_test.cpp". Attached patch file named "mfs_write.patch" can resolve this issue. Memory allocation issue when using MFS & NAND FFS Customer run pressure test for MFS and NAND FFS by creating multiple levels of sub-folders (up to 100 levels) and in each sub-folder they create random number of files (up to 50). For each file, they will write 250 bytes. They found code failed to open new file when create sub-folders to 41 level. Traced the code on K70 tower and found actually this is not problem with MFS to search clusters for the new file, instead when the issue occurs, it's the drive_ptr (MFS_DRIVE_STRUCT) which is corrupted when MFS use memory allocation routine to allocate file path. The pressure test code for this case is attached. File named "MultiLevel_Folder_Test.zip". The memory corruption for MFS drive info is due to there is no protection in MFS_Parse_pathname() on whether the actual path name used passed from fopen will be exceeding 260 bytes which is fixed in mfs.h file to be compatible with Windows. So need to take care of this internal limitation when handling multiple level folders. MFS deadlock issue when using NAND FFS Customer reported random code block issue when running pressure test against NAND FFS. The issue is quite random, sometimes takes 12 hrs to reproduce the issue. Test code attached. Name is "MFS deadlock issue.zip". The resolution and description on this issue is in attached file named "MQX-4919 NandFFS explanation". Hao

Introduction the BSP configuration file in MQX for Kinetis SDK 1  Overview of BSP directory in MQX classic  and MQX for KSDK If you compare the BSP directory of MQX classic and MQX for KSDK , you will find that there are significant differences in how the Board Support Package for MQX for KSDK and classic MQX are configured.  For MQX classic directory, the compiled BSP library is used for drivers and hardware configuration (see picture 1), there are 35 files, while for MQX for KSDK directory (see picture 2), the BSP directory is nearly empty, much of the equivalent functionality of the BSP library is now moved to the example board directory. See picture 3. If you want to port your application to your custom board, these files are very important, you need to review them carefully. Picture 1   BSP in MQX classic Picture 2  BSP in MQX for KSDK Picture 3   board directory in MQX for KSDK 2  Introduction of the BSP configuration file in MQX for KSDK The BSP configuration  files are located at  sdk_install_folder/examples. Please see picture 3. We need to modify these files according to schematic and reference manual 2.1 Board.c/h: The C file contains clock and oscillator initialization functions. The header file contains board-specific configuration macros for things such as debug terminal configuration, push buttons, LEDs and other board-specific items. 2.2 Gpio_pins.c/h: Kinetis SDK uses pin configuration structures for each pin --Pin configuration structures in gpio_pin.c configures input/output, pull-up/pull-down, pin filtering, interrupt enabled/disabled, initial output polarity, slew rate and driver strength setting Gpio_pins.h --declares Pin names used by board, PORT pin to use  (ie: PTE3) --contains definitions for LED, switch, and SD card chip select /*! @brief Pin names */ enum _gpio_pins_pinNames{   kGpioSW2      = GPIO_MAKE_PIN(GPIOC_IDX, 6U),   kGpioSW3      = GPIO_MAKE_PIN(GPIOA_IDX, 4U),   kGpioSdhc0Cd  = GPIO_MAKE_PIN(GPIOE_IDX, 6U),   kGpioLED1     = GPIO_MAKE_PIN(GPIOE_IDX, 26U),   kGpioLED2     = GPIO_MAKE_PIN(GPIOB_IDX, 22U),   kGpioLED3     = GPIO_MAKE_PIN(GPIOB_IDX, 21U), }; #endif Gpio_pins.c Contains GPIO options for each pin const gpio_output_pin_user_config_t ledPins[] = {   {     .pinName = kGpioLED1, .config.outputLogic = 1,     .config.slewRate = kPortSlowSlewRate,     .config.isOpenDrainEnabled = false, .config.driveStrength = kPortLowDriveStrength,   },   {     .pinName = kGpioLED2, .config.outputLogic = 1,     .config.slewRate = kPortSlowSlewRate, .config.isOpenDrainEnabled = false, .config.driveStrength = kPortLowDriveStrength,   },   {     .pinName = kGpioLED3, .config.outputLogic = 1,     .config.slewRate = kPortSlowSlewRate, .config.isOpenDrainEnabled = false, .config.driveStrength = kPortLowDriveStrength,   },   {     .pinName = GPIO_PINS_OUT_OF_RANGE,   } }; 2.3  Pin_mux.c/h: Kinetis devices provide great flexibility in muxing signals, each digital port pin has up to 8 signals muxed on pin, some peripherals route same signals to multiple pins. In Pin_mux.c:  It implements functions to set pin mux option for all pins used on board, and functions for each peripheral type, like configure_can_pins() void configure_can_pins(uint32_t instance) {   /* PORTB_PCR19 */   PORT_HAL_SetMuxMode(PORTB,19u,kPortMuxAlt2);   /* PORTB_PCR18 */   PORT_HAL_SetMuxMode(PORTB,18u,kPortMuxAlt2); } Not all instances will be populated so may need to add void configure_i2c_pins(uint32_t instance) {   switch(instance) {        case I2C0_IDX:                       /* I2C0 */       /* Affects PORTE_PCR24 register */ PORT_HAL_SetMuxMode(PORTE,24u,kPortMuxAlt5);       PORT_HAL_SetOpenDrainCmd(PORTE,24u,true);       /* Affects PORTE_PCR25 register */ PORT_HAL_SetMuxMode(PORTE,25u,kPortMuxAlt5); PORT_HAL_SetOpenDrainCmd(PORTE,25u,true);       break;     case I2C1_IDX:                       /* I2C1 */       /* Affects PORTC_PCR10 register */ PORT_HAL_SetMuxMode(PORTC,10u,kPortMuxAlt2); PORT_HAL_SetOpenDrainCmd(PORTC,10u,true);       /* Affects PORTC_PCR11 register */ PORT_HAL_SetMuxMode(PORTC,11u,kPortMuxAlt2); PORT_HAL_SetOpenDrainCmd(PORTC,11u,true);       break;     default:       break;   } 2.4  hardware_init: Project specified hardware initialization, it uses functions provided in board configuration layers in pin_mux.c during startup void hardware_init(void) { /* enable clock for PORTs */ CLOCK_SYS_EnablePortClock(PORTA_IDX); CLOCK_SYS_EnablePortClock(PORTB_IDX); CLOCK_SYS_EnablePortClock(PORTC_IDX); CLOCK_SYS_EnablePortClock(PORTE_IDX); /* Init board clock */ BOARD_ClockInit(); dbg_uart_init(); } 3   Kinetis SDK Porting example—Change Default UART To change default UART port, we need to change the UART instance in board.h, and change the pin muxing in pin_mux.c 3.1   Modify board.h to select the UART and baud rate to use /* The UART to use for debug messages. */ #ifndef BOARD_DEBUG_UART_INSTANCE     #define BOARD_DEBUG_UART_INSTANCE   0     #define BOARD_DEBUG_UART_BASEADDR   UART0 #endif #ifndef BOARD_DEBUG_UART_BAUD     #define BOARD_DEBUG_UART_BAUD       115200 #endif 3.2  Modify pin_mux.c to select the pins to use void configure_uart_pins(uint32_t instance) {   switch(instance) {        case UART0_IDX:                      /* UART0 */       /* Affects PORTB_PCR16 register */ PORT_HAL_SetMuxMode(PORTB,16u,kPortMuxAlt3);       /* Affects PORTB_PCR17 register */ PORT_HAL_SetMuxMode(PORTB,17u,kPortMuxAlt3);       break;     case UART4_IDX:                      /* UART4 */       /* Affects PORTC_PCR14 register */ PORT_HAL_SetMuxMode(PORTC,14u,kPortMuxAlt3);       /* Affects PORTC_PCR15 register */ PORT_HAL_SetMuxMode(PORTC,15u,kPortMuxAlt3);       break;     default:       break;   } }

The new Freescale MQX™ RTOS 4.1.0 FRDM-K64F release is now available on the www.freescale.com ·         Files available # Name Description 1 FSL_MQX_FRDM-K64F_RELEASE_NOTES Freescale   MQX™ RTOS 4.1.0 FRDM-K64F Release Notes 2 Freescale   MQX RTOS 4.1.0 for the FRDM-K64F Includes   an RTOS, File System, TCP/IP and USB host/device software stacks. Does not   require MQX™ 4.1 installation. ·         Target HW board o   FRDM-K64F ·         New features o   PSP support for the Kinetis K64F o   BSP for the FRDM-K64F development board o   Standard set of I/O drivers supporting the K64F peripherals including: §  LWGPI/O driver §  Serial interrupt and polled driver §  SPI driver §  I2C interrupt and polled driver §  LWADC §  Flash Driver §  RTC Driver §  PIT Timer §  LPT Timer §  WDOG §  Low-power Mode §  SAI §  DMA §  SD Card §  Ethernet driver o   USB Host and Device drivers and stacks o   Example and demo applications demonstrating MQX, USB, RTCS, and MFS usage ·         Known issues o   For known issues and limitations please consult the release notes.

May 7, 2014   MQX plugins were rebuilt to support latest DS5.18.   Zip attached to this email contains following plugins:   - com.freescale.projectofprojects   - com.freescale.buildtoolbar   - com.freescale.mqx.configuration.editor   The plugins installation procedure is described in the MQX DS5 getting started manual (chapter 2). Plugins are backward compatible and should work also in older DS5 versions.   https://community.freescale.com/thread/323233   Regards, David Seymour

Rev0.2 - 8/28/2012 NOTE: for an update to this patch for MQX v4.0.2, see TWR-K21D50M lowpower MQX Patch for v4.0.2 This patch addresses several issues with using the lowpower example in MQX on the twrk21d50m BSP. The lowpower example is provided to demonstrate the MQX Low-Power Manager (LPM) driver, and change low-power modes on the K21 board.  The BSP provided in MQX v4.0 has several issues interfering with these low-power modes, and the lowpower example. To use this patch, copy the patch directory into the MQX v4.0 root directory.  The patch will over-write some existing files in the MQX installation.  The changes addressed by this patch include the following: User_config.h MQX_ENABLE_LOW_POWER macro enabled.  Required for LPM driver and lowpower example. VLPR Clock configuration dividers Updated the clock dividers in the SIM_CLKDIV1 register to set the core/system/bus clock frequencies at 2MHz as expected, instead of 1MHz.  Modified Cpu_SetClockConfiguration() in bsp_cm.c.  Fixes issue in lowpower example where characters printed to terminal are incorrect baud rate in VLPR mode. UART settings for LPM Operation modes BSP has incorrect settings for UART2 (TTYC) for the LPM operation modes.  Causes UART2 to be disabled in Run mode when MQX_ENABLE_LOW_POWER is enabled, which causes a bus error exception, stopping the BSP startup before main() is entered.  Modified init_sci.c Over-writing internal oscillator trim value The BSP was not using the factory trimmed settings for the internal oscillators.  The BSP is configured for a user-trim value to be stored at 0x3FE and 0x3FF.  The BSP checks these flash locations, and if not erased having 0xFF, it writes these locations to the MCG trim registers.  The issue is the vector table filled the vector location at 0x3FC, fooling the BSP into thinking user-trim value was present.  Modified vector.c to replace final vector with 0xFFFFFFFF, forcing BSP to keep the factory trim settings.  Fixes issue in lowpower example where characters printed to terminal are incorrect baud rate in VLPR mode. Disabled clock monitor when entering a stop mode BSP had clock monitor enabled in BSP, and did not disable before entering a stop mode.  This prevents the lowpower example from recovering properly from LLS mode. Modified _lpm_set_cpu_operation_mode() in lpm_smc.c to clear the CME bit before entering a stop mode, and then restore CME setting after waking up. Disabled SPI0 peripheral before entering a stop mode lowpower example was aborting the stop mode entry, and never entered stop mode.  The issue was caused by the SPI0 peripheral preventing the entry to LLS mode.  Modified _lpm_set_cpu_operation_mode() in lpm_smc.c to disable SPI0 clock gate before entering a stop mode, and re-enabled after waking up.  If SPI0 peripheral is required in a stop mode, register the SPI driver with the LPM driver to properly configure when LPM changes operation mode to a stop mode.  Refer to LPM documentation for details.

Hi all, I want to share this document that describes steps to create a new driver using MQX 4.1 and CW 10.6.  I used the Null-Device Driver,  the null device driver provides an I/O device that functions as a device driver but does not perform any work. I hope it helps. Regards Sol

Video Tutorial 3 of 6 for the iDigi Connector for MQX: Writing Your First iDigi Enabled Application (3 of 6) - iDigi Device Cloud More information and free download at http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=KINETIS_IDIGI_M2M

Atheros WiFi Tower Module (TWR-WIFI-AR4100P) support patch for Freescale MQX™ 4.0.2  is available at MQX Downloads. Files available # Name Description 1 FSL_MQX_ATHEROS_RELEASE_NOTES_4_0_2  Freescale   MQX™ Atheros Wifi package 4.0.2 Release Notes 2 Freescale   MQX RTOS 4.0.2 Atheros Wifi package Atheros   Wifi solution for MQX™ 4.0.2

Tutorial 5 of 6 for the iDigi Connector for MQX: Enabling iDigi Remote Firmware Update (5 of 6) - iDigi Device Cloud More information and free download at http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=KINETIS_IDIGI_M2M

Video Tutorial 2 of 6 for the iDigi Connector for MQX: iDigi Connector for MQX Extensions Overview (2 of 6) - iDigi Device Cloud More information and free download at http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=KINETIS_IDIGI_M2M

Video Tutorial 1 of 6 for the iDigi Connector for MQX: Installing and Configuring the iDigi Connector for MQX (1 of 6) - iDigi Device Cloud More information and free download at http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=KINETIS_IDIGI_M2M

The Freescale MQX™ RTOS for Kinetis SDK FRDM-KL43Z Freescale Freedom Platform is now available on the www.freescale.com ·         Release Files             # Name Description 1                                   Freescale_MQX_KSDK_1.0.0-KL43Z.exe Windows installer. Freescale MQX™ RTOS software   components fully pre-integrated with the Kinetis SDK. Includes the MQX   kernel, USB host and device stacks, MFS file system, and example   applications. Does not require prior installation of Kinetis SDK. 2                                   Freescale_MQX_KSDK_1.0.0-KL43Z.bin Linux installer. Freescale MQX™ RTOS software   components fully pre-integrated with the Kinetis SDK. Includes the MQX   kernel, USB host and device stacks, MFS file system, and example   applications. Does not require prior installation of Kinetis SDK. 3 MQXKSDKKL43Z.pdf Freescale MQX™ RTOS for Kinetis   SDK FRDM-KL43Z Freescale Freedom Platform Release Notes ·         Target HW boards: o   Freescale Freedom FRDM-KL43Z platform with a MKL43Z256VLH4 processor ·         Key features:  o   PSP support for the MKL43Z256VLH4 Microcontroller o   BSP for the Freescale Freedom FRDM-KL43Z platform with a MKL43Z256VLH4 processor o   MQX STDLIB o   nShell o   KSDK Support for the MKL43Z256VLH4 Microcontroller o   MFS file system ·         Known issues For known issues and limitations please consult the release

Tutorial 4 of 6 for the iDigi Connector for MQX: Building and Running the Kinetis K60 Tower Demo Sample (4 of 6) - iDigi Device Cloud More information and free download at http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=KINETIS_IDIGI_M2M

Rev0.1 - 8/28/2013 This is an update to the previous patch TWR-K21D50M lowpower Patch In MQX v4.0.2, most of the issues reported in the earlier patch have been fixed in the BSP.  But the lowpower example for this board still fails to enter LLS mode because of a conflict with the SPI peripheral.  There is only a minor edit in one file needed to fix the example. User_config.h MQX_ENABLE_LOW_POWER macro enabled.  Required for LPM driver and lowpower example. Disabled SPI0 peripheral before entering a stop mode lowpower example was aborting the stop mode entry, and never entered stop mode.  The issue was caused by the SPI0 peripheral preventing the entry to LLS mode.  Modified _lpm_set_cpu_operation_mode() in lpm_smc.c to disable SPI0 clock gate before entering a stop mode, and re-enabled after waking up.  If SPI0 peripheral is required in a stop mode, register the SPI driver with the LPM driver to properly configure when LPM changes operation mode to a stop mode.  Refer to LPM documentation for details.  Replace the file \Freescale_MQX_4_0_2\mqx\source\io\lpm\lpm_smc.c with the attached.