Hello all,      So, this time there is a query on implementing IRDA communication by bit banging the GPIOs. So, I come up with an experiment to do so. Before that, why bit banging when KE02 supports IR communication right away by using FTM at TX and ACMP at RX? something similar to this Implementing infrared functions on UART0 with FRDM-KE02Z platform.        The answer lies in the waveform attached. In the code from the above discussion, the PWM modulation is performed on FTM channel for transmission, while the communication that customer required was different and the waveform required is the one attached.                                                                                           Note that the IRDA transmitter on FRDM-KE02Z is connected to UART0. But, in the attached code, UART0 is not configured for IRDA_TX. while ACMP is used for RX.      This post is intended to be a reference to those who want to implement IRDA with 3/16th bit width by bit banging.      Here is the schematic snapshot of the FRDM-KE02.   There are 2 sets of codes attached. 1. FRDM_KE02_singleboard_IRDA_BITBANGING_TX_RX - IRDA on a single board. 2. FRDM_KE02_interboard_IRDA_BITBANGING_TX_RX - IRDA between 2 boards.   To run a single board demo, the orientation of IRDA Transmitter and IRDA receiver is already taken care as both are on the same board. But, to run the second demo, the orientation is supposed to be something like this.   Both the demos are configured for 9600baud to communicate with PC. And the IRDA communication is at 2400baud.      The figure in page 13 of this document is referred while development. http://www.vishay.com/docs/82513/physical.pdf                                                                            Transmission - 1. The bit width is calculated depending on the required IRDA baud and PIT1 modulo is adjusted accordingly. There are 3 MOD values initialized one after the other to generate required IR frame. 2. The data to be transmitted is sent over the HyperTerminal @ 9600baud. This data is accordingly transmitted on PTB1.      The green waveform in the below oscilloscope snap is the IR frame from the above picture. The data being sent is 'e', the hex value of which is 0x65 which can be made out from the waveform. 0x65 is 0xa6 in reverse since LSB is sent out first in the IRDA protocol[The first logic high is the start bit. In IRDA transmission, logic low is data '1' and logic high is data '0'].                                                                                      Reception - 1. ACMP0 is configured to generate interrupts on either the rising edge or the falling edge. 2. The falling edge of the start bit triggers ACMP. 3. The logic received on PTA1 is decoded to arrive at the received data. 4. The falling edge on ACMP channel decides logic 0 and the PIT0 interrupt decides the logic 1.      The below waveform is the one probed at PTA1.                                                                     Thanks, Pramod TM

I recently developed a Visual Studio .NET application that uses an OpenSDA virtual serial port to communicate with a FRDM-K64F. My serial protocol is a binary command-response protocol, which means that every time the .NET application sends a command packet to the serial port, it should always receive a response packet back. You can find more details about the protocol in the Freescale Intelligent Sensing Framework, but for the purposes of this document, all that matters is that every command should receive a response. My Visual Studio .NET application uses the SerialPort class, and worked beautifully...until I changed the OpenSDA firmware. Originally I used OpenSDA firmware from P&E; this time I had tried out Segger. In theory, this change should not have made a difference, however with the Segger firmware my .NET application never received response packets. I knew that the command packets were transmitting correctly from PC to board because they would turn a board LED on and off as expected. I tried using a binary terminal, RealTerm, to send commands to see if it would receive responses, and it did. So the problem had to be in my .NET application. After a lot of googling and some trial-and-error, I ultimately found that enabling the Data Terminal Ready (DTR) signal did the trick. Strangely, I didn't need to enable DTR in RealTerm. The moral of the story is that if you want to use Segger OpenSDA with a .NET SerialPort, then you must enable DTR. Fortunately this configuration also works with P&E and mbed OpenSDA.

