MQX Software Solutions Knowledge Base

Discussions

General MQX FAQ page on the Freescale MQX product support page FAQ specific to the TWR-MCF51CN-KIT MQX labs Q: What software tools do I need for TWR-MCF51CN-KIT demos and lab tutorials? A: The TWR-MCF51CN-KIT requires CodeWarrior for Microcontrollers 6.2 Professional Edition (30-day evaluation available) with the 6.2.2 patch to unlock the full potential of the demos and labs. Is version 6.2.2 necessary? Yes, the 6.2.2 patch contains the necessary support for the MCF51CN128. What about CodeWarrior Special Edition? Due to the code size limitation (<64k) of Microcontroller Special Edition, the labs for the TWR-MCF51CN-KIT will not compile. What about CodeWarrior Basic and Standard Edition? Those versions will work with the labs. Q. Where is MQX Task Aware Debugging? A: The TAD feature is only available on V2 cores or above. Q. Why must I install the CW 6.2.2 patch after Processor Expert Update? A: Due to a bug in Processor Expert Update 3.05, the 6.2.2 patch must be installed after Processor Expert. This issue was fixed in PE 3.06 or later. If you did not install PE before the 6.2.2 patch, simply re-run the 6.2.2 patch installer again, and the problem should be solved. Q: I'm having trouble establishing an Ethernet connection between my PC and the board. What do I do? A: 1) Hit the Reset button on the board after you plug in the cable. 2) Wait a minute or two for your computer to connect. Connect the board directly to your computer with an ethernet crossover cable. You must wait a minute or two for your computer to try to aquire a network address. Since you're no longer connected to your network the computer will eventually revert to an Auto IP address on the same subnet as board (169.254.x.x). 3) Disable your wireless router if you have one. 4) Disable proxy server settings in your web browser. Notes: When connected your computer might report limited or no connectivity, but it should still work. If all else fails, configure your IP address manually as instructed by the quick start guide. Q. I'm using Windows Vista and when I type telnet into a command prompt, it tells me it cannot find the program. Where is it? A: The telnet client is not enabled by default in Windows Vista. To enable it, perform the following steps: 1. Go to Start > Control Panel > Programs and Features. 2. Select "Turn Windows features on or off" 3. Select the check box next to "Telnet Client" and hit OK. Q. Why does the debugger say it's hitting an illegal breakpoint when executing the labs, and the Run button keeps flashing on and off? A: This is a bug in the OSBDM and CW6.2.2 where it loses debug connection when it encounters a stop instruction. The code is still executing so it will not affect the running of the labs. A new version of OSBDM and installation instructions will be available soon. Message Edited by amh on 2009-12-09 02:44 PM This document was generated from the following discussion: TWR-MCF51CN-KIT MQX Lab FAQs - Updated

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; } }

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.

