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

Tutorial 6 of 6 for the iDigi Connector for MQX: Adding Remote Configuration Support (6 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

Que tal, Este documento es para toda persona que comienzan a trabajar con MQX . El documento describe como crear una tarea y como usar el driver LWGPIO. Esta escrito en español pensando en nuestros clientes de habla hispana. Saludos Sol

MQX ppp communication. Could be imported to wireshark as hexdump.

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.

Rev0.1 - 8/28/2012 Adding to the patch at TWR-K21D50M lowpower MQX Patch for v4.0.2, this updates the MQX BSP and lowpower example to add VLPS mode. The example works the same as the default lowpower example, except after waking from LLS, the application immediately enters VLPS.  It uses the LPTMR to wake after 10 seconds, and returns to RUN mode and restarts the example.  Because the transition is immediate from the user perspective, the user will press the switch to enter LLS mode, after 10s the MCU will wake, turn on the blue LED, enter VLPS, wait another 10s, wake, turn off the blue LED, return to RUN mode and resume printing to the terminal.  There is no text printed to the terminal between LLS and VLPS to show a quick transition. This patch covers several files to enable VLPS mode in the twrk21d50m BSP, and modifies the lowpower example. 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 in the release provided does not include support for VLPS. To use this patch, copy the patch directory into the MQX v4.0.2 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. LowPower Example main.c Modified as described above to add transition into VLPS mode bsp_cm.c Added case for VLPS mode for clock mode transition init_lpm.c Added mode to LPM_CPU_OPERATION_MODES[] for LPM_OPERATION_MODE_VLPS init_lpm.h Added mode LPM_OPERATION_MODE_VLPS to enumeration LPM_OPERATION_MODE init_sci.c Added settings for mode LPM_OPERATION_MODE_VLPS to the _bsp_sciX_operation_modes arrays for all the UARTs in the BSP lpm_smc.c Added mode DOM_VLPS to LPM_PE_OPERATION_MODE_MAP[] Disabled SPI0 clock gate when entering stop mode, otherwise stop entry is aborted.  Re-enabled clock gate 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. Disabled the SysTick interrupt for the 5ms RTOS tick before entering stop mode, and re-enabled after waking up.  Without this, the example was entering VLPS mode fine without the debugger, but with the debugger the SysTick interrupt was causing VLPS entry to abort. 

Hi, Many people has been asking about migrating from MQX RTOS to MQX RTOS for KSDK. Such guide is now available in the following link: http://www.freescale.com/files/soft_dev_tools/doc/support_info/MQXKSDKPUG.pdf?fsrch=1​ If you need to create a new MQX RTOS for KSDK project please note that there is not a New MQX for KSDK Project Wizard, therefore it is necessary to create it manually. You can find a guide in the link below. How To: Create a New MQX RTOS for KSDK Project in KDS Best regards, Carlos Musich Technical Support Engineer

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.

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

The new Freescale MQX™ 4.1 for TWR-K64F120M release is now available on the www.freescale.com ·         Files available # Name Description 1 FSL_MQX_TWRK64F120M_RELEASE_NOTES Freescale   MQX™ RTOS 4.1.0 TWR-K64F120M Release Notes 2 Freescale   MQX RTOS 4.1.0 for the TWRK64F120M Includes   an RTOS, File System, TCP/IP and USB host/device software stacks. Does not   require MQX™ 4.1 installation. ·         Target HW board o   TWR-K64F120M ·         New features o   PSP support for the K64F120M Microcontroller o   BSP for the TWR-K64F120M tower system module o   Standard set of I/O drivers supporting the K64F120M peripherals including: §  LWGPI/O driver §  Serial interrupt and polled driver §  DMI SPI driver §  I2C interrupt and polled driver §  ADC §  LWADC §  Flash Driver §  RTC Driver §  PIT Timer §  LPT Timer §  SD card driver §  SDHC §  FlexCAN §  SAI §  ENET o   USB Host and Device drivers and stacks o   Example and demo applications demonstrating MQX, USB, RTCS, and MFS usage o   RTCS TCP/IP stack o   MFS file system o   Shell command line interface ·         Known issues o   For known issues and limitations please consult the release notes.