Hello, I've created a application of USB FLASH Drive acessing the 1MB internal FLASH of K64 using the Freescale's bareboard USB Stack 5.0 software + FRDM-K64F to be used by anyone as reference. It seems to be stable, I already wrote some files on that and checked the integrity of the volume. It can be very useful for datalogger application where the equipment can store data on the MCU FLASH using a internal filesystem, and read it through PC as it was a regular USB stick. It also very much cheaper than using a external SD Card, as it only needs the MCU + a external crystal and a USB connector.The only limitation so far is that it cannot exceed the number of the erase/write cycles of the device (of course!). Please see the file attached with the USB Stack and the example on the folder "{Installation Path}\Freescale_BM_USB_Stack_v5.0\Src\example\device\msd\bm\iar\dev_msd_disk_frdmk64f". The project was wrote using IAR. Also I have attached the srec file if you don't want to build the project by yourself. Any issues, doubts or suggestions, please let me know. Denis

The attached zip file contains software that accompanies the document UART Emulation Using the FTM or TPM.  It contains two sample applications:  one that uses the TPM, and one that uses the FTM. The TPM example targets the FRDM-KL26Z development board and is written in baremetal code.  The FTM example targets the TWR-K22F120M and FRDM-K22F and is written using the Kinetis SDK 1.0 release.  Installation instructions are contained within the zip package. Unzip the package to an empty folder and then copy the appropriate folders to the the appropriate locations on your PC per the instructions located in the zip file. 

当芯片被加密后，在Keil或IAR中下载或者调试时，会弹出以下提示信息： 这时如果点击Yes,那么将会对Flash进行一次mass erase,这样就可以重新下载或者调试程序了。 如果把Do not show this message again复选框勾选上的话，那么以后将不再弹出此提示框，并且会自动进行一次mass erase。 实际使用中，不建议勾选Do not show this message again这一复选框，因为勾上之后就无法直观的看到芯片被锁的提示了。 如果不小心把这一复选框勾上了的话，想要恢复到原来的设置，只能通过修改注册表的方法来实现，具体步骤如下 1) 在CMD窗口下，输入regedit，打开注册表    2)设置 HKEY_CURRENT_USER => Software => SEGGER => J-Link => DontShowAgainUnlockKinetis 为0   

Hi, Anybody has sample code for K22 SPI? where shall I get the same? Thank Sarvani

Hi,, Can anyone please post the code for SPI (Serial peripheral interface) using MK22D5.h....I tried doing using processor expert but im getting errors in the main program..please post the code for SPI Thank you

