Overview This reference design is based on 32-bit DSC MC56F84789, to demo a micro-step stepper motor control solution. This reference design jump-starts your ability to leverage the NXP ®  DSCs' advanced feature sets via complete software, tools and hardware platform. Two phases four wires stepper motor Motor self-adaptive function, auto motor parameters identification and control system adjustment Rated peak current selection by switch, the maximum current is up to 8 A Speed ratio: 1 : 1000 with position and speed closed loop control Current PID regulator Micro-step resolution selection by switch, the maximum resolution is up to 25600 steps/rev The maximum speed is up to 3000RPM with loading capability Pulse command mode: single pulse plus direction control Maximum 1 MHz pulse command input Smooth filter function for pulse command, enabled by switch Stop with half rated current FreeMASTER software control interface and monitor Features MC56F84789 Micro-Step Stepper Motor Control MAPS-56F84000 EVK Board MAPS-MC-LV3PH Motor Control Power Stage Block Diagram Design Resources

  Overview The Altimeter Barometer Reference Design is used for directly measuring the barometric pressure, determining altitude and making simple weather predictions. The barometer pressure readings are achieved using the compensated MPX2102A pressure sensor, a HCXX series of Flash microcontroller unit (MCU), and an LCD display. This reference design enables the user to evaluate a pressure sensor for barometer, personal weather station and altimeter applications. This design can be used for altimetry features in wrist watches, cell phones, GPS systems and other electronic devices. In addition, many systems require barometric pressure data to correct system response errors. This application note describes the reliability and accuracy that our sensors can provide in a barometer or altimeter system. Archived content is no longer updated and is made available for historical reference only.   Features Demonstrates barometric pressure and altitude Pressure Sensor: MPXM2102A MPAK Package Sensitivity: 0.4 mV / kPa Pressure Rating: 100kPa (Max) Microprocessor: MC68HC908QT4 4.0K Bytes of in-application reprogrammable Flash and 128 Bytes of RAM High performance, easy to use, HC08 CPU 4 Channel 8-bit analog to digital converter 8-pin DIP or SOIC packages       Design Resources

Overview Security is an increasingly key concern in the Smart Metering market. Coupled with the need for greater control over energy expenditure and ease of recharging credits for energy usage, NXP® has the perfect market requirement for secure prepayment via an electricity meter with near field communications (NFC) technology. This reference design provides a secure prepaid electricity meter with the ability to securely reload an energy balance Firmware for this reference design is based on MQX™ RTOS A variety of communication interfaces are available for remote data collecting, making this an ideal solution for residential metering Features Rich in Security features (Authentication, Secure storage) Physically secure due to Hermetic Sealing Energy balance reload through near field communications Remote secure interfacing (through smartphone) Ability to reload the meter’s balance Anti-counterfeiting check Integrated Metrology Solution based on Arm ®  Cortex ® -M4 Core MQX™ RTOS based design is suitable for advanced markets Cost-effect BoM Block Diagram Design Resources

Demo Wheel rotation is controlled by the SB0400 DC motor pre-driver. When the wheel is stopped manually, the Wheel Speed Sensor -KMI23- detects it & sends a signal to the SB0400 motor pre-driver & S32K MCU to activate the electromagnet Products 32-bit Automotive General Purpose MCUs|NXP Motorcycle Two-Wheel Antilock Braking (ABS)|NXP KMI23_KMI25|NXP  Links Motorcycle Two-Wheel Antilock Braking (ABS)|NXP  Analog Expert Software and Tools|NXP  Recommended product Link S32K144EVB https://www.nxp.com/design/development-boards/automotive-development-platforms/s32k-mcu-platforms/s32k144-evaluation-board:S32K144EVB?&fsrch=1&sr=1&pageNum=1

  Overview   The Freescale Airbag Reference Platform (ARP) is an application demonstrator system which provides an airbag Electronic Control Unit (ECU) implementation example using complete Freescale standard products for the growing automotive safety segment. The GUI firmware does not constitute a true airbag application but is intended to demonstrate features and capabilities of Freescale's standard products aimed at the airbag market.     Features   Device Description Features MPC560xP|32-bit MCU|Chassis-Safety | NXP  Qorivva 32-bit Microcontroller Scalable MCU family for safety applications e200z0 Power Architecture 32-bit core up to 64 MHz Scalable memory, up to 512 KB flash MC33789 | Airbag Power Supply and PSI5 Sensor Interface | NXP  Airbag System Basis Chip (PSI5) Power supply for complete ECU Up to four Satellite Sensor interfaces (PSI5) Up to nine configurable switch input monitors for simple switch, resistive and Hall-effect sensor interface Safing block and watchdog LIN 2.1 physical layer interface MMA68xx ECU Local X/Y Accelerometer ±20 g to ±120 g full-scale range, independently specified for each axis SPI-compatible serial interface 10-bit digital signed or unsigned SPI data output Independent programmable arming functions for each axis 12 low-pass filter options, ranging from 50 Hz to 1000 Hz MC33797 | Four Channel Squib Driver IC | NXP  Four Channel Squib Driver Four channel high-side and low-side 2.0 A FET switches Externally adjustable FET current limiting Adjustable current limit range: 0.8 to 2.0 A Diagnostics for high-side safing sensor status Resistance and voltage diagnostics for squibs 8-bit SPI for diagnostics and FET switch activation MC33901 High Speed CAN Physical Layer ISO11898-2 and -5 compatible Standby mode with remote CAN wake-up on some versions Very low current consumption in standby mode, typ. 8 μA Excellent EMC performance supports CAN FD up to 2 Mbps MMA52xx MMA51xx High G Collision Satellite Sensor ±60 g to ±480 g full-scale range PSI5 Version 1.3 Compatible (PSI5-P10P-500/3L) Selectable 400 Hz, 3 pole, or 4 pole low-pass Filter X-axis (MMA52xx) and Z-axis (MMA51xx) available

