In many of user applications we use a CRC/checksum to verify that the code/flash on the target is not modified. For this, not only the code/data in flash counts, but as well all the unused gaps in the memory map. Instead to leave it up to the flasher/debugger (which usually erases it to 0xFF), I want to fill it with my pattern. For example 0xAA.   How to implement? There may be several ways,  but I think the easiest way is to modify linker file.   the linker file structures are different for different MCUs.   For example, CW for 8bit/16bit and Coldfire V1 uses PRM file;  while CW for kinetis Gnu compiler uses ld file. We will talk about each of the case separately. 1. CW for 8bit/16bit and Coldfire V1. 1.1 .  NO FILL command involved. We define a segment  in prm file MYCONST_ROM     =  READ_ONLY    0x0870 TO 0x08FF; Then allocate MYCONST  into it inside PLACEMENT. MYCONST    INTO  MYCONST_ROM; In C code, we only define  my_const_var(0xCCDD) at this range. #pragma CONST_SEG MYCONST const unsigned int my_const_var = 0xCCDD; #pragma CONST_SEG DEFAULT   After build, we will see only 0xCCDD in this area in generated s19 file: S1050870CCDDD9   1.2  use FILL command to fill unused area of MYCONST_ROM With FILL command we can fill unused area of a section.  Add “FILL 0xAA” : MYCONST_ROM       =  READ_ONLY 0x0870 TO 0x08FF FILL 0XAA;   Rebuild the project. we will see the rest of the field of MYCONST_ROM  is filled in  S19 file: S1230870CCDDAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACF S1230890AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA04 S12308B0AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAE4 S12308D0AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAC4 S11308F0AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA54 2. CW for kinetis GNU compiler: 2.1 . No fill() command involed. Define segment in MEMORY section: my_section    (rx) : ORIGIN = 0X00000800, LENGTH = 0x20   define output  SECTION: .myData : {     . = ALIGN(4);           KEEP(*(.myData))     . = ALIGN(4); }> my_section In C code, define const variable “my_const” (0xCCCCDDDD) const int my_const __attribute__((section(".myData"))) = 0xCCCCDDDD;   After build, we will see only 0xCCCCDDDD in this area in generated s19 file: S1070800DDDDCCCC9E 2.2 Use FILL(0xaa)  command to fill unused area of my_section with 0xAA. Here is the modified code in ld file, I highlight the code I add: .myData : {        . = ALIGN(4);                   KEEP(*(.myData))     . = ALIGN(4);     FILL(0xaa)     . = ORIGIN(my_section) + LENGTH(my_section) ;   }> my_section Rebuild the project. we will see the rest of the field of my_section is filled with 0xAA in  S19 file: S1130800DDDDCCCCAAAAAAAAAAAAAAAAAAAAAAAA9A S1130810AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA34

This document describes the steps required for U-Boot debugging using the CodeWarrior IDE for low-end and high-end Power Architecture CPU, from NOR, NAND, SPI and SD card flash devices.

  Today I woke up with the inquiry-ish mood, so I would like to make you some questions, dear reader...ready?   So, you've been working on CodeWarrior Development Tools? Nice! I've become really close with this developing tool due to the major benefits that it's portfolio brings to the developers' community.   Have you experienced any trouble finding .bins or actualizing updates manually? If the answer is "yes", well, me too! Sometimes it's kinda difficult getting to know IDEs completely or finding out all the features that are contained within them.   Did you know that CodeWarrior can be turned into a more graphical coding environment? If the answer is "no", let me tell you there is a way! And a pretty easy one...   If I told you CodeWarrior and Eclipse get together to empower developing tasks...? Yes indeed, they can be merged and they'd easy things up!   Why would I like to merge CodeWarrior and Eclipse features? Basicly, because the classical IDE provided by CodeWarrior turns out to be very manual when it comes to updates; besides, whenever you decide to search for an update, you must sync it and organize it all by yourself...and I know it might not be that hard, but it's not funny when you end up with tons of versions for each update.   The marvellous thing of working with CodeWarrior inside Eclipse IDE is that the graphical environment makes it way easier and friendlier for you, for us developers, and there is no need to search for updates or even trying to get the code segments when working with Processor Expert, for example, it is all viasually arranged and set for you to just have a blast programming.   This time I'll attach the Quick Starts of the CodeWarrior Project Importer, where you can find all the info you need to start using CodeWarrior tools from Eclipse IDE.   Amazing thing, have fun!

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.

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!

