LED Description Driver for an LED. Component Led.PEupd Dependencies GenericBitIO License License : Open Source (LGPL) Copyright : (c) Copyright Erich Styger, 2012, all rights reserved. This an open source software implementing an LED driver using Processor Expert. This is a free software and is opened for education, research and commercial developments under license policy of following terms: * This is a free software and there is NO WARRANTY. * No restriction on use. You can use, modify and redistribute it for personal, non-profit or commercial product UNDER YOUR RESPONSIBILITY. * Redistributions of source code must retain the above copyright notice.

Note: the full USB 4.0 stack can be downloaded from the FSL website and contains Processor Expert components for many classes, not just the CDC class. So think of this as a useful tutorial. You can find it here: USB Stack Product Summary Page. Once installed, the default location for the components is C:\Freescale\Freescale USB Stack v4.0.1\ProcessorExpert. FSL_USB_Stack Description Wrapper for the Freescale USB Stack using the USB Stack v4.0.0. This wrapper currently only supports the CDC class and has been tested with the Kinetis K40/K60, TWR-MCF52259 , TWR-S08MM128, TWR-MCF51MM256, plus the MCF51JM128 and S08JM60 on the DEMOJM board. An article on this can be found here. Component FSL_USB_Stack.PEupd Dependencies RingBufferUInt8 License (c) Copyright Freescale, all rights reserved, 2012 Ported as Processor Expert component: Erich Styger http: www.freescale.com Copyright notice from Freescale: /****************************************************************************** * * Freescale Semiconductor Inc. * (c) Copyright 2004-2010 Freescale Semiconductor, Inc. * ALL RIGHTS RESERVED. * ****************************************************************************** * * THIS SOFTWARE IS PROVIDED BY FREESCALE "AS IS" AND ANY EXPRESSED OR * IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. * IN NO EVENT SHALL FREESCALE OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, * INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES * (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR * SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, * STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING * IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF * THE POSSIBILITY OF SUCH DAMAGE. * **************************************************************************//*!

S19 Description S19 File Parser Component S19.PEupd Dependencies none License This component is based on the Freescale Application Note AN3748. The copyright notice of the original file is provided below: /****************************************************************************** * * (c) copyright Freescale Semiconductor 2008 * ALL RIGHTS RESERVED * * File Name: ParseS19.c * * Purpose: This file is for a USB Mass-Storage Device bootloader. This file * has functions to read S19 file sent over USB, and parse s-records * to program to flash. * * Assembler: Codewarrior for Microcontrollers V6.2 * * Version: 1.0 * * * Author: Derek Snell * * Location: Indianapolis, IN. USA * * UPDATED HISTORY: * * REV YYYY.MM.DD AUTHOR DESCRIPTION OF CHANGE * --- ---------- ------ --------------------- * 1.0 2008.06.10 Derek Snell Initial version * * ******************************************************************************/ /* Freescale is not obligated to provide any support, upgrades or new */ /* releases of the Software. Freescale may make changes to the Software at */ /* any time, without any obligation to notify or provide updated versions of */ /* the Software to you. Freescale expressly disclaims any warranty for the */ /* Software. The Software is provided as is, without warranty of any kind, */ /* either express or implied, including, without limitation, the implied */ /* warranties of merchantability, fitness for a particular purpose, or */ /* non-infringement. You assume the entire risk arising out of the use or */ /* performance of the Software, or any systems you design using the software */ /* (if any). Nothing may be construed as a warranty or representation by */ /* Freescale that the Software or any derivative work developed with or */ /* incorporating the Software will be free from infringement of the */ /* intellectual property rights of third parties. In no event will Freescale */ /* be liable, whether in contract, tort, or otherwise, for any incidental, */ /* special, indirect, consequential or punitive damages, including, but not */ /* limited to, damages for any loss of use, loss of time, inconvenience, */ /* commercial loss, or lost profits, savings, or revenues to the full extent */ /* such may be disclaimed by law. The Software is not fault tolerant and is */ /* not designed, manufactured or intended by Freescale for incorporation */ /* into products intended for use or resale in on-line control equipment in */ /* hazardous, dangerous to life or potentially life-threatening environments */ /* requiring fail-safe performance, such as in the operation of nuclear */ /* facilities, aircraft navigation or communication systems, air traffic */ /* control, direct life support machines or weapons systems, in which the */ /* failure of products could lead directly to death, personal injury or */ /* severe physical or environmental damage (High Risk Activities). You */ /* specifically represent and warrant that you will not use the Software or */ /* any derivative work of the Software for High Risk Activities. */ /* Freescale and the Freescale logos are registered trademarks of Freescale */ /* Semiconductor Inc. */ /*****************************************************************************/