Description The user interface of a product is a key element that design engineers need to address to provide a compelling user experience. Touchpads, slides and rotaries offer a more intuitive and effective way of user interaction than traditional buttons. And, designing a touch-based user interface is simplified with this NXP touch solution. The touch function is more and more popular in the consumer market, especially in the white-good field. The KE15Z series of MCUs offers the Touch Sensing Interface (TSI) which recognizes finger touch by sensing capacitance changes. Features Advanced EMC robustness, pass IEC61000-4-6 standard test Supports both self-cap sensor and mutual-cap sensor, up to 36 touch keys Low BOM cost per touch key, no need for external devices Adjustable touch sensing resolution and sensitivity, high-performance for waterproof applications Low-power support Block Diagram Products Category Name 1: MCU Product URL 1 Arm Cortex-M0+|Kinetis KE1xZ 32-bit 5V MCUs with Touch Interface | NXP  Product Description 1 The KE1xZ includes a robust TSI module which provides a high level of stability and accuracy to any HMI system. These MCUs support up to 256 KB flash, 32 KB RAM, and a complete set of analog/digital features. Category Name 2: Wireless Product URL 1 Arm® Cortex®-M0+|Kinetis® KW41Z 2.4 GHz Bluetooth Low Energy Thread Zigbee Radio MCUs | NXP  Product Description 1 The KW41Z is an ideal solution for true single-chip designs that require concurrent communication on both a Bluetooth Low Energy network and an 802.15.4-based network such as Thread and Zigbee. Documentation KE15Z TSI Development for Low Power Applications:  https://www.nxp.com/docs/en/application-note/AN5420.pdf  Demos Touch Sense Interface for Kinetis KE15Z MCUs  Tools Product Link FRDM-KW41Z: Freedom Development Kit for Kinetis® KW41Z/31Z/21Z MCUs FRDM-KW41Z |Bluetooth Thread Zigbee enabled Freedom Development Kit | NXP  FRDM-TOUCH: Touch Module for Freedom Board FRDM-TOUCH|Touch Module for Freedom Board | NXP 

Description   Sigfox is a French company founded in 2009 that builds wireless networks to connect IoT devices. Their original focus was on industrial/professional applications such as water meters. Sigfox has recently been applying their technology to consumer applications such as smart watches and home alarms. The key parameters for the application is the requirement to exchange continuously and securely small amounts of data. A wireless base station is a transceiver that connects other devices to one another and/or to a wider area. In this particular application we are implementing a Sigfox base station.   Features Low power Securely Small amounts of data Securely transmitting small amounts of data   Block Diagram     Products   Category Name 1: MCU Product URL 1 Layerscape LS1012A Communication Processor for the IoT | NXP  Product Description 1 The QorIQ® LS1012A processor, optimized for battery-backed or USB-powered, space-constrained networking and IoT applications.   Category Name 2: Wireless Product URL 1 Low-Power Multi-Channel UHF RF Wireless Platform | NXP  Product Description 1 The OL2385 device is a radio frequency transceiver with an embedded MCU designed for a wide range of industrial and home applications requiring a very high link budget for bi-directional RF communication.   Category Name 3: Power Management Product URL 1 VR5100 Multi-output DC-DC for COMM Processor | NXP  Product Description 1 The VR5100 is a high-performance, multi-output DC-DC regulator designed to power single or dual core LS1 processors like LS1012A and LS1024A.   Category Name 4: Peripherals Product URL 1 Logic controlled high-side power switch | NXP  Product Description 1 The NX5P2190 is an advanced power switch with adjustable current limit. It includes under-voltage and over-voltage lockout, over-current, over-temperature, reverse bias and in-rush current protection circuits. Product URL 2  TJA1101 | 2nd generation PHY Transceiver | NXP  Product Description 2 TJA1101  offers 100Mbit/s transmit and receive capability per port over up to at least 15m of unshielded twisted pair (UTP) cable.   Tools   Product Link OM2385/SF001 - OL2385 Wireless sub-GHz Transceiver SIGFOX Development Kit with KL43Z OM2385/SF001 - SIGFOX Development Kit | NXP  Layerscape FRWY-LS1012A board FRWY-LS1012A Development Platform | NXP  KITVR5100FRDMEVM: Evaluation Kit for VR5100 Power Management Integrated Circuit Evaluation Kit for VR5100 Power Management Integrated Circuit | NXP 

