Body & Comfort: Exploring the Automotive General-Purpose MCU Portfolio Overview of S32K, MagniV and other GPIS products. Overview of S32K, MagniV and other GPIS products.

Amazon Alexa音声サービス <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Amazon Alexaは音声制御を永遠に変えました。Amazon Alexaの i.MX ベースのソリューションをご覧ください。リファレンスプラットフォーム、AVS認定システムIntegraotsを使用したソリューション、音声制御ソリューションを設計する際に考慮すべき重要な要素、およびAlexaを次世代デバイスに簡単に追加できる方法をご覧ください。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Amazon Alexaは音声制御を永遠に変えました。Amazon Alexaの i.MX ベースのソリューションをご覧ください。リファレンスプラットフォーム、AVS認定システムIntegraotsを使用したソリューション、音声制御ソリューションを設計する際に考慮すべき重要な要素、およびAlexaを次世代デバイスに簡単に追加できる方法をご覧ください。

Hands-On Workshop: i.MX RT Overview and Training This class will provide an overview of the i.MX RT series, key peripheral, including a hands-on tutorial using the i.MX RT EVK. This class will provide an overview of the i.MX RT series, key peripheral, including a hands-on tutorial using the i.MX RT EVK.

NFC Click Element available Over the week-end we have updated the Rapid IoT Studio servers to improve user experience further. On top of few examples on elements usage, we have now made the NFC Tag element available. Check attached example project on a simple use case. The tag embedded in Rapid Iot is updated every 10 seconds with the temperature sensor information. You can read the NFC Tag back using a NFC reader and taping it at the back of Rapid IoT

NXPとHacksterがあなたを招待します!ラピッドIoTプロトタイピングコンテストに参加して賞品を獲得しましょう! <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> HacksterはNXPと提携して、最初のラピッドIoTプロトタイピングコンテストを開催します。Fitbitウォッチ、ワイヤレスヘッドフォンなどの賞品を獲得できます。 NXP は、新しいRapid IoTプロトタイピングキットを使用して作成できるIoTエンドノード設計のタイプを確認したいと考えています。 アプリケーションカテゴリの例を次に示します。 スマートエネルギー・環境 スマートセキュリティ スマートホーム/ビル スマート識別 ....などなど! お見逃しなく、今日コンテストに参加してください! 応募するには、 ここ をクリックしてコンテストのランディングページにアクセスし、青い「参加者として登録」ボタンをクリックしてください。 ここに戻ってきて、あなたの経験についてすべて教えてください。皆様からのご意見をお待ちしております。 ラピッドプロトタイピングの頑張ってください! アプリ動画 迅速なIoT

边缘计算 - 时间、原因和手段 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 边缘计算将云计算软件基础设施置于嵌入式处理平台上，以减少延迟和上行带宽消耗。Layerscape 系列涵盖从 1 核到 16 核的设备，集成了重要的 I/O 功能并集成了硬件信任根，是边缘计算平台的理想选择。EdgeScale 等补充软件提高了这些平台的易用性并加快了客户的产品上市时间。本次会议概述了在 Layerscape 系列处理器上运行边缘计算应用程序。它涵盖了边缘计算的概念及其必要性，并进一步阐述了其可用的各种用例。它解释了客户如何使用 Layerscape SDK 运行基于容器的边缘计算应用程序，并利用 AWS、Azure、阿里巴巴等流行的边缘计算框架。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 边缘计算将云计算软件基础设施置于嵌入式处理平台上，以减少延迟和上行带宽消耗。Layerscape 系列涵盖从 1 核到 16 核的设备，集成了重要的 I/O 功能并集成了硬件信任根，是边缘计算平台的理想选择。EdgeScale 等补充软件提高了这些平台的易用性并加快了客户的产品上市时间。本次会议概述了在 Layerscape 系列处理器上运行边缘计算应用程序。它涵盖了边缘计算的概念及其必要性，并进一步阐述了其可用的各种用例。它解释了客户如何使用 Layerscape SDK 运行基于容器的边缘计算应用程序，并利用 AWS、Azure、阿里巴巴等流行的边缘计算框架。 Layerscape 处理平台 软件和工具