Bootloader是一种面向用户应用程序的引导代码，可以在没有烧写器的情况下烧录用户程序，也可以用于在线更新程序。飞思卡尔提供了三种实现bootloader的方式，分别为： 1.预烧写在ROM中的bootloader     这种方式是MCU中内置了专用的ROM来存放bootloader，目前支持ROM型bootloader的Kinetis系列MCU包括KL03，KL17，KL27和KL43等。其中KL03和KL17的ROM bootloader包含SPI/UART/IIC三种接收方式，KL27和KL43还增加了USB的方式。 2.预烧写在FLASH中一次性bootloader     这种类型的bootloader在芯片出厂前预写在FLASH中，因此可以像ROM型bootloader一样直接使用。但与ROM型不同的是，上电后bootloader会从FLASH搬移到RAM 中运行，再将FLASH整片擦除并烧写用户程序，因此这种bootloader是一次性的。其优点是不需要片内ROM且方便量产烧写，缺点是无法支持以后的程序更新。目前支持预烧写在FLASH中一次性bootloader的Kinetis系列MCU包括K22、K24和KV3x等。 3.开放源码的bootloader     这种方式将FLASH空间分为两个部分，一部分用于存储bootloader代码；另一部分用于存储用户应用程序代码。这种方式的bootloader方便客户定制自己的代码。     目前飞思卡尔提供开放源代码的Kboot，支持UART/SPI/IIC/USB HID 几种接口方式，其网址链接为：     www.freescale.com/kboot     除了Kboot，还有以下独立版本的bootloader，包括：     1）AN2295（开发人员的串行引导加载程序）         文档下载地址为：http://cache.freescale.com/zh-Hans/files/microcontrollers/doc/app_note/AN2295.pdf         代码下载地址为：http://cache.freescale.com/files/microcontrollers/doc/app_note/AN2295SW.zip        另外FAE Yang Liang 对其进行了移植，目前已经支持FRDM-KE02,KE06,KL25,KL26,KL43,KL46, TWR-K60, KV4x, KV10.下载地址为：Kinetis/AN2295_Bootloader · GitHub     2）AN4767 （Kinetis E 系列上的UART Boot Loader 设计）         文档下载地址为：http://cache.freescale.com/zh-Hans/files/32bit/doc/app_note/AN4767.pdf         基于AN2295，没有提供代码。     3）AN4775 （Kinetis E 系列上的IIC Boot Loader设计）         文档下载地址为：http://cache.freescale.com/zh-Hans/files/32bit/doc/app_note/AN4775.pdf         代码下载地址为：http://cache.freescale.com/files/32bit/doc/app_note/AN4775SW.zip     4）AN4368 （USB 大容量存储设备主机引导加载程序）          文档下载地址为：http://cache.freescale.com/zh-Hans/files/microcontrollers/doc/app_note/AN4368.pdf          代码下载地址为：GitHub - Wangwenxue/USB_MSD_Host_Bootloader_K60: This is usb msd Bootloader for K60 （For K60）                                        GitHub - Wangwenxue/USB_MSD_Host_Bootloader_K64: This USB MSD bootloader for K64 （For K64）     5）AN4379  （Freescale USB大容量存储设备引导加载程序）          文档下载地址为：http://cache.freescale.com/zh-Hans/files/microcontrollers/doc/app_note/AN4379.pdf          代码下载地址为：http://cache.freescale.com/files/microcontrollers/doc/app_note/AN4379SW.zip     6）AN4764   （USB Human Interface Device Boot Loader for ColdFire Plus, Kinetis K, and Kinetis L MCUs）          文档下载地址为：http://cache.freescale.com/files/32bit/doc/app_note/AN4764.pdf          代码下载见附件     7）AN4370   （用于 MCU 的 USB DFU 引导加载程序）         文档下载地址为：http://cache.freescale.com/zh-Hans/files/microcontrollers/doc/app_note/AN4370.pdf         代码下载地址为：http://cache.freescale.com/files/microcontrollers/doc/app_note/AN4370SW.zip       8）AN4367   （用于 MCU 的 以太网引导加载程序）         文档下载地址为：http://cache.freescale.com/zh-Hans/files/microcontrollers/doc/app_note/AN4367.pdf?fromsite=zh-Hans         代码下载地址为：http://cache.freescale.com/files/microcontrollers/doc/app_note/AN4367SW.zip         最新的代码请到FNET官网下载：http://fnet.sourceforge.net/    9）Kinetis Bootloader to Update Multiple Devices in a Network - for Cortex-M0+         代码及文档下载地址为：https://community.freescale.com/docs/DOC-328168            

