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!

  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!

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

You remember the previous post regarding the new awesome TAP for CodeWarrior applications?   Today I'd like you to meet this device shown up here. Is the CWH-STC-COP-YE, a removable probe tip for StarCore and DSC processors. This probe tip connects your StarCore or DSC processor target system’s ONCE port to the CodeWarrior TAP base unit’s 30-pin target connector.   And of course this tip is compatible with the CodeWarrior TAP previously mentioned (CWH-CTP-BASE-HE). As a matter fact, the base unit doesn't come with a probe tip, so it is necessary to acquire one of the tips available to debug your device. Check out the main features!   Features Removable probe tip Low-cost and economical to order several spares Allows base unit to work with several different target types System Requirements StarCore or DSC target system with ONCE header CodeWarrior TAP  

The CodeWarrior Development Studio provides a common interface for developing, debugging, and analyzing your applications. The project-oriented Workbench window provides numerous perspectives containing views, editors, and controls that appear in menus and tool bars. After creating a project, build your application, define a launch configuration, and then wait for data collection and data display.   The StarCore linker is a part of StarCore development tools and generates an executable file for the StarCore family of digital signal processors. In addition, the linker also lets you define a Linker Command File (LCF) that you use to instruct the linker to store different parts of the executable file in different areas of the processor address space. Currently, StarCore development tools support two linker versions: • SC100 • SC3000   The SC3000 linker specifically targets SC3850 family of processors. This user guide explains SC3000 linker. For information on SC100 linker, see StarCore SC100 Linker User Guide. What are you waiting for? Amazing features are right here, and  u p d a t e d!!

We talked of RTOS a little while ago. This time it's turn for The SmartDSP Operating System (OS), and more specifficly, SmartDSP API.   But, what is the SmartDSP OS? It 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: MSC815x MSC825x PSC9131   The StarCore CodeWarrior (CW) Development Studio includes SmartDSP OS royaltyfree source code. Further, SmartDSP OS has a high-level Application Programming Interface (API) that lets users develop integrated applications for StarCore processors. This Reference Manual documents SmartDSP OS API.   Having this API updated and available for processors MSC815x/MSC825x/PSC9131, possibilities of coding within CodeWarrior features become even broader. Start trying it up now!!!

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!!!      

Inside {CW10 install folder}\eclipse there is ecd.exe which is used to run build projects from command line. this article focuses on ecd.exe usage with examples. Especially How to use ecd.exe command to build, generateMakefiles,make and reference a project.

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

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 C and C++ compilers use the Embedded Warrior Library (EWL) for C to provide and extend the libraries documented in the ISO/IEC standards for C. EWL C also offers facilities described in the POSIX specification and some common application programming iwnterfaces (APIs) from UNIX operating systems.   Intrinsic functions generate in-line assembly code instead of making a call to a library function. Intrinsic functions generate less object code and perform faster than their regular counterparts. In some cases these functions generate just a single assembly instruction.Get the EWL for C   n o w !   For the EWL C++ reference libraries you can also find:   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.   ...and so on! Find out what the rest of the libraries have got to give you to improve and update CodeWarrior tools! Check out the manual here!

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

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.

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