車載ワイヤレス充電設計 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ワイヤレス充電の受け入れは、利便性と耐久性、および自動車への設置により、消費者の間で指数関数的に増加しています。このセッションでは、車載ワイヤレス充電の設計に関する詳細な技術的詳細とガイダンスを提供します。また、低電力と中電力の両方のアプリケーションをカバーするNFC / RFIDカード保護のレビュー。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ワイヤレス充電の受け入れは、利便性と耐久性、および自動車への設置により、消費者の間で指数関数的に増加しています。このセッションでは、車載ワイヤレス充電の設計に関する詳細な技術的詳細とガイダンスを提供します。また、低電力と中電力の両方のアプリケーションをカバーするNFC / RFIDカード保護のレビュー。

Quick Start of i.MXRT 1050 EVK + MCUXpresso In the i.MXRT 1050 EVK web page, there is a very nice "Getting Started" page to show the videos and steps how to use the board. 1. Connect the board to your PC by a USB cable. 2. Build and download the SDK. a. In the SDK Builder web page, you can customize and download the specific SDK of your board. b. On the next page, you can select different OS and different IDE. Select "MCUpresso IDE" for Windows here. c. You can add the software component that you wanted. d. Request to build the SDK. e. When the build request has completed, the SDK is available for download under the SDK Dashboard page. - Download icon : Download the SDK - Rebuild icon : Rebuild the SDK with different setting - Share icon : Share the SDK to others - MCUConfigTool icon : Run the MCU Configuration Tool to configure the pinmux and clocks for your own design board. - Remove icon : Remove the SDK from the Dashboard. 3. Install the MCUXpresso IDE. a. Go to the MCUXpresso IDE weg page to download the IDE and then install it. 4. Build and run the example on EVK. a. Open the MCUXpresso IDE. Simply drag & drop the SDK zip file to "Installed SDKs" view. b. Import the SDK examples and then click "Next". c. Select the "hello_world" under the demo_apps. d. Click "Build" to build the demo. e. Execute the terminal software (e.g. PuTTY). The COM port of the console output can be found in "devices manager". The COM setting is 115200,8,N,1. f. Click the "bug" icon to start the debugging. g. Click "Resume All Debug Sessions" icon to run the demo. h. "hello world" print out in console. Reference: i.MXRT1050 web page ( Contain the datasheet, reference manual of the i.MXRT1050 processor) i.MXRT1050EVK web page ( Contain the user's guides of the i.MXRT1050 EVK) MCUXpresso IDE web page ( Contain the user's guides of the MCUXpresso IDE ) i.MXRT 105x

AUTOSAR MCAL快速入门 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 该课程面向刚入门或有兴趣了解如何使用 AUTOSAR MCAL 生成和实施代码的工程师。使用 Tresos 配置工具生成 AUTOSAR 定义的结构来呈现“Hello world”级别的示例。这些指令与 NXP 编写的驱动程序和用户代码相结合来构建应用程序。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 该课程面向刚入门或有兴趣了解如何使用 AUTOSAR MCAL 生成和实施代码的工程师。使用 Tresos 配置工具生成 AUTOSAR 定义的结构来呈现“Hello world”级别的示例。这些指令与 NXP 编写的驱动程序和用户代码相结合来构建应用程序。

CAN FD and Partial Networking Provide an overview of the protocol and implementation of CAN FD in system architectures, including the use of partial networking in relation to the deployment of CAN FD. Provide an overview of the protocol and implementation of CAN FD in system architectures, including the use of partial networking in relation to the deployment of CAN FD. Re: CAN FD and Partial Networking I am using i.MXRTOS1170 EVKB. I am using sample project "evkbmimxrt1170_canfd_interrupt_transfer_cm7" but it is not working the way it should I am getting garbage data from transmitter. Any help. I configured CAN3 and LPUART1 no warnings or errors. It is failing below  Re: CAN FD and Partial Networking If CAN FD communication is exposed to a CAN node, the CAN node willsee the CAN FD frame as an error and block the communication, thereby rendering the network useless. By using original CAN protocol on the CAN FD nodes all advantages of CAN FD are lost. prepaidgiftbalance

1秒未満で起動しますか?中国How_Connects学ぶ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> プラットフォームが 1 秒未満で起動することを期待してください...あなたの顧客はそれを求めていますか?それが場合によっては十分に速くない場合でも...ブートパフォーマンスを向上させるために何ができるかについて説明します。ブートROM、ブートローダからOSやアプリケーションまでのブートプロセスを設計および最適化する方法について、専門家から学びます。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> プラットフォームが 1 秒未満で起動することを期待してください...あなたの顧客はそれを求めていますか?それが場合によっては十分に速くない場合でも...ブートパフォーマンスを向上させるために何ができるかについて説明します。ブートROM、ブートローダからOSやアプリケーションまでのブートプロセスを設計および最適化する方法について、専門家から学びます。

電動化:HV EVパワーインバーターシステムとGD3100のレビュー <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> このコースでは、高電圧電気インバータシステムのシステム分析を行います。NXPの電動化ソリューションについてもっと知りたいと思っているすべての人にとって良いセッションです。電気自動車のパワートレインのアーキテクチャと機能安全をレビューします。MC33GD3100の概要、主要な機能、および設計サポートに重点を置いています。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> このコースでは、高電圧電気インバータシステムのシステム分析を行います。NXPの電動化ソリューションについてもっと知りたいと思っているすべての人にとって良いセッションです。電気自動車のパワートレインのアーキテクチャと機能安全をレビューします。MC33GD3100の概要、主要な機能、および設計サポートに重点を置いています。