Hello All, This document explains how to add GPIO pins to the default BSP configurations. This example shows how add a LED pin for the BSP TWR-K70FN1M board. The procedure is the same for other ports and peripherals, using Kinetis devices. MODIFY THE TWRK70F120M.h FILE The TWR-K70F120M Tower Module contains two pushbutton switches connected to GPIO/interrupt signals, one pushbutton connected to the master reset signal, four capacitive touch pad electrodes, four user controllable LEDs, and a potentiometer connected to an ADC input signal. The following table provides details on which K70FN1M0 pins are used to communicate with the LEDs and switches onboard the TWR-K70F120M. Feature Connection Port Pin Pin Function Pushbuttons SW1 (IRQ0) PTD0 PTD0 SW2 (IRQ1) PTE26 PTE26 SW3 (RESET) RESET_b RESET_b LEDs E1 / Orange LED PTA11 PTA11 E2 / Yellow LED PTA28 PTA28 E3 / Green LED PTA29 PTA29 E4 / Blue LED PTA10 PTA10 Touch Pads E1 / Touch PTA4 TSI0_CH5 E2 / Touch PTB3 TSI0_CH8 E3 / Touch PTB2 TSI0_CH7 E4 / Touch PTB16 TSI0_CH9 Table 1. I/O Connectors and Pin Usage Table NOTE: Some port pins are used in multiple interfaces on-board and many are potentially connected to off-board resources via the Primary and Secondary Connectors. Take care to avoid attempted simultaneous usage of mutually exclusive features. For more information please consult the “TWR-K70F120M Tower Module User's Manual”. http://cache.freescale.com/files/microcontrollers/doc/user_guide/TWRK70F120MUM.pdf?fpsp=1&WT_TYPE=Users%20Guides&WT_VENDOR=FREESCALE&WT_FILE_FORMAT=pdf&WT_ASSET=Documentation The <board>.h file is used to provide information needed by an application program using the kernel running on the Freescale Evaluation board. This file contains the GPIO board specifications. It is located at the next path: <Freescale_MQX_4_x_install_path>\mqx\source\bsp\<name_board> Figure 1. GPIO board specifications for the TWR-K70F120M. The twrk70f120m.h file contains the GPIO board definition for the TWR-K70F120M, however if customer creates his own board and he needs to connect LEDs in deferent pins to the TWR-K70F120M, it is necessary to modify this file. Suppose a custom_board where is connected a LED to PTE18 pin, in order to add this pin definition it is necessary to follow the below steps, the pin will be called BSP_LEDCustom. 1. Define the pin name and assign the port and pin number. #define BSP_LEDCustom (GPIO_PORT_E | GPIO_PIN18) 2. Assigning the requested functionality to the pin for the GPIO mode or any other peripheral mode. #define BSP_LEDCustom_MUX_GPIO (LWGPIO_MUX_E18_GPIO) 3. Save and close the twrk70f120m.h file. USE THE NEW LED IN A PROJECT The following example shows one task named LEDCustom_TASK, where the LEDCustom is used. 1. Open a new MQX project. 2. In the main.h module replace the following lines: #define MAIN_TASK 1 extern void Main_task(uint_32); With the next lines: #define LEDCustom_TASK 5 extern void ledCustom_task(uint_32); 3. In main.c, modify the MQX_template_list entry for the Main_Task. Replace the following line: {MAIN_TASK, Main_task, 1500, 9, "main", MQX_AUTO_START_TASK}, With the next line: { LEDCustom_TASK, ledCustom_task, 1500, 9, "init", MQX_AUTO_START_TASK, 0, 0}, NOTE The last entry in the MQX_template_list must be all zeros. 4. In main.c, comment out the Main_task. /*void Main_task(uint_32 initial_data) { print(“/n Hello World /n”); _mqx_exit(0); } */ 5. It is necessary to write the tasks code. This task uses LWGPIO driver in order to toggle a pin. The lwgpio_init() function has to be called prior to calling any other API function of the LWGPIO driver. This function initializes the LWGPIO_STRUCT structure. The pointer to the LWGPIO_STRUCT is passed as a handle parameter. To identify the pin, platform-specific LWGPIO_PIN_ID number is used. It is necessary to have a variable to assign the pointer to the LWGPIO_STRUCT, for do that it is required to add the following line: LWGPIO_STRUCT ledC; The following lines initialize lwgpio handle for LWGPIO_MUX_E18_GPIO pin. The BSP already knows the address and the pin number for each GPIO PORT and each PIN. This is defined in mqx/source/bsp/<bsp_name>/<bsp_name>.h file. That is the reason the twrk70f120m.h file was modified. if (!lwgpio_init(&ledC, BSP_LEDCustom, LWGPIO_DIR_OUTPUT, LWGPIO_VALUE_NOCHANGE)) { printf("Initializing Port TE pin18 GPIO of the K70 as output failed.\n"); _task_block(); } 6. Once it is initialized, it is necessary to assign the requested functionality to the pin like GPIO mode or any other peripheral mode. The lwgpio_set_functionality() function sets the functionality of the pin. The value of the functionality parameter represents the number stored in the multiplexer register field which selects the desired functionality. For the GPIO mode, you can use the pre-defined macros which can be found in the lwgpio_ <mcu>.h file. Add the following lines switch pin functionality to GPIO mode: lwgpio_set_functionality(&ledC, BSP_LEDCustom_MUX_GPIO); The lwgpio_set_value() function sets the pin state (low or high) of the specified pin. In order to toggle the pin value write the following code: while (TRUE) { _time_delay(1000); lwgpio_set_value(&ledC, value); /* toggle pin value */ value = value^1; } 7. Create the other three functions. The name of each function, delay, and the first parameter must be different in LWGPIO functions use (lwgpio_init(), lwgpio_set_functionality(), lwgpio_set_value()). 8. At this point it is possible to build the project, flash it to the board and run the project; for more details about building, flashing and running please refer to the compiler documentation of your choice, that is located at the next path: C:\Freescale\Freescale_MQX_4_x\doc\tools\cw Thanks!!!! a. main.c /**************************************************************************** * * This file contains MQX only stationery code. * ****************************************************************************/ #include "main.h" #if !BSPCFG_ENABLE_IO_SUBSYSTEM #error This application requires BSPCFG_ENABLE_IO_SUBSYSTEM defined non-zero in user_config.h. Please recompile BSP with this option. #endif #ifndef BSP_DEFAULT_IO_CHANNEL_DEFINED #error This application requires BSP_DEFAULT_IO_CHANNEL to be not NULL. Please set corresponding BSPCFG_ENABLE_TTYx to non-zero in user_config.h and recompile BSP with this option. #endif TASK_TEMPLATE_STRUCT MQX_template_list[] = { /* Task number, Entry point, Stack, Pri, String, Auto? */ {LEDCUSTOM_TASK, ledCustom_task, 1500, 9, "init", MQX_AUTO_START_TASK, 0, 0}, {0, 0, 0, 0, 0, 0, 0, 0} }; /*TASK*----------------------------------------------------- * * Task Name : Main_task * Comments : * This task prints " Hello World " * *END*-----------------------------------------------------*/ void ledCustom_task(uint_32 initial_data) { int value = 0; LWGPIO_STRUCT ledC; printf("\n LedCustom task \n"); /* initialize lwgpio handle for LWGPIO_MUX_TC0_GPIO pin (defined in mqx/source/bsp/<bsp_name>/<bsp_name>.h file) */ if (!lwgpio_init(&ledC, BSP_LEDCustom, LWGPIO_DIR_OUTPUT, LWGPIO_VALUE_NOCHANGE)) { printf("Initializing Port TE pin18 GPIO of the K70 as output failed.\n"); _task_block(); } /* swich pin functionality to GPIO mode */ lwgpio_set_functionality(&ledC, BSP_LEDCustom_MUX_GPIO); while (TRUE) { _time_delay(5000); lwgpio_set_value(&ledC, value); /* toggle pin value */ value = value^1; } } /* EOF */ b. main.h #ifndef __main_h_ #define __main_h_ #include <mqx.h> #include <bsp.h> #define LEDCUSTOM_TASK 5 extern void ledCustom_task(uint_32); /* PPP device must be set manually and ** must be different from the default IO channel (BSP_DEFAULT_IO_CHANNEL) */ #define PPP_DEVICE "ittyb:" /* ** Define PPP_DEVICE_DUN only when using PPP to communicate ** to Win9x Dial-Up Networking over a null-modem ** This is ignored if PPP_DEVICE is not #define'd */ #define PPP_DEVICE_DUN 1 /* ** Define the local and remote IP addresses for the PPP link ** These are ignored if PPP_DEVICE is not #define'd */ #define PPP_LOCADDR IPADDR(192,168,0,216) #define PPP_PEERADDR IPADDR(192,168,0,217) /* ** Define a default gateway */ #define GATE_ADDR IPADDR(192,168,0,1) #endif /* __main_h_ */

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

