Introduction The LS1046A MPU capabilities to manage data are one of the cornerstones in its design, this makes it a perfect choice when the end-application is related to data network management. The Frame Management features enable the possibility to process big data files that later on can be distributed by the network. The LS1046A also offers up-to 3 PCIe 3.0 Lanes to connect-state-of-the-art wireless cards and one SATA 3.0 interface that can be used for high-speed storage purposes. Overview This demonstration belongs to a demo bundle of the FRWY LS1046A, it intends to showcase the performance of the board in different use cases regarding edge computing. This demo provides the user an example of the LS1046A behavior when is used as a video streamer box over the QCA M.2 Wi.Fi. card. The user can access to the video vault by using a LAN infrastructure and reproduce any video in a tablet, smartphone or smart tv. Video streaming applications, centralize the highest workload in specific single or distributed systems, leaving the end-device a low demand workload. Having single-purpose systems allows an easier upgradable storage capacity, which translates to lower costs in these devices. Block Diagram Products NXP Product Link FRWY LS1046A TP LS1046A Freeway Board | NXP

Demo   Resonant Power Supply Video from IEEE.TV   The TEA19161T is a resonant / LLC half bridge converter and the TEA19162T is a PFC converter. Combining these two IC’s together with the SR controller TEA1995T at the secondary side results in a high efficient converter over the whole output power range. These demos show 2 examples of a resonant power supply; one with an output power of 240 W (12V / 20A), and another with an output power of 90 W (19.5V / 4.6A). Both showing a very low component count and small design. The resonant supplies operate in normal mode for high and medium power levels, in low power mode at medium and low power levels and in burst mode at (very) low power levels. Low power mode and burst mode operation provides a reduction of power losses, resulting in a higher efficiency at lower output power levels. Power levels for switching over from one mode to another mode can be selected by the end customer by adjusting component values. The efficiency at high power is well above 90%. No load power consumption is well below 75 mW. At 250mW output power the input power is only 360mW, which is well below the 500 mW required to be compliant with EUP lot6 power saving specification, soon becoming mandatory for consumer electronics sold in Europe.   Features: Full digital output voltage regulation and burst mode control Easy and low-cost application with cycle-by-cycle capacitive voltage control Very high efficiency over wide load range Special low power mode enabling high efficiency at 0–30% load Extremely low no-load stand-by power (< 75 mW), saves auxiliary supply cost ___________________________________________________________________________________________________________________________   Featured NXP Products:   Resonant power supply control IC|NXP GreenChip Synchronous Rectifier controller|NXP ______________________________________________________________________________________________________________________   Desktop PC Supply. 12v, 20A (240W)                                                   Ultra Slim 90W Adaptor. 19.5V / 4.6A (90W)              C17

Demo Owner: Nicholas Sargologos Demonstration of the IoTgateway reference design based on QorIQ Processor LS1021A multicore - utilizing the Freedom board, the Node Red network configuration tool and IBM Cloud Services   Features Multi-protocol support for IoT devices and high speed WAN / LAN for cloud connectivity The demo supports two data flows using Open source MQTT messaging protocol. There are two nodes powered by Kinetis micro-controllers and IoT Gateway. Node 1 is equipped with a sensor cluster serves as a publisher Node 2 is connected to as small fan and serves as a subscriber MQTT flows are carried from the nodes and the Iot gateway via Wi-Fi Java based environment is used to establish connectivity between nodes   Featured NXP Products LS1021A Links Product Link LS1021A-IoT Gateway Reference Design LS1021A-IoT Gateway Reference Design | NXP  Freedom Development Platform for Kinetis® KL14, KL15, KL24, KL25 MCUs FRDM-KL25Z|Freedom Development Platform|Kinetis® MCU | NXP  Block Diagram   News Buzz IoT designs need to start in the right direction - Embedded Computing Design

In BLE spec there is no standard wireless pass through profile, so different chip vendors have their own implementations, which is also called Proprietary Profile, the compatibility is a big challenge. There are two wireless pass through demos in NXP BLE demos. For QN90XX chip, it’s called QPP. For KW3X, it’s called wireless UART. The wireless UART is more complex. It doesn’t support always-connection and have many limitations for the app. The common BLE debug tool app on phone side cannot communicate with it, while the QPP can work well.  This demo code is target to port the QPP profile to KW3X SDK, which can simplify user’s development.