i.MX RT1170 crossover MCUs are part of the Edge Verse™ platform and are setting speed records at 1 GHz. This ground-breaking family combines superior computing power and multiple media capabilities with ease-of-use and real-time functionality. For reducing the overall system cost, RT117x didn't have embeded flash, need external Flash as program storage and XIP place, NXP and third party like IAR, KEIL and Segger all provide mature tool to make Nor Flash‘s programing with their own flashloader, can fulfillment most customer’s application requirement, but still some users need to customize the flash programing algorithm due to programing speed optimization and difference of the nor Flash from different vendor and, such as SFDP support, QE bit's position, default sector size, DDR/OPI/QPI feature, default 3 Bytes/4 Bytes mode and also operating sequence, but the default Flashloader is based on the ROM API, it's hard to debug and customize as there is no source code. This reference demo will use source code Flash operation API instead of ROM API. In addition, it also add two new useful feature, first one is current Flashloader framework can't support some nor flash which need pre-configuration, such as Cypress's S25HL01GT, its sector size is not unified, need to config additionally. This reference demo give some function interface to implement it with 3 bytes/4bytes command mode and DDR/SDR mode, it also improve the original framework by adding read-erase-write demonstration code, which can help user to verify their customized Flashloader without need to copy to IDE every time, improve the efficiency greatly. Second advantage is it can support download flow‘s log generation, by default there is no log info in overall download flow, hard to locate which step(get configure/init/erase/program/verify) the failure occur, this demo code add log function to record every detailed download step, by which users can optimize their download speed, it's helpful for mass production. Developers can also debug and customize depend on their own specific requirement and different nor Flash.

About this demo This demo was created to give you a headstart for a UART - based GPRS module. The goal was to build the project on top of FreeRTOS ensuring a good implementation for task management and adaptability for any other project based on AT commands using a UART module.  According to the documentation of the module, the SIM800L from SIMCOM is controlled via AT commands. The advantage of using these commands is that, by tweaking some of the tasks, the application can be used for any other AT command based module. In this demo I'm going to walk you through the key elements that were used and give you a functional project that has the addition of working on a FreeRTOS environment. This offers great reliability for a fully working application that won't hang for an untested reason. Exploring this project should give you a good idea of how semaphores are implemented for various tasks management depending on each priority. Project Scope The project is intended to work with a SIM800L connected to a Freedom Development Platform for Kinetis® K64 through UART. Due to the high current consumption during some functions, the SIM800 module requieres a >1200mAh battery or a >2A buck converter. This GPRS module is a low-cost item but requires a 2G SIM card to work properly. This might be complicated to obtain in some countries. The project was built using the MCUXpresso SDK's FreeRTOS UART example. Useful Links Link Description https://mcuxpresso.nxp.com/en/builder SDK Builder for the Kinetis K64 https://www.simcom.com/product/SIM800.html SIMCOM SIM800 site documentation https://www.freertos.org/xSemaphoreCreateBinary.html FreeRTOS   Required Items Link Description https://www.nxp.com/design/development-boards/freedom-development-boards/mcu-boards/freedom-development-platform-for-kinetis-k64-k63-and-k24-mcus:FRDM-K64F NXP's FRDMK64 Board https://simcom.ee/modules/gsm-gprs/sim800/ SIMCOM SIM800 GPRS Module Buck converter   Power supply to deliver up to 4.3 V and 2 Amps   Cellular antenna     Hardware Diagram Due to the SIM800 module's high current consumption, powering it requires a buck converter that is capable of delivering a current larger than 2 Amps while the module is sending a message. This is when the module consumes the highest current.    SIM 800L  ===>    FRDM K64         VCC    ===>    3V9 Buck Converter           RX     ===>    TX (PTC17/J1-4)           TX     ===>    RX (PTC16/J1-2)        GND    ===>    GND   Step-by-Step Guide for testing the Demo Get the K64 SDK from https://mcuxpresso.nxp.com/en/select   Get the latest version of MCUXpresso using this link: https://www.nxp.com/design/software/development-software/mcuxpresso-software-and-tools-/mcuxpresso-integrated-development-environment-ide:MCUXpresso-IDE Get the SIM800 AT commands documentation in this link: https://www.elecrow.com/wiki/images/2/20/SIM800_Series_AT_Command_Manual_V1.09.pdf Install the K64 SDK in MCUXpresso. Import the attached project in this document.  Attachments are found at the bottom of this document. Connect the K64 through the USB cable. Connect the SIM800L as indicated in the previous chapter: Diagram. Build and Debug the project using MCUXpresso. In the console, you should be able to see the flow of the Tasks that are being executed. Also, the commands that are being sent and received by the UART. Due to the TaskDelay from the send_task, the application will execute every 10,000 ticks. This depends entirely on the portTick_PERIOD_MS, in this case, which in this case is roughly every 25 seconds. Additional Demo Information These next steps are intended to guide the developer to an easier understanding of the modifications that were made from the base project. This additional information intends to give you a greater understanding of how the project was built and a further explanation of the different topics this application needs for its implementation. The usage of FreeRTOS wasn't mandatory, but the usage of an operative system gives the application an additional layer of reliability for safe deployment. In addition to the actual tasks, you could implement a new task for an OTA update for new drivers, a fully functional response parser, or any other addition depending on your project needs. The usage of a task-based project ensures flexibility of the project since many modifications will not require a complete rebuilding of the application. As mentioned before, the implementation of semaphores will provide reliable task management depending on the required function. The project started from the freertos_uart example and from there three additional tasks were built: a connect task, send task, and a check task. Here is a brief explanation of each task to provide a full understanding of the functionality.  uart_task() This task was only slightly modified. The UART was changed to the UART3 interface. The UART_RTOS_Send() and UART_RTOS_Receive() functions are in the loop because the semaphore implementation is doing the release of retainment of the different tasks based on their priority. Priority is very important for this project because based on its priority the application flow would be affected. uart_task() has the highest priority. This will ensure that every time a new command is required to be sent, the application will retain the actual task and release the uart task. At the end of this task, a new semaphore is called. This semaphore will call the check_task() whose functionality is to compare the received string to the expected one. check_task() This task is executed right after the buffer has received the number of bytes that were expected from the function parameters. The first step of this task is to eliminate the extra characters ´\n´ and ´\r´ that compose the SIM800 module answer message. Depending on the command sent, the task compares the response in order to look for an Error response or a positive one. This might be different than a simple OK, depending on the command. connect_task() This task is called when the SIM800 module is disconnected. This implementation is a simple string copy that use semaphores to call the task uart and then the check task compares the received string. After the module returns an IP address, the semaphore gives the order to call the send task to continue the application flow. send_task() This task has the least priority but is the first one created, it calls the sendRoutine() function which intends to gather the data to be sent. This connect task is triggered when a command that expects an IP address, returns an ERROR response. The command sent is AT+CIFSR plus the response comparison. The application flow enters to an if conditional that calls a semaphore for the connect_task() routine. Then, the frame to be sent through the TCP function of the SIM800 module is built. Due to the protocol chosen, the SIM800 module expects a response from the server, specifically a 200 HTTP code. Depending on your module, this is where the protocol modifications can be done. A point that is worth mentioning is that the module works in a 2G bandwidth. This can be a problem in some countries due to the SIM card version incompatibility between your area network and the module. If this is the case in your country, I strongly recommend looking for a 4G module like the SIM7080 or any other NB-IoT module. This might be more expensive but you are ensuring your project will work on top of the newest cellular bands.    