aips_demo_s32k118.zip <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> AIPS-liteの使用例、GPIOポートへのアクセスを保護します。この例は、UART 端末 115200 bps で使用できます。インターフェースメニューは次のように表示されます。 AIPSの例が始まりました 0 + Enterを押して、GPIOポートに赤いLEDを設定してください GPIOポートに赤いLEDを設定するには、1 + Enterキーを押してください 2を押してください:GPIO周辺機器は信頼できるマスターからのアクセスのみを受け入れます、書き込みアクセス時にM0(コア)は信頼できないものとして設定され、AIPSをコアから変更できなくなり、次のGPIOアクセスでリセットが発生します 3を押してください:GPIOアクセスは書き込み保護されており、GPIOへの書き込みアクセスはハードフォールトを生成します <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> AIPS-liteの使用例、GPIOポートへのアクセスを保護します。この例は、UART 端末 115200 bps で使用できます。インターフェースメニューは次のように表示されます。 AIPSの例が始まりました 0 + Enterを押して、GPIOポートに赤いLEDを設定してください GPIOポートに赤いLEDを設定するには、1 + Enterキーを押してください 2を押してください:GPIO周辺機器は信頼できるマスターからのアクセスのみを受け入れます、書き込みアクセス時にM0(コア)は信頼できないものとして設定され、AIPSをコアから変更できなくなり、次のGPIOアクセスでリセットが発生します 3を押してください:GPIOアクセスは書き込み保護されており、GPIOへの書き込みアクセスはハードフォールトを生成します

如何使用面向动力总成和VDS应用的Green Box平台 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 如何借助Green Box开发工具进行面向新一代汽车动力和安全(VDS)应用的S32P2/S2器件的早期开发。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 如何借助Green Box开发工具进行面向新一代汽车动力和安全(VDS)应用的S32P2/S2器件的早期开发。

Computing at the Edge - When, Why and How Edge computing puts cloud-computing software infrastructure on embedded-class processing platforms to reduce latency and uplink bandwidth consumption. Ranging from 1-core to 16-core devices, integrating important I/O features and integrating a hardware root of trust, the Layerscape family is ideal for edge-computing platforms. Complementary software like EdgeScale increases these platforms ease of use and accelerates customers' time to market. This session provides an overview of running Edge compute applications on Layerscape family of processors. It covers the concept of Edge computing and why it is needed, and goes on to elaborate the various use-cases where it can be used. It explains how customers can use the Layerscape SDK to run container based Edge compute applications, and leverage popular Edge Compute frameworks from AWS, Azure, Alibaba amongst others. Edge computing puts cloud-computing software infrastructure on embedded-class processing platforms to reduce latency and uplink bandwidth consumption. Ranging from 1-core to 16-core devices, integrating important I/O features and integrating a hardware root of trust, the Layerscape family is ideal for edge-computing platforms. Complementary software like EdgeScale increases these platforms ease of use and accelerates customers' time to market. This session provides an overview of running Edge compute applications on Layerscape family of processors. It covers the concept of Edge computing and why it is needed, and goes on to elaborate the various use-cases where it can be used. It explains how customers can use the Layerscape SDK to run container based Edge compute applications, and leverage popular Edge Compute frameworks from AWS, Azure, Alibaba amongst others. Layerscape Processing Platforms Software & Tools

在MCUXpresso IDE v11.0.0中使用LPC55S69 SDK Trustzone示例 [中文翻译版] 见附件 原文链接： https://community.nxp.com/community/mcuxpresso/mcuxpresso-ide/blog/2019/06/12/using-lpc55s69-sdk-trustzone-examples-with-mcuxpresso-ide-v1100 General

Docker On i.MX8MM With Ubuntu i.MX 8M | i.MX 8M Mini | i.MX 8M Nano

