Freescale Semiconductor, Inc. Document Number: KSDKGSKDSUG User’s Guide Rev. 1, 04/2015 ___________________________________________________________________ Getting Started with Freescale MQX™ RTOS for Kinetis SDK and Kinetis Design Studio IDE 1 Overview This section describes the steps required to configure KDS to build, run, and debug MQX™ RTOS demo applications and necessary driver libraries provided in the KSDK framework. The Hello World demo application targeted for the TWR-K64F120M Tower System hardware platform is used as an example in this guide. Contents 1 Overview .................................................................. 1 2 Installing KSDK Eclipse update ................................ 2 2.1 Installing MQX RTOS Task Aware Debugger for GDB plug-in (TAD) .................................................. 3 3 Building MQX RTOS example project and libraries .. 5 3.1 Import example project and libraries to workspace .................................................................... 5 3.2 Build the libraries ............................................. 7 3.3 Build demo application..................................... 9 4 Run the demo application ....................................... 10 4.1 Run demo application .................................... 10 4.2 Using MQX RTOS Task Aware Debugger for GDB plug-in ................................................................ 13 5 Revision history ...................................................... 16
17
Embed
Getting Started with Freescale MQX™...Stack Usage – Displays information about interrupt and task stacks. Typically, a stack overflow is a root cause for vast majority of problems
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
address and status of synchronization objects created by the MQX RTOS system or
application. When a synchronization object is allocated either as a global or static variable in
the system, or as an array element or as a structure member allocated as global or static
variable, the TAD plug-in also displays the symbolic name of the object.
Figure 20: MQX RTOS Semaphores screen
Getting Started with Freescale MQX™ RTOS for Kinetis SDK and Kinetis Design Studio IDE, Rev. 1, 04/2015
16 Freescale Semiconductor, Inc.
5 Revision History
This table summarizes revisions to this document.
Table 1 Revision History
Revision number Date Substantial changes
1 04/2015 Kinetis SDK 1.2.0 release
0 12/2014 Kinetis SDK 1.1.0 release
Document Number: KSDKGSKDSUG
Rev. 1
04/2015
How to Reach Us:
Home Page:
freescale.com
Web Support:
freescale.com/support
Information in this document is provided solely to enable system and software implementers to use Freescale products. There are no express or implied copyright licenses granted hereunder to design or fabricate any integrated circuits based on the information in this document.
Freescale reserves the right to make changes without further notice to any products herein. Freescale makes no warranty, representation, or guarantee regarding the suitability of its products for any particular purpose, nor does Freescale assume any liability arising out of the application or use of any product or circuit, and specifically disclaims any and all liability, including without limitation consequential or incidental damages. “Typical” parameters that may be provided in Freescale data sheets and/or specifications can and do vary in different applications, and actual performance may vary over time. All operating parameters, including “typicals,” must be validated for each customer application by customer’s technical experts. Freescale does not convey any license under its patent rights nor the rights of others. Freescale sells products pursuant to standard terms and conditions of sale, which can be found at the following address: freescale.com/SalesTermsandConditions.
Freescale, the Freescale logo, and Kinetis are trademarks of Freescale Semiconductor, Inc., Reg. U.S. Pat. & Tm. Off. All other product or service names are the property of their respective owners.