In some of the post I've talked about the many advantages that the combination CodeWarrior-Eclipse can bring up. One of those was the installation on service Packs in a friendlier way than when it's done with the classical view of CodeWarrior. That is why I introduce today the Installing Service Pack for CodeWarrior Tools Quick Start   This Quick Start, in case you are choosing the hard and equally great way to do your own thing with CodeWarrior, it explains how to install a service pack or an update for your classical version of the software running on the Windows platform.   It shows step by step how to do this manually and correctly, preventing you from having an IDE full of stuff you don't even want to use.

CodeWarrior Development Studio for HCS12(X) Microcontrollers (Classic IDE) v5.2 has been released for several months.   Recently, since v5.2 release, I have received many questions from customers. These questions are almost similar: how to add the missing devices back to my CodeWarrior v5.2 ?   From my side I think there is one workaround if a specific device has a service pack. For detail, please see attached document.

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!

The following is a list of our documents in regards to developing MCU on CodeWarrior platform.   If you need to log an issue in Case System,  or obtain a license for your CodeWarrior product, please refer to:  How to log an issue in Case system instead CRM (Service request - not used anymore)?   1.  CodeWarrior Common Feature   1.1 Reversion Release History CodeWarrior for MCU V10.6 Update 3.0.0 available New CodeWarrior for MCU v10.6.4 available CodeWarrior v10.6.4 Update 5 available   1.2 IDE and Installation How install (or check availability) patch and update under Eclipse ? How to solve “IDE failed to start …” message - Classic version on Windows OS (most of the time 64 bit as Win 7 or Win 8.1)   1.3 Project Management Convert a Processor Expert project from linked mode to standalone mode   1.4 Build Tool Chain (Assembler, Compiler, Linker) Linking and compiling with CodeWarrior Classic - How to use dashboard (Jenkins) to build a CodeWarrior project?   2. CodeWarrior for Kinetis   2.1 Board Bring-up  How to work KV10 with CW10.5   2.2 RTOS  MQX applications...new at this, too?~   2.3 Build Tool Chain (Assembler, Compiler, Linker) How to fill unused memory for CW for 8/16bit and kinetis Gnu. Interrupt Vector Redirection Method in Kinetis Relocating Code and Data Using the CW GCC Linker File for Kinetis Relocate Code (configuration linker files) - CW10.6 - Kinetis Extended inline assembly with GCC in CodeWarrior   2.4 Programmer and Debugger Preserve Memory Ranges In CodeWarrior v10.6   3. CodeWarrior for MPC5xxx   3.1 Build Tool Chain (Assembler, Compiler, Linker) Generate CRC value for MPC56xx in CodeWarrior for MCU v10.6.4   3.2 Programmer and Debugger Debug code using CodeWarrior 10.5 Flash two .elf files using CodeWarrior 10.6   4. CodeWarrior for DSC   4.1 Project Management How to migrate PE project from Classic CodeWarrior to Eclipse CodeWarrior How to solve PE bean migration for 56F84xxx in CodeWarrior V10.3   4.2 Build Tool Chain (Assembler, Compiler, Linker) To use 56F800EX new additional 32bit multiplication instructions on CodeWarrior V10.3/V10.5/V10.6.   4.3 Programmer and Debugger Workaround for programming 56F8323 in CodeWarrior v10.6 debugger   4.4 External Tool Integration Integrate Quick Start 2.6 for DSC with CodeWarrior 10.6.4 Using TWR-56f8400 board with FreeMASTER via USBTAP interface   5. CodeWarrior for Coldfire   5.1 Build Tool Chain (Assembler, Compiler, Linker) Relocating code with CodeWarrior CodeWarrior and ColdFire get optimized!   5.2 Programmer and Debugger Problem with Multilink Rev C  - not running after MCU V10.6 Update3 installed & CW for MCF V7.2   6. CodeWarrior for 8/16bit MCU   6.1 IDE and Installation CW MCU v10.5 for 8bit MCU Banked Memory Patch Installation   6.2 Build Tool Chain (Assembler, Compiler, Linker) Classic - Is it possible (How) to use HCS12 on Eclipse? How to fill unused memory for CW for 8/16bit and kinetis Gnu.

Processor Expert offers static code which allows choosing standalone mode and linked mode for each project. You can select either linked mode or standalone mode for static code during project creation. But what if you want to change mode for a created project? With the below steps you can learn how to convert a project from linked mode to standalone mode in CodeWarrior v10.6.   1. From the original linked mode PEx project, remove the “static_code” folder. 2. Close the project in CW10.6. Navigate to the top folder of the project, then open the ProcessorExpert.pe file using text editor software, for example, windows notepad. 3. Seach the key world “LINKED” in the ProcessorExpert.pe file. Replace the line <ProjectStaticFilesGenerationMode>LINKED</ProjectStaticFilesGenerationMode> with <ProjectStaticFilesGenerationMode>STANDALONE</ProjectStaticFilesGenerationMode>   4. Remove the .ProcessorExpert.g_c file and .ProcessorExpert.g_x file under the top folder of the project. 5. Then re-open the project in CW10.6. Click “Generate PEx Code” button from Pex components view.   You will see a “static files track changes” dialog pop up. Click OK, PEx will create static files under the project folder. 6. You will see that IO_Map, PDD and System files have been generated under Static_Code folder.   Unfortunately PEx doesn’t generate Peripherals files automatically. So you need copy the Peripherals files to the project manually. For dsc 56F82748 MCU in this case, the peripherals static files are located under the “C:\Freescale\CW MCU v10.6\MCU\ProcessorExpert\lib\56800\pdd2\MC56F82748VLH\perihperals” folder on my machine. You can simply drag and drop the folder to the project.     Then select “Copy files and folders” option and click “OK”.     7. Now you can see that the static files are placed under the project folder now. You can verify this by checking if there is an arrow mark on the static file icons. Alternatively, you can also check by right clicking on a static file and then click “Show In Windows Explorer” item from the context menu. The stitic files should be located under the project folder.   With above tricks, you can also convert a project from standalone mode to linked mode easily.

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!