本文探讨了如何解决i.MX8MP EMC测试遇到的问题，主要针对辐射超标问题。除了硬件方案，着重探讨了LVDS展频等软件方案。

Overview Small high-speed BLDC motors have a very low inductance, which is different from conventional BLDC motors. When PWM control is applied to the phases of a small high-speed BLDC motor, the current follows the rectangular PWM voltage shape. This change of current magnetizes and demagnetizes the motor iron at a frequency equal to the PWM frequency, which can cause the motor to become hot enough to be damaged. To prevent this, special techniques are required to control this type of motor. The method used in this reference design consists of a DC/DC inverter that generates the desired voltage for the motor. The motor then uses a conventional 3-phase inverter for commutation. Features Voltage control of a BLDC motor using Hall sensors Targeted at the MC56F8013 Controller Board Running on "3-Phase Power Stage with DC/DC Inverter Lite" Control technique incorporating: BLDC motor closed-loop voltage control using a DC/DC inverter BLDC motor closed-loop speed control Both directions of rotation (however, because an impeller fan is used in the application, the FreeMASTER page is locked to one direction only) Both motor mode and generator mode Starting from any motor position without rotor alignment Minimum speed - 300 RPM Maximum speed - 38000 RPM FreeMASTER software control interface (motor start/stop, speed setup) FreeMASTER software monitor FreeMASTER software graphical control page (required speed, actual motor speed, start/stop status, DC bus voltage level, motor current, system status) FreeMASTER software speed scope (observes actual and desired speeds) FreeMASTER software Hall sensors scope (observes actual state of the Hall sensors) DC bus over- and under-voltage, over-current, and Hall sensor cable error fault protection Block Diagram Board Design Resources