1. Getting Started with MQX - Duration: 13 Minutes (English & Chinese) Setting up the Environment Architecting your Application Task Template Adding Ethernet Connectivity 2. Introduction to the MQX Platform - Duration: 20 Minutes (English & Chinese) Components of MQX MQX Features Task Scheduling Memory Management Synchronization RTCS Features USB Host /Device Directory Structure Task Aware Debugging 3. Writing Your First Freescale MQX™ Application - Duration: 1 hr Freescale MQX Software Solution Offering Introduction to Real Time Operating System (RTOS) Install and setup Freescale MQX MQX Application Demo LED Blinking Demo Client-Server 4. Implementing Ethernet Connectivity with the Freescale MQX™ RTOS - Duration: 45 min

The new Freescale MQX™ 4.0.2 release is now available on the www.freescale.com/MQX · Files available # Name Description 1 FSL_MQX_RELEASE_NOTES_4_0_2 Freescale MQX™ RTOS 4.0.2 Release Notes 2 FSL_MQX__FFS_RELEASE_NOTES_4_0_2 Freescale MQX™ FFS package 4.0.2 Release Notes 3 FSL_MQX_ATHEROS_RELEASE_NOTES_4_0_2 Freescale MQX™ Atheros Wifi package 4.0.2 Release Notes 4 Freescale MQX RTOS 4.0.2 Atheros Wifi package Atheros Wifi solution for MQX™ 4.0.2 5 Freescale MQX RTOS 4.0.2 FFS package NAND Flash File System solution for MQX™ 4.0.2 6 Freescale MQX RTOS 4.0.2 MQX™ Source code. Includes an RTOS, File System, TCP/IP and USB host/device software stacks. Does not require MQX™ 4.0 installation. · What is New? o AutoEVB Vybrid A5 and M4 Board support packages § Support for CortexA5 and CortexM cores of dual core Vybrid processor § Supporting standard set of IO drivers o Vybrid BSP extensions § RTC and NAND flash driver ported to Vybrid platform § MMU support extended by handling of 4KB memory block § Introduced new QuadSPI driver § CortexM4 boot option enabled. § Direct code execution from QuadSPI flash – XIP provided. Feature demonstrated in Vybrid QuadSPI bootloader. Introduced the first version of eDMA driver – the driver is experimental and will be further extended in the next MQX version. Documentation is not provided. o Kinetis SPI driver was updated to use the eDMA driver. o Hardware timer driver support extended to Systick and GPT HW modules. Kinetis and Vybrid BSPs updated to leverage the Hardware timer to provide MQX tick time. o RTCS Hardware checksum acceleration enabled in ENET driver (for TCP and UDP); the benefits are the increased throughput and a reduced processor loading. This option is enabled by default for the K60N512 platform. o HTTP server redesigned to provide a faster and more robust solution. The server API is simplified and changed to correspond to the RTCS standard. o New SMTP client functionality provided as a part of the RTCS network suite. The client offers a simple API for e-mail handling. The new RTCS Shell command “email” demonstrates its functionality. o The security_email, security_webserver, and security_telnet demo applications are removed from this release. Networking functionality is demonstrated in RTCS shell and httpsrv example applications. o Multicore Communication (MCC) library updated to version 1.1. Fixed the incorrect usage of cache macros in the mcc_send() function. · Known issues o For known issues and limitations please consult the release notes.