安全防篡改认证_Connects China <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 介绍 A100x 安全认证器（包括新款 A1007），作为整体培训认证协议的一部分，介绍安全 IC 中需要寻找的内容以及潜在用例。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 介绍 A100x 安全认证器（包括新款 A1007），作为整体培训认证协议的一部分，介绍安全 IC 中需要寻找的内容以及潜在用例。

AMF-DES-T2409 - DornerWorks: Xen on the i.MX 8 Applications Processors The continued growth of processing capabilities and new features introduced with the ARM®v8 based System-on-Chip has made virtualization a realistic option for embedded system developers. With virtualization, system architects can design solutions that reduce the size, weight, power, and cost of legacy systems by consolidating disparate software functions onto a single chip, even if those different software functions require different operating systems or otherwise incompatible software stacks. Virtualization allows architects to partition and isolate software components with different safety, security, or licensing requirements. The virtual machine manager, or hypervisor, is the key piece of software technology enabling virtualization. Open source hypervisor, Xen, supports the ARMv8 processor family. The continued growth of processing capabilities and new features introduced with the ARM®v8 based System-on-Chip has made virtualization a realistic option for embedded system developers. With virtualization, system architects can design solutions that reduce the size, weight, power, and cost of legacy systems by consolidating disparate software functions onto a single chip, even if those different software functions require different operating systems or otherwise incompatible software stacks. Virtualization allows architects to partition and isolate software components with different safety, security, or licensing requirements. The virtual machine manager, or hypervisor, is the key piece of software technology enabling virtualization. Open source hypervisor, Xen, supports the ARMv8 processor family.

Patch to support Ethernet PHY KSZ8081 (Rev1) on i.MX6UL/i.MX6ULL EVK board Overview In latest i.MX6UL/i.MX6ULL EVK boards, Ethernet PHY chip is upgraded with new revsion ID (01) although the same part number KSZ8081RNBIA is used. The detailed change is as follows: Mark on old Ethernet PHY chip (Silicon Revision ID is 0, Mark is A2):             KSZ8081             RNBIA             1439A2T             M147J18M02 Mark on new Ethernet PHY chip (Silicon Revision ID is 1, Mark is A3)               KSZ8081               RNBIA               1602SA3T                M159S28M23                                   Software Patch Linux BSP requires to be updated to support this new Ethernet PHY because PHY setting is designed to be associated with silicon ID. See attached patch for the details (Please note: i.MX6ULL/i.MX6UL EVK shared the same board file.) The formal patch is also included into the releases starting from L4.1.15_2.0.1. See http://git.freescale.com/git/cgit.cgi/imx/meta-fsl-bsp-release.git/tree/imx/meta-bsp/recipes-kernel/linux/files?id=imx_4.1.15_2.0.1 If ethernet doesn't function on your i.MX6UL/i.MX6ULL EVK board in kernel, please check whether Silicon Revion Mark is A3 on the board and then apply for attached file for the test. i.MX6UL Re: Patch to support Ethernet PHY KSZ8081 (Rev1) on i.MX6UL/i.MX6ULL EVK board Hi Llly, On my imx6ul Evaluation board, Silicon Revision ID is 1, Mark is A3 I tried to patch but not successful. root@imx6ulevk:~# root@imx6ulevk:~# patch < /home/root/work/0001-ARM-imx-imx6ul-add-PHY-KSZ8081-new-silicon-revision-.patch  patching file mach-imx6ul.c patch: can't open 'mach-imx6ul.c': No such file or directory root@imx6ulevk:~# FYI, Linux version of my machine is 4.1.15-1.1.0+ga4d2a08 & machine model : freescale i.mx6 ultralight 14x14 Evk board Please Help Jaydeep