Demo Demo Summary User case: Quality of Service Feature Demo. Two PCs and one router. One PC serves as the WAN side (Server), the other PC acts as the LAN (Client). There is streaming video from the WAN Side to the LAN side. Traffic can be analyzed and compared Other router possible use cases: WAN Failover,  Load Balancing, Firewall, etc. Products QorIQ® Layerscape 1024A|NXP  QorIQ Layerscape Processors Based on ARM Technology|NXP  Links Small Business Router|NXP  QorIQ® Layerscape 1024A|NXP 

NXQ1TXH5 One-Chip Qi Low Power Wireless Charging Transmitter     Demo Owner: Rick Dumont   The NXQ1TXH5 is a one-chip low power Qi transmitter, and it enables an ultra-low cost wireless charging transmitter dramatically reducing application cost while still providing latest WPC version 1.2 Qi compliant performance. The NXQ1TXH5 demo is provided in a small form-factor on which Qi enabled phones can be charged. The demonstration shows the extremely low component count, which is interesting for professionals to understand, and at the same time showing a real-life eye-catching form-factor that draws non-technically skilled person attention. The demonstration challenges people to actually charge their phone and experience charging without wires.   Features: Ultra low component count solution. Reducing application cost by 30-50% compared to other solutions Easy to layout on 2-sided PCB Excellent EMI behaviour without additional external filtering Ultra low standby power of 10 mW meeting 5-start smartphone charger standby rating High efficiency of 75% Excellent thermal behaviour due to NXPs proprietary low RDSon power silicon technology _________________________________________________________________________________________________________________________________________   Featured NXP Products: Product Link NXQ1TXH5: One-chip 5 V Qi wireless transmitter https://www.nxp.com/products/power-management/wireless-power/one-chip-5-v-qi-wireless-transmitter:NXQ1TXH5?&lang_cd=en NXQ1TXL5: Low-cost one-chip 5 V Qi wireless transmitter NXQ1TXL5: Low-cost one-chip 5 V Qi wireless transmitter | NXP  NXQ1TXH5 WPC 1.2 Qi-compliant wireless charger demo board NXQ1TXH5 WPC 1.2 Qi-compliant wireless charger demo board | NXP    _________________________________________________________________________________________________________________________________________    

Watch this demonstration that shows designing made easy with NXP's MMPF0100 and MMPF0200. These devices are optimized for i.MX 6 applications processors. Power-sensitive applications include portable medical devices, gateways, routers, home security systems, e-readers, tablets, and home energy management solutions.   Features MMPF0100 and MMPF0200 (PMIC) evaluation kit PMICs are optimized for i.MX 6 applications processors Light-Load Efficiency Exceptional Quiescent current Large amount of One-Time Programmable memory on board Flexibility: Programming kit connects the device via USB port and user can set up the start-up frequency, voltage levels, current limit and the timing of each regulator on the device Featured NXP Products MMPF0100 MMPF0200https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fwww.nxp.com%2Fproducts%2Fpower-management%2Fpmics%2Fpmics-for-i.mx-processors%2F12-channel-configurable-power-management-ic%3AMMPF0200 Block Diagrams

Overview To improve performance in industrial drives, Field Oriented Control (FOC) is an advanced technique used for Permanent Magnetic Synchronous and other motor types. This reference design jump-starts your ability to leverage the NXP® DSCs' advanced feature sets via complete software, tools and hardware platform. Features Bi-directional rotation Application speed ranges from 0 to 100 percent of nominal speed (no field weakening) Four state machine Fault protection for driver DC-bus overcurrent, SW overcurrent, overvoltage and over speed Current control loop execution time: 17 us @ 100 MHz MCU speed PMSM vector control using the quadrature encoder Block Diagram Design Resources

Demo Owner: Kwok Wu Introducing the high-performance SSL acceleration and public key offload achieved with the C29x crypto coprocessor and industry-leading performance per watt QorIQ Processing Platforms T4240 SoC.     Features SSL Acceleration with Public Key Offload C29x crypto coprocessor runs on the industry-leading QorIQ Processing Platforms T4240 SoC or any x86 device Enables efficient scaling with growth in secure networking traffic Breakthrough performance per Dollar   Featured NXP Products C29x: Crypto Coprocessor Block Diagram  