This post will step by step show how to report a software  defect or problem to NXP support team. Please take a few minutes to read it. This will help us investigate the issue more efficiently and quickly. Basically we need prepare:      1. Your IDE version: - If you use classic version: Start the IDE and click on Help | About Freescale CodeWarrior. Click on Installed Products. Save all info displayed into a txt file. - If you use eclipse version: Start the IDE and click on Help | About CodeWarrior Development Studio or About Kinetis Design Studio. Save the version and build id. 2. Demo Code: - Create a demo project to show the problem.  Then send the entire sample code folder in zip format. - If the problem is in NXP SW package, for example SDK package, please provide the SW version or download link.      3. Mention how to reproduce the problem step by step with the demo code.      4. Error screenshot.     Steps of submitting the case: 1. Go to Sales and Support page, click on Hardware & Software for Submit new ticket: http://www.nxp.com/support/sales-and-support:SUPPORTHOME    2. Then click on “Add a new case”   3. Fill the New Case form. Here is an example:                                                         

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.

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

How to use error directive in codewarrior version 10.6 as i am facing problem which is able to see in  attached sheet

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

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!

Another attachment in thead

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

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

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!

I am working on a project in which I decided to use ColdFire Architectures , but within the classical view of CW. Luckily, there is another version of this document in which the conversion of ColdFire projects to CW Development Studio is also shown in a brief and easy way!   It can be read in the introductory part of the document: "This application note explains how to convert a ColdFire project created in CodeWarrior Development Studio for Microcontrollers V6.2 or CodeWarrior Development Studio for ColdFire Architectures V7.1 to CodeWarrior Development Studio for Microcontrollers V10.0."   I'll admit it was a thrill finding this document, I hope it is of great help for you as it was for me! And if you're not into CodeWarrior development tools, I don't know what you're waiting for!   Converting ColdFire Projects to CodeWarrior Development Studio for Microcontrollers V10.0  

The great thing with CodeWarrior development Suites is that you can develop almost in any programming environment out there, even if it's assembly.   In this occassion, I ran into a Reference Manual regarding a StarCore ABI (Application Binary Interface)   This document defines a set of standards to ensure interoperability between conforming CodeWarrior for StarCore software components, such as, compilers, assemblers, linkers, debuggers, and assembly language code. These standards cover run-time aspects as well as object formats to be used by compatible tool chains from StarCore and third-party tools developers.   A benefit of this standard definition is interoperability of conforming tools so that users can select the best tool for each phase of the application development cycle, rather than being constrained to using an entire tool chain. Another benefit is compatibility of conforming libraries. Us programmers can build compatible binary libraries and assembly code libraries and be assured of their continued compatibility over time.   So if you are ready for a new experience at programming (in case binary interfaces are your thing) start along with this Reference Manual!  

CodeWarrior development suites allow ready access to any or all of the CodeWarrior products contained within each suite, which means you get freedom to design across Freescale's extensive silicon portfolio.   CodeWarrior development tools provide the capabilities required by every engineer in the development cycle, and this suites right here make easier the filter process for you to know which product list meets your needs, 100% flexibility to choose the required purchasing model.   This means you can license the entire portfolio of CodeWarrior tools within the suite you purchase. Each suite also contains all functionality of the products in the suites below it.   Purchasing and accessing these tools now is easier and more affordable!!!       CodeWarrior suites include:   •           CodeWarrior Professional Suite: Fullfeatured development suites •           CodeWarrior Standard Suite: Selectively featured development suites •           CodeWarrior Basic Suite: Compiler upgrades to special editions, Linux applications editions and flash programmers •           CodeWarrior Special Editions: Featurelimited development tools   Flexible purchasing models are shown here! And you can also check the quick reference guide for further info!

Recently I have two customers asking me same questions – How to use S12Z Burner under CW10 for S12Z. Unlikely CW10 for S08, S12Z build process does not use the Burner to generate S-Record file. By default, after a successfully build, S12Z build tool chain generates elf file only. The Burner panel has remained as part of the S12Z properties since the build tools configuration panels were imported from S08 build tools. Thus even users configure it, it doesn’t generate bbl file and s19/hex/bin files. Fortunately we have workaround to integrate burner tool into CodeWarrior10 post build steps. doc and demo code is attached. We can also refer article from Erich. S-Record, Intel Hex and Binary Files | MCU on Eclipse