How to test pass CTSV for camera Hi freescale, For using platform I.MX6QP and Android 6.0.1, test camera format is failed in CTSV R13. CTSV need to test format N21, YV12, YUY2,(160x120, 176x144, 320x180, 320x240, ...,640x480). Question list : (1.) It test YUY2 format is failed for handing preview screen was show green screen. For logcat issue log: 01-18 03:10:50.856 221 1252 E imx6.gralloc: int GPUBufferManager::lockYUVHandle(private_handle_t*, android_ycbcr*) not support format:0x14 01-18 03:10:50.856 221 1252 W GraphicBufferMapper: lock(...) failed -22 (Invalid argument) 01-18 03:10:50.892 221 311 E FslCameraHAL: processBufferWithIPU:320, IPU_CHECK_TASK ret=12 01-18 03:10:50.892 221 1252 E imx6.gralloc: int GPUBufferManager::lockYUVHandle(private_handle_t*, android_ycbcr*) not support format:0x14 01-18 03:10:50.892 221 1252 W GraphicBufferMapper: lock(...) failed -22 (Invalid argument) 01-18 03:10:50.924 221 311 E FslCameraHAL: processBufferWithIPU:320, IPU_CHECK_TASK ret=12 01-18 03:10:50.924 221 1252 E imx6.gralloc: int GPUBufferManager::lockYUVHandle(private_handle_t*, android_ycbcr*) For failed status: Test_fail_picture (2.) For test YV12 , 424X240, the result is failed. Logcat failed log: 01-18 03:29:51.547 1213 1229 D OpenGLRenderer: endAllStagingAnimators on 0x917f0700 (ListPopupWindow$DropDownListView) with handle 0x92564f30 01-18 03:29:51.637 221 1259 I FslCameraHAL: Stream::Stream(int, camera3_stream_t*, Camera*) create preview stream 01-18 03:29:51.637 221 1259 I FslCameraHAL: stream: w:424, h:240, format:0x103, usage:0x8000302, buffers:3 01-18 03:29:51.637 221 1259 I FslCameraHAL: create callback stream 01-18 03:29:51.637 221 1259 I FslCameraHAL: stream: w:424, h:240, format:0x101, usage:0x8000303, buffers:3 01-18 03:29:51.650 221 1325 I FslCameraHAL: int32_t VideoStream::configure(android::sp 😞 w:160, h:120, sensor format:0x14, stream format:0x103, fps:15, num:3 01-18 03:29:51.651 221 311 I FslCameraHAL: virtual int32_t UvcDevice::UvcStream::onDeviceStopLocked() 01-18 03:29:51.664 221 311 I FslCameraHAL: virtual int32_t DMAStream::freeBuffersLocked() 01-18 03:29:51.664 221 311 I FslCameraHAL: freeBufferToIon buffer num:3 01-18 03:29:51.664 221 311 I FslCameraHAL: virtual int32_t UvcDevice::UvcStream::onDeviceConfigureLocked() 01-18 03:29:51.664 221 311 I FslCameraHAL: virtual int32_t DMAStream::onDeviceConfigureLocked() 01-18 03:29:51.664 221 311 I FslCameraHAL: virtual int32_t USPStream::onDeviceConfigureLocked() 01-18 03:29:51.664 221 311 I FslCameraHAL: virtual int32_t MMAPStream::onDeviceConfigureLocked() 01-18 03:29:51.664 221 311 I FslCameraHAL: Width * Height 424 x 240 format YUYV, fps: 15 01-18 03:29:51.664 221 311 E FslCameraHAL: width:424 height:240 is not supported. 01-18 03:29:51.694 221 311 I FslCameraHAL: virtual int32_t DMAStream::allocateBuffersLocked() 01-18 03:29:51.694 221 311 I FslCameraHAL: allocateBufferFromIon buffer num:3 01-18 03:29:51.696 221 311 I FslCameraHAL: phyalloc ptr:0xa9b8d000, phy:0x26180000, ionSize:208896 01-18 03:29:51.698 221 311 I FslCameraHAL: phyalloc ptr:0xa9b21000, phy:0x261c0000, ionSize:208896 01-18 03:29:51.701 221 311 I FslCameraHAL: phyalloc ptr:0xa9aee000, phy:0x26200000, ionSize:208896 01-18 03:29:51.701 221 311 I FslCameraHAL: virtual int32_t UvcDevice::UvcStream::onDeviceStartLocked() 01-18 03:29:51.701 221 311 I FslCameraHAL: buf[0] length:203520 01-18 03:29:51.701 221 311 I FslCameraHAL: buf[1] length:203520 01-18 03:29:51.701 221 311 I FslCameraHAL: buf[2] length:203520 Fail Piture: YV12_test_fail For freescale camera HAL description ./hardware/imx/mx6/libcamera3/CameraHAL.cpp /* Hardware limitation on I.MX6DQ platform * VPU only support NV12&I420 format. * IPU doesn't support NV21 format. * But android framework requires NV21&YV12 format support. * YV12&I420 Y/UV stride doesn't match between android framework and IPU/GPU. ** Android YV12&I420 define: * - a horizontal stride multiple of 16 pixels * - a vertical stride equal to the height * - y_size = stride * height * - c_stride = ALIGN(stride/2, 16) * ** GPU YV12&I420 limitation: * - GPU limit Y stride to be 32 alignment, and UV stride 16 alignment. * ** IPU hardware YV12&I420 limitation: * - IPU limit the Y stride to be 2x of the UV stride alignment. ** IPU driver YV12&I420 define: * - y_stride = width * - uv_stride = y_stride / 2; * So there is work around to treat the format on I.MX6DQ platform: * Change format NV21&YV12 to NV12&I420 in Camera framework. * The NV21 format required by CTS is treated as NV12. * YUV alignment required by CTS doesn't match on I.MX6DQ platform. */ How to fix the issue in IMX6qp for CTSV? General

DEVKIT-ZVL128 EVB review The DEVKIT platform The NXP released new board platform for automotive products – DEVKIT. The DEVKIT is a low-cost development platform with Arduino UNO/Mega pin compatibility. In my review, I will focus mainly on DEVKIT-ZVL128 board.                                          The DEVKIT boards are similar to FRDM boards, but they are slightly wider (58mm versus 53mm) due to moving MCU specific pins to external rows of Arduino pin compatible connectors. So, we should be able to access MCU specific pins even when we connect any Arduino shield on top of this board.   The other currently or soon available DEVKIT boards are: DEVKIT-S12ZVL DEVKIT-S12ZVC DEVKIT-S12G128 DEVKIT-S12XE DEVKIT-S12VR64 DEVKIT-MPC5748G DEVKIT-MPC5744P FRDM-KEA128 FRDM-KEA64 FRDM-KEA32 DEVKIT-COMM - 6 LIN and 4 CAN transceivers shield DEVKIT-MOTORGD – three-phase motor control shield with GD3000 N-channel MOSFETs driver and power stage Note: The FRDM-KEA boards belongs also into the DEVKIT platform despite on the “FRDM” in the board name. The Content What you will get for US$35 (current price on NXP web pages): Antistatic paper box DEVKIT-ZVL128 board short micro-USB cable       The sticker on the box points to the NXP web pages for downloading more documents such as the quick start guide, schematic, PCB BOM and design files, code examples or buy the same board again ;-). Unfortunately, the board User Guide is not available yet. This web page is also offering “Getting Started” tab with the interactive quick start guide – quite useless feature since the page forgets on necessary 12V power supply for MCU powering and it proposes old CW5.1 (Classic IDE) for S12(X) instead of CW10 (Eclipse IDE). What else you will need: The IDE – for example, the NXP CodeWarrior or Cosmic ZAP 12V DC power supply (3.8V~40V) with barrel connector (6mm outside diameter x 2mm inside diameter) MCU code The Board DEVKIT-ZVL128 board is assembled by: S12ZVLA128 MCU (Big Knox) in 48-pin LQFP package 8MHz crystal Standard 2mm DC power jack connector for 12V power supply On-board OSBDM debugger trough micro-USB connector Standard BDM connector Arduino UNO pin compatible connectors with extended connectivity (the internal rows of the connectors are arranged to fulfill Arduino™ shields compatibility) RGB LED and 2 x push button switches LIN and CAN connectors CAN transceiver MC33901 5k potentiometer and RESET switch 3V/150mA and 5V/150mA LDO voltage regulators The great thing is that the board has connector pins named from the bottom side of the PCB = less tracking on schematic.     On another side, some of the MCU pins may be routed to Arduino connectors trough zero Ohm resistors. Since these resistors are very small (size 0402), the potential re-routing will need a solid hand.     It is great that loop type test points arrived finally also on low-cost development boards – now in surface mount version. The small loops may be simply locked by test hooks and measured by laboratory equipment.       The MCU The S12ZVLA128 is one of MagniV family MCUs using the 180nm NVM + UHV technology that offers the capability to integrate 40V analog components. It integrates S12Z core, features from the existing S12 portfolio together with “high-voltage” analog modules, including the voltage regulator (VREG) and a Local Interconnect Network (LIN) physical layer (LIN PHY). The S12ZVL(A)128/96/64 derivatives introduces several unique enhancements in comparison with older S12ZVL32/S12ZVL16 derivatives: Significantly bigger memories (64/96/128kB flash, 1/2kB EEPROM, and 4/8kB RAM) The VDDX voltage regulator is capable of providing 5V or 3.3V MsCAN module The S12ZVLA derivatives additional features/improvements: 2% VDDX regulator tolerance improvements 10/6 channel 12bit ADC 8bit DAC module the rail-to-rail analog comparator (ACMP) the Programmable Gain Amplifier (PGA) I am going to use the PGA for thermocouple measurement in the near future. Software The Software Integration Guide guides us through CW 10.6.4 installation and creating a new project with Processor Expert (PE) tool. Unfortunately, while following that guide, I discovered that the CW10.6.4 does not offer PE as an option (only project without PE) when I tried to create an S12ZVL128 project. But this option is available in newer CW10.7 version. Note: If S12ZVL(A)128 derivative is missing in your CW10.6.4 IDE, please update your CW IDE via menu-Help-Install New Software-FSL MCU Eclipse Update Site and focus mainly on “S12Z Support” and “MCU 10.6.4 Updates” folders. The code examples contains three primitive example projects: DEVKIT-ZVL128_Lab1GPIO – configure GPIO pins DEVKIT-ZVL128_Lab2ADC – initialize and measure ADC value DEVKIT-ZVL128_Lab3PWM – configure voltage regulator, initialize CLOCK, initialize and measure ADC value, generate PWM Note: The zip file contains already built projects. The loading it into MCU does not work due to different paths. We have to clean it and build again in our workspace prior loading into the MCU. These projects are really simple, but they omit some specific potential issues. For example: I would like to recommend to configure CPMUVREGCTL_VREG5VEN bit also in GPIO example since this bit influences output pin voltage levels. The value of the CPMUVREGCTL_VREG5VEN bit is not influenced by any MCU reset. So, we have to be careful especially when we are starting a new project with new peripherals connected to the S12ZVL128 GPIO pins. The ADC command lists (adc0_cmdlist) and ADC result lists (adc0_results) are not aligned in these example codes. It may be fixed by simple modification: volatile unsigned char adc0_cmdlist[1][4] __attribute__ ((aligned (4))) = {0xC0,0xD0,0xA0,0x00}; volatile unsigned short adc0_results[1] __attribute__ ((aligned (4)));‍‍‍‍ The NXP offers for this MCU also LIN2.x and SAE J2602 Stack and S12Z NVM Standard Software Driver (Flash/EEPROM driver). There are also well-documented example codes at Community from Technical support team which may be used for an inspiration. For example: S12ZVM clock module and PLL configuration - SW examples S12Z Interrupt catcher for unexpected interrupts S12Z voltage measurement A Library of Functions for HD44780 Based LCD Modules (no R/W) for S12Z devices S12ZVL-TIM-FrequencyMeasurement S12Z Flash example code S12Z EEPROM example code … The next source of information may be NXP application notes. For example: AN4723 S12Z MagniV Bootloader with SW, AN4731 Understanding Injection Current on Freescale Automotive Microcontrollers, AN4841 S12ZVL LIN Enabled Ultrasonic Distance Measurement with SW, AN4842 S12ZVL LIN Enabled RGB LED Lighting Application with SW, AN5084 Hardware Design Guidelines for S12ZVL Microcontrollers, AN5122 Using Freescale’s LIN Driver with the MagniV Family with SW Summary One of the best advantages of DEVKIT platform is the price. When we compare DEVKIT board prices with alternative evaluation boards (if any exist), we may save between 40 and 95 % EVB price depending on target MCU family. For example, the older TRK-S12ZVL board (assembled by S12ZVL32) is bigger, additionally offers 9 user switches, buzzer, HVI potentiometer, switchable LIN_OUT connector and header ring with all MCU pins. But the price is also almost three times higher than the price of DEVKIT-ZVL128. Also, the connectors with standard 100mils pitch are definitely plus in comparison with previously used TWRPI/PCI EXPRESS connectors and the board allows using plenty of available Arduino shields without complex hardware interconnections. You may look for it for example at Arduino pages, shieldlist.org, Adafruit, … From my side - thumbs up :smileycheck:. Re: New EVB platform: DEVKIT-ZVL128 Review. Hi Peter, Thank you for notification. I reported this issue almost two years ago. It seems, that nobody fixed it until now. I will report it again. The issue is related to QSG and Getting Started page also … There is just simple Note on the board web page “12V (1 Amp) power supply is required for debugging and CAN/LIN communication, this is not included in the kit” https://www.nxp.com/support/developer-resources/hardware-development-tools/ultra-reliable-mcus-development-platform/16-bit-mcus-platforms/development-board-for-s12zvl128-mcu-evaluation:DEVKIT-ZVL128 Best regards Radek Re: New EVB platform: DEVKIT-ZVL128 Review. Hello Radek, Thanks for the clear explanation. Do you know if this is somewhere documented? I have found the quick-reference-guide/DVKITZVL128QSG.pdf but this only suggests the opposite: "CAUTION:                When powered from the USB bus, do not exceed the 500mA maximum allowable current drain. Damage to the target board or host PC may result." Re: New EVB platform: DEVKIT-ZVL128 Review. Hi Peter, Unfortunately, the DEVKIT-ZVL128 board cannot be directly powered from USB. The assembled S12ZVL128 MCU is part of MagniV family which is designed for powering directly from 12V line. So, the 5V from USB is simply not sufficient for MCU powering. Note: The S12ZVL128 MCU may be theoretically directly powered from 5V power supply connected to the VDDX/VDDA pin (MCU is not designed for such use). However, in such case we must connect also VSUP pin the same power line for avoiding any issue with transient effects. Such connection will also disable main features of this MCU(integrated power supply, internal LIN PHY,…) Yes, the 'Power Supply Selection section with jumper option to P5V_SWUSB' is just misunderstanding. The jumper J13 (+JP1) choose one of source power supplies (MCU, USB, U13 voltage regulator) only for on-board CAN transceiver and Arduino-Uno compatible J3 header. The output from J13 jumper is P5V0 signal. I hope it helps you. Best reagrds Radek Re: New EVB platform: DEVKIT-ZVL128 Review. Hi, You mention a "12V DC power supply (3.8V~40V) with barrel connector (6mm outside diameter x 2mm inside diameter)" is needed. Can the board also be powered by USB? My guess is yes as the schematic shows a 'Power Supply Selection section with jumper option to P5V_SWUSB' . Therefore I tried setting the jumper 13 between 2-3 but no connection 'Target MCU is not responding'. Measuring their is no power on J13 Pin3. This makes me believe MIC2026-1YM is not enabling OUTB because ENB is not powered. (Measuring proves this hypothesis). Why is +VTRG_ENB not enabled by MC9S08JM60CGTE? Or am I misunderstanding jumper 13? Re: New EVB platform: DEVKIT-ZVL128 Review. Hi Robin, You are right and thank you for notification. The final name is DEVKIT-MOTORGD. I will update this document. I hope it helps you. Have a great day, Radek Re: New EVB platform: DEVKIT-ZVL128 Review. Hi One of the customer want to get the DEVKIT-MCSHIELD. I notice that "Note: The grayed names are just for prototype boards, the final board names may be different." I am not sure if that board has another name: DEVKIT-MOTORGD. Since it look like the same. Would you please tell me where can the customer get DEVKIT-MCSHIELD? Thank you for the help in advance!   Best Regards, Robin

