Greetings, A new release V1.1.1 of KDS is available from the Download tab on http://www.freescale.com/kds V1.1.1 is a full release, and it is recommended to use this new release going forward. V1.1.1 supports Windows (7/8), Linux (32bit binaries for Ubuntu, RHE and CentOS): What's new: Linux RHE and CentOS installation (RPM) Updated KDS User Guide Updated P&E updated site handling to allow support for incremental device support Fixed IP Adddress Setup for P&E Ethernet connection devices (Cyclone MAX, TraceLink) For details, see the V1.1.1 Release Notes.   In addition to the KDS V1.1.1 release, there is an Eclipse update for Processor Expert and Kinetis SDK support. Implemented workaround for HEAP size needs of Newlib-nano GNU library Fixed include path delimiter for Linux hosts Fixed flash configuration field values for several bare project derivatives Updated board configuration templates. Details in the Update1 Release Notes.   Download this .zip file, then install it in Eclipse/KDS using the menu Help > Install New Software (the update will be available on the KDS Eclipse online update site too)   :   Please use KDS V1.1.1 with Eclipse/Processor Expert/SDK Update1 going forward. KDS V1.1.0 projects and settings can be used with V1.1.1.   Best regards, Erich

This document explains how you can debug the FRDM-K22F board with the Segger J-Link OpenSDAv2.1 Firmware and the Kinetis Design Studio V1.1.0.   Applicable to: OpenSDAv2.1 boards (FRDM-K22F for now) Kinetis Design Studio V1.1.0     Outline The FRDM-K22F board (FRDM-K22F|Freedom Development Board|Kinetis|Freescale) comes with OpenSDAv2.1 programmed on it, and has the CMSIS-DAP debug firmware on it by default. (see 'Technical Details' at the end about the OpenSDA differences)   OpenOCD with CMSIS-DAP for FRDM-K22F is not supported in KDS V1.1.0. Trying to debug the FRDM-K22F board with KDS V1.1.0 and OpenOCD/CMSIS-DAP results in an error in the Console View and is currently not possible, until OpenSDA gets updated (see Kinetis Design Studio V1.1.0: Release Notes and News).   One solution is to use the Segger J-Link OpenSDAv2.1 firmware to debug the board. (Another solution is to use the P&E Multilink OpenSDAv2.1 firmware, see FRDM-K22F: Debugging with P&E OpenSDAv2.1 Firmware)   Installation of Segger J-Link OpenSDA V2.1 Firmware You need to install the Segger J-Link OpenSDAv2.1 firmware on the board, and you only need to do this once (unless you change the firmware again).   Go to SEGGER - The Embedded Experts - OpenSDA / OpenSDA V2 and download the OpenSDA V2.1 firmware (zip file) Unzip the firmware file (JLink-OpenSDA_v2_1.bin) in the zip file to your harddisk. Power the board/Plug in the USB cable with the OpenSDA USB port, while having the Reset/SW1 pressed. The device should enumerate BOOTLOADER: device on your host. You are now in bootloader mode. Copy the Segger .bin file to that BOOTLOADER device. Wait a few seconds to complete the operation. Unplug the board, and now power it normally (without SW1 pressed) The board should now show up as J-Link device and with a virtual COM port: You are ready to use to debug the FRDM-K22F as if you would do with a Segger J-Link 🙂   Debugging with Segger J-Link OpenSDAv2.1 Create a new debug/launch configuration: Select your project, then use the menu Run > Debug Configurations. Use the 'new' Icon to create a new configuration for your application and project (Main tab):   Specify MK22FN512xxx12 as your device name, and make sure 'SWD' is selected:   Have SWO disabled:   That's it. Now you can debug your application with Segger J-Link OpenSDA V2.1 firmware on the board :-). You can use the 'Debug' button in the launch configuration: Or use the debug icon drop-down list:   Happy Debugging 🙂 Technical Details There are so far three versions of the OpenSDA available: OpenSDAv1.0: this one is on all the FRDM boards like FRDM-KL25Z, FRDM-KL26Z, FRDM-KL46Z, FRDM-K20, ... (prior FRDM-K64F). The bootloader on these boards is protected and cannot be erased and supports P&E, Segger and CMSIS-DAP debug applications (*.sda). OpenSDAv2.0: This version was released at FTF 2014 with the FRDM-K64F board. This is an open source bootloader, and the bootloader can be replaced by the user. It supports *.bin files and P&E, Segger and CMSIS-DAP debug applications. OpenSDAv2.1: This version is released with the FRDM-K22F board. It is the same as The debug circuit on the board is the same for all OpenSDA versions (Kinetis K20 microcontroller): the difference is what bootloader is programmed on the K20: the bootloader on the OpenSDAv1.0 cannot be erased/changed. The bootloader on OpenSDAv2.x can be erased/changed, and the difference between the OpenSDAv2.0 and v2.1 is the address where the debug application starts: for OpenSDAv2.0 it expects the application at address 0x5000, while OpenSDAv2.1 expects the application to start at address 0x8000.   See also: OpenSDAv2