Hello, The below attachment is the code for UART with the input data as a character..But i need the input data to be a STRING...Can anyone please post the code for UART with input as a string using MK22D5.

        IAR使用过程中有一点不太方便的是：当我们打开一个工程之后，如果再直接双击其他eww文件试图打开另外的工程，那么原来的工程就会被覆盖。解决这个问题的方法是：        1. 双击FileTypesMan.exe（该软件见附件，32位系统请解压filetypesman_x86.zip文件，64位系统请解压filetypesman_x64.zip文件）。打开该软件之后，找到.eww 格式并单击一下，显示界面如下图所示：             2. 双击open 所在行，对此条目进行更改，将Command-Line 中的内容：C:\PROGRA~2\IARSYS~1\EMBEDD~1.0\common\bin\IarIdePm.exe "%1" 先复制出来，Default Action 不选，Disable勾选，如下图所示：       3.在FileTypesMan界面的下方区域点击右键，选择New Action，如下图所示：            4.新建action 如下图所示，Action Name和Menu Caption 可随便命名，Command-Line 将上一步复制的内容粘贴过来即可。Default Action 勾选，Disable不选。          5. 最后配置如下图所示：       经过以上简单设置之后，就可以通过直接双击eww文件打开多个工程了。                  Original Attachment has been moved to: filetypesman_x64.zip Original Attachment has been moved to: filetypesman_x86.zip

  当我们在使用Keil 时，经常会遇到无法下载程序的问题，以下对两种常见的情况进行总结：    1. 在我们需要将某工程代码移植到同系列其他型号器件上使用时，如果只是更改了器件型号，这时可能会导致无法正确下载。需要注意的是不仅要在Device中更换型号，还需要在Flash Download栏中选择正确的flash loader 并且设置正确的RAM起始地址。   举个例子：假设我们需要将FRDM_KL26的Sample code中的hello_world工程移植到256K flash的KL26上使用。打开FRDM_KL26的Sample code中hello_world工程，我们可以看到Device中器件为MKL26Z128xxx4，        在Target中可以看到Flash和RAM的起始地址和大小信息。          如果使用Jlink调试接口，选择J-LINK/J-TRACE Cortex  ，之后选择Setting，可以看到flash loader的相关信息。         将此工程移植到到256K flash的器件上，我们需要做的事情是：      在device中进行修改，选择MKL26Z256xxx4               在Target中可以看到这时flash和RAM的起始地址和大小信息已经自动做了更改。不需要再手动修改了。         但是在Flash Download中的设置还是之前的设置，并没有改变。           所以这时是无法正确下载程序的，需要我们手动去修改这里的两处配置。     一是 RAM for Algorithm中的Start应该设置为0x1FFFE000（从Target栏中可以获取该值），Size不用更改。      二是Program Algorithm 删除掉128k的flash loader ，添加256K的flash loader。       2.第二种可能遇到的情况是：本来可以正常下载的程序当复制到另外一台电脑时就无法正常下载了。遇到这种现象时，需要检查一下Flash Download中的相关配置是否正确，很可能会遇到 Program Algorithm中flashloder为空的情况，发生这种情况的原因可能是两个电脑的Keil版本不同，所以flash loader所在路径就会不同，这样flash loader就会变成空白，这时需要自己手动添加一下即可。

      Kinetis SDK是针对于Kinetis系列MCU所做的软件开发套件，又称为KSDK。它由强大的外设驱动代码库，协议栈库与示例代码库等部分组成，能够简化和加快对于Kinetis 系列MCU的应用开发。另外，Kinetis SDK是免费的工具，而且所有的硬件抽象和外设驱动软件均开放完整源代码。目前最新版本为2.0，支持 Kinetis 主流MCU，随后会不断更新完善。对于SDK支持MCU的更新情况，可登陆以下KSDK的下载页面了解。       有关KSDK的更多信息可以从网址www.nxp.com/ksdk 获得。

1.基于CMSIS-DAP的脱机编程工具         飞思卡尔的FRDM开发板都板载OpenSDA仿真器，该仿真器基于MK20DX128VFM5芯片，内部由Bootloader和app所组成，当用户按下Reset按钮后再插上USB接口，此时会进入Bootloader模式，此时PC端会出现一个名为Bootloader的可移动存储器，用户可以通过拖入预编译好的*.SDA升级app，更新v114版本的app后，重新插拔USB即可生效，此时会枚举出虚拟串口，仿真器以及MSD的可移动存储器。Bootloader占用了MK20DX128VFM5内部从0开始到0x5000的地址，App从0x5000地址开始。        CMSIS-DAP(mbedmicro/CMSIS-DAP · GitHub)是ARM公司的一个开源项目，它提供了一个基于Web的开发环境(mbed | welcome), 开发环境提供了基于C++的开发库，用户可以通过Web编程，然后下载编译好的bin文件，通过CMSIS-DAP烧写到FRDM开发板中。CMSIS-DAP与OpenSDA类似，也是由Bootloader和app所组成，最大的区别是CMSIS-DAP的Bootloader占用的地址为0x0~0x8000。        由于CMSIS-DAP是Apache License开源的，通过修改其Bootloader代码可以比较容易的做出一个脱机烧写器参考。        1. 添加SWD的访问接口。        2. 修改链接文件，默认Bootloader是运行在0地址上的，而实际编程工具最好运行在0x5000或者0x8000这两个地址上，这样不需要通过仿真器对于MK20DX128进行编程即可更新其内容，同时也可以轻松在仿真器及烧写器间进行切换。        3. 修改MSD烧写文件的地址，默认Bootloader是烧写从0x5000或者0x8000开始的地址，而这个地址现在放的是脱机烧写器代码，所以需要向后移动到0x10000，并将目标文件大小存放在0x1F800地址上。脱机烧写器由于将目标文件存放在K20芯片内部，所以受到K20内部flash大小的限制，只能烧写目标文件小于60K。        4. 添加编程算法工程，由于目标芯片内部的flash需要不同的驱动，所以可以将他们生产的算法代码先放到K20内部0x1FC00的地址上，烧写器开始工作时，先将编程算法通过SWD下载到目标文件的RAM中，并修改目标芯片的SP PC指针，让其运行。编程算法与烧写器的运行程序通过RAM进行交互。 参考代码下载地址： hudieka/OpenSourceOfflineProgrammerTools · GitHub 具体使用方法可以参考附件：