The Processor Expert Software Wiki provides useful “how to” and FAQ information not available on Freescale websites or  forums.  The links below provide useful design resources for Processor Expert product designers and users. Software Suites Component Exchange Integrated with CodeWarrior Tools Microcontroller Driver Suite QorIQ Configuration Suite QorIQ Optimization Suite Component Development Environment Freescale Components (buy now) Community Components (freeware) Frequently Asked Questions (FAQ) Processor Expert Software Suites FAQs (coming soon) QorIQ Configuration Suite (coming soon) Component Development Environment FAQs (coming soon) Components Exchange FAQs (coming soon)

Select the Help > Cheat sheets… from the CodeWarrior menu.   Unfold the CodeWarrior Processor Expert Features and select Processor Expert Basics for CodeWarrior for MCUs. Click OK. Click the Go to Creating Project link in the Processor Expert Basics and follow the shown steps.

SimpleEvents Description Set/clear/check event flags Component SimpleEvents.PEupd Dependencies LowPower License License : Open Source (LGPL) Copyright : (c) Copyright Erich Styger, 2011, all rights reserved. This an open source software implementing a simple event module using Processor Expert. This is a free software and is opened for education, research and commercial developments under license policy of following terms: * This is a free software and there is NO WARRANTY. * No restriction on use. You can use, modify and redistribute it for personal, non-profit or commercial product UNDER YOUR RESPONSIBILITY. * Redistributions of source code must retain the above copyright notice.

