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!      

The content is to tell user how to add nand flash(MT29F2G08ABBDA) support in CW 10.3.

  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!

This project is an example of using the DSC CodeWarrior linker to place code in a different area of memory.  In this case, the FlexNVM flash block is used. The example uses three different methods in the linker command file to force specific code to a different memory segment, see examples below.  For more information on the linker syntax, see the manual installed with CodeWarrior at \CW MCU v10.6.x\MCU\Help\PDF\MCU_DSC_Compiler.pdf     This project was developed for the TWR-56F8400 Tower development board, using CodeWarrior for Microcontrollers v10.6.6.  The project was created using Processor Expert, and blinks an LED using the PIT timer interrupt.     The linker command file is located at \Project_Settings\Linker_Files\FLASH_SDM.cmd.Here are the key changes to the project:     MEMORY {         # Added .p_FlexNVM memory segment         .p_FlexNVM(RWX) : ORIGIN = 0x00068000, LENGTH = 0x00004000 }     # Added .FlexNVM_Code memory section .FlexNVM_Code : {   TI1_c.obj (.text) # Place whole source file in this section   OBJECT (FPE_low_level_init, cpu_c.obj) # Place individual function in this section   * (FlexNVM_code.text) # Place from section defined in source code, see main.c     } > .p_FlexNVM     and in main.c: #pragma define_section FlexNVM_code "FlexNVM_code.text"  RX #pragma section FlexNVM_code begin void main(void) {   /* Write your code here */ } #pragma section FlexNVM_code end

The rumors say that CodeWarrior (CW) can be turn into a faster and lighter tool to get optimal performance on some micros and processors. Such is the case of Power Architectures for e200 core. And guess what! Rumors are true and completely functional.   There is a document explaining how to make CW development suites faster and lighter, specifiying step by step the process to rock on programming power architecture features.   This document provides the two sets of options to produce optimal code generation. One set optimizes for speed; another set optimizes for size. You can choose from one of these or apply them both, getting a whole new experience on programming with this useful app note. Are you trying it already? CodeWarrior Build Tools Options for Optimal Performance on the Power Architecture® e200 Core  

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.    

CodeWarrior MCU 10.5 for Kinetis KV10   To setup your CodeWarrior development environment for Kinetis KV10 applications. Read the documents attached for download and installation instructions. Download and install the CW MCU v10.5  product, patch and service pack in the order specified:   Evaluation: CodeWarrior for Microcontrollers 10.5 (Eclipse, Offline) CW MCU v10.5 PEx MQX Lite Update 1.0.1 CW MCU v10.5 Kinetis KV10 75MHz Service Pack   the updates were just posted on the following URLs: http://www.freescale.com/webapp/sps/site/overview.jsp?code=CW_UPDATES_MCU_10_5

This Quick Start explains how to install service pack updater archive for your CodeWarrior software running on the Windows or Linux platform.   Support for new devices and/or updates can be added to the CodeWarrior Development Studio for Microcontrollers v10.x (CW MCU10.1) directly from the Internet (Online mode) or from a downloaded archive (Offline mode).   This document describes both the Offline and Online modes of updating CodeWarrior MCU v10.1 and a troubleshooting update. These instructions will show you how to manipulate that list to ensure that you can focus on the right URL for the CodeWarrior tools update.The topics covered in this document are:   • Updating Online: Lists the steps required to complete the update when you are connected to the Internet.   • Troubleshooting Updates:  Lists the troubleshooting updates.   • Updating Offline: Lists the steps required to complete the update when you are not connected to the Internet.   Start catching up with this updater archive!

The CodeWarrior Ethernet TAP probe is a tool that helps you develop and debug a number of processors and microcontrollers.   The Ethernet TAP probe uses advanced emulation technology to provide control of and visibility into your target system. Combined with a host debugger, it speeds the debugging process by letting you interactively control and examine the state of your target system.   The Ethernet TAP probe has these features: • Supports the following systems: PowerPC™ processors, StarCore processors, ColdFire® processors, 56800 Hybrid Controllers (processors and microcontrollers), ARM® processors, and RCF base-band controllers. (All products reference at Freescale web page!) • Supports all CPU core speeds. • Lets you control and debug software running in-target, with minimal intrusion into target system 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 system.   ...and many more of them! Get it updated today!!!      

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

The SmartDSP Operating System (OS) is a Real Time Operating System (RTOS) that, in addition to providing drivers for the MSBA8100 processor, also runs on the following StarCore DSP-based processors: • PSC9131 • MSC815x/MSC825x • MSC814x • MSC812x • MSC8101/3 • MSC711x   The StarCore CodeWarrior (CW) Development Studio includes SmartDSP OS royalty-free source code. Further, SmartDSP OS has a high-level Application Programming Interface (API) that lets users develop integrated applications for StarCore processors.   In SmartDSP OS, most functions are written in ANSI C. However, when needed, Assembly optimizes time-critical functions by maximizing StarCore’s multiple execution units.   Other SmartDSP OS features include the following: • small memory footprint ideal for high-speed StarCore processors • priority-based event-driven scheduling (triggered by user applications or HW) • dual-stack pointer for exception and task handling • inter-task communication using queues, semaphores, and events.   And this is just the beginning of what you can do with SmartDSP OS, get updated here and start coding with DebuggerGuys!

I just download FNET2.5.0, it can't debug it by CW10.4, it comes error message when I start debug "Could not open memory configuration file".   The CW10.4 works for other examples project.   Why?   Regards Sam

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

The purpose of this document is to help understand and create Flash configuration files for the Flash Programming interface.   A Flash Configuration file is an XML format file. Its file extension is always “XML”. It is possible to open and edit this file with any text editor. This file is a “handmade” file and is not created automatically with any tool.   Some microcontrollers can address the flash in multiple ways ─ banked and paged. Therefore, multiple overlapping devices can be defined for one microcontroller. Each of them is defined in its own Flash Configuration XML file.   The *.XML files contain microcontroller- dependent parameters and applets to handle internal flash modules. Applets are small programs which are loaded into the on-chip RAM. They will run at well-defined speed (depending on the microcontroller clock speed) and can collect data about the state of the memory modules, can control the memory modules (including erasing and programming). There are three applets for each flash module: http://pcdn.500px.net/4130499/a271bcea97e80e8d223b3338b27c9f116cdd98a3/3.jpg• INFO applet ─ Collects information about the module. • CONTROL applet ─ Controls and erases the module. • PROGRAM applet ─ Programs the module.   Parameters are passed to these applets at fixed memory addresses, which are relative to the workspace. *.XML files are written by Freescale and are delivered within the installation.   Keep learning and pull off your own applet with this Application Note!

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?  

CodeWarrior it's constantly updating and optimizing the way everything gets together to pull great things off. In this occasion I found some features updated within Processor Expert's Service Pack, and more specifically, for MCU v10.2.   The update is now available on Freescale's webpage, and the preview shows a list of derivatives that support Processor Expert, such as:   F84441 MC56F84442 MC56F84451 MC56F84452 MC56F84462 MC56F84540 MC56F84543 MC56F84550   And many,  m a n y  more!   In order for this Service Pack to work well, you must count with an update of CodeWarrior for MCU v10.2, which can be also found on Freescale's webpage ready to be downloaded.   Give it a try already! Updates here!

This document explains how to use the Flash Tool Kit to support additional flash devices on the Flash Programmer for CodeWarrior Development Studio for Microcontrollers V10.0 by creating new programming algorithms and support files.   This application note applies only to the external flash devices used with ColdFire V2/V3/V4 processors.     This document includes these topics.   • Create a flash device XML configuration file • Create new target task • Create external flash algorithm • Flash programmer examples • Create new flash utility • Flash utility examples • Troubleshooting flash programmer   The application note we are here suggesting provides you the necessary info to add devices to the FreescaleCodeWarrior Flash Programmer, along with some specifications that might be really useful depending on each CPU setup and the files and documentation that is required.   Many manufacturers use the same flash device algorithms, so it is likely that flashes can be programmed using the algorithms included with the CodeWarrior software. In addition, many manufacturers produce devices compatible with those of Intel, Advanced Micro Devices (AMD), or STMicroelectronics (ST).   Anyways, enjoy and keep finding interesting content with DebuggerGuys!   Adding Device(s) to CodeWarrior Flash Programmer for Microcontrollers V10.0

If you recently acquired the CodeWarrior Development Suite, you'll find this document very useful; it provides access and technical support to a multitude of CodeWarrior products.   This quick start also explains how to register your CodeWarrior Development Suite (Section A). Section Bexplains how to activate and install one of your products. Section C describes other items that come with your CodeWarrior Development Suite, and Section D discusses the available purchase options. Section E contains the Technical Support Certificate. As you may not have access to fully license all the CodeWarrior products, keep the following Web link handy, as it lists all the products in the differently priced levels of the CodeWarrior Development Suites (Basic, Standard and Professional). www.freescale.com/CodeWarriorSuites Check it out now! CodeWarrior Development Suite Quick Start