Teensy Prop Shield : Motion activated Light This demo shows a basic gesture controlled light sequence using NXP motion sensors available in the Teensy Prop Shield LED lights can be found on the following link: https://www.adafruit.com/product/2238 <script src="https://players.brightcove.net/6153537070001/default_default/index.min.js"></script>(view in My Videos) Features The Teensy Prop Shield is an add-on sensor shield board for the Teensy 3.1 which is an USB based microcontroller development platform. The Teensy 3.1 has a 32 bit ARM Cortex M4 processor from NXP -MK20DX256. The board can be programmed using Arduino IDE + Teensyduino plugin. The prop shield consists of the following devices: Motion Sensors - Allows motion interactive light & sound. Audio Amplifier - Clear quality audio output to a small speaker. Fast LED Driver - Drive APA102 / Dotstar LEDs for colorful lighting with rapid response. Flash Memory - 8 Mbyte storage for images, sound clips, and data logging\ Featured NXP products FXOS8700CQ - 6 Axis Linear Accelerometer & Magnetometer FXAS21002C   - 3 Axis Digital Angular Rate Gyroscope MPL3115A2     - Precision Pressure/Altitude & Temperature sensor MK20DX256   - 32 bit ARM Cortex M4 processor Demo Setup: Wiring[1] : Software: After setup, Download Arduino IDE and Teensyduino add on and follow the instructions as defined in the page below http://www.pjrc.com/teensy/td_download.html Note: Arduino version used for this demo:  1.6.8. Run the “Teensy_RGB_Led_Strip.ino” sketch attached. Sample Code: // Full orientation sensing using NXP's advanced sensor fusion algorithm.  //  // You *must* perform a magnetic calibration before this code will work.  //  // To view this data, use the Arduino Serial Monitor to watch the  // scrolling angles, or run the OrientationVisualiser example in Processing.      #include <NXPMotionSense.h>  #include <Wire.h>  #include <EEPROM.h>  #include <FastLED.h>      #define NUM_LEDS 60  CRGB leds[NUM_LEDS];      NXPMotionSense imu;  NXPSensorFusion filter;  int a;  int acc_rms;  void setup() {    Serial.begin(9600);    imu.begin();    filter.begin(100);    delay(2000);         FastLED.addLeds<APA102,11,13,BGR,DATA_RATE_MHZ(1)>(leds, NUM_LEDS);     pinMode(7, OUTPUT);    digitalWrite(7, HIGH);  // enable access to LEDs  }      void loop() {    float ax, ay, az;    float gx, gy, gz;    float mx, my, mz;    float roll, pitch, heading;        if (imu.available()) {      // Read the motion sensors      imu.readMotionSensor(ax, ay, az, gx, gy, gz, mx, my, mz);          // Update the SensorFusion filter      filter.update(gx, gy, gz, ax, ay, az, mx, my, mz);          // print the heading, pitch and roll      roll = filter.getRoll();      pitch = filter.getPitch();      heading = filter.getYaw();      Serial.print("Orientation: ");      Serial.print(heading);      Serial.print(" ");      Serial.print(pitch);      Serial.print(" ");      Serial.println(roll);      a=abs(roll/3);      Serial.print(" ");            acc_rms=sqrt(ax*ax+ay*ay+az*az)/3;      Serial.println(acc_rms);            //flash red if a violent shake event is detected            if(acc_rms==1)      {         for(int n = 0; n < NUM_LEDS; n++)          {             leds[n] = CRGB::Red;             FastLED.show();             delay(8);             leds[n] = CRGB::Black;        }      }            // Move a single white led as per rotation      for(int n = 0; n < NUM_LEDS; n++)       {         if(a==n)         {            leds[n] = CRGB::White;            FastLED.show();            delay(8);          }         else          {             leds[n] = CRGB::Black;          }      }    }  } PJRC Store Sample Code: // Full orientation sensing using NXP's advanced sensor fusion algorithm.  //  // You *must* perform a magnetic calibration before this code will work.  //  // To view this data, use the Arduino Serial Monitor to watch the  // scrolling angles, or run the OrientationVisualiser example in Processing.      #include <NXPMotionSense.h>  #include <Wire.h>  #include <EEPROM.h>  #include <FastLED.h>      #define NUM_LEDS 60  CRGB leds[NUM_LEDS];      NXPMotionSense imu;  NXPSensorFusion filter;  int a;  int acc_rms;  void setup() {    Serial.begin(9600);    imu.begin();    filter.begin(100);    delay(2000);         FastLED.addLeds<APA102,11,13,BGR,DATA_RATE_MHZ(1)>(leds, NUM_LEDS);     pinMode(7, OUTPUT);    digitalWrite(7, HIGH);  // enable access to LEDs  }      void loop() {    float ax, ay, az;    float gx, gy, gz;    float mx, my, mz;    float roll, pitch, heading;        if (imu.available()) {      // Read the motion sensors      imu.readMotionSensor(ax, ay, az, gx, gy, gz, mx, my, mz);          // Update the SensorFusion filter      filter.update(gx, gy, gz, ax, ay, az, mx, my, mz);          // print the heading, pitch and roll      roll = filter.getRoll();      pitch = filter.getPitch();      heading = filter.getYaw();      Serial.print("Orientation: ");      Serial.print(heading);      Serial.print(" ");       Serial.print(pitch);      Serial.print(" ");      Serial.println(roll);      a=abs(roll/3);      Serial.print(" ");            acc_rms=sqrt(ax*ax+ay*ay+az*az)/3;      Serial.println(acc_rms);            //flash red if a violent shake event is detected            if(acc_rms==1)      {         for(int n = 0; n < NUM_LEDS; n++)          {             leds[n] = CRGB::Red;             FastLED.show();             delay(8);             leds[n] = CRGB::Black;        }      }            // Move a single white led as per rotation      for(int n = 0; n < NUM_LEDS; n++)       {         if(a==n)         {            leds[n] = CRGB::White;            FastLED.show();            delay(8);          }         else          {             leds[n] = CRGB::Black;          }      }        }  }

  Overview The conventional timing relays offers a simple solution where the control of the systems needs to be simple or the communication isn’t possible. These have some inconvenient since they aren’t precise and are vulnerable to be modified. This application can control one or many relays. Using NFC communications, the time outputs are configured precisely and also can be programmed some functions that conventional timing relays can’t replicate. Also, the device can be password protected to block intruders or any external disturbance. Block Diagram Products Category MCU Product URL LPC8N04: Low-Cost Microcontrollers (MCUs) based on Arm® Cortex®-M0+ Core  Product Description LPC8N04 is a cost-effective MCU which serves as an entry-level connectivity solution for embedded applications with integrated NFC connectivity.   Category Power Management Product URL TEA1721BDB1065: TEA1721 Universal Mains White Goods Flyback SMPS Demo Board  Product Description This reference design demonstrates the TEA1721 as a -12 V and -3.3 V AC/DC SMPS converter that can provide 5 W into a load.   Category RTC Product URL PCF8563: Real-time clock/calendar  Product Description The PCF8563 is a CMOS Real-Time Clock (RTC) and calendar optimized for low power consumption.