Introduction This document describes migration steps of CW MCU 10.6 projects with Processor Expert into KDS 3.0.0. Note: We strongly recommend backup of your original CodeWarrior application. If you want to use default configuration of compiler and debugger (toolchain) in KDS 3.0.0 use instructions described in the document Processor Expert project (CW MCU 10.6) migration into new project in KDS 3.0.0 The following document describes conversion of the whole project (toolchain configuration, source code files, Processor Expert configuration). Steps of the conversion by using CodeWarrior Converter and KDS Upgrade Assistant 1. Create a new workspace in KDS 3.0.0 (it is a workaround for KDS Upgrade Assistant that does not allow selection of migrated project in non-empty workspaces) 2. Import the project by using File > Import command, see below. Select File > Import, from the IDE menu.           The import dialog appears. Expand the General tree and select Existing Projects into Workspace. Click Next. The Import projects screen appears. Click Browse and select the root directory to search for an existing Eclipse project Select the projects you want to import in your Workspace Check Copy project into workspace if want to create a copy of the project in the workspace (otherwise the project is linked into the workspace only). Click Finish - the imported project appears in the Project Explorer view. 3 Convert CodeWarrior Project file by using command Convert CodeWarrior project file… in the context menu of the project in Project Explorer window, see detailed steps below. Select the recently imported legacy project you want to convert. Right-click and select Convert CodeWarrior Project file. Note: The context menu Convert CodeWarrior project file... will only work with GNU/gcc CodeWarrior project and not for CodeWarrior projects using the legacy Freescale compiler (for this compiler use instructions described in the chapter Steps of the conversion by manual configuration of the toolchain or Processor Expert project (CW MCU 10.6) migration into new project in KDS 3.0.0​). The CodeWarrior to KDS project migration assistant dialog appears and prompts whether you want to convert the project. Click Yes. The CodeWarrior to KDS project migration assistant will prompt that the conversion has completed and a backup of the original *cproject file has been created in .cproject_backup. Click to OK to close the CodeWarrior to KDS project migration assistant dialog. Note: To see the conversion process log, navigate to the project's root directory and open the KDSConverter.log file. 4. Process update of the project by using Project > KDS Upgrade Assistant… Select the project: Select settings for conversion (for details see the document Kinetis Design Studio: Migrating KDS V2.0.0 Projects to GNU Tools for ARM Embedded (Launchpad, KDS V3.0.0). For CodeWarrior project can be used following settings. Click on the Finish button to process the upgrade. Known Issues: The converter does not distinguish between Executable projects and Static Library projects. In the latter case the options for converting Newlib-nano and adding semihosting should be suppressed. When selecting options to add _exit() implementation and semihosting=rdimon on projects from KSDK_1.1.0demos\hello_world\kds a Cross ARM C Linker errors reports "multiple definition of _isatty". It is necessary to remove the user definition of _isatty. When you want to upgrade a converted CodeWarrior project you must use a new empty workspace otherwise the KDS Upgrade Assistant may not find the project in the workspace (the project is not displayed in the list of projects for the upgrade). GNU ARM Embedded (launchpad) on Linux - because the GNU ARM Embedded tools are 32-bit only for Linux, on Ubuntu 14.04 64-bit (and others) you may see error messages suggesting that arm-none-eabi-gcc could not be found. The tools do exist, however the system doesn't know how to run them. This is because the 32-bit compatibility packages need to be installed: See http://gnuarmeclipse.livius.net/blog/toolchain-install for details and suggested solution. 5. Remove all CW MCU 10.6 startup code (delete all files in the Project_Settings/Startup_Code project folder) and add a new Startup file by using Build options of CPU component: 6. Generate code (a new startup source code file is added into Project Settings/Startup_Code folder in the project). 7.Build the application. If the application is built without errors you can use it and debug it. If there are errors (e.g. linker error) check the Console window of the compiler and linker. There can be for example missing parameter of the selected target CPU – the toolchain settings (the configuration) is damaged and cannot be used due to the following issues: C/C++ Development Toolkit issues Editing the toolchain may damage the project In certain conditions, changing the toolchain for a project in the C/C++ Build → Tool Chain Editor page from another plug-in to GNU ARM Eclipse plug-in might not work; even worse, there are cases when the project is permanently damaged. There is not known way to repair such a broken project; you have to create a new project and copy the content (this is a CDT bug, not a plug-in bug). See the website http://gnuarmeclipse.livius.net/blog/known-problems/#Editing_the_toolchain_may_damage_the_project. Toolchain configuration Issue When you use the latest version of the GNU ARM Eclipse plugin you can get message "Orphaned CDT build configuration [org.eclipse.cdt.cross.arm.gnu.sourcery.windows.elf.debug.1561998926.1100932005.1237614533.626146708.187750101.514251714]: parent extension cfg [org.eclipse.cdt.cross.arm.gnu.sourcery.windows.elf.debug] not found". The “org.eclipse.cdt.cross.arm.gnu.sourcery.windows.elf.debug” ID comes from a project generated with the old version of the plug-in, no longer supported. Recreate the project with the latest version and it will work. See also http://sourceforge.net/p/gnuarmeclipse/support-requests/6/ In this case you must create a new configuration from a template and set all options manually. Skip following steps and continue below in the chapter Steps of the conversion by manual configuration of the toolchain. 8. Open the context menu of the project in the Project window and select Debug As > Debug Configurations. Add a new debug configuration, e.g. GDB SEGGEER J-Link Debugging. 9. Verify the settings of the debugger (for example select the Device Name). 10. Click on the Apply button and then on the Debug button. Steps of the conversion by manual configuration of the toolchain When the previous conversion process fails you can follow these instructions. Delete the converted project (that has been damaged) from the workspace and follow these steps. 1. Import the project by using File > Import command, see detailed steps in the previous chapter – Step number 2. 2. Select the C/C++ Build / Tool Chain Editor in the Properties of the project (see following screenshot). You see the warning message “Orphaned configuration ….”.  You must create a new configuration for this project (the current configuration is created by a previous version of plugins and it is not compatible). 3. Click on the Manage Configurations… 4. Click on the New button 5. Write the name of the new configuration and select the Copy Settings from. You can copy configuration from an existing project or you can use default template (the following description  suppose default configuration). 6. Click on the OK button. New configuration is created. 7. Select the old configuration and click on the Delete button. 8. Click on the OK button. 9. The new configuration is selected in the Properties window, see below: 10. Click on the Apply button. 11. Select the C/C++ Build/Settings, Tools Settings tab (in the same Properties window). 12. On the Target Processor page select the correct target Processor, the ARM family e.g. cortex-m0plus for KL25Z. Click on the Apply button. 13. On the Optimization page select the Optimization Level: None (-O0). Click on the Apply button. 14. On the Debugging page select the Debug level: Maximum (-g3). Click on the Apply button. 15. On the Cross ARM C Linker / General page add the following script:      Script files (-T): "${ProjDirPath}/Project_Settings/Linker_Files/ProcessorExpert.ld" 16. On the Cross ARM C Linker / Libraries page add the following script:      Library search path (-L): "${ProjDirPath}/Project_Settings/Linker_Files/" 17. On the Cross ARM C Linker / Miscellaneous page add the following script:       Check the option: Use newlib-nano (--specs=nan.specs)      Add the following parameter to the Other linker flags:  -specs=nosys.specs 18. Click on the Apply button. 19. Set the Build Artifact (see below) and click on the OK button. 20. Remove all CW MCU 10.6 startup code (delete all files in the Project_Settings/Startup_Code project folder) and add a new Startup file by using Build options of CPU component: 21. Generate code (a new startup source code file is added into Project Settings/Startup_Code folder in the project). 22. Build the application. 23. If you see the following error: Error: Cannot run program "gcc": Launching failed Modify the PATH variable in the Properties of the Project. Select C/C++ Build/Environment page, double-click on the PATH variable and add the absolute path to the folder KDS_3.0.0\toolchain\arm-none-eabi\bin\ (e.g. add c:\Freescale\KDS_3.0.0\toolchain\arm-none-eabi\bin\; at the beginning of the PATH values). Click on the OK button. Build the application again. The project should be compiled without any error. If you still see any toolchain settings error and you are not able to fix these issue use instructions described in the document Processor Expert project (CW MCU 10.6) migration into new project in KDS 3.0.0​. 24. Open the context menu of the project in the Project window and select Debug As > Debug Configurations. Add a new debug configuration, e.g. GDB SEGGEER J-Link Debugging. 25. Verify the settings of the debugger (for example select the Device Name). 26. Click on the Apply button and then on the Debug button. The application is migrated and debugging should work properly.