For Remote Control means, that is needed two computers - Server Computer and User Computer, which will be in connection. There are two types of connection, which can be used - HTTP or DCOM. There are two different ways how to set up the remote control in Windows. I made the tutorial, which describes both types of Remote Control. Ok - so, let´s start! HTTP Settings On the Server Computer side: 1. Plug the board to the Server Computer 2. Go to Remote Communication Server 3. Set HTTP connection and choose the right COM Port according the plugged board If the plugged board is on e.g. COM23, it is possible to edit number of Port in Device Manager On the User PC side: 1. Open FreeMASTER,  go to Project -> Options 2. Choose Plug-in Module: FreeMASTER CommPlugin for Remote Server (HTTP) and type the IP address of the server, do not forget join to IP address :8080 3. And start communication by STOP button to successful connection DCOM Settings On the Server Computer side: 1. Plug board to the Server Computer 2. Launch DCOM in FreeMASTER Remote Server Choose COM according plugged board or edit COM according to step 2 - Server Computer in HTTP Connection (up). 3. Setting permissions for the user, User PC. Right click on Computer -> Manage. In Computer Management click to Distributed COM Users. In Distributed COM Users Properties add the user, User Computer. After that, set the permissions in Component Services. In cmd type dcomcnfg.exe In Component Services go to Computers -> My Computer -> DCOM Config -> MCB FreeMASTER Remote Server Application Right click on MCB FreeMASTER Remote Server Application and go to Properties. In Security Tab is possible to add the permissions. There are 3 types of permissions. First permission - Launch and Activation Permissions. There are 4 permission options. Local Launch and Remote Launch means, that user, User Computer can launch e.g. FM Remote Server Application. But for success communication is needed allowing Local Activation and Remote Activation. Second permission - Access Permissions. Click to Edit and Allow Local Access and Remote Access for the user. Do not forget that if there is a change of permissions, specifically allowing, it is necessary for User to log out and log in. On the User Computer side: 1. Open Freemaster, go to Project -> Options 2. Choose Plug-in Module: FreeMASTER CommPlugin for Remote Server (DCOM) and for filling Connect string is possible to use Configure. Definitely, type the IP address of the server and ;Port Name. 3. And start communication by STOP button in FreeMASTER to successful connection And now.. you can do anything 🙂