The DDR validation tool helps pinpoint the best DDR settings providing the best possible reliability. Without this tool, engineers are likely to spend months trying to figure out the settings, if they try at all.     Features The DDR validation tool helps pinpoint the best DDR settings providing the best possible reliability. Without this tool, engineers are likely to spend months trying to figure out the settings, if they try at all Featured NXP Products PE_QORIQ_OPTI_SUITE: Processor Expert QorIQ Optimization Suite DDRv Validation Tool Scenarios Tool DPAA Packet Tool - Processor Expert QorIQ Packet Tools Links P4080: QorIQ P4080/P4040/P4081 Communications Processors with Data Path  

Smart Sensor Demo Kit Highlighted Features Multi-protocol bi-directional data stream support from/to any IP-enabled remote system Data parsing and abstraction mapping layer for normalizing data from heterogeneous devices Drag-and-drop business and analytics processing logic (akin to using Visio and Excel fused together) Report and web page builder that assembles Table reports (including data for exposure to the secure API) Time-series graphs Pie, line, spark and other chart types Uploaded visuals such as photos, CAD/CAM drawings, diagrams, schematics, etc. Full location-based services incorporating Google Maps, NOKIA here, CloudMade and Open Street Maps Business Forms assembly system so you can deploy workflow for Firmware push Remote command and control (on/off, settings, reboot, etc.) Device inventory tracking and control Asset management Financial transactions from machines Many other possibilities   Description The SeeControl Cloud Service allows embedded systems engineers to quickly assemble scalable 3-tier web applications that collect, analyze and display systems data. The service is drag and drop so you don't have to script or code to create a web app. The Service natively supports the following IoT/M2M communication protocols: UDP TCP MQTT HTTP MODBUS CoAP There is additional support for vendor-specific communication stacks such as GE, CalAmp, Sierra Wireless, etc. Customers can also create their own device adapter using protocol and language of choice. You can stream data to these data adapters at http://com2.seecontrol.com. We will give you a specific port range for each protocol/device type. You can also send your data through a device API. Guidance is here. Once the data has been received by our system. You will use a data abstraction tool to define fields that are in the packets you are sending. For example, if you send a variable field called tmp_123 from a temperature sensor you will tell the SeeControl service that tmp_123 is a a number and specifically a unit of measure called "Temperature" and then select whether Celsius or Fahrenheit. Once that is done, you can use the rest of the system to build a scalable web app, typically in 1-2 days depending on how complex our solution needs to be. To see the full range of interfaces available for visualizaing IoT data and managing devices/process, you can log in to: http://cloudx.seecontrol.com user:                fslcommunity1 password:        fslcomms1 This account only shows the visualization output, not the tools used to collect and process data. To try out the whole toolset, please acquire a full demo kit. The demo kit includes a cloud account that you can connect to the sample connectivity and sensor items listed below (or any hardware/system you would like to try out). Full Bill of Materials See bottom of this page for BOM Table Basic Data (To be filled out by FSL) Demo Number: Current Version: Current Demo Reproducibility: Intended to be Modified By: Current Demo Operation: BOM: See bottom of this page Demo Video   Freescale IoT Cloud Demo Kit     System Block Diagram   Hardware Kit & Data Flow Diagram     IoT Physical Components Gateways SOC's: i.MX6 Dual Boards/Modules: Utilite Standard Box Software: https://community.nxp.com/docs/DOC-103268 Utilite Linux BSP Connectivity Software: USB Local TCP/IP over Ethernet HTTP to Cloud Sensors End User Products: Commercial Temperature and Electric Current Sensors (See below for list) Cloud Infrastructure/Services https://community.nxp.com/docs/DOC-103268 IoT System Capabilities Device Management Add Device Remove Device Device Inventory Management Check Online/Offline Status View real time and historical messages Communications/Interworking HTTP (other protocols such as CoAP, MQTT, etc. optional) Security HTTPs (secured HTTP) Middleware / Analytics / Data SeeControl Cloud Communications & Data Mapping Tool SeeControl No Coding Analytic Engine SeeControl No Coding Visualizer Note: For additional Products/Components used in this demo see bottom of this page. IoT Product Type Product/Component Vendor Research or Procure This Product/Component Gateway NXP Utilite Standard Box NXP Contact NXP IoT Center Temperature Sensor Lascar USB Temperature Logger MicroDAQ Visit MicroDAQ Website Electrical Meter eGauge eg3000 Electric Meter eGauge Visit eGauge Website In online or phone order, please ask for SeeControl Turnkey Part Number Current Transformer(s) eGauge Current Transformers eGauge Visit eGauge Website Connectivity / Messaging Middleware SeeControl No Coding IoT Cloud Service    SeeControl Get a live demo Analytics SeeControl No Coding IoT Cloud Service SeeControl Get a live demo Data Visualization SeeControl No Coding IoT Cloud Service SeeControl Get a live demo

