Greetings, The third update for CodeWarrior for MCU V10.6 is available. This update includes the previous 1.0.0 and 2.0.0 updates, and applies to CodeWarrior for MCU v10.6 only. New device support: •             S12Z: S12ZVC96, S12ZVCA128, S12ZVCA192, S12ZVCA64, S12ZVCA96 •             DSC: MWCT1012, MWCT1212, MWCT1111 Updated support for silicon revisions: •             Kinetis K Series: K11DN512A,  K11DX128A, K11DX256A, K21DN512A, K21DX128A, K21DX256A, K21FN1M0A, K21FX512A See attached release notes for further details.   There are two ways of installation: Offline or Online. Offline installation is recommended as the size of the installation files is up to 900 MB (depending on the installed architectures).   Offline Installation: Go to https://www.freescale.com/cwmcu10 Click on the 'Downloads' tab and select the product download: Select 10.6: Download the Update 3: From CodeWarrior for MCU10.6, select the menu Help > Install new Software and select the downloaded archive file: Check the MCU 10.6 Updates and go through the installation with 'Next >' button. Restart Eclipse as prompted.   Online Installation In CodeWarrior, use the menu Help > Install New Software Use the following Eclipse update site: http://freescale.com/lgfiles/updates/Eclipse/MCU10_6/com.freescale.mcu.updatesite Install the update Restart CodeWarrior as prompted   Full release notes are attached to this document.

The StarCore assembly language tools consist of an assembler, a linker, an archiver, and several utilities.   Freescale's DSP (Digital Signal Processors), built on StarCore technology, offer high-performance programmable devices for baseband, aerospace, defense, medical and test and measurement markets. The StarCore DSP portfolio provides customers with fully scalable and flexible solutions to get to market faster. Combine that with the low power and low cost of the StarCore DSPs and they are the ideal solution for your next design.   Today we're bringing up the Assembler User Guide that contains the walk-thrus of StarCore DSP Architectures on CodeWarrior Development Studio. This manual explains the assembly language tools for the StarCore DSP cores. As it is mentioned somewheren within the User Guide, the StarCore assembler architecture is compiler-friendly, so you can combine it with a compiler that generates exceptionally compact code.   With this great advantage, you can write applications in C, for example, yet achieve code density and high performance comparable to that of hand-coded assembly programs!   Get a glance at this manual and start using CodeWarrior for StarCore DSP today!   Don't be afraid and ask any questions to DebuggerGuys

There is a problem in programming 56F8323 with CodeWarrior 10.6 and USBTAP.  The attached document gives a workaround before the update release is available.

Hey there! Are you familiar with this device shown on top? If you find it similar to the CodeWarrior TAP probe then you are ringing the right bells.   The magic thing of this innovative device is that you can debug systems remotely or more effectively share a single system with multiple developers. When a shared system is not needed, CodeWarrior TAP connects directly to the developer’s workstation with a single USB cable. Power is supplied by the USB port so that no additional cables are required!   This means that the TAP also enables Freescale target system debugging via a standard debug port (usually JTAG) while being connected to your workstation via Ethernet or USB. For this reason this device can also be found under the name of probe, JTAG probe, JTAG emulator or target probe.   These are some of the great features offered by the TAP: Allows either USB or Ethernet (10/100 ) host connection for the developer workstation USB powered, even when using Ethernet Low cost removable probe tips sold separately Supports debugging via JTAG interface Automatically supports system voltage levels from 1.2 to 3.3 Supports all available core speeds and voltages for supported Freescale processors As a convenience feature, the CodeWarrior can connect to a target systems serial port allowing telnet access to a remotely located system and control of the U-boot program.   Keep finding more features and applications within the Fact Sheet If you'd like to dig further into the TAP world, you can also find The User Guide equally useful!      Please note that this device is not up for sale (just yet!). Regardless, Freescale is accepting pre-orders for CodeWarrior TAP now with shipments planned in late October, and DebuggerGuys will keep you informed on this! Don't hesitate on asking beyond!      

  It's true, coding isn't always an easy job, specially when it comes to tools you are not familiar with. I'm not an expert atCodeWarrior, but I really enjoy developing embedded systems or at least parts of them. Obviously, there will be a bunch of error messages depicting on the IDE at the beginning. (great feature for some, altough C and C++ don't show lexic nor command mistakes right away).   While trying to pull off a set of code lines I had been working on, there usually come along a bunch of funy error messages deploying, such as  "illegal 'friend' declaration" or "function has no prototype".   Well, I recently found an updated  BUILD TOOLS MESSAGE REFERENCE MANUAL at Freescale's web page. The Build Tools Message Reference Manual documents the messages generated by your CodeWarrior build tools. This information helps you fix problems the build tools encounter as they build your projects. Note that this manual documents just those messages that are generated by compiler, assembler, and linker.   It shows a broad list of error messages and how to fix them, so go check it now, useful as it can be!