下面简单介绍下Kinetis M0+相关的几大系列MCU: 1. Kinetis L    Kinetis L系列MCU的最大特点是它具有非常出色的低功耗特性，L系列目前包含KL0X、KL1X、KL2X、KL3X、KL4X和KL8X六个子系列，除了KL8X的主频为72 Mhz以外，其他主频都为48 Mhz。KL0X系列是入门级MCU，它的Flash相对较小，引脚数量相对较少。KL1X系列是通用型MCU，KL2X系列带有USB功能，KL3X系列支持段式LCD，KL4X系列同时带有USB和支持段式LCD。KL8X系列具有很多Security相关的特性，包括篡改检测、真正的随机数生成器和低功耗可信加密引擎，支持AES、DES、3DES、SHA、RSA和ECC。 2. Kinetis E    Kinetis E系列MCU的最大优势是电磁抗噪性能，Kinetis E系列是业界首款在Cortex M0+基础上构建5V (2.7~5.5V)MCU系统的产品，结合了低成本、高性能、先进的EMC和ESD保护功能，E系列目前包括KE02、KE04和KE06三个子系列，KE02主频有20M和40M两种，KE04和KE06都为48M，KE06相比KE02和KE04主要是多了1个CAN接口。 3. Kinetis V    Kinetis V系列MCU专为BLDC、PMSM和ACIM电机控制以及数字电源转换应用而设计。V系列目前包含KV1X、KV3X、KV4X和KV5X四 个系列，其中Kinetis KV1X系列是入门级产品，Cortex-M0+内核，采用75 MHz M0+内核及硬件平方根和除法模块，与同等级32位MCU相比，在无传感器PMSM控制应用中的性能提高27%。 4. Kinetis W Kinetis W系列集成了领先的Sub-GHz和2.4 GHz射频收发器，可创建可靠、安全、低功耗的嵌入式无线解决方案。W系列目前包含KW0X、KW2X 、KW3X和KW4X四个系列，其中KW0X是M0+内核，48 Mhz，Sub-GHz无线电，超低功耗无线微控制器，KW3X是M0+内核，48 Mhz，具备Bluetooth® Smart/Bluetooth® Low Energy (BLE) v4.1射频连接。KW4X也是M0+内核，具备Bluetooth® Smart/Bluetooth® Low Energy (BLE) v4.1和IEEE® 802.15.4-2011射频连接。 5. Kinetis M      Kinetis M系列 MCU适用于单芯片1、2和3相电表和流量计，以及其它高精度测量应用。M系列目前包括KM1X、KM2X两个系列，KM1X主要用作计量，KM3X不仅具有计量功能，同时还有段式LCD控制器。 选型的方法主要有以下几种： 1）如果您已经知道要查找的产品的基本信息,最常用的方法是在飞思卡尔官网主页进行查找； 2）如果您并不清楚需要查找的芯片基本信息，飞思卡尔还提供了一些辅助的选型工具来帮助用户进行芯片的选型，包括：i）参数选型工具;   ii）选型神器Cross Check;  iii）解决方案顾问; 具体的选型操作流程可以参考:针对飞思卡尔单片机的快速上手指南中的2.2小节，其中有非常详细的介绍。

The document describes how to port yaffs2 file system for MQX. The detailed porting user guide can refer to the attached doc which use TWR-K70F120M as example. The reference code can be found in the attached source code package. Now, the yaffs2 for MQX can support NFC and non-NFC at the same time, the only difference is NAND driver. For NFC, you should use NFC driver and for non-NFC, you should use softnand driver. In yaffs2 porting package, include the files which should be modified in MQX release package. user_config.h should be placed at \config\platform name\ init_nandflash.c should be placed at \mqx\source\bsp\platform name\ \nandflash is the NAND driver, should be at \mqx\source\io\ \yaffs2 is the yaffs2 porting codes should be at the root directory of MQX release package softnand2K.c is the NAND driver for non-NFC(simulated by flexbus).

1. CycloneMAX,    支持 Kinetis, ColdFire V2/V3/V4, Power MPC5xx/8xx, Qorivva MPC5xxx, DSC, MAC7xxx    PE Micro, http://www.pemicro.com/ 2. Flasher ARM     支持ARM公司全系列内核，包括传统的ARM7, ARM9和ARM11，已经新的Cortex-A, Cortex-M和Cortex-R系列，可以给目标板供电.    Segger, SEGGER - The Embedded Experts - Flasher ARM 3. Flasher Portable    支持ARM公司全系列内核，包括传统的ARM7, ARM9和ARM11，已经新的Cortex-A, Cortex-M和Cortex-R系列，电池供电，便携式烧写器.    Segger, SEGGER - The Embedded Experts-Flaser Portable 4. SmartPRO    支持 Kinetis, S12, S12X, ColdFireV2.    周立功，http://www.zlgmcu.com/ 5. MCP-104    支持飞思卡尔ARM based Microcontroller Kinetis.    祥佑科技(Micetek), http://www.micetek.com 6. 西尔特编程器，http://www.xeltek.com 7. 河洛编程器，http://www.hilosystems.com.tw

