Working with ColdFire Architectures for CodeWarrior is really simple and very useful. One little problem that many people has run into, is the relocation of code and data within the MCUs that are being used.   Maybe this will help those who have that issue, the Document I recently found explains the solution I now present.   It provides guidance for relocating code and data within the Microcontroller memory map. It also explains how to create new memory segments and sections by editing the CodeWarrior Linker Command File (LCF) for ColdFire Architectures.   The Linker Command File (LCF) along with other compiler directives, places pieces of code and data into RAM and ROM. You can do this by creating specific sections in the LCF and then matching them to the source code using pragma directives.   Other than making a program file from your project's object files, the linker has several extended functions for manipulating program code in different ways. You can access these functions through commands in the linker command file (LCF).   Linker command files consist of three kinds of segments, which must be in this order: • A memory segment, which begins with the MEMORY{} directive, • An optional closure segment, which begins with the FORCE_ACTIVE{}, KEEP_SECTION{}, or REF_INCLUDE{} directives, and • A sections segment, which begins with the SECTIONS{} directive.   LCF only gets more interesting, so get the Document read now!

How to install and use eGit plug-in in CodeWarrior

How to log an issue in Case system instead CRM (Service request)?     After the merge of Freescale and NXP, technical support cases are answered in a different system. To submit your case into the new system, please follow below steps:    1) Go to http://www.nxp.com/support/sales-and-support:SUPPORTHOME.    2) On the bottom of the page under Submit New Issues, click Hardware & Software.    3) Register with your business email to access NXP technical online support.    4) A verification email will be sent to your account. Click the link embedded in that email to verify your access.    5) On the NXP online support page, select Contact Support from the top menu and click “submit a new case” to start the process.   Attached you will find a video explaining the process to follow.

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.

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!

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.   

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.

This document shows a general way how to preserve memory range using target task in CW10.6.   I am using k64 freedom board and Segger J-link in my project as an example. K64 freedom board use MK64FN1M0 MCU which has 1 M size flash.  In my project I divide the flash into two areas in the link file as below:   /* Specify the memory areas */ MEMORY { m_interrupts       (rx) : ORIGIN = 0x00000000, LENGTH = 0x198 m_cfmprotrom       (rx) : ORIGIN = 0x00000400, LENGTH = 0x10 m_text             (rx) : ORIGIN = 0x00000800, LENGTH = 512K m_text2            (rx) : ORIGIN = 0x00080800, LENGTH = 512K - 0x800 m_data         (rwx) : ORIGIN = 0x1FFF0000, LENGTH = 64K                  /* Lower SRAM */ m_data2        (rwx) : ORIGIN = 0x20000000, LENGTH = 192K                 /* Upper SRAM */ } m_text2 is the memory area that I am trying to keep it from being erased while downloading the application to m_text memory area. Here are the steps to do this using target task in CW10.6. Add a target task view by clicking Window -> Show View -> other from menu bar, then select Debug -> Target Tasks view in the popup window. From the Target Tasks view, select “Import” from the context menu. Then select the flash (.xml) file for your target device. In this case I need to select MK64FN1M0.xml file. After that you will see a “MK64FN1M0” task in the list. Double click the task name, you will see there are two actions (“Erase” and “Program and Verify”) in the “Flash Programmer Actions” view.   The default Erase action will mass erase all flash, so I remove this action by unchecking the “Erase” action. I can add erase action in “Program and Verify” action later. Double click the “Program and Verify” action. In the popup dialog, check “Erase sectors before program” option. Check “Restrict to Addresses in this Range” option, and then specify the address range you want to program. The data/code out of this range will be preserved (will not be erased or changed). Click “Update Program Action” button to update the settings of this action. Move to Debug configurations window by clicking Run -> Debug configurations from Menu bar. Select a debug configuration, in this case I select the run configuration for Segger J-Link. Select Download tab which is under Debugger tab. By default, Standard Download will be executed and all the flash will be erased. As I am going to execute target task in this case, so uncheck “Perform Standard Download” and then check “Execute Tasks”. Click “Add” button to add a task. In this case I add K64F1M0M12 task which I created in previous step in target task view. Click “Debug” button, the application will be downloaded to flash but preserved area which was not specified in restrict flash range will not be erased. You can check this from memory view.   With the above steps, you can preserve a specified flash range while downloading application. I am using Segger J-link in my project as an example and the steps also work for other tools like P&E Multilink and USB Tap.

T1040 is new to all the customers. The ecosystem is still not mature in this moment in Jan'2014 The note is for someone who is using Codewarrior PA10.3.3 for T1040 platform board bring up or debugging on this moment. if you have problem to connect T1040 platform with Codewarrior, the document might help you.

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.

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

If you would like to migrate a project which is created by classic CW to eclipse CW, this file illustrates one of the ways to import PE beans to eclipse IDE manually. Test environment: 56F8037 in CW for DSC V8.3, CW for MCU V10.3, CW for MCU V10.4.

This is a test for 56F800EX new additional 32bit multiplication instructions on CodeWarrior V10.3/V10.5/V10.6.

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!

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.

Did you know that the CodeWarrior IDE includes assemblers that support several specific processors? Well, it does, and for you, codewarrior programmer this is one of its many cool tools to develop great code!   Today I found this manual that helps us out and explains the corresponding assembly-language syntax and IDE settings for these assemblers, in this case, thesyntax for assembly-language statements that the CodeWarrior assemblers use.   These explanations not only cover simple statements, they also include macros and directives!   You might be thinking, "dude, all the assemblers share the same basic assembly-language syntax!". I won't argue that, it's true, but instruction mnemonics and register names are different for each target processor.   To get the most from this manual, you should be familiar with assembly language and with your target processor, so I'd recommend you to start getting into this whole low-level programming style!   Unless otherwise stated, all the information in this manual applies to all the assemblers, enjoy!   CodeWarrior Development Studio for Microcontrollers V10.x ColdFire Assembler Reference Manual