Using Flash Programmer Task for Standalone programming Standalone Programming is widely used when user doesn’t need a debugger for programming in CodeWarrior 10. Thus people only uses elf/s19 file to program target without using project and source files. There is a very famous article written by Erich Styger regarding using “Flash File to Target” as a standalone programmer for target programming. https://mcuoneclipse.com/2012/08/02/standalone-flash-programmer/   Besides this method, Flash Programmer Task is also good for standalone programming.  As I know some customers prefer to use this method because it can also do checksum, dump flash,etc during programming. I will introduce how to utilize Flash Programmer Task step by step in the following for brainstorming. This article is based on CodeWarrior 10.6.4 and FRDM-K64 board, but the method is same for all Kinetis,HCS08,HCS12Z,etc devices   For detail, see attached article and video. General

How to: import example in KSDK Very simple, but very often asked question - how can I import example in KSDK general? The easiest way is import .wsd file, it is a set of all needed files for your project.   1. Open KDS, go to Project Explorer Window and by right click select Import option 2. Choose Existing Projects Sets option 3. Click on Browse and select the project, which you would like to work. In case of KSDK 2.0 go to C:\Freescale\ \boards\frdmk64f\demo_apps\lwip\lwip_tcpecho\freertos\kds   4. You will see the demo project successfully imported in your Project Explorer window and now you can compile and execute demo project.   Enjoy! Iva General Re: How to: import example in KSDK The above procedure does not appear to work with current v2.2 KSDK examples, as there are no .wsd files included with the examples.  Could you provide instructions on the recommended procedure for importing/using KSDK v2.2 examples please ?

Excel MPC5777C 时钟配置器 该配置工具简化了 MPC5777C 设备的 PLL 设置计算和时钟配置。 版本 1.3 增加了在 264/300 MHz MCU 版本之间进行选择的选项。                 请按照以下步骤操作                 注意：必须启用宏！                 1. 输入使用的 XOSC 的频率以及所需的 PLL0 和 PLL1 输出。 - 将值输入“时钟”表的单元格 B14、Q13 和 Q20 - 检查它是否有效或无效 - “PLLconfig”表显示可能的 PLL 配置   2. 配置系统和AUX时钟选择器及其分频器 - 检查系统/外围时钟的计算频率 - 如果无效，请更改源时钟和分频器值以保持最大频率                 3. 按“复制代码”按钮复制生成的代码 测试

センサーの概要 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

