读取Kinetis K64内部闪存导致硬故障 症状 我们知道：擦除操作后必须对 Flash 进行编程。违反此规则将导致 Kinetis K64 部件编程失败，甚至出现硬故障（AHB 读取时）。 客户意外地使用 SDK 的 API 对同一扇区进行两次编程（过度编程），而没有进行擦除操作。然后当对该扇区执行 AHB 读取（包括使用 JFLash 读取该扇区）时，会发生 Hardfault。 诊断 K64 闪存的每个扇区都有内部 ECC。当发生过度编程时，ECC 将被破坏，并在 AHB 读取该扇区时触发 Hardfault。 解决方案 使用 SDK API FLASH_VerifyErase 检查该扇区是否已被擦除。每次对闪存进行编程之前，请调用 FLASH_VerifyErase。 该问题将影响所有具有 FTFE 闪存模块的 Kinetis 设备。 感谢 Alex Yang 提供的资料。

Measure the running time of one function on PowerPC Hi,      Some of PowerPC cores contain time base which could be the ruler to measure the running time of codes.     Generally, e200z4, e200z7 have such registers, RBL and TBU. They are SPR284 and SPR285.      Sample codes could be taken the reference within AN2865SW(Timebase project) .  Enjoy the measuring! Cheers! Oliver BTW, measure the running time of one function on S32K could also be gotten through the link. 

ARMがKinetisマイクロコントローラ向けKeil MDKソリューションを展示 ARMのRonan Synnottは、2014 FTF-AmericasでKeil Microcontroller Development Kit(MDK)のデモを行います。MDKは、Kinetisデバイス・ファミリ向けの包括的なソフトウェア開発環境です。 特長 Keil の Microcontroller Development Kit (ARM のフル機能デバッグ IDE) ソリューションのデモ Ulink Pro JTAGコネクタ経由で接続する ARMCC (ARMコンパイラ) ビューレジスタ、ビューメモリなど 値はオンザフライで更新され、ロジックアナライザーはシステム内の値を視覚化し、タイムライン形式で表示します   注目のNXP製品 Kinetisマイクロコントローラ リンクス ARM   オートモーティブ インダストリアル

[Solution] IAR version 8.32 can not debug revision '1B' of LPC55S69 silicon When you are the first time to debug LPC55S69, please read below document and double check your IDE, SDK and EVK version is correct. Usually, we prefer use the latest IDE, SDK and EVK boards. Important updates when using LPCXpresso55S69 Revision A2 boards and 1B silicon  [Problem Description] When you use IAR 8.32 to debug LPC55S69 '1B' silicon, the IDE will remind you "The debugging session could not be started", like below picture show: The reason of this failure is that IAR 8.32's LPC55S69 chip configuration files only support revision '0A' silicon, not '1B'. We strongly recommend customer download and use IAR 8.40.2 or latest version. The IAR IDE start support LPC55S68 '1B' silicon from 8.40.2. [Solution] If you have some reasons that must use IAR 8.32, you can download attached zip file. This zip file like a patch, include the IAR LPC55S69 '1B' support files. Un-zip this file and merge the same files under IAR installed path :IAR\arm\config\flashloader\NXP Then the IAR can support '1B' silicons. [How to identify LPC55(S)6x chip silicon versions] On the top-side marking code, there is '1B'  charactors at the end of mark strings. See below two pictures, the left one is '1B' version chips.                      LPC55(S)6x ver '1B'                                                               LPC55(S)6x ver '0A'                    LPC55xx

NXP Tech Session - CANopen and NXP Microcontrollers - Proliferating robust network communication with fast evaluation and deployment View Webinar Recording View Webinar Recording LPC55xx

i.MX27 ADS Board Video GST Encode Encode From YUV to H.264 gst-launch-0.10 filesrc location=file_in.yuv blocksize=w*h*1.5 ! \ mfw_vpuencoder codec type=std_avc framerate=fr ! filesink location=file_out.mpg Where: file_in.yuv: is the input file, a raw file. w*h*1.5: is the blocksize, it's calculated from input file dimensions: width * height * 1.5 mfw_vpuencoder: is the encoder with hardware acceleration for iMX27 std_avc: chooses the codec type for output file fr: indicates the framerate in that input file was created file_out.mpg: is the output file encoded in H.264 From Camera to H.264 gst-launch-0.10 mfw_v4lsrc ! mfw_vpuencoder codec-type=std_avc \ width=176 height=144 framerate=25 ! filesink location=test.video i.MX2x