MHW-N1978 Smart Pharma Solutions Increase Delivery Effectiveness For drug delivery to be effective, two very important conditions need to be met. First, drug quality needs to be ensured until the time of administration to the patient. Second, the patient needs to adhere to the prescribed therapy. Two easy-to-use solutions will be presented. They comprise a battery, an antenna and a single chip that integrates a sensor, storage and NFC connectivity. Both solutions support wireless communication with a smart phone. A temperature monitoring solution permits logging of transport conditions of each individual drug package at any point in time. Patients and healthcare professionals can confirm the drug quality at the moment of administration. A therapy adherence monitoring solution for drug blisters and bottles records medication intake events. In case the intake deviates from prescription, patients can be reminded and motivated to do better. For drug delivery to be effective, two very important conditions need to be met. First, drug quality needs to be ensured until the time of administration to the patient. Second, the patient needs to adhere to the prescribed therapy. Two easy-to-use solutions will be presented. They comprise a battery, an antenna and a single chip that integrates a sensor, storage and NFC connectivity. Both solutions support wireless communication with a smart phone. A temperature monitoring solution permits logging of transport conditions of each individual drug package at any point in time. Patients and healthcare professionals can confirm the drug quality at the moment of administration. A therapy adherence monitoring solution for drug blisters and bottles records medication intake events. In case the intake deviates from prescription, patients can be reminded and motivated to do better. Secure Mobile | Healthcare & Wearables