We are now showing a getting started guide from Freescale. This manual introduces you to the interface ofCodeWarrior for Microcontrollers V10.x. It describes basic components of the Microcontrollers 10.x IDE and the CodeWarrior development process.   You can check the CodeWarrior quick reference guide or visit freescale webpage for further info!   This manual also: • Provides an overview of Microcontrollers 10.x and Eclipse IDE. It also provides system requirements for installing Microcontrollers 10.x.   • Describes stages involved in developing an application using CodeWarrior IDE.   • Provides an overview of the Microcontrollers 10.x interface and its components, and describes how to work with the different components of the Eclipse interface.   • Describes how to create and debug projects in Microcontrollers 10.x.   What are you waiting for? Check out this manual now!

There have been some questions around here about Freescale's CodeWarrior Tool, it's features and what it's possible to do with it (and there are tooons of things!!!).   Regarding the last post about MCU V10.x, i found this FAQ guide that can be really useful, specially if we are beginners or we'd like to get everything clear and loud. Hope it's as useful to you as it is for me!!!   This FAQ Guide lists most frequently asked or most anticipated questions about Microcontrollers V10.x. In this document, the FAQs are divided into various categories based on the Microcontrollers V10.x feature they are associated with, such as Installation, IDE, Editor, Project Management, Project, Compiler, Assembler, Linker, Debugger, Debugger Shell, USBTAP, Ethernet TAP, and Profiling and Analysis Tools.   CHAPTER DESCRIPTION IDE and Installation Lists IDE related FAQs Project Management Lists project management related FAQs Project Lists project related FAQs Compiler Lists compiler related FAQs Linker Lists linker related FAQs Debugger Lists debugger related FAQs Debugger Shell Lists debugger shell related FAQs Profilling and Analysis Tool Lists profiler related FAQs   Take a look here!      

The documentation regarding Power Architecture Processors (version 10.1.1) already shows the great features that Code Warrior offers to this embedded-systems develompment tool kit powered for both Windows and Linux users. This release note provides important information for users of CodeWarrior Development Studio for Power Architecture 10.1.2, upgrading and expanding the Quick Start sessions and improving its content to help us programmers with this great developing suite, from its installation to the final process of debugging and testing our work!   If you are into programming with CodeWarrior suites, this document, (just updated, by the way!)  it's really important for you to become familiar with this release‟s supported targets, new features, errata with workarounds, and other useful information. The new features described in this document are new relative to the last general availability release, CodeWarrior for Power Architecture 10.1.1.   Get to read the document here! and if you have further questions, I'll be happy to help out! You can always visit Freescale for further information!

The CodeWarrior USB TAP probe is a cost-effective tool that helps you develop and debug a number of processors and microcontrollers. This chapter introduces you to the USB TAP probe.   The USB TAP probe uses advanced emulation technology to provide control of and visibility into your target system. Combined with the CodeWarrior IDE, the USB TAP speeds the debugging process by letting you interactively control and examine the state of your target system.   The USB TAP probe has these features: • Supports the following systems: Power Architecture processors, StarCore processors, 56800 Hybrid Controllers (processors and microcontrollers), and ColdFire™ processors. • Supports all CPU core speeds. • Lets you control and debug software running in-target, with minimal intrusion into target operation. • Lets you debug code in cache, ROM, RAM, and flash memory. • Provides high performance: – Split-second single-step execution. – Capable of download speeds greater than 12 MB per minute from host to target.   ...and so much more!!! Get into the USB TAP probe world to make it easier and faster! Watch how over here.    

Some customers often ask where or how to download previous version CodeWarrior(CW), for example the CW for HCS12Z(X) v5.1, the CW for MCUs v10.5 or some patch packages. It is really hard to find sometimes. So I write this document to introduce how to download them step by step. Also we can refer to this process  to download other old version for Kinetis Design Studio(KDS). This DOC mainly includes two parts: - How to Download Previous Version CodeWarrior: -  How to Download Patch for  CodeWarrior: About the detail steps please check the attachment. BR Alice

Standalone Programming is widely used when user doesn’t need a debugger for programming in CodeWarrior 10. Thus people only uses elf/s19 file to program target without using project and source files. There is a very famous article written by Erich Styger regarding using “Flash File to Target” as a standalone programmer for target programming. https://mcuoneclipse.com/2012/08/02/standalone-flash-programmer/   Besides this method, Flash Programmer Task is also good for standalone programming.  As I know some customers prefer to use this method because it can also do checksum, dump flash,etc during programming. I will introduce how to utilize Flash Programmer Task step by step in the following for brainstorming. This article is based on CodeWarrior 10.6.4 and FRDM-K64 board, but the method is same for all Kinetis,HCS08,HCS12Z,etc devices   For detail, see attached article and video.