SSD1289 Description Display driver for the Solomon Systech SSD1289 LCD (which is used on the TWR-LCD). Component SSD1289.PEupd Dependencies Wait License License : Open Source (LGPL) Copyright : (c) Copyright Erich Styger, 2011, all rights reserved. This an open source software in the form of a Processor Expert Embedded Component. This is a free software and is opened for education, research and commercial developments under license policy of following terms: * This is a free software and there is NO WARRANTY. * No restriction on use. You can use, modify and redistribute it for personal, non-profit or commercial product UNDER YOUR RESPONSIBILITY. * Redistributions of source code must retain the above copyright notice.

Learn the Processor Expert UI, what components are, and how to add one to a project in the CodeWarrior Development Studio.

The attached document shows how tou use Processor Expert Driver Suit to generate code for CW. You can see details in the notes at the botton of the slides.  Best regards, Carlos

Training Videos Processor Expert - Introduction (Driver Suite) (Video 04:01) - Learn the Processor Expert UI, what components are, and how to add one to a project.. Processor Expert: Working with Components (Driver Suite) (Video 03:53) - Using Microcontroller Driver Suite, learn how to add, configure, and remove a component, and how to generate code. Processor Expert: The Code Model (Driver Suite) (Video 04:45) - Using Microcontroller Driver Suite, learn the answers to the questions: What code does Processor Expert generate? Where does it put the code? And how do I use it? Processor Expert: Creating an MQX Lite Project (Driver Suite) (Video 05:15) - Using Microcontroller Driver Suite, learn how to create an MQX Lite component from scratch. You'll also learn where Processor Expert puts the task functions and the RTOS code itself. Processor Expert: An MQX Lite Example (Driver Suite) (Video 04:39) - See how a full MQX Lite application works, how the tasks are implemented, and how they interact with other components in Microcontroller Driver Suite. Processor Expert: Exporting and Importing Templates (Driver Suite) (Video 03:56) - Learn how to export and import a file that can completely configure and generate the code required for an arbitrarily complex hardware and software system with Microcontroller Driver Suite. Processor Expert: Integrating with IAR Embedded (Video 06:22) - Learn how to incorporate Processor Expert's generated code into an IAR Embedded Workbench project. Processor Expert: Integrating with Keil Microvision (Video 04:54) - Learn how to incorporate Processor Expert's generated code into a Keil Microvision project.