CAN in Future Car Networks—Understanding the Different Trends and Solutions Future networks will still use CAN to a huge extend - but the variety of trends is also significantly increasing. This session shows key values, technical background and differentiators of the different CAN trends and the NXP implementation. Future networks will still use CAN to a huge extend - but the variety of trends is also significantly increasing. This session shows key values, technical background and differentiators of the different CAN trends and the NXP implementation.

パワートレイン&電動化:ワイヤレスBMS <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 無線通信に基づく革新的なBMSシステムコンセプトの紹介。システム構成とコミュニケーション戦略の概要。OEMパートナーとのラボ作業による検証結果。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 無線通信に基づく革新的なBMSシステムコンセプトの紹介。システム構成とコミュニケーション戦略の概要。OEMパートナーとのラボ作業による検証結果。 パワー・マネジメント

Yocto Project™ Advanced A guide to developing with the Yocto Project for i.MX application processors. Learn how to leverage the Yocto Project in development by adding layers and recipes, customizing images, working with the kernel, and other essential Yocto development tasks. A guide to developing with the Yocto Project for i.MX application processors. Learn how to leverage the Yocto Project in development by adding layers and recipes, customizing images, working with the kernel, and other essential Yocto development tasks. i.MX Applications Processors Re: Yocto Project™ Advanced These slides use the 3.10 Kernel and meta-fsl-arm?  Isn't this stale?  The last commit to meta-fsl-arm was in 2016:  meta-fsl-arm - Layer containing Freescale ARM hardware support metadata  I was very much looking forward to reading about the current tips & tricks for building with i.MX & Yocto, but I don't think this is it. 

信息娱乐、连接和安全：适用于 i.MX 8 应用处理器的 AUTOSAR MCAL <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 本讲座将向您讲解 NXP 的 i.MX 8 AUTOSAR MCAL 和安全 MCAL 产品的具体信息。由于 ECU 设计方法从编码转向配置，它们为您的产品开发成本和时间带来巨大的好处。对于许多采用 i.MX MPU 的汽车 ECU 产品来说，它们成为 AUTOSAR 分层架构的重要组成部分。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 本讲座将向您讲解 NXP 的 i.MX 8 AUTOSAR MCAL 和安全 MCAL 产品的具体信息。由于 ECU 设计方法从编码转向配置，它们为您的产品开发成本和时间带来巨大的好处。对于许多采用 i.MX MPU 的汽车 ECU 产品来说，它们成为 AUTOSAR 分层架构的重要组成部分。 i.MX 应用处理器

SD-CPE—A CPE to be Deployed with VM (Docker, etc.) and Managed by Orchestrator Concept of SD-CPE, virtualization of functions/applications on CPE, centralized management of CPE by orchestrator, advantages, and applications scenario in home, enterprise and industry. Concept of SD-CPE, virtualization of functions/applications on CPE, centralized management of CPE by orchestrator, advantages, and applications scenario in home, enterprise and industry.

このビデオでは、LPC55S69を AWS に接続する方法を示します <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 詳細については、NXP設計の完全ガイドをご覧ください:https://community.nxp.com/docs/DOC-344585  (マイビデオで視聴) スマートホーム

NXP Technology Form #NXPFTF 2016, we will join! - TechNexion 2016 May 16 - 19 we will again be at the NXP Technology Forum. Formerly called ftf it is now the NXPFTF 2016 TechNexion will be there and show our latest small Modules or chat with you about our Software and where to get it. Of course we are also looking forward to see all the new cool things we are expecting NXP to show. Being exited to have our tiny PICO Module scaling from Cortex-A7 i.MX6 Ultralite over Cortex-A9 single/dual lite/quad or with the NXP i.MX7 solo and dual (both Cortex-A7) but also introducing our other solutions. I'm sure there are a lot of customer which will find our EDM solution the perfect fir for their needs: We are looking forward to meet yo and all the other amazing people and exchange our ideas! For sure it will be a great event, also if now under a slightly different name, but that's still ok  FTF, here we come!! Register here: http://www.nxp.com/support/classroom-training-events/nxp-ftf-tech-forum:NXP-FTF-TECH-FORUM-HOME nxpftftechforum​ General