Hi All, The new Freescale MQX™ 4.0.2.2 patch release is now available on the www.freescale.com. · Files available # Name Description 1 Freescale MQX RTOS 4.0.2.2 Patch This patch release is based on the MQX™ RTOS 4.0.2 release and provides the solutions to software issues identified in the released version. This patch release applies to all the BSPs. · Patch Description This patch provides the software workarounds for the following issues identified in MQX 4.0.2 release: o ENGR00278434 § Vybrid ARM Cortex®-A5: The float context is not properly saved when a task is blocked. § Affected BSPs: TWR-VF65GS10, AutoEVB Vybrid o ENGR00273581 § A memory allocation problem occurs when the system is out of memory. § Affected all BSPs o ENGR00276466 § Events are sometimes triggered immediately after they are added. § Affected all BSPs o ENGR00279275 § RTCS connect failures via Dell router § Affected all BSPs · Known issues o For known issues and limitations please consult the release notes document.

The new Freescale MQX™ 4.1.0.1 patch release is now available on the www.freescale.com. · Files available # Name Description 1 FSL_MQX_4_1_0_1_RELEASE_NOTE MQX™ RTOS 4.1.0.1 Patch Release Notes 2 Freescale MQX RTOS 4.1.0.1 Patch This patch release is based on the MQX™ RTOS 4.1.0 release and provides the solutions to software issues identified in the released version. · Patch Description o This patch provides the software workarounds for these issues identified in MQX 4.1.0 release: § IPv6 ping issues · Crashes during a ping from an unknown host (IPv6 only). · An unhandled interrupt is generated when using the IPv6 ping. § TCP/UDP issues · IPv4 sends an MSS and window size with a SYN. A SYN without an MSS or with a window size zero is dropped by some firewalls. · IPv6 UDP close issue. IPv6 only reuses the same IP and port. · Fixed the incorrect RTCS_selectset() unblocking. § APP protocol issues · TELNET and Eth_to_serial peformance improvement. · HTTPSRV accesses data incorrectly in a session buffer while searching for SSI. · FTPSRV session close is missing a shutdown of a data socket. § BSP issues · The TWR-K70F120M BSP is unstable when the DDR2 SDRAM is in high use due to incorrect DDR settings.