在KW3x蓝牙低功耗应用中集成NFC阅读器库 URL：https://community.nxp.com/t5/Wireless-Connectivity-Knowledge/Integrating-NFC-Reader-Library-in-a-KW3x-Bluetooth-Low-Energy/ta-p/1121247 版本历史 修订编号：1（共1） 最后更新：10-01-2019 03:59 AM 更新：ovidiu_usturoi 1.    简介 1.1 用途 本文提供了有关将NFC阅读器库如何集成到KW3x蓝牙低功耗应用程序的详细说明。 1.2受众 这篇文章的目的是为希望使用NFC 阅读器库并将其适配、集成到SDK无线连接示例中的软件开发人员提供指南。 1.3参考资料和资源 NFC阅读器库：nxp.com/pages/:NFC-READER-LIBRARY -NCF3320：nxp.com/products/：NCx3320 -CLRC663 plus：nxp.com/products/:CLRC66303HN -FRDM-KW36板：nxp.com/demoboard/FRDM-KW36 -KW35 / KW36 SDK：https：//mcuxpresso.nxp.com/en/select -MCUXpresso IDE：nxp.com/products/：MCUXpresso-IDE 2. NFC 阅读器库总览 恩智浦NFC阅读器库是用C语言编写的模块化软件库，它提供了一个API，使客户能够为恩智浦非接触式阅读器IC创建自己的软件栈和应用程序, 阅读器IC为： - PN512; - CLRC633 系列; - PN7462 系列; - PN5180; 此API简化了NFC应用程序中所需的最常见操作，例如： -读取数据或将数据写入非接触式卡或标签； -与其他支持NFC的设备交换数据； -允许NFC阅读器IC模拟为卡. NFC阅读器库的设计方式使其可以轻松移植到具有多层体系结构的许多不同微控制器中：   作为主模块，有以下组件： -应用层（AL）-实现命令集以与MIFARE卡和NFC标签进行交互。 -NFC activity-实现可配置的发现循环，以检测非接触式卡，NFC标签或其他NFC设备。 -HCE和P2P组件，分别用于仿真Type 4标签和P2P数据交换。 -协议抽象层（PAL）-包含ISO14443，Felica，近邻和NFC标准的RF协议实施。 -硬件抽象层（HAL）-实现用于控制NFC前端RF接口和功能的驱动程序。 -驱动程序抽象层（DAL）-在主机MCU和读取器IC之间实现GPIO，计时器配置和物理接口（BAL）。 -OSAL模块，负责抽象OS或RTOS细节（任务事件，信号量和线程） 3. KW3x无线微控制器概述 KW3x无线微控制器（MCU）是高度集成的单芯片设备，可为汽车，工业和医疗/保健嵌入式系统提供低功耗蓝牙（Bluetooth LE）和通用FSK连接。 KW36 / 35无线MCU集成了Arm®Cortex®-M0+ CPU，最高有512 KB闪存和64 KB SRAM，以及2.4 GHz无线电，支持蓝牙LE 5.0和通用FSK调制。 低功耗蓝牙在任何主/从组合中最多支持8个同时连接。 KW36A / 36Z包含一个集成的FlexCAN模块，该模块可以无缝集成到汽车或工业CAN通信网络中，从而可以通过Bluetooth LE与外部控制和传感器监视设备进行通信。 有关更多详细信息，请参阅恩智浦网站信息： https://www.nxp.com/products/wireless/bluetooth-low-energy:BLUETOOTH-LOW-ENERGY-BLE. 4. NFC阅读器库–与FRDM-KW36集成 当前的NFC阅读器库v5.21.01不支持运行于Kinetis KW3x MCU。 本文将使用参考K82 NFC Reader Library软件包：www.nxp.com/pages/:NFC-READER-LIBRARY. 集成库所需的步骤是： -硬件准备（连接FRDM-KW36和NFC阅读器板）； -设置开发环境（SDK下载，工作空间）； -为FRDM-KW3x板准备适配文件； -将NFC应用程序集成到Wireless_UART Bluetooth LE示例中； -运行演示； 4.1硬件准备 所需硬件： -NCF3320 Antenna v1.0电路板作为NFC收发器； -FRDM-KW36电路板作为主机MCU，用于加载和运行蓝牙低功耗协议栈和NFC应用逻辑；   板卡之间的通信将使用以下引脚配置通过SPI通信进行： ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Master board (FRDM-KW36)     Connects to       Slave board (NCF3320 Antenna v1.0)           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ PTB0  (J2-pin10)                                      -                   IRQ PTB1  (J2-pin9)                              -                    Reset PTA16 (J2-pin1 - SPI1_Sout)                    -                    MOSI PTA17 (J1-pin5 - SPI1_Sin)                      -                    MISO PTA18 (J1-pin7 - SPI1_SCK)                -                 SCK PTA19 (J2-pin3 - SPI1_CS)                 -                  CS GND   (J3-pin7)                           -                  GND ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 4.2搭建开发环境 安装MCUXpresso IDE（在本示例中，使用的版本是v10.2.0 build 759） -在MCUXpresso-IDE官方网页下载最新版本的IDE： www.nxp.com/products/:MCUXpresso-IDE. -安装IDE   获取最新的NFC Reader Library版本（在此示例中，使用的版本是v5.21.00） -在NXP NFC Reader Library官网下载（www.nxp.com/pages/:NFC-READER-LIBRARY） -切换到下载标签，然后点击下载按钮 -下载Kinetis K82F软件包的NFC阅读器库：   为FRDM-KW36板生成可下载的SDK软件包（SDK_2.2.1_FRDM-KW36） -导航至https://mcuxpresso.nxp.com/cn/select，然后选择FRDM-KW36板； -选择构建MCUXpresso SDK。 -确保工具链中已选择MCUXpresso IDE。 -使用“下载SDK”按钮开始下载SDK软件包：   创建MCUXpresso工作区 -打开MCUXpresso IDE并创建一个工作区； -将SDK_2.2.1_FRDM-KW36拖放到MCUXpresso IDE的installed SDKs选项卡中；   -将Wireless_Uart示例导入到当前工作空间：   4.3准备FRDM-KW3x板的适配文件 本章介绍驱动程序抽象层（DAL）为适配FRDM-KW36所需的更改： -解压缩NFC Reader Library并导航到boards文件夹：   -通过为GPIO和handlers设置正确的配置，为FRDM-KW36创建等效文件（Board_FRDM_KW36FRc663.h）； -与FRDM-K82F板相比，以下是FRDM-KW36板所需的差异：   -将FRMD-KW36添加到…DAL \ cfg \ BoardSelection.h文件中： #ifdef PHDRIVER_FRDM_KW36FRC663_BOARD #include <Board_FRDM_KW36FRc663.h> #endif -在KinetisSDK文件夹中，更新以下依赖项： o PIT驱动程序IRQ名称：   o打开漏极和引脚锁配置： - phDriver_KinetisSDK.c:   - phbalReg_KinetisSpi.c:   -将PHDRIVER_FRDM_KW36FRC663_BOARD定义添加到…\ NxpNfcRdLib \ types \ ph_NxpBuild_Platform.h文件中，以启用正确的NFC收发器：   4.4将NFC应用程序集成到Wireless_UART Bluetooth LE示例 在本章中，将把BasicDiscoveryLoop NFC示例集成到Wireless_UART Bluetooth LE应用程序中。 为此，需要执行以下步骤： -在wireless_uart项目位置上，创建一个“ nfc”文件夹：   -从修改后的NFC阅读器库中复制DAL，NxpNfcRdLib和phOsal文件夹：   -在wireless_uart项目位置的“source”文件夹中，创建一个新的“ nfc”子文件夹，以集成BasicDiscovery loop文件：   -BasicDiscoveryLoop文件将需要进行一些更改： o将主函数重命名为NFC_BasicDiscoveryLoop_Start； o删除驱动程序/操作系统初始化部分； （所有更改都可以在附件中看到） -通过按F5来更新最新的更改，以更新MCUXpresso工作区：   -更新链接器信息（项目属性-> C / C ++构建->设置）和预处理器定义（项目属性-> C / C ++构建->预处理器）：   -添加依赖项： o PIT模块/ PIT模块初始化； o更新LED，SW配置； o增加堆大小（gTotalHeapSize_c）； o在wireless_uart.c应用程序中为NFC添加功能； （所有更改都可以在附件中看到）； 考虑到随附的ZIP归档文件，我们可以轻松地将frdmkw36_w_uart_ncf3320_basic_discovery.zip文件拖放到MCUXpresso工作区：     4.5运行演示 -根据第4.1章描述连接硬件； -在PC端打开串行终端软件，并设置FRDM-KW36板对应的COM口。 使用的BaudRate是115200。 -在FRDM-KW36上按SW2键开始启动广播。 -打开移动应用程序-IoT toolbox-Wireless UART。 FRDM-KW36板将列为NXP_WU：   -创建蓝牙LE连接。串口将打印包含蓝牙LE操作的日志：   -使用靠近NCF3320 Antenna v1.0板的NFC卡来启动发现演示。 -一旦检测到卡片，便会将事件发送到移动应用程序，其中包括卡片支持的NFC技术以及卡的UUID，演示视频如下连接： (https://www.youtube.com/watch?v=wCCz5zDIwHE&feature=youtu.be) https://community.nxp.com/t5/video/gallerypage/video-id/8707 附件是本文应用例程的源码，下载链接： https://community.nxp.com/pwmxy87654/attachments/pwmxy87654/wireless-connectivity%40tkb/200/1/ble_nfc_demo.zip      