This manual explains how to use the CodeWarrior Development Studio tool set to develop software for Freescale StarCore DSP processors. Following now, we present you an overview of this manual as a little introduction to the CodeWarrior development tools and development process.   Before using the CodeWarrior IDE, this targeting manual recommends you to read the developer notes. These notes contain important information about last-minute changes, bug fixes, incompatible elements, or other sections that may not be included within the manual.   Programming for StarCore processors is much like programming for any other CodeWarrior platform target. If you have not used CodeWarrior tools before, start by studying the Eclipse IDE, which is used to host the tools.   If you are an experienced CodeWarrior user, note that the CodeWarrior Development Studio for StarCore DSP Architecture environment uses the Eclipse IDE and the interface is substantially different from the “classic” CodeWarrior IDE. But there's no reason to feel lost! The manual will give you the walk-thrus to become a skilled CodeWarrior programmer!   Start exploring the possibilities with this amazing development tool, what are you waiting for?  

This document contains an overview of what is the Codewarrior Linker File for Kinetis devices and how to edit it to relocate code and data. It also explains how to create a debug sesion out of external RAM.   Regards, Carlos

CodeWarrior Development Studio for StarCore DSP Architectures Quick Start for the Windows® Edition   The CodeWarrior software it's a very resourceful tool to program a wide variety of MCUs and Processors, and its flexibility makes it installable almost in any operative System. This Quick Start explains how to install the CodeWarrior software on a Windows PC, for example.   Also, the document explains how to use this software to create, build, and debug a simple StarCore DSP project.   In the procedures that are explained within this document, advanced users can use numbered steps. But don't feel bad, novices, there are plenty of detailed instructions that can be easily followed and understood by anyone, provided by substeps.   Enjoy and start programming with CodeWarrior on your PC!

Interrupt technology is an important method to improve the efficiency of real-time CPU. In Kinetis, interrupt vector table is allocated in lowest ROM address of whole memory.   However in some application, we need move vector table to other address. A typical usage is developing boot loader code. The boot loader code occupies the first region of the FLASH memory (the lowest memory address space starting from 0x0000000). This placement moves at the beginning of the available memory space and it is necessary to shift this address in the user application.   The CM0+ and CM4 core adds support for a programmable Vector Table Offset Register (VTOR) to relocate the exception vector table, which is not existing in Freescale 8/16bit MCU. This device supports booting from internal flash and RAM. Kinetis supports booting from internal flash with the reset vectors located at addresses 0x0 (initial SP_main), 0x4 (initial PC), and RAM with relocating the exception vector table to RAM.   for detail, see attached document and demo project made under CW10.6, and KDS

This reference manual describes the contents of the Embedded Warrior Library for C++. The C++ Standard library provides an extensible framework, and contains components for: language support, diagnostics, general utilities, strings, locales, containers, iterators, algorithms, numerics, and input/output. Additionally, EWL C++ offers extra facilities forinput/output, threads, and other components. Libraries included within this reference manual are:   The EWL C++ Library Overview of thismanual describes the language support library that provides components that are required by certain parts of the C++ language, such as memory allocation and exception processing.   “LanguageSupport Library” discusses the ANSI/ISO language support library.   Diagnostics Library elaborates on the diagnostics library that provides a consistent framework for reporting errorsina C++ program, including predefined exception classes.   General Utilities Libraries discusses the general utilities library, which includes components used by other library elements, such as predefined storage allocator for dynamic storage management.   Strings Library discusses the strings components provided for manipulating text represented as sequences of type char, sequences of typewchar_t, or sequences of any other “character-like” type.   Localization Library covers the localization components extend internationalization support for character classification, numeric, monetary, anddate/time formatting and parsing among other things. EWL_Utility utilities used for non standard headers.   Overview of EWL C++ Debug Mode describes the Embedded Warrior Library for C++  debug mode facilities.   Hash Libraries describes nonstandard “hash” libraries.   Metrowerks::threads is a reference to threads support in the Embedded WARRIOR  Libraries.   EWL std::tr1 is a reference about items that are proposed for inclusion in the Embedded Warrior Library   C++ Switches, Flags and Defines is a chapter on the various flags that you can use to create a customized version of the EWL C++ Library ...and many more resourceful subjects are contained!   Get ready to update your CodeWarrior Development Tools for EWL C++ programming! View manual here!

To start expanding horizons in CodeWarrior, a great portfolio to use is definetely ColdFire, which houses 32-bit MCUs solutions.   Enabled by a vast ecosystem of development tools and design resources, development on 32-bit gets as easy as it can be!   After having the proper guidance on ColdFire projects, one of the most important things to do is to optimize devices as for speed and size. Not saying that it is completely necessary, but if you already have it, why not using it?   The following documentation is a complete guide to configure compiler options for optimal performance of ColdFire devices, and provides two sets of options to do this: One set optimizes speed; Another set optimizes code size.   Besides, the document contains two main forms of pulling this optimizations off: • MCU 10.x Eclipse IDE • Command Line   Both ways are functional if you want to configure compiler options for speed or size, it's up to you!   It's easily and quickly done, get a try of the application note here! Configuration