Kinetis Expert System Configuration Tools V2 with Clocks Tool now available! A new version of the Kinetis Expert Configuration Tools has been released and is available both online (Welcome to Kinetis Expert | Kinetis Expert ) or for download as desktop tool (Software Development Kit for Kinetis MCUs|NXP ).   The set of the tools has a new member: the Clocks Tool: Simple UI for clock parameter viewing and modification Graphical view for easy navigation and visualization of settings and frequencies Generate configuration code using KSDK v2 Inspect and modify clock configuration from clock input source up to the core/peripherals Validate clock settings and calculate the resulting output clock frequencies Determines suitable clock settings for given output requirements Integrated with the Pins Tool   Main features of Pins Tool and Clocks Tool: Available as Web and Desktop application Kinetis SDK v2 support Multicore support Localized for English and Simplified Chinese Mostly Connected: On-Demand device data download Integrates with any compiler and IDE Generation of documented C code which is C++ aware   What's New Added Clocks Tool Added Support for boards, kits and templates Added Labels and Identifier support Added Log and Problems View Export downloaded data to copy or share device information data Bug fixes and improved documentation The release notes of the desktop application are attached to this article.   Clocks Tool The new member of the suite of configuration tools is the Clocks Tool.  Use the Tools menu to select and switch between the tools:   The Clocks Tool provides graphical views for configuration and navigation in the clocks of the hardware:   Templates, Kits, Boards and Processors When creating a new configuration, it offers Templates, Kits, Boards and Processors. Custom configurations can be stored as templates and then used for new configurations.   Board Specific Functions With the provided board and kit configurations, there are now pre-configured initialization functions for major blocks on the board:   Labels and Identifiers In the Pins Tool there are two new columns: Label and Identifier: The Label is a user name/string to identify or describe the pin. The Identifier is a user C/C++ identifier which is added to the generated source code to be used by the application.   Export Data To simplify downloading the device specific data for the desktop tool, the 'Export' function can be used to download and export the data. The data can be copied that way to another machine or all data for a set of devices can be loaded.     The device support for the clocks tool is staged, so initially not all SDK V2 devices are included. As of Oct 14, the the following Kinetis SDK V2 R1 devices are supported by the Clocks Tool: MK21FN1M0AVLQ12 MK21FN1M0AVMC12 MK21FN1M0AVMD12 MK21FN1M0VLQ12 MK21FN1M0VMC12 MK21FN1M0VMD12 MK21FX512AVLQ12 MK21FX512AVMC12 MK21FX512AVMD12 MK21FX512VLQ12 MK21FX512VMC12 MK21FX512VMD12 MK22FN128CAH12 MK22FN128VDC10 MK22FN128VLH10 MK22FN128VLL10 MK22FN128VMP10 MK22FN1M0AVLH12 MK22FN1M0AVLK12 MK22FN1M0AVLL12 MK22FN1M0AVLQ12 MK22FN1M0AVMC12 MK22FN1M0AVMD12 MK22FN1M0VLH12 MK22FN1M0VLK12 MK22FN1M0VLL12 MK22FN1M0VLQ12 MK22FN1M0VMC12 MK22FN1M0VMD12 MK22FN256CAH12 MK22FN256VDC12 MK22FN256VLH12 MK22FN256VLL12 MK22FN256VMP12 MK22FN512CAP12 MK22FN512VDC12 MK22FN512VLH12 MK22FN512VLL12 MK22FN512VMP12 MK22FX512AVLH12 MK22FX512AVLK12 MK22FX512AVLL12 MK22FX512AVLQ12 MK22FX512AVMC12 MK22FX512AVMD12 MK22FX512VLH12 MK22FX512VLK12 MK22FX512VLL12 MK22FX512VLQ12 MK22FX512VMC12 MK22FX512VMD12 MK24FN1M0VDC12 MK24FN1M0VLL12 MK24FN1M0VLQ12 MK26FN2M0CAC18 MK26FN2M0VLQ18 MK26FN2M0VMD18 MK26FN2M0VMI18 MK63FN1M0VLQ12 MK63FN1M0VMD12 MK64FN1M0VDC12 MK64FN1M0VLL12 MK64FN1M0VLQ12 MK64FN1M0VMD12 MK64FX512VDC12 MK64FX512VLL12 MK64FX512VLQ12 MK64FX512VMD12 MK65FN2M0CAC18 MK65FN2M0VMI18 MK65FX1M0CAC18 MK65FX1M0VMI18 MK66FN2M0VLQ18 MK66FN2M0VMD18 MK66FX1M0VLQ18 MK66FX1M0VMD18 MK80FN256CAx15 MK80FN256VDC15 MK80FN256VLL15 MK80FN256VLQ15 MK81FN256CAx15 MK81FN256VDC15 MK81FN256VLL15 MK81FN256VLQ15 MK82FN256CAx15 MK82FN256VDC15 MK82FN256VLL15 MK82FN256VLQ15 MKL13Z32VFM4 MKL13Z32VFT4 MKL13Z32VLH4 MKL13Z32VLK4 MKL13Z32VMP4 MKL13Z64VFM4 MKL13Z64VFT4 MKL13Z64VLH4 MKL13Z64VLK4 MKL13Z64VMP4 MKL17Z128VFM4 MKL17Z128VFT4 MKL17Z128VLH4 MKL17Z128VMP4 MKL17Z256VFM4 MKL17Z256VFT4 MKL17Z256VLH4 MKL17Z256VMP4 MKL17Z32VDA4 MKL17Z32VFM4 MKL17Z32VFT4 MKL17Z32VLH4 MKL17Z32VMP4 MKL17Z64VDA4 MKL17Z64VFM4 MKL17Z64VFT4 MKL17Z64VLH4 MKL17Z64VMP4 MKL27Z128VFM4 MKL27Z128VFT4 MKL27Z128VLH4 MKL27Z128VMP4 MKL27Z256VFM4 MKL27Z256VFT4 MKL27Z256VLH4 MKL27Z256VMP4 MKL27Z32VDA4 MKL27Z32VFM4 MKL27Z32VFT4 MKL27Z32VLH4 MKL27Z32VMP4 MKL27Z64VDA4 MKL27Z64VFM4 MKL27Z64VFT4 MKL27Z64VLH4 MKL27Z64VMP4 MKL33Z128VLH4 MKL33Z128VMP4 MKL33Z256VLH4 MKL33Z256VMP4 MKL33Z32VFT4 MKL33Z32VLH4 MKL33Z32VLK4 MKL33Z32VMP4 MKL33Z64VFT4 MKL33Z64VLH4 MKL33Z64VLK4 MKL33Z64VMP4 MKL43Z128VLH4 MKL43Z128VMP4 MKL43Z256VLH4 MKL43Z256VMP4 MKS22FN256VLL12 MKS22FN256VLH12 MKS22FN128VLL12 MKS22FN128VLH12   In November, the following SDK V2.0 R2 and R3 devices will be available in the Clocks Tool: MKL14Z32VFM4 MKL14Z32VFT4 MKL14Z32VLH4 MKL14Z32VLK4 MKL14Z64VFM4 MKL14Z64VFT4 MKL14Z64VLH4 MKL14Z64VLK4 MKL15Z128CAD4 MKL15Z128VFM4 MKL15Z128VFT4 MKL15Z128VLH4 MKL15Z128VLK4 MKL15Z32VFM4 MKL15Z32VFT4 MKL15Z32VLH4 MKL15Z32VLK4 MKL15Z64VFM4 MKL15Z64VFT4 MKL15Z64VLH4 MKL15Z64VLK4 MKL24Z32VFM4 MKL24Z32VFT4 MKL24Z32VLH4 MKL24Z32VLK4 MKL24Z64VFM4 MKL24Z64VFT4 MKL24Z64VLH4 MKL24Z64VLK4 MKL25Z128VFM4 MKL25Z128VFT4 MKL25Z128VLH4 MKL25Z128VLK4 MKL25Z32VFM4 MKL25Z32VFT4 MKL25Z32VLH4 MKL25Z32VLK4 MKL25Z64VFM4 MKL25Z64VFT4 MKL25Z64VLH4 MKL25Z64VLK4   MKW21D256VHA5 MKW21D512VHA5 MKW22D512VHA5 MKW24D512VHA5   In December, the SDK 2.0 R4 devices will be supported by the Clocks Tool: MKV10Z16VFM7 MKV10Z16VLC7 MKV10Z16VLF7 MKV10Z32VFM7 MKV10Z32VLC7 MKV10Z32VLF7 MKV10Z128VFM7 MKV10Z128VLC7 MKV10Z128VLF7   MKV10Z128VLH7   MKV10Z64VFM7 MKV10Z64VLC7 MKV10Z64VLF7   MKV10Z64VLH7 MKV11Z128VFM7 MKV11Z128VLC7 MKV11Z128VLF7   MKV11Z128VLH7   MKV11Z64VFM7 MKV11Z64VLC7 MKV11Z64VLF7   MKV11Z64VLH7   MKV30F128VFM10 MKV30F128VLF10 MKV30F128VLH10 MKV30F64VFM10 MKV30F64VLF10 MKV30F64VLH10 MKV46F256VLL16 MKV46F256VLH16 MKV46F128VLL16 MKV46F128VLH16 MKV44F256VLL16 MKV44F256VLH16 MKV44F128VLL16 MKV44F128VLH16 MKV44F64VLH16 MKV42F256VLL16 MKV42F256VLH16 MKV42F128VLL16 MKV42F128VLH16 MKV42F64VLH16 MKV44F128VLF16 MKV44F64VLF16 MKV42F128VLF16 MKV42F64VLF16 MKV58F1M0VMD24 MKV58F512VMD24 MKV58F1M0VLQ24 MKV58F512VLQ24 MKV58F1M0VLL24 MKV58F512VLL24 MKV56F1M0VMD24 MKV56F512VMD24 MKV56F1M0VLQ24 MKV56F512VLQ24 MKV56F1M0VLL24 MKV56F512VLL24 MKV31F128VLH10 MKV31F128VLL10 MKV31F256VLH12 MKV31F256VLL12 MKV31F512VLH12 MKV31F512VLL12   We hope you will find this new release useful.   Thanks for designing with NXP! General Re: Kinetis Expert System Configuration Tools V2 with Clocks Tool now available! Please, set the HSRUN power mode (Run mode settings). The RUN power mode does not support 180MHz core clock frequency. Best Regards, Marek Neuzil  Re: Kinetis Expert System Configuration Tools V2 with Clocks Tool now available! Using Clock Tool for MK26FN2M0VLQ18.  Can't set it above 120MHz.  The core is able to go to 180MHz. Using PEE mode with 16MHz external crystal. Any suggestions? Brad Re: Kinetis Expert System Configuration Tools V2 with Clocks Tool now available! The list of supported devices can be found here for all the tools: https://community.nxp.com/docs/DOC-333073  Re: Kinetis Expert System Configuration Tools V2 with Clocks Tool now available! Is there any plan for KL28Z7? I starts wondered whether I should use different chip or not. Regards, K Re: Kinetis Expert System Configuration Tools V2 with Clocks Tool now available! Erich, please disregard my last comment. I figured out how to use the tool now. This is excellent clock and pin tool. hy Re: Kinetis Expert System Configuration Tools V2 with Clocks Tool now available! HI Erich, How do you activate the IRC48M clock source for the  K64 ? It is grey out. Regards, hy Re: Kinetis Expert System Configuration Tools V2 with Clocks Tool now available! I have not seen the KE1x listed yet, digging on it... Re: Kinetis Expert System Configuration Tools V2 with Clocks Tool now available! No dates for MKE1x family? There is some information about the configuration of peripherals that is expected to be implement in Kinetis Expert System Configuration?   Re: Kinetis Expert System Configuration Tools V2 with Clocks Tool now available! Hi David, KL16 and KL26 were part of the Kinetis SDK release 2 (see https://community.nxp.com/docs/DOC-329783). The data for the clocks tool for the SDK release 2 and 3 is expected to be available on the server after Oct. 26. Re: Kinetis Expert System Configuration Tools V2 with Clocks Tool now available! Additional devices will be populated on the server over the coming weeks. I see if I can get a list/roadmap of them and put it up here for reference. Re: Kinetis Expert System Configuration Tools V2 with Clocks Tool now available! A list of supported processors would be good as well. Does not seem to support the KL16. Looks great though. Re: Kinetis Expert System Configuration Tools V2 with Clocks Tool now available! I tried to use the web version of the tool, but it said "MCU is not supported." (Using KL26Z) The release notes available from the help menu does list the KL26Z series. Is it wrong? Where is the list of supported processors?