Example MPC5777C MCAN-FD simpleTX RX-ISR GHS616 ******************************************************************************** * Detailed Description: * * Configures the MCANs to transmit and receive a CAN FD message with or without * bit rate switching for data phase. This is defined by BRS macro. * Baudrate during arbitration phase is set to 500kbps, during data phase 1Mpbs * because of PHY used on the EVB. * * In this config, MCAN_0 transmits a message. MCAN_1 receives the message. * * MCAN_0 sends message each 1sec. This interval is generated by PIT. * Single TX buffer is used to send n bytes. The message ID is changed for each * transmission. Two standard and 2 extended IDs are sent. * * MCAN_1 is configured to receive a message, ISR is used to read new message. * There are 2 standard and 2 extended ID filter tables defined. Classic filter * configuration is set, means filter ID & mask. * Messages with matched standard ID are received into RXFIFO_0, messages with matched * extended ID then stored in RXFIFO_1. *   * EVB connection: * * J37 and J38 to position 2-3 to connect MCAN1 TX/RX to transceiver * * CAN0-CANH on P15-1 to CAN1-CANH on P14-1 * CAN0-CANL on P15-2 to CAN1-CANL on P14-2 * * * ------------------------------------------------------------------------------ * Test HW:         MPC5777C-512DS Rev.A + MPC57xx MOTHER BOARD Rev.C * MCU:             PPC5777CMM03 2N45H CTZZS1521A * Fsys:            PLL1 = core_clk = 264MHz, PLL0 = 192MHz * Debugger:        Lauterbach Trace32 * Target:          internal_FLASH * Terminal:        19200-8-no parity-1 stop bit-no flow control on eSCI_A *           use USB connector (J21) on minimodule * * EVB connection:  ETPUA30 (PortP P23-15) --> USER_LED_1 (P7-1) *                  ETPUA31 (PortP P23-14) --> USER_LED_2 (P7-2) * ******************************************************************************** ******************************************************************************** * Detailed Description: * * Configures the MCANs to transmit and receive a CAN FD message with or without * bit rate switching for data phase. This is defined by BRS macro. * Baudrate during arbitration phase is set to 500kbps, during data phase 1Mpbs * because of PHY used on the EVB. * * In this config, MCAN_0 transmits a message. MCAN_1 receives the message. * * MCAN_0 sends message each 1sec. This interval is generated by PIT. * Single TX buffer is used to send n bytes. The message ID is changed for each * transmission. Two standard and 2 extended IDs are sent. * * MCAN_1 is configured to receive a message, ISR is used to read new message. * There are 2 standard and 2 extended ID filter tables defined. Classic filter * configuration is set, means filter ID & mask. * Messages with matched standard ID are received into RXFIFO_0, messages with matched * extended ID then stored in RXFIFO_1. *   * EVB connection: * * J37 and J38 to position 2-3 to connect MCAN1 TX/RX to transceiver * * CAN0-CANH on P15-1 to CAN1-CANH on P14-1 * CAN0-CANL on P15-2 to CAN1-CANL on P14-2 * * * ------------------------------------------------------------------------------ * Test HW:         MPC5777C-512DS Rev.A + MPC57xx MOTHER BOARD Rev.C * MCU:             PPC5777CMM03 2N45H CTZZS1521A * Fsys:            PLL1 = core_clk = 264MHz, PLL0 = 192MHz * Debugger:        Lauterbach Trace32 * Target:          internal_FLASH * Terminal:        19200-8-no parity-1 stop bit-no flow control on eSCI_A *           use USB connector (J21) on minimodule * * EVB connection:  ETPUA30 (PortP P23-15) --> USER_LED_1 (P7-1) *                  ETPUA31 (PortP P23-14) --> USER_LED_2 (P7-2) * ******************************************************************************** General Re: Example MPC5777C MCAN-FD simpleTX RX-ISR GHS616 Hi Luke, yes, you are correct. The MCAN1's base is 0xFFE3_8000 on MPC5777C. In fact this macro is not used in the code, so have no effect.  It comes from other project (for MPC5777M I think) and I forgot to delete it. BR, Petr Re: Example MPC5777C MCAN-FD simpleTX RX-ISR GHS616 Hello PetrS‌ Could you check my question about thie code? when I cheked main.c, I think that #define MCAN1_BASE_ADDR 0xFFEE8000 is not correct. As far as I know, MCAN1's base is 0xFFE3_8000... Could you check it? Thank you.

INS-N1880 Trends in Aviation and MCFA NXP is one of the pioneers in bringing helping bring multicore solutions to the aviation industry and helping customers navigate the certification requirements. This session will cover the roadmap and status of current certification activities, challenges for 2016 we are addressing for both PPC and ARM devices. NXP is one of the pioneers in bringing helping bring multicore solutions to the aviation industry and helping customers navigate the certification requirements. This session will cover the roadmap and status of current certification activities, challenges for 2016 we are addressing for both PPC and ARM devices. Insight & Innovation

モデル例: S12ZVM 台形波モーター制御 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> サンプル・モデル