Overview   The RDS12VR is a solution engineered for window lift, power windows, and sun roof systems. Developed in partnership with Tongji University and based on the 16-bit S12 MagniV® S12VR mixed-signal microcontrollers, the RDS12VR offers control by multiple LIN salve nodes or LIN master node, through the easy-to-control Graphics User Interface (GUI). The RDS12VR reduces unnecessary external components, lowers the total bill of material (BoM), improves system quality, and saves space in automotive applications through a smaller PCB. The RDS12VR solution includes hardware for real door/window in-vehicle applications, as well as software including anti-pinch algorithms and low-level S12VR drivers for reducing time to market. Block Diagram   Products Product Features S12VR  16-bit S12 MagniV® S12VR mixed-signal microcontrollers, efficient and scalable relay driven DC motor control solution   Features Features   Window manual/automatic up/down, automatic up/down with stop function Anti-pinch in both manual/automatic mode, anti-pinch region and force can be adjusted Stuck detection out of anti-pinch region, motor overload protection Soft stop when window is close to the top/bottom Self learning, calibration by updating the window/motor parameters stored in EEPROM Use hall sensor as well as current sense to judge anti-pinch in algorithm Power   Fault diagnosis, indicating low voltage, over voltage/current/temperature etc. Low power mode (leveraging S12VR low power mode) to reduce power consumption GUI Easy-to-control GUI, set the parameters and get the status Window lift can be controlled either by multiple LIN salve nodes or LIN master node, through GUI Functional Safety Able to comply with relevant content in US Federal Motor Vehicle Safety FMVSS No. 118 standard Document DRM160, Window Lift and Relay Based DC Motor Control Reference Design Using the S12VR Microcontrollers     