Smarter World Tour - ボルドー - 2016年11月28日 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> EUF-HMB-T2472 - 次世代のNFCへの準備はできていますか?  NXPセミコンダクターズの紹介  MCU製品のアップデートとロードマップ  環境契約およびセキュリティのためのNXPプロセッサ  プロセッサの概要  QorIQおよびLayerscapeプロセッサ・ソリューション  セキュアなワイヤレス接続ソリューション  センサーの概要

智慧世界巡回演唱会 - 波尔多 - 2016年11月28日 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> EUF-HMB-T2472 - 您准备好迎接下一代 NFC 了吗？ 恩智浦半导体简介 MCU产品更新及路线图 恩智浦环境合同和安全处理器 处理器概述 QorIQ和Layerscape处理器解决方案 安全无线连接解决方案 传感器概述

EUF-MHW-T2470 - ワイヤレスソリューション <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 主なワイヤレス・プロトコルと、それぞれのNXPの価値提案について、詳細をご覧ください。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 主なワイヤレス・プロトコルと、それぞれのNXPの価値提案について、詳細をご覧ください。

APF-HMB-T2467 - Wireless Charging Outline current wireless charging market situation and the trend. Outline current wireless charging market situation and the trend.

EUF-NET-T2471 - Layerscape アップデート <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 高いデータスループット、低電力、CPU負荷を維持しながら、データ伝送を保護する予定はありますか?Layerscapeファミリーはあなたの最良の選択です。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 高いデータスループット、低電力、CPU負荷を維持しながら、データ伝送を保護する予定はありますか?Layerscapeファミリーはあなたの最良の選択です。

APF-DES-T2464 - Introduction to vCPE Use Cases and Opportunities An introduction to NXP vCPE solution. An introduction to NXP vCPE solution.

APF-HMB-T2468 - 基于 i.MX 6 应用处理器的物联网家庭自动化 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 了解基于 i.MX 6 应用处理器的物联网家庭自动化。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 了解基于 i.MX 6 应用处理器的物联网家庭自动化。