Example MPC5748G-FlexCAN_with_interrupts S32DS_1.0 ******************************************************************************** * Detailed Description: * This example shows, how to initialize FlexCAN modules for simple transmission * and reception using RX interrupt. Both modules are configured for 100kbit/s * bit rate. CAN_0 module transmits message using MB0. CAN_1 module receives * message using interrupt via MB0. * * * ------------------------------------------------------------------------------ * Test HW:         MPC5748G-324DS, MPC574XG - Motherboard * MCU:             PPC5748GMMN6A 1N81M * Fsys:            PLL0 160MHz * Debugger:        Lauterbach Trace32 *                  PeMicro USB-ML-PPCNEXUS * Target:          internal_FLASH (debug mode, release mode) * EVB connection:  Connect jumpers J15 and J16 on motherboard *                    Connect P14 H to P15 H *                    Connect P14 L to P15 L * ******************************************************************************** ******************************************************************************** * Detailed Description: * This example shows, how to initialize FlexCAN modules for simple transmission * and reception using RX interrupt. Both modules are configured for 100kbit/s * bit rate. CAN_0 module transmits message using MB0. CAN_1 module receives * message using interrupt via MB0. * * * ------------------------------------------------------------------------------ * Test HW:         MPC5748G-324DS, MPC574XG - Motherboard * MCU:             PPC5748GMMN6A 1N81M * Fsys:            PLL0 160MHz * Debugger:        Lauterbach Trace32 *                  PeMicro USB-ML-PPCNEXUS * Target:          internal_FLASH (debug mode, release mode) * EVB connection:  Connect jumpers J15 and J16 on motherboard *                    Connect P14 H to P15 H *                    Connect P14 L to P15 L * ******************************************************************************** General Re: Example MPC5748G-FlexCAN_with_interrupts S32DS_1.0 Thank you, It works Best regards Re: Example MPC5748G-FlexCAN_with_interrupts S32DS_1.0 Hello, if you want FlexCAN example based on SDK, this is directly included in S32 Design Studio. If you want to use this one. you can simply create new project and manually migrate source codes or you can try to use following tutorial https://community.nxp.com/docs/DOC-335361  Regards, Martin Re: Example MPC5748G-FlexCAN_with_interrupts S32DS_1.0 Hello martinkovar, Do you have any updated version of this example to work with the SDK or new version of compiler? If not, could you please tell me what should I do to get this example to work on R1.2017? Thank you so much Re: Example MPC5748G-FlexCAN_with_interrupts S32DS_1.0 Hello, Do you have the example with DMA enabled on FlexCAN? Thanks, Xiaofeng Re: Example MPC5748G-FlexCAN_with_interrupts S32DS_1.0 Hello, which version of S32DS you use? If you recompiled this in S32DS v1.2 or R1.2017, it would not work correct, because there are some significant changes in compiler. Regards, Martin Re: Example MPC5748G-FlexCAN_with_interrupts S32DS_1.0 Hi，I download your code,it can run,but i have some problems when debug it. when i debug it ,it would go to dummy interruption function。like below picture, then,i press the F5(step into),it will enter main() function.like below; I'm confused, why it's not the first to go into main () function. Thank you . Regards, YSl

LPCXpresso54608 开箱即用 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> LPCXpresso54608 开发板可与我们的统一软件开发套件 (SDK) 一起开箱运行！ （在 “我的视频” 中查看）

SGTL5000 audio quality debug Now we are debugging audio quality with sgtl5000 on i.mx6DL platform. The test audio curve is attached, what we need now is to get 8dB more gain at 90Hz and 15dB more at 5KHz. Can anyone help on setting regs in sgtl5000 codec?How? Thanks in advance. General