Boot I.MX6q SABRE over the Network using TFTP and NFS Host TFTP and NFS Configuration Now configure the Trivial File Transfer Protocol (TFTP) server and Networked File System (NFS) server. U-Boot will download the Linux kernel and dtb file using tftp and then the kernel will mount (via NFS) its root file system on the computer hard drive. 1. TFTP Setup   1.1.1 Prepare the TFTP Service   Get the required software if not already set up. On host for TFTP: Install TFTP on Host $ sudo apt-get install tftpd-hpa   (Note: There are a number of examples in various forums, etc, of how to automatically start the TFTP service - but not all are successful on all Linux distro's it seems! The following may work for you.)   Start the tftpd-hpa service automatically by adding a command to /etc/rc.local. $ vi /etc/rc.local   Now, just before the exit 0 line edit below command then Save and Exit. $ service tftpd-hpa start  Now, To control the TFTP service from the command line use: $ service tftpd-hpa restart    To check the status of the TFTP service from the command line use: $ service tftpd-hpa status   1.1.1 Setup the TFTP Directories Now, we have to create the directory which will contain the kernel image and the device tree blob file. $ mkdir -p /imx-boot/imx6q-sabre/tftp Then, copy the kernel image and the device tree blob file in this directory. $ cp {YOCTO_BUILD_DIR}/tmp/deploy/images/{TARGET}/zImage /imx-boot/imx6q-sabre/tftp $ cp {YOCTO_BUILD_DIR}/tmp/deploy/images/{TARGET}/ /imx-boot/imx6q-sabre/tftp   OR we can use the default directory created by yocto {YOCTO_BUILD_DIR}/tmp/deploy/images/{TARGET}/ The tftpd-hpa service looks for requested files under /imx-boot/imx6q-sabre/tftp The default tftpd-hpa directory may vary with distribution/release, but it is specified in the configuration file: /etc/default/tfptd-hpa. We have to change this default directory with our directory   Edit default tftp directory $ vi /etc/default/tftpd-hpa   Now, change the directory defined as TFTP_DIRECTORY with your host system directory which contains kernel and device tree blob file. Using created directory TFTP_DIRECTORY=”/imx-boot/imx6q-sabre/tftp” OR Using Yocto directory path TFTP_DIRECTORY=”{YOCTO_BUILD_DIR}/tmp/deploy/images/{TARGET}” Restart the TFTP service if required $ service tftpd-hpa restart   1.2 NFS Setup 1.2.1 Prepare the NFS Service Get the required software if not already set up. On host for NFS: Install NFS on Host $ sudo apt-get install nfs-kernel-server The NFS service starts automatically. To control NFS services : $ service nfs-kernel-server restart To check the status of the NFS service from the command line : $ service nfs-kernel-server status 1.2.2 Setup the NFS Directories Now, we have to create the directory which will contain the root file system. $ mkdir -p /imx-boot/imx6q-sabre/nfs   Then, copy the rootfs in this directory. $ cp -R {YOCTO_BUILD_DIR}/tmp/work/{TARGET}-poky-linux-gnueabi/{IMAGE}/1.0-r0/rootfs/* /imx-boot/imx6q-sabre/nfs   OR we can use the default directory created by yocto. $ {YOCTO_BUILD_DIR}/tmp/work/{TARGET}-poky-linux-gnueabi/{IMAGE}/1.0-r0/rootfs 1.2.3 Update NFS Export File The NFS server requires /etc/exports to be configured correctly to access NFS filesystem directory to specific hosts. $ vi /etc/exports Then, edit below line into the opened file. <”YOUR NFS DIRECTORY”> ( rw,sync,no_root_squash,no_subtree_check) Ex. If you created custom directory for NFS then, /imx-boot/imx6q-sabre/nfs (rw,sync,no_root_squash,no_subtree_check) Ex: /imx-boot/imx6q-sabre/nfs 192.168.*.*(rw,sync,no_root_squash,no_subtree_check) OR /{YOCTO_BUILD_DIR}/tmp/work/{TARGET}-poky-linux-gnueabi/{IMAGE}/1.0-r0/rootfs (rw,sync,no_root_squash,no_subtree_check)   Now, we need to restart the NFS service. $ service nfs-kernel-server restart   2 Target Setup   We need to set up the network IP address of our target. Power On the board and hit a key to stop the U-Boot from continuing. Set the below parameters, setenv serverip 192.168.0.206       //This must be your Host IP address The path where the rootfs is placed in our host has to be indicated in the U-Boot, Ex. // if you choose default folder created by YOCTO setenv nfsroot /{YOCTO_BUILD_DIR}/tmp/work/{TARGET}-poky-linux-gnueabi/{IMAGE}/1.0-r0/rootfs   OR // if you create custom directory for NFS setenv nfsroot /imx-boot/imx6q-sabre/nfs Now, we have to set kernel image name and device tree blob file name in the u-boot, setenv image < zImage name > setenv fdt_file Now, set the bootargs for the kernel boot, setenv netargs 'setenv bootargs console=${console},${baudrate} ${smp} root=/dev/nfs ip=dhcp nfsroot=${serverip}:${nfsroot},v3,tcp' Use printenv command and check loadaddr and fdt_addr environment variables variables for I.MX6Q SABRE, loadaddr=0x12000000 fdt_addr=0x18000000   Also, check netboot environment variable. It should be like below, netboot=echo Booting from net ...; run netargs; if test ${ip_dyn} = yes; then setenv get_cmd dhcp; else setenv get_cmd tftp; fi; ${get_cmd} ${image}; if test ${boot_fdt} = yes || test ${boot_fdt} = try; then if ${get_cmd} ${fdt_addr} ${fdt_file}; then bootz ${loadaddr} - ${fdt_addr}; else if test ${boot_fdt} = try; then bootz; else echo WARN: Cannot load the DT; fi; fi; else bootz; fi; Now, set environment variable bootcmd to boot every time from the network, setenv bootcmd run netboot Now finally save those variable in u-boot: saveenv Reset your board; it should now boot from the network: U-Boot 2016.03-imx_v2016.03_4.1.15_2.0.0_ga+ga57b13b (Apr 17 2018 - 17:13:43 +0530)  (..) Net:   FEC [PRIME] Normal Boot Hit any key to stop autoboot:  0   Booting from net ... Using FEC device TFTP from server 192.168.0.206; our IP address is 192.168.3.101 Filename 'zImage'. Load address: 0x12000000 Loading: #################################################################         #################################################################         #################################################################         #################################################################         #################################################################         #################################################################         ###########################################################         2.1 MiB/s done Bytes transferred = 6578216 (646028 hex) Using FEC device TFTP from server 192.168.0.206; our IP address is 192.168.3.101 Filename 'imx6q-sabresd.dtb'. Load address: 0x18000000 Loading: ####         1.8 MiB/s done Bytes transferred = 45893 (b345 hex) Kernel image @ 0x12000000 [ 0x000000 - 0x646028 ] ## Flattened Device Tree blob at 18000000   Booting using the fdt blob at 0x18000000   Using Device Tree in place at 18000000, end 1800e344 switch to ldo_bypass mode!   Starting kernel ... i.MX6_All i.MX6DL i.MX6Dual i.MX6DualPlus6QuadPlus i.MX6Quad i.MX6S i.MX6SL i.MX6SoloX i.MX6UL i.MX7Dual i.MX7Solo i.MX7ULP Linux Yocto Project Re: Boot I.MX6q SABRE over the Network using TFTP and NFS karinavalencia‌ Hi Karina, Help me to publish this document in https://community.nxp.com/community/imx if you found this document helpful and suitable. Let me know if there is any modification required. Re: Boot I.MX6q SABRE over the Network using TFTP and NFS We can publish this document on community.nxp.com public portal, which can help others to utilize this.

i.MX8M DDR3Lレジスタプログラミング支援 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> i.MX8M_DDR3L_register_programming_aidはDDR3L検証ボード用に作成されています。

Get Started with LPC54018 Based IoT Module to Develop a Cloud-Connected End Node Using our product demonstration and reference design, this class will teach you how to build your own cloud connected end node with our latest power-efficient LPC54018 flashless MCU. We will use Amazon Web Services (AWS). Using our product demonstration and reference design, this class will teach you how to build your own cloud connected end node with our latest power-efficient LPC54018 flashless MCU. We will use Amazon Web Services (AWS).

S32 Design Studio for Power Architecture 2017.R1 - Update 2 available       Product Release Announcement Automotive Microcontrollers and Processors S32 Design Studio for Power Architecture 2017.R1 Update 2          What is new? S32 SDK for Power Architecture 0.9.0 BETA for MPC574x-B-C-G and MPC574xP derivatives (see attached release notes for more details) S32 SDK  Power Architecture v0.9.0  BETA Examples - "Create S32DS Project from Example" Updated version of GNU Build tools for e200 (see the release notes attached below) Support of GHS compiler in New Project Wizard - please contact GreenHills support to obtain toolchain plugin compatible with Eclipse Neon version Updated P&E Plugin (v1.7.3.201803261737) and drivers (v12.7.0) Fixed Defects • S32DS-3506 - [e200][MPC5744P] unable to connect to secured device - addressed by adding unsecure support for MPC5744P devices • S32DS-7326 - [e200][MPC5634M] Exception occurs when accessing peripheral A registers - MMU init script error is resolved by updating the script • S32DS-7991 - [e200 2017.R1] Semihosting disabling interrupts is resolved by not disabling interrupts when stepping over specific instruction • S32DS-7177 - [MPC5634M] unable to access RAM in the debug session • S32DS-7896 - [e200] default linker sections (.got2, .jsr...) are missing in the linker script file • S32DS-3681 - [S32DS E200 B170421] Project build fail with Library support = newlib, the startup.S update to add section _fini Installation instructions The update is available for online (via S32DS Eclipse Updater) or offline installation (direct download link) online installation:  go to menu "Help" -> "Install New Software..." dialog  select predefined update site "S32DesignStudio - http://www.nxp.com/lgfiles/updates/Eclipse/S32DS_POWER_2017.R1/updatesite" select all available items and click "Next" button   offline installation:   go to S32 Design Studio for ARM product page -> Downloads section or use  direct link to download the update archive zip file Start S32DS and go to "Help" -> "Install New Software..." Add a new "Archive" repository and browse to select the downloaded update archive zip file you downloaded in the previous step Select all available items and click "Next" button.   This will starts the update installation process. General Re: S32 Design Studio for Power Architecture 2017.R1 - Update 2 available Added tags for resolved issues in this update. GCC: CMPE200GCC-168 cmpe200gcc-181 cmpe200gcc-183 CMPE200GCC-184 Binutils: CMPE200GCC-176 Newlib: cmpe200gcc-126 cmpe200gcc-178 CMPE200GCC-170 #CMPE200GCC-180

LPC54018ベースのIoTモジュールを使用して、クラウドに接続されたエンドノードを開発します <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> このクラスでは、TI の製品デモとリファレンス・デザインを使用して、TI の最新の電力効率の高いLPC54018フラッシュレス・マイコンを使用して、独自のクラウド接続エンド・ノードを構築する方法を学びます。Amazon Web Services(AWS)を利用します。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> このクラスでは、TI の製品デモとリファレンス・デザインを使用して、TI の最新の電力効率の高いLPC54018フラッシュレス・マイコンを使用して、独自のクラウド接続エンド・ノードを構築する方法を学びます。Amazon Web Services(AWS)を利用します。

PCF8523 Bare metal example project In this publication, an example project using the PCF8523 is shown to demonstrate the easy use of the RTC devices from NXP. The PCF8523 is a real-time clock based on an ultra -low power oscillator and using an I2C- bus for interfacing. Some of its features are shown below: Has an ultra -low power consumption Provides time and calendar from seconds to years Accuracy is based on a 32.768 kHz quartz crystal Clock operating voltage: 1.0 V to 5.5 V Low backup current: typical 150 nA at VDD = 3.0 V and Tamb = 25 °C 2- line bidirectional 1 MHz Fast-mode Plus (Fm+) I2C interface, slave address: read D1h, write D0h Battery backup input pin and switch-over circuit Freely programmable timer and alarm with interrupt capability Integrated oscillator load capacitors, programmable for quartz crystals with CL=7pF or CL=12.5 pF Programmable offset register for frequency adjustment Internal Power-On Reset (POR) In this example, the PCF8523 is configured using the I2C interface based on the document UM10760 to generate an interrupt every second. Once the interrupt is generated, the time is read and stored into different variables. The project was created using the FRDM-KL25Z platform and the OM13511 (I²C-bus RTC PCF8523 demo board). The complete source code is written in KDS IDE. You may find the complete project attached to this post. I highly recommend using the OM13511 as a reference for your projects.

QN9080 USB Dongle QTool is a PC software tool that works with QN9080 USB dongle to assist in the development of BLE projects with the QN9080. You control the dongle via the QTool software, which issues and receives FSCI (Framework Serial Communication Interface) formatted commands over a virtual COM port. The dongle can then act either as a master or a slave to a QN9080DK board over BLE.  Before using the BLE dongle with QTool though, the firmware on the QN9080 Dongle must be updated. The updated firmware can be found inside the QTool installation directory, and you will need to put the dongle into bootloader mode to drag-and-drop new firmware on it. Updating the Firmware on the QN9080 Dongle. 1. Install QTool: https://www.nxp.com/webapp/sps/download/license.jsp?colCode=Connectivity-QTool-Setup   2. Plug the QN9080 Dongle into a USB port on your computer 3. Using a wire, connect TP5 to ground. You can use either TP4 or the USB shield for GND. 4. While that wire is connected, press the reset button on the dongle. This will now put the dongle into bootloader mode. 5. A drive will enumerate on your computer named “CRP_DISABLD”     6. You can now remove the wire 7. Delete the firmware.bin file found in that drive 8. Drag-and-drop the firmware.bin file found in C:\NXP\Connectivity QTool\bin files into that enumerated drive. 9. Once done copying, unplug and replug in the USB Dongle, and the new firmware will now be running.  Installing the QN9080 Dongle Driver The dongle will enumerate as a USB CDC COM device. If the CDC driver is not automatically detected, you will need to manually install the driver. 1. Right-click Computer and choose Properties, the System Management window appears. 2. Click Device Manager and navigate to MCU VIRTUAL COM DEMO      3. Right-click the device MCU VIRTUAL COM DEMO and choose Update Driver Software 4. Click the  Browse my computer for driver software option in the window. 5. Click Browse button to go to the folder  C:\NXP\Connectivity QTool\drivers 6. Click the Next button at the bottom to install the driver.  7. After the driver is installed you will see the Virtual Com Port device under the Ports category    Using QTool: Now that the QN9080 dongle has the updated firmware and has the correct driver installed, you can follow the instructions in the QTool documentation found at C:\NXP\Connectivity QTool\UM11085.pdf Related documentation: QN908x Quick Start Guide QN908x DK User's Guide BLE Software

Solution for S32K14x which could be attached while couldn't be re-programmed Hi,     I would like to share with you the follow solution for S32K14x which could be attached while couldn't be re-programmed and stopped at RAM initializing.     If you met the issue as title, please check the SIM_CHIPCTL's value in IDE with attach function. Maybe you can find that the value is 0x0, which is not as default value after reset which is 0x0030_0000.     If you check the meaning on SIM_CHIPCTL, you can find that SRAMU and SRAML are retained across resets.  To solute the issue, you should add 'WRITE_LONG=00300000/40048004/ ;' in front of it the algorithm (it's better after reset) of freescale_s32k144f512m15_pflash_dflash_eeprom.arp which is at  'C:\NXP\S32DS_ARM_v20\eclipse\plugins\com.pemicro.debug.gdbjtag.pne_3.3.3.201712132114\win32\gdi\P&E\supportFiles_ARM\NXP\S32K1xx' After that, you can download your project as normal. Cheers! Oliver