This document describes step-by-step how to run NFC on Raspberry Pi platform. Hardware setup: You need:    - Raspberry Pi (any model) : https://www.raspberrypi.org/products/:        - OM5578(PN7150 demokit) in RPi configuration (or OM5577(PN7120 demokit)😞         Then simply assemble boards together, stacking OM5578RPI (or OM5577RPI) to Raspberry Pi expansion connector:       Software setup:   Use Raspbian  (https://www.raspberrypi.org/software/operating-systems/) or any other Linux distribution (guidelines to set up Linux environment on raspberry pi: https://www.raspberrypi.org/documentation/installation/installing-images/). Step by step procedure: Enable i2c support:        On Raspbian: Run "sudo raspi-config" Use the down arrow to select "5 Interfacing Options" Arrow down to "P5 I2C" Select "yes" when it asks you to enable I2C Also select "yes" if it asks about automatically loading the kernel module Use the right arrow to select the <Finish> button Select "yes" when it asks to reboot       The system will reboot. when it comes back up, log in and enter the following command "ls /dev/*i2c*".       The Pi should respond with "/dev/i2c-1" which represents the user-mode I2C interface.   Install necessary tools:         On Raspbian execute the command:    sudo apt-get install autoconf automake libtool git Clone Linux libnfc-nci library repository:         Execute the command:    git clone https://github.com/NXPNFCLinux/linux_libnfc-nci.git Configure the library:         Execute the commands:    cd linux_libnfc-nci    ./bootstrap    ./configure --enable-alt Build and install the library:         Execute the commands:    make       sudo make install    export LD_LIBRARY_PATH=/usr/local/lib Run demo application (built and installed together with the library during previous step):         To simply display all data collected from remote NFC device (Peer, reader/writer or card), run the demo application in poll mode executing the command:    nfcDemoApp poll         For more details about the demo application modes execute command:    nfcDemoApp --help   One step further: Set environment variable to reference library installation:         Execute command: export LD_LIBRARY_PATH=/usr/local/lib         You may wan't to make this setting permanent by adding it to your .bashrc file for instance : echo "export LD_LIBRARY_PATH=/usr/local/lib" >> .bashrc Write your own application:         Several simple examples demonstrating use of the linux_libnfc-nci library for different use cases (Reader, Peer to peer, Host Card Emulation) are given as reference: https://github.com/NXPNFCLinux/linux_libnfc-nci_examples        - Simply clone the repository    git clone https://github.com/NXPNFCLinux/linux_libnfc-nci_examples.git        - Browse to the targeted example:    cd linux_libnfc-nci_examples/xxx_example        - Build the example:    make        - Run the example    ./xxx_example   Additional information: Another Platform ?        Using UDOO NEO (with OM5577 or OM5578 in Arduino configuration) ?           -> Follow step-by-step procedure, just updating src/halimpl/pn54x/tml/i2c/phTmlNfc_alt.h file to set CONFIGURATION flag to value 2, before building the library        Using BeagleBone Black (with OM5577 or OM5578 in BBB configuration) ?           -> Follow step-by-step procedure, just updating src/halimpl/pn54x/tml/i2c/phTmlNfc_alt.h file to set CONFIGURATION flag to value 2, before building the library        Using other Linux platform or others OM5578/OM5577 demokits configuration ?           -> Follow step-by-step procedure, just updating src/halimpl/pn54x/tml/i2c/phTmlNfc_alt.h file to set CONFIGURATION flag to value 0 and defining I2C_BUS, PIN_INT and PIN_ENABLE flags according to the HW connection, before building the library Running Android ? -> Follow guidelines provided in the related documentation: https://www.nxp.com/docs/en/application-note/AN11690.pdf