LPC800 Mini-Kit To help you get started with the LPC800 Mini-Kit, we've put together a few basic resources for you here. LPC800 Mini-Kit Code Base The LPC800 comes populated with an LPC810 MCU in a DIP8 package. The LPC810 package a lot of peripheral punch into a small, extremely affordable package, but as with any deeply embedded device, it's always a challenge to fit the most code and functionality possible into the smallest device available. The LPC810 with 4KB flash and 1KB SRAM is no exception. To help you get started writing light-weight, but easy to understand code in C, we've put together a basic code base for the LPC810 Mini-Kit based around NXP's free LPCXpresso IDE, which uses the free GNU toolchain beneath the surface. The latest version of the code can be viewed and downloaded online on github (LPC810 Code Base), or you can download the latest version directly. Board Schematic The schematics for the LPC800 Mini-Kit are available for download here. See what the LPCWare community did with it! In 2013, NXP ran the LPC800 Simplicity Challenge, and the LPCWare community showed amazing inventiveness in what they created. Check out what they did on our LPC800 campaign pages. Further LPC800 Resources In addition to the LPC800 Mini-Kit Code Base above, you may find some of the following links useful working with the LPC810: LPC810 Product Page on NXP.com LPC800 Switch Matrix Configuration Tool Introducing the LPC800 Videos on YouTube LPC800 Switch Matrix: Making life easier one pin at a time (LPCNow.com) LPC800 LPCXpresso Board Schematics LPCXpresso Forum (for LPCXpresso related support) Tutorial: Getting Started with the LPC810 (Adafruit.com) Programming the LPC800 Mini-Kit with Flash Magic The LPC800 mini board can be programmed using any SWD debugger and your favorite IDE -- NXP's own LPCXpresso, as well as IAR, Keil uVision, and Crossworks for ARM all support the LPC800 out of the box! -- but you can also use an inexpensive UART/USB adapter and ISP mode to program the flash memory on the LPC810. What You'll Need A USB to UART cable or adapter, such as FTDI's popular 'TTL-232R-3V3' cables or a breakout based on the FT232RL chipset The latest version of the free Flash Magic tool​ Configuring the LPC800 Mini Board The first step you will need to do is connect you UART to USB adapter cable to the 'FTDI' header on the top of the LPC800 Mini Board. The pin layout is setup to match FTDI's popular cables by default, specifically the 'TTL-232R-3V3'. Other adapters can of course be used, but you will need to connect the GND, VCC, TXD and RXD pins in the right location yourself. FTDI's TTL-232R-3V3 cable is shown connected here as a reference: LPC800-mini-board The next step is placing the LPC810 in 'ISP' mode. This is accomplished by pulling PIO0_1 'low' during reset, which causes the bootloader to enter ISP mode. The LPC800 mini board conveniently has an 'ISP' switch – the white button in the bottom left-hand side of the board – which we can hold down to pull the ISP pin low. While continuing to press the ISP button, press and then release the 'RESET' button (the red button on the opposite side of the board). This will cause the board to reset, the internal bootloader will see that the ISP pin is low, and it will enter ISP mode where we can program the flash in Flash Magic using the on-chip UART0 peripheral. Configuring Flash Magic for the LPC810 The next step requires you to download and install the latest version of Flash Magic if you haven't already done so. It's available for free at http://www.flashmagictool.com/. Once installed, open the tool, and the run through the following steps: Setup the 'Communications' options: Select LPC810M021FN8 as your target device Set your COM port to whatever port your USB to UART adapter enumerated as (you can find this in the device manager in Windows) Set the Baud Rate to 115200, or whatever matches your USB to UART adapter Make sure that the 'Interface' is set to 'None (ISP)' Set the Oscillator to '12', which matches the speed of the IRC used by the bootloader You can double-check all of your communications settings and connection by selecting the 'ISP > Read Device Signature …' menu item. If you are in ISP mode and properly connected, with the right 'Communications' settings, you should see something similar to the following screen:FlashMagic Device IDIf you get an error message, double check your connections and your settings in Flash Magic, making sure you are actually in ISP mode on the LPC810, and that you've selected the right COM port. Check the 'Erase blocks used by Hex File' checkbox in the 'Erase' section. Select your hex file in the 'Hex File' section: Use the 'Browse' button to point to the Intel Hex file generated by your toolchain or IDE (for example, LPCXpresso). You can also use one of the sample .hex files available here if you don't have a .hex file ready yet. You should end up with Flash Magic configuration as follows ('Verify after programming' is optional): Flash magic settings: Now click the 'Start' button to program the flash … … and finally, once the device has been programmed, reset your board (via the red 'Reset' button). If at some point you want to change your firmware, simply repeat the process of re-entering ISP mode by holding the ISP pin low, resetting the LPC810, releasing the ISP pin, and the programming the device via Flash Magic again. Known issues There is an issue with some of the LPC810 DIP8 parts that are populated on the mini board that prevents the analog comparator from functioning. To see if the part on your board is affected, locate the date code on the top of the DIP8 package (the last line of text on top of the chip). If this line end with either "2X" or "2A", your part is affected. LPC800 mini board schematics Rev AR2.pdf - Attached

AMF-AUT-T2346 - 实践研讨会：S32K、设计工作室和 SDK <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 与会者将通过简短的教程和实际软件示例了解 S32K144 上的模块。该实验室将使用 NXP 的 S32 Design Studio 工具，包括 Processor Expert 和 S32K SDK。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 与会者将通过简短的教程和实际软件示例了解 S32K144 上的模块。该实验室将使用 NXP 的 S32 Design Studio 工具，包括 Processor Expert 和 S32K SDK。