Industry 4.0 Connectivity Demo Industry 4.0 connectivity or Industrial IoT  combines the existing high Level network based on Ethernet type Protocols and the access  to a single sensor data.  IO Link protocol helps in that convergence by providing an easy migration of current of non-connected sensors to networked one. The demonstration show a typical Industrial Network using ModBus and IO Link sensors Features Modbus TCP Slave based on LS1021A Open source stack & Support for Industrial Strength Security Master IOLink Modem  node based on Kinetis KL17 + transceiver Device Node IOlink based on Kinetis KE02 + transceiver NXP Recommends Product Link QorIQ® Layerscape 1021A Dual-Core Communications Processor with LCD Controller https://www.nxp.com/products/processors-and-microcontrollers/arm-processors/layerscape-communication-process/qoriq-layerscape-1021a-dual-core-communications-processor-with-lcd-controller:LS1021A?&lang_cd=en Freedom® Development Platform for Kinetis® KL17 and KL27 MCUs FRDM-KL27Z|Freedom Development Platform|Kinetis® MCU | NXP  Freedom Development Platform for Kinetis KE02 MCUs https://www.nxp.com/design/development-boards/freedom-development-boards/mcu-boards/freedom-development-platform-for-kinetis-ke02-mcus:FRDM-KE02Z40M?&lang_cd=en QorIQ® LS1021A Tower® System Module QorIQ® LS1021A Tower® System Module | NXP  Industrial

Team 8 UC Berkeley Freescale Cup Report

eMSG インバウンドコンテキスト管理 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