Demo Owner: Neil Krohn NXP's MM9Z1_638 is a fully integrated battery monitoring device for mission critical automotive and industrial applications. An S12Z microcontroller, SMARTMOS analog control IC, CAN protocol module and LIN interface for communications functions are embedded into this single-package soltuion. The MM9Z1_^38 battery sensor measures key battery parameters for monitoring state of health, state of charge and state of function for early batteries as well as emerging battery applications, such as 14 V stacked cell Li-Ion, high voltage junction boxes, and 24 V truck batteries.     Features The MM9Z1_638 is a fully integrated battery monitoring device for mission critical automotive and industrial applications. An S12Z microcontroller, SMARTMOS analog control IC, CAN protocol module and LIN interface for communications functions are embedded into this single-package solution. The MM9Z1_38 battery sensor measures key battery parameters for monitoring state of health, state of charge and state of function for early batteries as well as emerging battery applications, such as 14 V stacked cell Li-Ion, high voltage junction boxes, and 24 V truck batteries. Featured NXP Products MM9Z1_638: Battery Sensor with CAN and LIN Product Features: Wide range battery current measurement; on-chip temperature measurement Four battery voltage measurements with internal resistor dividers, and up to five direct voltage measurements for use with an external resistor divider Measurement synchronization between voltage channels and current channels Five external temperature sensor inputs with internal supply for external sensors Low-power modes with low-current operation Links Freescale Concept Car  

Overview This reference design describes the design of a 3-phase BLDC (Brushless DC) motor drive, which supports the NXP® 56F80X and 56F83XX Digital Signal Controllers (DSCs). The speed-closed loop BLDC drive using an encoder sensor is implemented The system is targeted for applications in both industrial and appliance fields (e.g. washing machines, compressors, air conditioning units, pumps or simple industrial drives required high reliability and efficiency) Features Voltage control of BLDC motor using Encoder sensor Targeted for 56F80X, 56F83XX, and 56F81XX Digital Signal Controllers Running on 3-phase Motor Board Control technique incorporates: Voltage BLDC motor control with speed-closed loop Current feedback loop Both directions of rotation Motoring mode Minimal speed 500 RPM Maximal speed 1000 RPM (limited by power supply) Manual interface (Start/Stop switch, Up/Down push button control, LED indication) FreeMASTER software control interface (motor start/stop, speed set-up) FreeMASTER software monitor Block Diagram Board Design Resources

This guide is intended as a reference for creating a demo application using the SLN-VIZN-IOT kit. In this guide, we will be constructing a demo e-lock application using the SLN-VIZN-IOT kit for secure face recognition using liveness detection/anti-spoofing. If you haven’t already, be sure to check out the Getting Started Guide for the SLN-VIZN-IOT kit here. Build Process Our e-lock design will make use of GPIO_AD_B0_2 and GPIO_AD_B0_03 to drive an H-Bridge circuit which actuates a lock using a 9-volt battery. These pins (and our ground) can be found on the serial header located on the front of the kit as shown below: To build our e-lock, we will be modifying the sln_vizn_iot_userid_oobe application found in the SLN-VIZN-IOT SDK. Instructions for downloading the SDK and importing the userid_oobe application can be found in the ‘Get Software’ and ‘Build and Run’ sections of the Getting Started Guide. The following video shows the modifications necessary to implement the E-Lock demo using the sln_vizn_iot_userid_oobe project To enable these pins as GPIOs, we must modify pin_mux.h and pin_mux.c found under the board folder. For simplicity, we contained these initializations in a function called BOARD_InitDoorLockPins. The code to enable these pins was generated using MCUXpresso’s integrated Config Tools, although this is not necessary. The MCUXpresso Config Tools can be read about in-depth here. Next, we need to make sure that the BOARD_InitDoorLockPins function we just created actually gets called so that the GPIOs will work the way we want them to. To do this, we will add the function call inside of our main function in main.c. After adding the door lock initialization to main, we will modify sln_system_state.cpp found under the source folder to add the code which will toggle the GPIO’s we setup in the previous step. To do this, we will make use of the GPIO_PinWrite function found in “fsl_gpio.h.” Using this function requires us to add the line “#include fsl_gpio.h” at the top of sln_system.cpp like shown below: The GPIO_PinWrite functions here will be used to unlock the door whenever a face is recognized (sysStateDetectedKnownUser) and lock the door whenever no known users are in view of the camera (sysStateDetectedNoUser). With the software modifications complete, we need to compile the code and flash our kit with the updated firmware. This can be done by using the ‘Debug’ option found in the Quickstart Panel as shown below. Make sure that the project is compiled and flashed is the sln_vizn_iot_userid_oobe project by verifying the name of the project shown at the top of the Quickstart Panel. For more detailed instructions about flashing the SLN-VIZN-IOT, check out the Flash and Debug SLN-VIZN-IOT Project section under Build, Run in the Getting Started Guide.  With the software modifications complete and the updated firmware installed, all that’s left to do is to add some wires from the GPIO pins to the door lock and power on the kit. Now our e-lock is ready to go! When a user with an unrecognized face (indicated by a red LED) tries to turn the handle nothing happens.  But when a user with a recognized face (indicated by a green LED) tries to turn the handle, the lock is disengaged allowing the latch to move. Conclusion With just a few lines of code and some external hardware, we were able to create a fully-functioning face-controlled e-lock that works entirely offline just by using the SLN-VIZN-IOT. Not to mention the fact that there was no need for any ML experience whatsoever. Because the SLN-VIZN-IOT was designed with flexibility in mind, all sorts of use cases can be supported with only minimal effort when compared to a face recognition implemented from scratch. By using the production-ready software that comes provided with the kit, it’s now possible to add local (no cloud connectivity necessary) face and emotion recognition capabilities to all sorts of products in record time. We hope this guide was helpful in showing you how to jumpstart your face recognition project with the power of the SLN-VIZN-IOT. 