Layerscape多核通信处理器的ARM® v8虚拟化 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> EUF-NET-T1745 - ARMv8 虚拟化技术概述、其与基于 NXP Layerscape ARMv8 的 SoC 的集成以及通过 QorIQ SDK 实现。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> EUF-NET-T1745 - ARMv8 虚拟化技术概述、其与基于 NXP Layerscape ARMv8 的 SoC 的集成以及通过 QorIQ SDK 实现。

Kinetis KW41Z Bluetooth® Low Energy Bike Computer Demo This demo consists of a Kinetis KW41Z with a TFT display that will be mounted on a bike and collecting speed and cadence measurements from Bluetooth® Low Energy mass market sensors as the ride goes. The logged data will be sent to another Kinetis KW41Z connected to a PC that forwards data to the Cloud   https://community.nxp.com/players.brightcove.net/4089003392001/default_default/index.html?videoId=4939361163001 Features: Kinetis KW41Z SoC Bluetooth® Low Energy 4.2 compliant Simultaneous Bluetooth® Low Energy Connections with market ready sensors products Bluetooth® Cycling Speed and Cadence Profile implementation interoperable with market ready product Wireless Connectivity   _______________________________________________________________________________________________________   Featured NXP Products: Product Link Kinetis® KW41Z-2.4 GHz Dual Mode: Bluetooth® Low Energy and 802.15.4 Wireless Radio Microcontroller (MCU) based on Arm® Cortex®-M0+ Core Arm® Cortex®-M0+|Kinetis® KW41Z 2.4 GHz Bluetooth Low Energy Thread Zigbee Radio MCUs | NXP  Freedom Development Kit for Kinetis® KW41Z/31Z/21Z MCUs FRDM-KW41Z |Bluetooth Thread Zigbee enabled Freedom Development Kit | NXP  Bluetooth Low Energy/IEEE® 802.15.4 Packet Sniffer/USB Dongle USB-KW41Z|Bluetooth Low Energy Thread Zigbee Wireless Packet Sniffer | NXP  _______________________________________________________________________________________________________ Smart City

CodeWarrior Licensing Document List These are CodeWarrior Licensing Community Document list:   Web License System: New Web license system - December 8th, 2014 & Problems with Freescale Account. New Web license system - Registering your physical shipment Software and Support contracts. How to download a Service Pack / Patch / Update from Web License System?   Register and Purchase: How to register and retrieve CodeWarrior suite licenses How to complete a Software Activation Share Account Invite. Are you getting an Error that your registration code does not exist? How to extend my evaluation license file for CodeWarrior   Renewal: How to apply renewal code on registration? How to renew support for CodeWarrior suite licenses How to purchase your support renewal for multi-seat software registration. How to renew MQX RTOS add-on SW IPv6 DL-MQXIPV6-SR-PS   Rehost: How to rehost CodeWarrior suite license Cannot Re-host a license - License Lists is empty  (valid to generate a license file associated to a registration too).   Floating License Related: How to install/check if my floating license file is running ? (known issues) Step Byt Step Screenshot Guide Floating license FlexLM for CodeWarrior.pdf   USB Dongle Related: How to install/use USBdongle license under Win 8.1? (Include test with CW for MPC55xx V2.7 & CW for HC12 v5.1) USBdongle license is not running for CW for PA V10.4 and MCU V10.4 (sometimes) ->  "LM_NOTTHISHOST"   Misc: How to merge multiple floating and NL license files in 1 file What is the difference between the Offline and the Online Installer for MCU 10.5   License FAQ: Licensing and Registration FAQ|NXP   More CodeWarrior Licensing Discussions: CodeWarrior Licensing Community General