How to add support for K60 120MHz part in USB stack ver 4.1.1 Actually the latest FSL USB stack has become part of KSDK , so it is recommended customer design USB application based on KSDK, while there are some old parts like K70, K60F and KL25 are still not supported in KSDK yet, so USB stack ver 4.1.1 is somewhat of help for those who still develop application based on those parts. USB stack ver 4.1.1 supports K70 instead of K60F, but since they are both Kinetis 120MHz parts, so the porting is very easy, here I provide a porting guide for this part. The porting is based on K70 USB examples, either Host or Device. 1. Replace the device header file. Use MK60F12.h instead, which may be extracted from KINETIS_120MHz_SC(Kinetis 120MHz bare metal sample code) , and put this header file in the folder of "C:\Freescale\Freescale USB Stack v4.1.1\Source\Host\source\bsp\P3" for Host or "C:\Freescale\Freescale USB Stack v4.1.1\Source\Device\app\common\kinetis" for device, and modify derivative.h as  below: 2. Macro definition changes in MK60F12.h, MCU_MK60F12 is defined instead of MCU_MK70F12, so in this step we will have to change some code snippet related with MCU_MK70F12. Firstly search MCU_MK70F12 in the project, for example ， in the Host demo USB_MSD project based on IAR, you may do that as below: and you may find some macro like "#ifdef MCU_MK70F12" or "#ifndef MCU_MK70F12", and change them as below: #ifdef MCU_MK70F12 ----> #if (defined MCU_MK60F12) || (defined MCU_MK70F12) #ifndef MCU_MK70F12 ----> #if (!defined MCU_MK60F12) && (!defined MCU_MK70F12) 3. IO driver modification. Since TWR-K70F120 has almost the same hardware as TWR-K60F120, there is no need to change the driver code after replacing the header file, except the serial port driver, referring to USB_MSD demo, the serial driver is in sci_kinetis.c, TWR-K70F120M uses PTE16 and PTE17(UART2) as the console, while TWR-K60F120M use PTE8 and PTE9(UART5) instead, so you have to change the driver as below to make printf work properly. void sci2_init(){ #if (defined MCU_MK60F12) || (defined MCU_MK70F12)     register uint_16 sbr, brfa;     uint_8 temp; #ifdef MCU_MK70F12     /* Enable the UART2_TXD function on PTD3 */     PORTE_PCR16 = PORT_PCR_MUX(0x3); // UART is alt3 function for this pin     /* Enable the UART2_RXD function on PTD2 */     PORTE_PCR17 = PORT_PCR_MUX(0x3); // UART is alt3 function for this pin     /* Enable the clock  */     SIM_SCGC4 |= SIM_SCGC4_UART2_MASK;     /* Make sure that the transmitter and receiver are disabled while we      * change settings.      */     UART_C2_REG(UART2_BASE_PTR) &= ~(UART_C2_TE_MASK | UART_C2_RE_MASK);     /* Configure the UART for 8-bit mode, no parity */     UART_C1_REG(UART2_BASE_PTR) = 0;    /* We need all default settings, so entire register is cleared */     /* Calculate baud settings */     sbr = (uint_16)((SYSCLK*1000)/(UART_BAUDRATE * 16));     /* Save off the current value of the UARTx_BDH except for the SBR field */     temp = UART_BDH_REG(UART2_BASE_PTR) & ~(UART_BDH_SBR(0x1F));     UART_BDH_REG(UART2_BASE_PTR) = temp |  UART_BDH_SBR(((sbr & 0x1F00) >> 8));     UART_BDL_REG(UART2_BASE_PTR) = (uint_8)(sbr & UART_BDL_SBR_MASK);     /* Determine if a fractional divider is needed to get closer to the baud rate */     brfa = (((SYSCLK*32000)/(UART_BAUDRATE * 16)) - (sbr * 32));     /* Save off the current value of the UARTx_C4 register except for the BRFA field */     temp = UART_C4_REG(UART2_BASE_PTR) & ~(UART_C4_BRFA(0x1F));     UART_C4_REG(UART2_BASE_PTR) = temp |  UART_C4_BRFA(brfa);       /* Enable receiver and transmitter */     UART_C2_REG(UART2_BASE_PTR) |= (UART_C2_TE_MASK    | UART_C2_RE_MASK); #else   //MCU_MK60F12         /* Enable the UART2_TXD function on PTE8 */     PORTE_PCR8 = PORT_PCR_MUX(0x3); // UART is alt3 function for this pin     /* Enable the UART2_RXD function on PTE9 */     PORTE_PCR9 = PORT_PCR_MUX(0x3); // UART is alt3 function for this pin                /* Enable the clock  */     SIM_SCGC1 |= SIM_SCGC1_UART5_MASK;     /* Make sure that the transmitter and receiver are disabled while we      * change settings.      */     UART_C2_REG(UART5_BASE_PTR) &= ~(UART_C2_TE_MASK | UART_C2_RE_MASK);     /* Configure the UART for 8-bit mode, no parity */     UART_C1_REG(UART5_BASE_PTR) = 0;    /* We need all default settings, so entire register is cleared */     /* Calculate baud settings */     sbr = (uint_16)((SYSCLK*1000)/(UART_BAUDRATE * 16));     /* Save off the current value of the UARTx_BDH except for the SBR field */     temp = UART_BDH_REG(UART5_BASE_PTR) & ~(UART_BDH_SBR(0x1F));     UART_BDH_REG(UART5_BASE_PTR) = temp |  UART_BDH_SBR(((sbr & 0x1F00) >> 8));     UART_BDL_REG(UART5_BASE_PTR) = (uint_8)(sbr & UART_BDL_SBR_MASK);     /* Determine if a fractional divider is needed to get closer to the baud rate */     brfa = (((SYSCLK*32000)/(UART_BAUDRATE * 16)) - (sbr * 32));     /* Save off the current value of the UARTx_C4 register except for the BRFA field */     temp = UART_C4_REG(UART5_BASE_PTR) & ~(UART_C4_BRFA(0x1F));     UART_C4_REG(UART5_BASE_PTR) = temp |  UART_C4_BRFA(brfa);        /* Enable receiver and transmitter */     UART_C2_REG(UART5_BASE_PTR) |= (UART_C2_TE_MASK    | UART_C2_RE_MASK); #endif        #endif } #ifdef __CC_ARM int sendchar (int ch) #else void TERMIO_PutChar (char ch) #endif { #if (!defined MCU_MK60F12) && (!defined MCU_MK70F12)     #if (defined MCU_MK20D5) || (defined MCU_MK20D7) || (defined MCU_MK40D7)         /* Wait until space is available in the FIFO */         while(!(UART1_S1 & UART_S1_TDRE_MASK)){};                /* Send the character */         UART1_D = (uint_8)ch;       #elif(defined MCU_MK21D5)         while(!(UART2_S1 & UART_S1_TDRE_MASK)){};                /* Send the character */         UART2_D = (uint_8)ch;       #elif(defined MCU_MKL25Z4) || (defined MCU_MKL46Z4)         /* Wait until space is available in the FIFO */         while(!(UART0_S1 & UART_S1_TDRE_MASK)){};        /* Send the character */        UART0_D = (uint_8)ch;       #else         /* Wait until space is available in the FIFO */         while(!(UART3_S1 & UART_S1_TDRE_MASK)){};                /* Send the character */         UART3_D = (uint_8)ch;     #endif   #else #ifdef MCU_MK70F12     /* Wait until space is available in the FIFO */     while(!(UART2_S1 & UART_S1_TDRE_MASK)){};     /* Send the character */     UART2_D = (uint_8)ch; #else      /* Wait until space is available in the FIFO */     while(!(UART5_S1 & UART_S1_TDRE_MASK)){};     /* Send the character */     UART5_D = (uint_8)ch; #endif #endif } 4. Set the correct device type in IDE settings. For IAR, change the device family in view of project options. Now, you can start to run the USB demos on TWR-K60F120M, please note the above steps is ok for USB device stack, but USB Host stack has some code issue , as mentioned in [USB stack ver 4.1.1] a code issue in msd_mfs_generic host demo , so please fix the issue before going further. Hope that helps, Best Regards, Kan USB Re: How to add support for K60 120MHz part in USB stack ver 4.1.1 Hi, I made these changes but ran into an error due to this function not being defined when compiling: void USB_ISR(void); In usb_dci_kinetis.h, this function is only defined for #if !HIGH_SPEED_DEVICE  Is this portion of the code different for a HIGH_SPEED_DEVICE? I am trying to use HS for my application. Thanks for any insights!!