Demo Owner AngelC This demo shows the ability to control various wireless devices within a home network with a smart phone / Tablet. This is done by having a so-called gateway system consisting in Tower System TWR K60 Kinetis development module connected via Ethernet/Wi-Fi with a wireless router,  plus a Kinetis KW2x MCU device controls a ZigBee-based home automation 1.2 and a TCP/IP network using a single radio (Dual PAN) . In brief, the Android application running in the tablet connects via Wi-Fi to the gateway, which translates every command to both ZigBee HA 1.2 and TCP/IP networks, thus enabling any Wi-Fi enabled device to control several devices even if using different communication protocols. Features ZigBee and TCP/IP connection Android application Featured NXP Products Product Link Kinetis® K60-100 MHz, Mixed-Signal Integration Microcontrollers based on Arm® Cortex®-M4 Core Arm® Cortex®-M4|Kinetis K60 100 MHz 32-bit Microcontrollers|NXP | NXP  Kinetis K60 100 MHz MCU Tower System Module TWR-K60D100M|Tower System Board|Kinetis MCUs | NXP 

Demo This demo consists of a Kinetis KW41Z with a TFT display that will be mounted on a bike and collecting speed and cadence measurements from Bluetooth® Low Energy mass market sensors as the ride goes. The logged data will be sent to another Kinetis KW41Z connected to a PC that forwards data to the Cloud   https://community.nxp.com/players.brightcove.net/4089003392001/default_default/index.html?videoId=4939361163001 Features: Kinetis KW41Z SoC Bluetooth® Low Energy 4.2 compliant Simultaneous Bluetooth® Low Energy Connections with market ready sensors products Bluetooth® Cycling Speed and Cadence Profile implementation interoperable with market ready product Wireless Connectivity   _______________________________________________________________________________________________________   Featured NXP Products: Product Link Kinetis® KW41Z-2.4 GHz Dual Mode: Bluetooth® Low Energy and 802.15.4 Wireless Radio Microcontroller (MCU) based on Arm® Cortex®-M0+ Core Arm® Cortex®-M0+|Kinetis® KW41Z 2.4 GHz Bluetooth Low Energy Thread Zigbee Radio MCUs | NXP  Freedom Development Kit for Kinetis® KW41Z/31Z/21Z MCUs FRDM-KW41Z |Bluetooth Thread Zigbee enabled Freedom Development Kit | NXP  Bluetooth Low Energy/IEEE® 802.15.4 Packet Sniffer/USB Dongle USB-KW41Z|Bluetooth Low Energy Thread Zigbee Wireless Packet Sniffer | NXP  _______________________________________________________________________________________________________