HMB-N1962 IPv6 Over Bluetooth® Low Energy (6LoBLE) Lecture and Demo The course will detail RFC 7668 (6LoBLE), Bluetooth® low energy 4.2 and the Internet protocol support profile that are used to transport IPv6 frames in an IoT environment. The demo will be based on the Kinetis KW41 MCU. The course will detail RFC 7668 (6LoBLE), Bluetooth® low energy 4.2 and the Internet protocol support profile that are used to transport IPv6 frames in an IoT environment. The demo will be based on the Kinetis KW41 MCU. Smart Home & Buildings Re: HMB-N1962 IPv6 Over Bluetooth® Low Energy (6LoBLE) Lecture and Demo Hello lisahughes  laurenhernandez, Thanks for this Document. I really would like to implement this Demo on my own OpenWRT device to get a communication to each 6LN Node, which is connected to the 6LBR. So i'm interested in the slides 20 to 32. What I'm missing is a detailed description, which software hast to be implemented on the USB-KW41Z from the SDK_2.2_USB-KW41Z ? Which binary has to be implemented on the K22F on USB-KW41Z and which which HCI-example hast to be implemented on the KW41Z itself?  On slide 21 is only mentioned that USB-KW41Z implements HCI App over UART! More detailed informations would be awesome! And which role, does the wireless_examples > bluetooth > ipv6router  from the SDK, playing in this Demo!? Thanks a lot! Best Regrads, Steffen

DES-N1908 USB Type-C概述 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> USB Type-C和USB-Power交付是什么? 为什么消费电子产品和移动计算产品采用这种新的Type-C接头？ 使用这种接头的优点和缺点是什么？ USB Type-C和PowerDelivery的未来会是什么样？ 在本次培训中，恩智浦(SIP)将重点介绍这一新技术和生态合作体系。 本次培训是由市场和生态合作体系驱动的讨论，而不是技术讨论。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> USB Type-C和USB-Power交付是什么? 为什么消费电子产品和移动计算产品采用这种新的Type-C接头？ 使用这种接头的优点和缺点是什么？ USB Type-C和PowerDelivery的未来会是什么样？ 在本次培训中，恩智浦(SIP)将重点介绍这一新技术和生态合作体系。 本次培训是由市场和生态合作体系驱动的讨论，而不是技术讨论。 设计 | 软件与服务

USDPAA および Linux カーネルでの QMAN 専用チャネルとプール チャネルの使用 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> FQ 上のフレームを処理する準備ができると、FQ はワーク キュー (WQ) にエンキューされます。WQ はチャネルに編成されます。チャネルは、8 つのワーク キューの固定されたハードウェア定義の関連付けであり、"優先ワーク キュー" でもあります。QMAN では、次の 2 種類の WQ チャネルが定義されています。 専用チャネルは、常に 1 つのエンティティによって処理されます。 プール チャネルは、プロセッサ コアのプールなど、類似エンティティのプールによって処理されます。 このドキュメントでは、専用チャネルとプール チャネルに関する基本的な概念、専用チャネルとプール チャネルをフロー順に使用する方法、保持シナリオ、ワーク キュー チャネルの割り当て、Linux カーネルで使用される専用チャネルとプール チャネル、および PPAC および USDPAA QMAN ドライバを USDPAA アプリケーションで専用チャネルを使用するように変更する方法について説明します。 1. QMANチャネルの基本概念 2. フロー順序の保持シナリオで使用される専用チャネル 3. Hold Active Schedulingを使用した順序保持で使用されるプールチャネル 4. ワークキューチャネルの割り当て 5. Linuxカーネルでの専用チャネルとプールチャネルの使用 6. USDPAAの専用チャネルの使用 QorIQ P2デバイス QorIQ P3デバイス QorIQ P4デバイス QorIQ P5デバイス