The new Freescale MQX™ 4.0.2.1 patch release is now available on the www.freescale.com · Files available # Name Description 1 FSL_MQX_4_0_2_1_RELEASE_NOTE Freescale MQX™ RTOS 4.0.2.1 Patch Release Notes 2 Freescale MQX RTOS 4.0.2.1 Patch This patch release is based on the MQX™ RTOS 4.0.2 release and provides Software workaround for Errata e7166. This patch release applies to TWR-K70F120M and TWR-K60F120 board support packages. · Patch Description · This patch provides a software workaround for Errata e7166, which is relevant to the Mask 3N96B silicon. · Errata: SoC: SDHC, NFC, USBOTG, and cache modules are not clocked correctly in low-power modes. o Errata Description: SDHC, NFC, USBOTG, and Cache controller modules are connected to a single master port on the crossbar switch through a multiplexer. While the modules are still clocked in Wait mode, the multiplexer clock, which is connecting the modules to the crossbar switch, shuts off at entry into low-power modes. This prevents the three modules either to complete bus transactions during a low-power mode entry, or to start new bus transactions when the system enters Wait mode (even though the modules themselves remain clocked in Wait mode). Because the cache tag clock and data RAM clock are gated off in Wait mode, cache contents may be corrupted at low-power entry. · Software workaround provided: To resolve the Cache Controller issue, all bus master operations for each module should be complete before requesting system entry into any low-power mode. o To prevent cache corruption at low-power mode entry in idle task and low power manager, the WFI instruction is encapsulated in a special code sequence. The code sequence is executed from a memory location that is not cached (SRAM_L is recommended). Additionally, the code sequence must execute without interruption from the start of the code sequence to the WFI. If an interrupt occurs between the start of the sequence and the WFI instruction, MQX dispatcher code ensures that the code sequence is restarted from the beginning. · Known issues o For known issues and limitations please consult the release notes document.

Hi Community members: Here you can find the source code of a MSD ftp server, it is implemented on the MQX 4.2 using the FRDM-K64 and IAR 7.40.3. The USB storage device should be connected to the board and the board to a Ethernet network. In this demo, usb stick is mounted as a:/ You can upload or download files saved in the memory device. I hope this can be helpful. Best regards Daniel Original Attachment has been moved to: shell.zip

MQX Software Solutions Knowledge Base

MQX Software Solutions Knowledge Base

Discussions

TWR-MCF51CN-KIT MQX Lab FAQs - Updated

Introduction the BSP configuration file in MQX for Kinetis SDK

TWR-K21D50M lowpower MQX Patch for v4.0.2

How to add GPIO pins to the default BSP configurations

MQX Software Solutions Wiki

HOW TO GET THE CODE SIZE OF MQX 4.x PROJECT

MQX4.1/tools/ds-5/ds5_update_site.zip updated and new name "MQX Support.zip"

Video - Cloud Development Tutorial 5/6: Enabling Remote Firmware Update (K60)

Video - Cloud Development Tutorial 4/6: Building and Running the Kinetis K60 Tower Demo Sample

Video - Cloud Development Tutorial 2/6: iDigi Connector for MQX CodeWarrior Extensions Overview

MQX online training video

MQX Installation Guide

Freescale MQX™ 4.0.2 Release

Freescale MQX™ 4.0.2.2 patch release

MQX™ RTOS 4.1.0.1 Patch Release

pppdump01.hex

Freescale MQX™ 4.0.2.1 patch release

Video - Tutorial 1/6: Installing and Configuring the iDigi Connector for MQX

MSD FTP Server Demo

Como hacer una tarea en MQX.pdf