This tutorial shows a basic steps to create a CodeWarrior project with Processor Expert configured for the FRDM-KL25 board. The steps apply to CodeWarrior version 10.3 or newer. 1. In the CodeWarrior , go for [File | New | Bareboard Project]. 2. Type a project name such as e.g. KL25Z-PE” then click [Next] 3. In Devices page, please go to the line [Device or board to be used], type in part of the name our target device:  "kl25z" and select the final target device MKL25Z128 from the filtered list. Then click [Next]. 4. In the Connections window select only the [OpenSource SDA] connection type and click [Next]. Note: This is the on-board USB debug connection on FRDM-KL25. 5. In the Rapid Application Development select [Processor Expert] and click [Finish]. 6. The CodeWarrior Projects view contains a newly created project. Double-click the Processor Expert.pe file to ensure to see  the Processor Expert components from the project in the Component view. 7. In the Component view open the view menu (small down-heading arrow) and select Apply Board Configuration command 8. Click Browse… button and select FREEDOM-KL25Z / cpu / CPU_default.peb 9. Click Finish to confirm replacement of the default CPU component by the pre-configured one for the FRDM-KL25 board. Now the project is configured to run from on-board crystal at 48MHz. You can continue with adding components from the Components library view and configuring them in the Inspector or for example try the follow tutorial Toggling Pin on Kinetis Using a Timer Output .

Using Microcontroller Driver Suite, learn the answers to the questions: What code does Processor Expert generate? Where does it put the code? And how do I use it?

SMAC 2.4 GHz stack for MC13213 and MC13201 Description Simple MAC (Freescale SMAC) implementation. Component SMAC.PEupd Dependencies SPHY License (c) Copyright Freescale Semiconductor, 2012 Adoption as a Processor Expert component: Erich Styger

This file can be used on the MC56F8322 device to output clock signals to pins for checking the ROSC frequency as trimed by the factory trim values. The code was generated by processor expert with GUI selections made in Code Warrior IDE.

Learn how to export and import a file that can completely configure and generate the code required for an arbitrarily complex hardware and software system with Microcontroller Driver Suite.