Overview In the industrial world, technologies to track performance and correct problems instantly have become critical to meeting output expectations and keeping personnel safe. This is especially true with organizations facing the impact of an unpredictable economic environment and aging infrastructure. Our NXP two-way radio solution takes advantage of our complete technology portfolio of high-performance MPUs, MCUs, and peripheral devices that integrate security and connectivity features and a 10-15 year product longevity program. This combination delivers high reliability and quality communication and performance that enables your customers to work safely, efficiently and enables seamless communication that boosts productivity and insight to extend the life of business assets.   Interactive Block Diagram Recommended Products   Category Products Features MCU Arm® Cortex®-M4|Kinetis® KV3x Real-time Control MCUs | NXP  100/120 MHz Cortex®-M4 core with DSP and floating-point unit – improves performance in math-intensive applications (e.g., processing of sensorless FOC (field-oriented control) algorithms) 2x 16-bit ADCs with two capture and hold circuits and up to 1.2 MSPS sample rate – simultaneous measurement of current and voltage phase, reduced jitter on input values improving system accuracy Up to 2 x 8-channel and 2 x 2-channel programmable FlexTimers – high-accuracy PWM generation with integrated power factor correction or speed sensor decoder (incremental decoder/hall sensor) MPU i.MX 8M Applications Processor | Arm® Cortex®-A53, Cortex-M4 | 4K display resolution | NXP  Quad Arm Cortex-A53; Cortex-M4F 6x I2S/SAI (20+ channels, each 32-bits @384 kHz); SPDIF Tx/Rx; DSD512 OpenGL® ES 3.1, OpenGL® 3.0, Vulkan®, OpenCL™ 1.2 Secure Element A1006 | Secure Authenticator IC: Embedded Security Platform | NXP  Advanced security using asymmetrical public/private key Diffie-Hellman authentication protocol with two different keys for encryption and decryption based on ECC (Elliptic Curve Cryptography) with a NIST B-163 bit strong binary field curve Authentication time (on-chip calculations) < 50 ms Power Consumption: 500 μA active CapTouch Sensor PCF8883 | NXP  Wide input capacitance range (10 pF to 60 pF) Wide voltage operating range (VDD = 3 V to 9 V) Designed for battery-powered applications (IDD = 3 μA, typical) Automatic calibration RTC PCF8523 | NXP  Provides year, month, day, weekday, hours, minutes, and seconds based on a 32.768 kHz quartz crystal Resolution: seconds to years Analog Switch Logic controlled high-side power switch | NXP  Wide supply voltage range from 3 V to 5.5 V 30 V tolerant on VBUS ISW maximum 2 A continuous current Load Switch USB PD and type C current-limited power switch | NXP  VIN supply voltage range from 4.0 V to 5.5 V All-time reverse current protection with ultra-fast RCP recovery Adjustable current limit from 400 mA to 3.3 adjustable current limits from 400 mA to 3.3 A Clamped current output in the over-current condition Very low ON resistance: 30 mΩ (typical) USB Type-C PTN5150 | NXP  USB Type-C Rev 1.1 compliance Compatible with legacy OTG hardware and software Support plug, orientation, role and charging current detection Level Translator PCAL6416AEX | NXP  The 16-bit general-purpose I/O expander Latched outputs with 25 mA drive maximum capability The operating power supply voltage range of 1.65 V to 5.5 V GPIO Expander PCAL6416AEX | NXP  The 16-bit general-purpose I/O expander Latched outputs with 25 mA drive maximum capability The operating power supply voltage range of 1.65 V to 5.5 V PMIC PMIC with 1A Li+ Linear Battery Charger | NXP  Input voltage VIN from 5V bus, USB, or AC adapter (4.1 V to 6.0 V) withstands up to 22V transient DDR memory reference voltage, VREFDDR, 0.5 to 0.9 V, 10 mA I2C interface User-programmable Standby, Sleep/Low-power, and Off (REGS_DISABLE) modes Accelerometer ±2g/±4g/±8g, Low g, 14-Bit Accelerometer | NXP  1.95 V to 3.6 V supply voltage 1.6 V to 3.6 V interface voltage ±2g/±4g/±8g dynamically selectable acceleration full-scale range Temperature Sensor PCT2075: I2C-bus Fm+, 1 Degree C Accuracy | NXP  Pin-for-pin replacement for LM75 series but allows up to 27 devices on the bus Power supply range from 2.7 V to 5.5 V Temperatures range from -55 °C to +125 °C Wireless MCU Arm® Cortex®-M0+|Kinetis® KW41Z 2.4 GHz Bluetooth Low Energy Thread Zigbee Radio MCUs | NXP  2.4 GHz Bluetooth Low Energy version 4.2 Compliant IEEE Std. 802.15.4 Standard Compliant AES-128 Accelerator (AESA), True Random Number Generator (TRNG)