Normally when debugging you need to know the status of your registers in the Embsys Registers section. Most of the time when a board or chip are just released you are not able to select them (because they're not available) and therefore it makes it more difficult for you to debug. In this document I will guide you through the process for adding any chip you are working with to EmbSys Registers section. 1. First of all it is needed to know where the Embsys Registers' Folder is located. Go to the folder where KDS is installed. 2. Go to eclipse folder. 3. \org.eclipse.cdt.embsysregview.data_0.2.4.freescale 4. \data 5. \SVD(CMSIS) 6. \Freescale 8. Finally this folder contains XML files, these files can be processed purely as data by the program. To add a new XML file which describes the new chip: 1. go to your chip's package (In my case \SDK_2.2_MKL28Z512xxx7.zip). Note: If you don't know where to build a package, please go to the following post: https://community.nxp.com/docs/DOC-333304  2. \SDK_2.2_MKL28Z512xxx7.zip\devices 3. \SDK_2.2_MKL28Z512xxx7.zip\devices\MKL28Z7 As you can see, the MKL28Z7 is not available in EmbsysRegView. Locate the XML and copy it to the route: C:\Freescale\KDS_v3\eclipse\plugins\org.eclipse.cdt.embsysregview.data_0.2.4.freescale\data\SVD(CMSIS)\Freescale Paste it in Freescale's folder: Go to EmbSysRegView again and now it will be available Restart Kinetis Design Studio and you'll be able to see your chip's registers: By Ivan Ruiz.

Writing to Acceleometer data to SD Card in KDS   Description:   A project made in KDS using the FRDM-MK64FN1MOVLL12 board to write the Accelerometer data to an SD Card. Every second, the time and the value of the variables x, y and z taken from the Accelerometer will be written to an SD Card. They will be written in a log.txt file, which will be created if it does not exist. The LED will flash green every second when writing. In case of an error, the LCD will flash red every second.   Sections of code taken from http://mcuoneclipse.com/2014/05/26/tutorial-data-logger-with-the-frdm-k64f-board/   Issues:   Time will always begin at 17:51:31 after being flashed. This is due to it being set as such at TmDt1_Init.

Greetings, attached is the material of the Kinetis Design Studio (KDS) hands-on training held at FTF 2014 in Dallas. It was using the V1.0 pre-beta version of the tools. There will be some changes for the final V1.0 beta coming out early in May, but is very close to the upcoming beta.   Erich Original Attachment has been moved to: Lab_1.zip

When you want to start debugging with SEGGER J-Link lite debugger in Kinetis Design Studio 1.1.1 you must set properly several options otherwise the debugger behave incorrectly (it seems that debugger works but the application execution does not work - e.g. functions are not called).   When you create a new Kinetis Design Studio project (with Processor Expert), write you code and build the application you must also create a debug configuration (open the context menu of the project in the Project Exporer and select Debug As / Debug Configurations...). In the Debug Configuration window create a new debugger connection for GDB SEGGER J-Link Debugging and set the correct values for the derivative of your project (e.g. MKL25Z128 derivative on FRDM-KL25Z target board): On the Debugger tab set the device name (see the list of Supported device names)  (e.g.set value MKL25Z128xxx4 for the MKL25Z128) and uncheck the Allocate console for semihosting and SWO (it is not supported).     On the Startup tab uncheck Enable semihosting and Enable SWO.   Click on Apply to save the settings. the debugger is connection is set properly now and you should be able to debug your application (click on the Debug button). Note: You can use this option for the OpenSDA connection when the SEGGER firmware is flashed. SEGGER offers a firmware running on the Freescale OpenSDA platform which makes OpenSDA compatible to J-Link Lite (see pages https://www.segger.com/opensda.html). You can find more details about OpenSDA MSD Bootloader in the OpenSDA User’s Guide document, see http://www.freescale.com/files/32bit/doc/user_guide/OPENSDAUG.pdf

Recently, there were some customers asking how to change MCU for a KDS2.x  project in KDS. It’s not difficult but the question is typical. So I wrote an article on this topic.   Attached document sets an example of porting a KSDK2.0 K21F project to K22F.  Step by step. User can use it as a reference to change MCU for other kinetis device.

The Kinetis Bootloader(KBOOT) v2 is now available on www.nxp.com/kboot webpage, it supports building bootloader image on KDS v3.2  IDE. About how to use the KBOOT to load a user's application on kinetis MCU please refer to the DOC”Kinetis Bootloader Demo Application User’s Guide”(It is under the KBOOT install package: NXP_Kinetis_Bootloader_2_0_0\doc).   When using KDS build the bootloader image, there is one point need to be paid attention: the image size in debug mode build is over 0xa000(the 0xa000 is user's application start address). That is to say , if we download the debug build image to mcu, can’t use it . So this doc povides the correct way to use the KBOOT on KDS, the problem shows in FRDM-K64 and FRDM-K22 boards, on other chips , if they also have the out of range problem, the correct method is the same .   How to correctly use the KBOOT v2 on KDS ? Please check this DOC on attachment !

Writing to SD Card in KDS   Description:   A project made in KDS using the FRDM-MK64FN1M0VLL12 board to write to SD Card. Every second, the time and the value of the variables x, y and z will be written to an SD Card. They will be written in a log.txt file, which will be created if it does not exist. x, y and z are set to 1, 2, and 3 by default.   Sections of code taken from http://mcuoneclipse.com/2014/05/26/tutorial-data-logger-with-the-frdm-k64f-board/   Issues:   Time will always begin at 17:51:31 after being flashed. This is due to it being set as such at TmDt1_Init.

A service pack has been published in the download section of Kinetis Design Studio on http://www.freescale.com/kds which adds bare metal (no Processor Expert, no Kinetis SDK) support for the following Kinetis M devices:   The update is available for KDS v3.0.0 for Linux, Mac and Window:   The download is available for each of the host operating systems supported by KDS: The downloaded archive (zip file) contains the release notes and the Eclipse update which gets installed into KDS using the menu Help > Install New software and then using the zip file inside the archive (unpack the archive first).

Greetings, the new release of Kinetis Design Studio V2.0.0 has been released and is available on the web (http://www.freescale.com/kds).   V2.0.0 is a new full release, supporting Windows (7/8 (both 32 and 64bit) and Linux (64bit binaries for Ubuntu, RHE and CentOS) from the download tab: Kinetis Design Studio Integrated Development |Freescale (current description says 32bit for Linux, but it is really 64bit, this should be fixed soon).   What's new: Support for 64bit Linux with 64bit binaries. Improved NPW (New Project Wizard) which automatically creates debugger launch configurations for OpenOCD, P&E and Segger. Automatic device filtering in the NPW. Greatly improved Kinetis SDK support with automatically adding compiler include paths for new Kinetis SDK component and files. Updated P&E and Segger debug connections Built-in support for the upcoming Kinetis SDK v1.1 release Updated Processor Expert (V10.4.2) Many bug fixes and other improvements Details in the Kinetis Design Studio V2.0.0 release notes (Documentation Tab). As with the previous V1.1.0 release, new device support and Kinetis SDK support is added through the SDK Eclipse update, present in the Kinetis SDK. See the release notes for details.   There is no need to uninstall V1.1.1, as V2.0.0 can be installed in parallel, and projects are compatible. Moving to V2.0.0 is highly recommended for Linux users and anyone using the Kinetis SDK.   Best regards, Erich Styger

Hi everybody,   this time you will find in the attached document the required settings to build a C++ project using KDS3.0 and MQX for KSDK1.2.   For information about creating a simple C MQX RTOS for KSDK1.2 project please see the following document. How To: Create a New MQX RTOS for KSDK Project in KDS   For information about creating a simple C FreeRTOS for KSDK1.2 project please see the following document. How to: Create a New FreeRTOS for KSDK1.2 Project in KDS3.0   Best regards, Carlos

Greetings, By default the Java heap memory size in Kinetis Design Studio V3.0.0 (and earlier version) is set to 512 MBytes. Depending on Eclipse usage (number of open projects, views open) that might not be enough, causing Eclipse to react slowly. The solution is to increase the available memory for Java. The attached technical note describes the problem and how to increase the heap size.   Erich

'Bare' (no PEx, no SDK) projects created with KDS V1.0.1 beta have the issue that the watchdog is not disabled (see KDS V1.0.1beta release notes). This document explains how to disable the watchdog for the FRDM-KL25Z (steps are similar to other boards).   1. Add Derivative Header file Add the derivative header file to your project. The header files are located in C:\Freescale\KDS_1.0.1\eclipse\ProcessorExpert\lib\Kinetis\iofiles Copy the matching header into the Startup_Code folder:   2. Disable Watchdog Open startup.c and locate the function __init_hardware(). Include the derivative header file and the code to disable the watchdog:   This will disable the watchdog during startup. The above project is attached as a reference.   Code for the K64F #define STARTUP_WDOG_STCTRLH_VALUE                     0x01D2U   /* WDOG_STCTRLH value */ #define STARTUP_WDOG_KEY_1                             0xC520U   /* Watchdog unlock key 1 */ #define STARTUP_WDOG_KEY_2                             0xD928U   /* Watchdog unlock key 2 */   void __attribute__ ((weak)) __init_hardware(void) {   /* Disable the WDOG module */   WDOG_UNLOCK = (uint16_t)STARTUP_WDOG_KEY_1; /* Key 1 */   WDOG_UNLOCK = (uint16_t)STARTUP_WDOG_KEY_2; /* Key 2 */   WDOG_STCTRLH = (uint16_t)STARTUP_WDOG_STCTRLH_VALUE; /* Disable WDOG */ }

Temperature in KDS   Description:   A project made in KDS using the FRDM-MKL46Z256VLL4 board's LCD screen to display temperature. The LCD will display temperature data taken from the magnetometer in degrees Celsius. Data is read every 500ms as this lowers flickering when between temperatures.   Updates:   After initially submitting this project after having it working, I tried to load it up and found out the temperature not displaying correctly. After much trial and error I managed to find out that not initializing the magnetometer was causing the issues, even though it was not the previous day! Have edited the project to add in the initialization just in case it causes anyone else errors.

- This document introduces how to develop a simple CAN module application on KDS, it is suitable for the beginners to start using the KDS and Processor Expert, and it mainly focus on how to developing a CAN Loopback application, how to use the “Typical Usage” of “help on component”. - About the Sending or Receiving data demo(with interrupt or polling) we can find on  the "Typical Usage" of "help on component" . - Pay attention that , in the Typical Usage code , the Transfer Message ID is 0x123u, while in the CAN_LDD default configuration , the Receive Message ID is 0x7FF, they are should be same . So we should change one of them (In standard frame format, the admissible range is from 0x00 to 0x7FF; in extended format, the range is from 0x00 to 0x1FFFFFFF ), on my project , I change the TX ID from 0x123u to 0x7FFu on the code, about the detail information, please look at the document and application project.   This application hardware is TWR-K21F120M board, software is KDS v3.2.0 .

USB Keyboard in KDS   Description:   A project made in KDS using the FRDM-KL25Z128M4 board as a USB keyboard input. The LED will flash red while not connected as a USB keyboard, and flash green when it is. The reset button will press the print screen button. The reset button can be configured to press any possible key as long as they are correctly #defined. Use http://www.usb.org/developers/devclass_docs/Hut1_11.pdf as a reference for keys. Strings may also be output, see the commented out H1DK1_SendStr call in main.c for an example.   Sections of code taken from http://mcuoneclipse.com/2013/06/30/using-the-frdm-kl25z-as-usb-keyboard/

USB Mouse in KDS   Description:   A project made in KDS using the accelerometer on a FRDM-MKL46Z256VLL4 board to control a USB mouse input. A red LED will flash while not connected as a USB mouse, and green LED will flash when it is. SW1 will right click. SW3 will left click.   Sensitivity of the mouse can be changed by altering the HIDM1_Move command in main.c   Sections of code taken from: - http://mcuoneclipse.com/2012/09/21/tutorial-accelerating-the-kl25z-freedom-board/ - http://mcuoneclipse.com/2013/08/01/using-the-frdm-kl25z-as-a-usb-mouse-device/

This project is a re-build of Yayra Kwaku Adugu's E14 project, now built in KDS. The project allows the FRDM KL25Z to utilise an external E14 sensor board for accellerometer, magnetometer and pressure sensor, printing data to terminal.   Unfortunately this project runs afoul of a printf bug in KDS and not all printf calls will display properly. More information/examples of this bug can be seen at Re: printf() weirdness - Using printf() with ConsoleIO and TeraTerm via OpenSDA - issues   Hopefully if/when the printf implementation is fixed in KDS, the project should work fine and display data to terminal.   Project Info: Board used: MKL25Z128VLK4 Terminal Baud Rate: 9600

After we released the "Kinetis Bootloader to Update Multiple Devices in a Network for Cortex-M4" (Kinetis Bootloader to Update Multiple Devices in a Network for Cortex-M4 ), many customers want to port it to FRDM-K64 board, so here I share it.   - This bootloader is based on KDSv3.2. -About the detail introduce and user guide, please refer to:    https://community.nxp.com/docs/DOC-328365 - There also some points when porting, please check the attachment. - I attached the project source code. And also two user application projects.   Customers can refer to the application and user guide to configure your application project. - The GUI is the same with bootloader for k22, we do not change anything.   BR Alice