When you get a good answer, it is extremely helpful to everyone if you mark it as a correct answer. A hundred people may look at a hot topic, and when there is an answer, they can jump straight to it. So for everyone's benefit, when you get a good answer, mark it! It's part of being a good community member. As well, but much less importantly, one of the things we're going to measure is how quickly the community answers questions. But we're far more interested in people being able to find the right answer. So from time to time, if it looks like people forget to mark answers, we may go through and do it for you. But we aren't your mom. Help your colleagues, and mark the good answers. In fact, you know better than us what's right.

Learn how to incorporate Processor Expert's generated code into an IAR Embedded Workbench project.

The C project that doesn't use Processor Expert can be converted to Processor Expert. This is useful when the user finds out that he/she would like to use additional features of Processor Expert. WARNING! Note that in most cases this conversion involves necessary manual changes in the application code, because for example the register interrupt vectors table definitions created by the user often conflicts with Processor Expert definitions. Don't forget to backup the whole project before the conversion. Some files will have to be removed from the project. The conversion to Processor Expert is recommended to experienced users only. Steps: Select the command in the main menu File > New > Other and in the New Project Wizard select Processor Expert / Enable Processor Expert for Existing C Project Select the project you want to update. Select the derivative that will be included in PEx project (you should use the same derivative that has been selected when the project was created without PEx). Select the target compiler (select the GNU C Compiler by default if you have not installed any other compiler in the Kinetis Design Studio) Confirm changes (renaming of main.c module and any other changes you want to apply) and click on the Finish button. The project with PEx is created but there need to be done following changes: Remove the duplicate main.c module – the main_backup.c file (copy content of the old main.c module into the new one created by PEx) and delete the old version of the file (main_backup.c) Remove all IO maps files from the original project. The KDS bareboard project have all these files included in the Includes folder by default (core_......h files and IO map files). Remove all startup files from the original project. The KDS bareboard project have all these files (startup_xxxxxx.S and system_xxxxxx.c files) included in the Project_Settings/Startup_Code folder. Remove linker file xxxxxxxxxxxx_flash.ld from the original project. Use the Processor Expert.ld linker file that is generated by Processor Expert. In the context menu of the project select Properties and in the Properties window go the C/C++ Build > Settings > Tool Settings, select the Cross ARM C++ Linker / General and select the ProcessorExpert.ld file instead of MK......_flash.ld (see the following screenshot).

This tutorial will show step-by-step how to create a simple Processor Expert project that periodically toggles an output pin using a timer output without writing a single line of code. The FRDM-KL25 board is used with one of the LEDs (blue) connected to the Timer/PWM Module 0 (TPM0), channel 1. Timer Operation Description The Timer/PWM Module 0 (TPM0) provides (besides other features) a counter with variable period (modulo), compare register an output pin suitable for the goal of periodic toggling. The counter will be configured to continuously run in modulo range with a 300ms period, the output will be set when counter reaches the compare register value (150ms) and cleared when the counter resets. The following picture describes the operation: Creating the Project First, create a new project with Processor Expert for KL25 configured as described in the tutorial Creating Processor Expert Project for FRDM-KL25 Switch to Components Library view and its Categories tab and add the TimerUnit_LDD component from the category Logical Device Drivers / Timer by double-clicking on it or selecting pop-up menu command ‘Add to project’. The component appears in the Components view: Use the Rename component command from the TU1’s context menu and change the name to BlueLED. : Double click the component to open it in the inspector and configure the properties according to the following picture: Invoke code generation by clicking on the Generate Processor Expert Code button in the Components view of the project: The generated code is present in the Generated_Code folder of the project: Note: The generated code contains automatic initialization provided by Processor Expert configuring all needed registers, so it's not necessary to write any user code. Build the project using the Project / Build All. After the successful build, you can connect the FRDM-KL25 board and run the application by clicking the "Debug" icon and after the code gets loaded into the board the "Resume" button. The LED should start periodically blinking with blue color.