Working with FreeRTOS projects using KDS and KSDK 1.3 Project Generator tool Hello all, This document describes how to create a FreeRTOS project in KDS using the Kinetis SDK Project Generator tool. If you are interested in how to Create a FreeRTOS project using KDS and Kinetis SDK Project V2.0 please check the below link: https://community.freescale.com/docs/DOC-330183 In order to follow this document, first it is necessary to install: Kinetis Design Studio (KDS) Kinetis Design Studio Integrated Development |NXP KINETIS-SDK: Software Development Kit for Kinetis MCUs Software Development Kit for Kinetis MCUs|NXP KSDK Project Generator tool Software Development Kit for Kinetis MCUs|NXP Creating a new project using the Project Generator tool Kinetis SDK Project Generator tool is a supplement to the KSDK. It is intended to provide users with a convenient method for generating KSDK based projects for their intended target hardware. The KSDK Project Generator requires the user to install an instance of KSDK 1.2.0 or 1.3.0 before generating new projects. The KSDK Project Generator requires operates on Windows, Linux, and Mac OSX. 1. Launch the Project Generator executable. 2. Introduce the Project Name and choose the board used. For this example it is used the TWR-K64F120M. 3. In order to generate a FreeRTOS project, click on the "Advanced" button. 4. Choose the operating system, in this case FreeRTOS, the IDE KDS and select Generate standalone project. 5. After that, click on "Advanced Generate" button to create the project. Open the project in KDS Every application/example created using the KSDK Project Generator tool has one associated working set description file which includes the path to the example project file and the dependent RTOS library project file. Simply import that file into KDS working space. At this point you should be able to build the library and the project created. Developing a FreeRTOS with KSDK application Operating System Abstraction layer (OSA) provides a common set of services for drivers and applications so that they can work with or without the operating system. OSA provides these services: task management, semaphore, mutex, event, message queue, memory allocator, critical part, and time functions. An easy method to create a task is using  the OSA_TASK_DEFINE macro and the function OSA_TaskCreate(). The macro OSA_TASK_DEFINE declares a task handler and task stack statically. The function OSA_TaskCreate() creates task base-on the resources declared by OSA_TASK_DEFINE. The parameters for this function are: The stack size in byte. Pointer to the stack. The stack size in byte. Pointer to the stack. Initial priority of the task: OSA supports task priorities 0∼15, where priority 0 is the highest priority and priority 15 is the lowest priority. Pointer to be passed to the task when it is created. If this task will use float register or not. Pointer to the task handler. NOTE: The disadvantage with this method is that task function can only create one task instance. The project created using the Project Generator tool creates one  task (task_example) implementing OSA. For more information about functions, macros and drivers please consult the Kinetis SDK v.1.3 API Reference Manual. This is located, after install Kinetis SDK, at the path: \doc GPIO Example 1. Add a new task named task_led. Add also a macro for OSA_TASK_DEFINE, the priority of the task and the prototype. To initialize and start RTOSes, OSA uses abstract functions OSA_Init() and OSA_Start(). Call OSA_Init() after calling hardware_init(). 2. Create the empty body of task_led 3. Add the following code initialization code for GPIO driver. PRINTF("\nLED TASK is running \n"); /* Enable clock for PORTs */ CLOCK_SYS_EnablePortClock(PORTA_IDX); CLOCK_SYS_EnablePortClock(PORTE_IDX); //Initializes GPIO driver GPIO_DRV_Init(switchPins, ledPins); 4. Now add logic to toggle a LED when a button is pressed. while(1) { //  check if SW2 is pressed if(GPIO_DRV_ReadPinInput(kGpioSW3) == 0) { GPIO_SW_DELAY; GPIO_DRV_TogglePinOutput(BOARD_GPIO_LED_BLUE); } } 5. It is needed a delay for the push buttons debounce. In this case it is GPIO_SW_DELAY which is defines as follows: /*Delay for Switch debounce*/ #define GPIO_SW_DELAY \ do \ { \ uint32_t i; \ for (i = 0; i < 0x2FFFFF; i++) \ { \ __asm("nop"); \ } \ } while (0) GPIO 6. Build and debug the project. Enjoy... Re: Working with FreeRTOS projects using KDS and KSDK 1.3 Project Generator tool I'm using Project Generator 2.2, KSDK 1.3 to generate FreeRTOS project for TWL-POS-K81. The Project Generator does not complete. please advice.

面向新虚拟网络的强大QorIQ多核处理器 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> EUF-NET-T1744 - QorIQ 路线图和处理解决方案概述，用于解决虚拟化网络中的新技术挑战。我们将介绍基于 Power Architecture ®和 ARM ®最新产品衍生产品，同时重点介绍 NXP 在数据包加速、安全功能连接、功耗和可扩展性方面的关键差异化因素。您将了解基于 LS1021、T1024、LS1043、T4240 和 LS208X 的智能网络新参考设计。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> EUF-NET-T1744 - QorIQ 路线图和处理解决方案概述，用于解决虚拟化网络中的新技术挑战。我们将介绍基于 Power Architecture ®和 ARM ®最新产品衍生产品，同时重点介绍 NXP 在数据包加速、安全功能连接、功耗和可扩展性方面的关键差异化因素。您将了解基于 LS1021、T1024、LS1043、T4240 和 LS208X 的智能网络新参考设计。