A Bug exists in the KMS 1.2 SNLESSHALL project fixed with this update There was a bug in the KMS 1.2.0 SNLESSHALL reference projects when using torque mode.   The drv.c file provided in the attachment is for the SNLESSHALL reference project.     In the SNLESSHALL project, the goal is to start the motor using the Hall sensors but then transition into FOC.  It isn't intended to use the Halls for the complete speed range. In this version, it now does the startup similar to sensorless velocity.  In that it will track the speed reference until it reaches the crossover speed ("Speed Threshold" in GUI), once the speed reference reaches the crossover speed it will transition into FOC and will run in torque mode as you expect.  If you want to speed up faster before getting into FOC, you can increase the acceleration and jerk of the speed profile before the transition into FOC. Archive Re: A Bug exists in the KMS 1.2 SNLESSHALL project fixed with this update Hi,Adam Reynolds    This is the case, I understand. It seems impossible to get a detailed process of the code. thank you. Best regards！ wang xuan Re: A Bug exists in the KMS 1.2 SNLESSHALL project fixed with this update Eval board information, don't know if it's useful to you. Re: A Bug exists in the KMS 1.2 SNLESSHALL project fixed with this update Hi，Philip Drake    Thank you for your prompt reply.    Do you mean that the PMSM KMS library is no longer available in the HVP-KV46F150? Must I buy the HVP-KV31F120M again because it has the PMSM KMS library?    In addition, what was the situation with the board of HVP-KV46F, HVP-MC3PH that I purchased from Mouser Electronics in November 2017?   I have two control cards. Best regards！ wang xuan Re: A Bug exists in the KMS 1.2 SNLESSHALL project fixed with this update Wang, That software is located in the firmware library. It is not provided as open source. The HALL block decodes the Hall Effect sensor inputs and calculates the speed, the SPEED block handles setting the requested current, the CURRENT block handles setting the requested voltage, the SVPWM block takes the requested voltage and Hall Effect sensor readings in order to excited the appropriate phases. Re: A Bug exists in the KMS 1.2 SNLESSHALL project fixed with this update Hi, I have a couple of notes to make after you described your hardware.  Going forward the KMS library saved in the HVP-KV46F150 is the ACIM KMS library not the PMSM KMS library. For now if you want to try the PMSM KMS library you have to use the HVP-KV31F120M since it has the PMSM KMS library. By 3rd quarter NXP should be stocking samples of the KV46 MCU part numbers with KMS support.  The suffix P will be the PMSM library and the Q suffix on the part number will be the ACIM part number.   Depending on when and from whom you obtained your HVP-mc3ph and HVP-KV46F150 there might not be any KMS library at all in the KV46 MCU.  I only recently pulled back the stock of HVP-mc3ph and HVP-KV46F150 from the warehouses at NXP and pushed into the MCU the  KMS library.  When did you purchase the Kit?  From where did you buy it, from NXP or from a distributor? If the card is not KMS enabled I will be happy to fix that, but I would ask that you send the card to me at NXP. Regards, Philip Drake Re: A Bug exists in the KMS 1.2 SNLESSHALL project fixed with this update Hi，@Adam Reynolds    Thanks for your reminder, the hardware I use is HVP-mc3ph and HVP-KV46F150. The reference I opened is HVPKV46F150M_SNLESSHALL_IAR_1_2_0_426. I would like to know where the code for the part of the Hall sensor is located, mainly the 6-step commutation control process. Thank you again! Best regards！ wang xuan Re: A Bug exists in the KMS 1.2 SNLESSHALL project fixed with this update Wang, When you choose your reference project make sure that you pick "Sensorless Velocity - Hall Start". This is the only control mode that uses the Hall Effect sensors. Re: A Bug exists in the KMS 1.2 SNLESSHALL project fixed with this update Hi,        Sensorless speed - Hall started this part of the code I have been looking for for several days, similar to the HALL_run function mentioned in the Kinetis Motor Suite API Reference Manual can not be found, the annex is missing this part of the code? Best regards！ wang xuan