1. USB Multilink Universal    支持 Kinetis, HCS08, HC(S)12(X), S12Z, RS08, ColdFire V1/+V1, ColdFire V2-4*, Qorivva 5xxx, DSC.    PE Micro, http://www.pemicro.com/ 2. USB Multilink Universal FX    支持 Kinetis, Qorivva MPC5xxx, ColdFire +V1/ColdFire V1, ColdFire V2/3/4, HC(S)12(X), S12Z, HCS08, RS08, DSC, 683xx, HC16.    PE Micro, http://www.pemicro.com/ 3. J-Link    支持飞思卡尔ARM based Microcontroller Kinetis.    可以配合PC端的软件JFlash对目标板进行烧写。    Segger, http://www.segger.com 4. ULink2    支持飞思卡尔ARM based Microcontroller Kinetis.    Keil, http://www.keil.com/arm/ulink/ 5. USBDM    开源调试器    可以配合PC端的上位机对目标板进行烧写。    http://usbdm.sourceforge.net/    https://github.com/podonoghue    http://sourceforge.net/projects/usbdm/ 6. CMSIS-DAP    ARM公司开源调试器    仿真器相关介绍页: http://mbed.org/handbook/cmsis-dap-interface-firmware    仿真器的源码下载: https://github.com/mbedmicro/CMSIS-DAP 7. OpenSDA     P&E Microcomputer Systems

1. Kinetis L系列外部IO中断分配问题（Tips about extern IO interrupt distribution of Kinetis L serious） 2. KL26通过UART的DMA方式发送数据包（Send data package through UART with DMA mode on KL26） 3. Freescale ARM Cortex-M系列软复位的使用方法 4.分享飞思卡尔KL25使用UART通信唤醒低功耗模式代码 5. 飞思卡尔KL系列低功耗特性和唤醒时间测试 6. BME学习心得(BME Study Notes) 7. 分享一个基于Kinetis KL25/KL26 USB读写U盘的例程 8. 如何实现Kinetis ADC自校准 9. Kinetis系列Flash烧写数据时写命令需要放到RAM中运行 10. Kinetis内部ADC转换速率探讨 11. KE02底层驱动库内部时钟Trim造成的UART通信不准的问题 12. Kinetis之教你将K60主频超到200MHz以上 13. 在Kinetis参考手册中快速找到芯片的Flash和SRAM地址空间分配 14. KL26 SD卡读写程序 15. KL03不能正常进入低功耗模式的原因及解决办法 16. 对Flash擦写数据时使用ESFC位以避免写冲突造成擦写失败（Using ESFC bit - Flash programming routines in Cotex M0+ kinetis MCU） 17. M0+单周期快速GPIO的使用方法 18. Kinetis 16-bit ADC+DMA+定时器实现AutoScan自动通道扫描采样 19. Kinetis将Flash保护打开造成程序下载失败的解决办法 20. 移植ARM CMSIS USB Stack的CDC类到飞思卡尔Kinetis KL25 21. I2C总线被挂起的原因和解决办法 22. 使用Kinetis系列中UART的IDLE Line功能识别帧结束 23. Kinetis K系列SPI接口设计注意事项 24. I2C从机地址左移一位的原因 25. Kinetis 使用eDMA完成串口接收功能 26. 移植ARM CMSIS USB Stack 的CDC类到飞思卡尔Kinetis KL26[Keil]​ 27. KE 驱动库中UART中断问题​ 28. KE驱动库中KE06 CAN Demo的遇到几个问题和说明​ 29. 深入剖析Kinetis系列内部IO结构​ 30. ARM Cortex-M4和Cortex-M0+中断优先级及嵌套抢占问题​

1. Kinetis L系列将NMI和Reset管脚复用成GPIO需要注意的问题 2. 如何在IAR、Keil和Codewarrior中禁止掉Kinetis的NMI脚 3. Kinetis Reset管脚与外部看门狗/复位芯片接法 4. Kinetis L系列外部IO中断分配问题 5. KL2x/KL4x使用USB模块时需要注意VOUT33管脚的接法 6. Kinetis K系列SPI接口设计注意事项 7. Kinetis芯片Reset管脚出现方波的原因及解决办法