本文说明S32G LLCE CAN Linux驱动的 快速测试方法。 目录 1 参考资料 .................................................................... 2 1.1 参考资料 ................................................................. 2 1.2 版本匹配说明 .......................................................... 2 2 环境搭建 .................................................................... 3 2.1 使用Yocto编译 ........................................................ 3 2.2 使用Standalone编译 ............................................... 4 3 测试 ........................................................................... 5 3.1 硬件连接 ................................................................. 5 3.2 测试方法 ................................................................. 6 4 LLCE CAN Linux驱动说明 ......................................... 7 4.1 DTS ........................................................................ 7 4.2 源代码 .................................................................... 9  

Overview This reference design demonstrates a vector control technique of a 3-phase AC induction motor with a position encoder coupled to the motor shaft. The algorithm runs on Our 56F80X or 56F83XX Digital Signal Controller as the dedicated motor control device It can be adapted to NXP® 56F81XX Digital Signal Controllers The speed closed loop ACIM drive is implemented The system is targeted for applications in both industrial and appliance fields (e.g. washing machines, dishwashers, industrial drives, machine tools, variable speed drives, elevators etc.) Features Vector control technique used for ACIM control Targeted for 56F80X, 56F83XX, and 56F81XX Digital Signal Controllers Running on a 3-phase AC induction motor control development platform at variable line voltage 115/230V AC Encoder used for a speed calculation Control technique incorporates: Speed control loop with inner q axis stator current loop Rotor flux control loop with inner d axis stator current loop Field-weakening technique Stator phase currents measurement method DC-Bus ripple elimination Motor and generator mode DC-Bus brake Overvoltage, undervoltage, overcurrent and overheating fault protection FreeMASTER software control interface and monitor Block Diagram Board Design Resources

New generation Microwave oven. Delivery of highly efficient, controlled RF power will modernize RF and microwave heating applications, and create a new cooking and heating paradigm. Explore NXP's comprehensive solid state solutions with a complete line of drivers, power amplifiers, microcontrollers, antenna and reference design support, as well as smart, economical application development tools.     Features Long Life span Ability to focus energy directly into the food being cooked Phase, Frequency and Amplitude control Vary maximums and minimum thresholds of power within the oven Links RF Heating RF Power  

Demo New S32V234 silicon demonstrating the MIPI CSI camera connection with execution of ISP algorithm and comparison with original camera image. New ADAS solution for vision, sensor fusion and surround view application Quad-core ARM® Cortex®-A53 processor, CogniVue APEX™, Vivante GC3000 GPU, and advanced memory bus system architecture Integrated ISP for camera video input and filtering Featured NXP Product S32V230 Family of Processors for Advanced Dri|NXP Other Advanced Driver Assistance Systems (ADAS)|NXP

Description Controlling all your home devices using Amazon Voice services (aka Alexa), Google assistant or a third-party/proprietary cloud-based IA is today’s trend. Sometimes it requires a mix of these IAs. To avoid constantly sending sound, keyword/hot word detection must be done locally. These devices connect to the voice-controlled intelligent personal assistant service such as Alexa or Google to control the devices paired to it. This voice control gateway can control multiple smart devices in your house with cloud-to-cloud communications and access to multiple services such as, streaming music, accessing an agenda, turning lights on and off, making phone calls and searching the internet. NXP has developed a range of solutions for adding voice control directly into any product. From flexible implementations to completely turnkey solutions, NXP offers scalable options from high-performance MPUs to cost-effective MCUs. Features Multi-channel audio and digital microphone inputs Connectivity (I2C, SAI, UART, SPI, SDIO, USB, PCIe, Gigabit Ethernet) Consumer and Industrial Programmable LED brightness Android™, Linux®, FreeRTOS and partner commercial operating systems. Block Diagram Products Category Name 1: MPU Product URL 1 i.MX 8M Mini Applications Processor | Arm Cortex A53/M4 | 1080P display | NXP  Product Description 1 Your design can leverage the latest voice control capabilities. Software solutions support reliable voice control in noisy environment without a DSP. Category Name 2: Driver Product URL 1 14-channel power management IC optimized for i.MX 8M | NXP  Product Description 1 The PF4210 is a high-performance PMIC that is optimized to power low-cost consumer applications with the i.MX 8M family of applications processors. Product link 2 PCA9626 | NXP  Product Description 2 The PCA9626 is an I²C-bus controlled 24-bit LED driver optimized for voltage switch dimming and blinking 100 mA Red/Green/Blue/Amber (RGBA) LEDs. Product link 3 3.4 W I2S input mono class-D audio amplifier | NXP  Product Description 3 The TFA9882 is a mono, filter-free class-D audio amplifier in a 9-bump WLCSP (Wafer Level Chip-Size Package) with a 400 µm pitch. Category Name 3: Wireless Product URL 1 Arm® Cortex®-M0+|Kinetis® KW31Z Bluetooth Low Energy 32-bit MCUs | NXP  Product Description 1 The KW31Z is an ultra-low-power, highly-integrated single-chip device that enables Bluetooth® low energy v4.2 RF connectivity for portable, extremely low-power embedded systems. Product link 2 IEEE802.15.4 Wireless Microcontroller | NXP  Product Description 2 The JN5179 device is an ultra-low-power, high-performance wireless microcontroller, optimized as a platform for ZigBee 3.0 applications in Smart Home and Smart Lighting networks. Demo i.MX for Voice Recognition  Tools Product Link i.MX 8M Development Kit for Amazon Alexa Voice Service i.MX 8M Development Kit for Amazon Alexa Voice Service | NXP