Taking TWR-56F8400 as an example, this document shows how to create a project in CodeWarrior v10.6 and get its global data visualization in FreeMaster through USBTAP. This example shows three global variables (test8, test16, test32) in ‘Variable Watch Window’ of FreeMASTER , displays the changing curve of test8 in scope, and displays test16 as curve in Recorder.   

Hello!   I'm currently trying to adapt a MC56F8356 Project on the Codewarrior 8.3. When I try to download my programme into the DSP,I failed with a outcom like this picture uploaded.   I doubt it's the hardware circuit problem,but I do not know where the problem is.   Can you tell in what situation this may be ?   Thank you for help! YANQING YU

Actually, this document here shows the quick starts for any freescale's V10, but specifications are depicted for V10.2 Microcontrollers. This quick tart also explains how to install the CodeWarrior Development Studio for Microcontrollers V10.x software (totally necessary) on Windows and Linux operating systems, and how to use the CodeWarrior IDE to create, build, and debug a project.   It also includes special cases, like how would it be done for Special product Editions, hardware and software specifications and further notes that will make the "creating something new" process easier! Not only a challenge, but a fun one!   Want to get it started already? QUICK STARTS    

Scanboard is a tcl proc within the IDcode.tcl script that can be used as a quick sanity check for basic JTAG connectivity. This routine will return the JTAG ID codes for devices on the scanchain and if they are known Freescale devices (at the time the script was last updated) the core indexes will also be displayed for CodeWarrior project configuration. IDcode.tcl is included automatically during the CodeWarrior installation but updates may be available.   This script is executed within the CodeWarrior Connection Server (CCS) and not the CodeWarrior IDE itself where ccs is the conduit that the CodeWarrior Debugger talks to the TAP hardware. CCS can also be used standalone but this is not a supported mode and the use of it is not documented.   On a windows machine start ccs via the Start menu for the CodeWarrior installation you wish to use.   i.e. Start → All Programs → Freescale CodeWarrior →CW for Power Architecture v10.2.1→ CodeWarrior Connection Server   CCS starts iconized in the task bar so double click on the icon to display the ccs console window   On a Linux machine start ccs manually via the ccs executable location within the CodeWarrior installation directory ($CW_INSTALLDIR)/PA/ccs/bin/ccs   i.e. /usr/local/Freescale/CodeWarrior_PA_10.2.1/PA/ccs/bin/ccs Once the CCS console is available the IDcode.tcl file must be brought into the tcl environment via the source command. Beware that on a Linux system the file name is case sensitive.   % source IDcode.tcl   The script will automatically query the host system to determine if there are any available CodeWarriorTAP or USBTAP devices connected via USB which can be used for a remote connection. Specify the connection option that is attached to the target system. For example to configure the connection to be a CodeWarriorTAP on the network select 2 and then enter the IP address or the CodeWarriorTAP name if it is in the host table or can be found within the DNS tables.   It is also possible to predefine custom remote connections via the DefinedCCSConnections.tcl located within the …/ccs/bin directory as well. See this file for details. Once the remote connection has been specified the script will the automatically execute the scanboard proc and attempt to read back the IDcode(s) available on the JTAG scanchain.     In this example the CodeWarriorTAP is connected to a system that has a T4240 processor and displays the IDcode for this device. If there had been multiple processors available on the scan chain each device would have been identified and displayed.

Sometimes we don't use external debugger but OpenSDA on-board . The debugger controller clock setting need more attention because of slow debug by OpenSDA on-board. if you set the bus clock too high to make step by OpenSDA. The Non error will report at the stage of download(Fig2) and pause, even stop(Fig1). Fig 1  Pause and stop error  Fig 1  Download error  when you encounter. you can set debugger follow some steps. 1 open debug configurations-Target setting-Edit... 2 In Edit you need remove the selection of 'use bus clock as debug controller clock source ' and then reopen the CW and project debug fine works. Enjoy!

The StarCore assembly language tools consist of an assembler, a linker, an archiver, and several utilities. With the simulator user guide provided for Freescale's DSP (Digital Signal Processors), it's possible for us CodeWarrior users to know which are the software simulation models released with CW Development Studio for StarCore Architecture.   This guide contains a list of simulator models supported by DSP, • Instruction Set Simulators (ISS) • Performance Accurate Simulators (PACC) • Instruction-accurate ISS • Unified simulators   It also contains the requirements needed to launch the simulator system, and of course, all the instructions to pull the simulation off! Take a look at it, it's great the amount of things you can do with this! CodeWarrior Development Studio for StarCore DSP Architectures Simulator User Guide

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

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!