Kinetis M series VREF module trim function linearity Analysis VREF module provide one input pin VREF, this pin can provide reference voltage for both external circuit but also for internal Sigma Delta ADCs, AFE and DAC.  Also it includes trim function in it. In this document, I would like to use my testing to do a linearity analysis. From figure1 and 2, you can find how to make VREF as reference voltage of different analog module. For example, you can find when S1 switches down, S0 closes and S2 select VREF, VREF will be voltage resource of SAR ADC.                                               Figure 1: Voltage reference function configuration                                   Figure 2: Voltage reference module diagramming I do a testing for VREF trim value linear analysis. The process is connecting the voltmeter to VREFH pin, then record measure result for each setting of VREF trim. There will be 64 records for every different setting. Testing chip is MKM34Z256. Please find my testing result from testing data table. From testing result, you can get the formula that y = kx + x0, where k is about 0.005 (5mV) and x0 is about 1.1881, x is trim value.  You can find there is only a little offset from offset curve.                                         Table 1: Trim voltage testing date                                                                 Figure 3: Offset curve

RIoTboard <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> RIoTboard是一个开源单板平台，基于采用 ARM ® Cortex ® -A9 架构的 i.MX 6Solo 处理器，旨在帮助设计师和业余爱好者加快开发速度。     •更快的上市时间 •成本低 •支持 Linux 和 Android Jelly Bean •开放平台参考设计   •开源 •以开发者为中心的社区 RIoTboard.org •参考设计可作为知识共享 （点击放大） • 采用 NXP 的设计 i.MX 6Solo处理器 基于ARM ® Cortex ® -A9 Core ®架构，运行速度高达1 GHz。 使用 Kinetis K20 MCU 的 集成调试电路 PMIC（电源管理集成芯片）（MMPF0100）   在R IoT board.org开始你的革命   概述 回复：RIoTboard <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 你好： 我对这块主板很感兴趣，因为 i.MX6 SOLO 芯片最适合我们的应用。不幸的是，这款主板似乎不再生产或出售。如果有人能验证我的结论是否正确和/或提供任何其他结论，我将不胜感激。 此致，

飞思卡尔 iMX6 处理器 - Garz & Fricke SANTARO 10.4 盒装 PCT/电阻 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Garz & Fricke 产品 SANTARO 将在即将于纽伦堡举行的嵌入式世界展会期间在飞思卡尔展位上展出。 SANTARO 使用飞思卡尔 iMX6 处理器。单核、双核和四核。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Garz & Fricke 产品 SANTARO 将在即将于纽伦堡举行的嵌入式世界展会期间在飞思卡尔展位上展出。 SANTARO 使用飞思卡尔 iMX6 处理器。单核、双核和四核。