NXP Designs ナレッジベース

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

NXP Designs Knowledge Base

ディスカッション

ソート順:
Overview Remote virtual smartphones promise the same benefits as remote computer desktops and cloud-based gaming: low-cost client hardware, sandboxed user environments, and persistent user state. The way they work is that the physical smartphone runs only thin-client software and the smartphone application runs remotely on a server. To be economical, this server hosts multiple of these virtual smartphones, taking advantage of hardware virtualization support built into its processor. Slotted into the machine, an add-on GPU provides high-performance graphics. To reduce latency for real-time gameplay, the server is best located near the end-user in the edge of the mobile network. For virtual smartphones to be compatible with physical smartphones, Arm compatibility is required. At the 2020 Consumer Electronics Show, NXP demonstrated the Layerscape LX2160A processor hosting Redfinger’s cloud-based Android emulator and virtual smartphone. NXP’s processor integrates 16 CPU cores, enabling it to host 16 or more virtual smartphones. Games and other software execute with the same look and feel as if they were running locally on a smartphone. Like other Layerscape processors, the LX2160A delivers excellent performance per watt and is designed to work in high-temperature environments, such as being packed densely in a rack in a data center or deployed remotely at an edge-computing site. Although NXP designed it for stringent embedded applications, the LX2160A processor is powerful enough for servers—making it a great solution for Android emulation.     Block Diagram NXP Products Name of Product QorIQ LX2160A Development Board | NXP    Related Documents from Community Name of Document Discover i.MX: Industry-Leading Processor Solution for Media, Smart Home, Smart Industrial, Health/Medical and Broad Embedded Applications    Related Communities Name of Document Layerscape 
記事全体を表示
Flomio was able to take our SLN-POS-RDR and develop their first EASyPOS prototype in 2 short months! What is an EASyPOS? EASyPOS is an item level point of sale. A light weight terminal that connects wirelessly to the payment network to securely process transactions and unlock from products for consumers to take. EASyPOS is the first of it’s kind and though placing a POS on every item may seem impractical, it offers several advantages. For one the device is able to monitor it’s location with a high degree of accuracy, guiding shoppers directly to the products they seek and consistently delivering positive purchase experiences. Also, inventory accuracy is all but guaranteed so omnichannel commerce and other popular retail trends are supported. Finally, EASyPOS has lights and sound alerts to enable smart filtering and encourage impulse buys.     How do I use it? Using the EASyPOS is —in fact— “easy”. Follow these steps to complete your purchase: - Grab the product you want to purchase.  - Place your Contactless Payment credential on the surface of the contactless payment logo and wait for 4 LEDs to blink green. EASyPOS is now disarmed. - Slide apart the magnetic halves and remove your from your purchase.     How is it built? The EASyPOS was built by Flomio, an expert in mobile NFC device design. It operates at very low power while actively monitoring for payment engagements, remote notifications, tamper attacks, and location changes throughout the retail environment. Smaller than a deck of cards, the EASyPOS is a payments certifiable device leverages the hardened security and miniaturization advances of NXP Semiconductors. It’s split in two assemblies, the top hosting active components like the freakishly loud 90dB speaker and the bottom containing the wireless recharging power system.   Short Video: https://www.youtube.com/watch?v=FQrnTWPpRHE About Flomio, Inc. Disney’s Magic Band™ technology revolutionized their theme park business. Companies eager to “Disney-fy” their businesses without their own team of imagineers and billions to invest turn to Flomio, imagineers for the rest of us. Flomio creates proximity ID solutions that help enterprise clients and developers cross the chasm to the next web, the Internet of Things (IoT). Funded by TechStars, Flomio is fundamentally changing the way people engage with the spaces around them by making proximity ID simple to integrate, easy to deploy, and fun to use. Soon, 50 billion devices will regularly connect to the internet. Flomio’s platform empowers enterprise customers and developers to create applications that communicate with these devices. The future is ubiquitous connectivity. Flomio makes sure businesses take advantage of it.
記事全体を表示
This demo shows a demonstration of NXP's wireless charging reference design for a tablet computer.       Features Consumer and Automotive Applications Compliance with wireless power consortium QI standard Transfer efficiency Touch sensing Featured NXP Products WCT1000 Links Link to Wireless Charging Links to document page Block Diagram  
記事全体を表示
Demo 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 an exciting form-factor with a backlight module 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.   One of the table modules is provided with a table-fan in which there is a Qi power receiver built-in. It can be used as a standby-demo to further draw attention to the demo, even when no phone is placed, and it avoids phones getting lost when there is no expert attending the demo.     The Qi wireless charging demo consists of a module that can be built into any table, using a 181mm round hole and it can simply be dropped into the hole. It is delivered with a universal mains power supply and hence easy to install. Below pictures show the Qi wireless charging table module demo, as well as dimensions to help building it into available infrastructure.   Demo / product 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 NXP Recommends   NXQ1TXH5 - Low cost version; contact your local sales representative for information on NXQ1TXL5
記事全体を表示
Vital signs patient monitoring module using K60 Family MCU. Medical grade device, meets stringent safety / regulatory requirements Multi channel, real time data collection and processing:  Electrocardiogram, blood pressure, blood oxygenation etc. Usable as bed-side unit or part of distributed patient monitoring system This Project of Interest If You: Are interested in industrial medical products Are interested in real time analysis of live sensor data Description The module was developed as main functional part of portable patient monitor. It has a compact design, and unified serial interface to the host unit.  We developed it as a single board PC designed for main patient monitor application hosting and system purposes. The module provides comprehensive solution for patient vital signs monitoring. It has simplified connections, requiring only a power connection and a single data connection to the host or the distributed monitoring system. The design also meets the safety requirements for galvanic isolation of the patient. Kinetis K60 Family MCU was used as a core of this module, for data acquisition, signal preprocessing (digital filtration), data analysis and system tasks including extended supervisor functionality (with additional NIBP reserve/alarm system). The module has the following features: Module can be used in a bed-side unit, or part of a distributed monitoring system 7-lead electrocardiogram (ECG) (3-lead capable mode without RLD); Respiration rate (transimpedance on ECG lead I or lead II); SpO2 (oxygen saturation) using Nellcor OxiMax™ technology NIBP (noninvasive blood pressure) with patient adaptive fast measure mode for continuous monitoring, STAT mode; Body temperature, 2 channels Optional IBP (invasive blood pressure) up to 4 channels. This module meets all IEC safety requirements and is CE certified (as a part of patient monitor). Full Listing of Products/Components Protected by NDA IoT Physical Modules Sensors ECG / Respiration Blood oxygenation Blood pressure: invasive, non-invasive Body temperature Kinetis K60 MCU used for: Data acquisition Signal preprocessing and filtering Analysis, result output Supervisory functions Alarm generation IoT System Capabilities Under NDA
記事全体を表示
Cellular Freedom Quickly move sensor data to the cloud using the FRDM-K64F End-Device certified Skywire cellular modems provide a path to production Complete mbed code provided This Demo Is Probably of Interest If You: Need a quick proof of concept Have to demonstrate cellular connectivity to a customer or client Don’t want to build your own Thing for your IoT demo Differentiation - This Demo Highlights End-Device certified modems require no Carrier certifications to use on the cellular network XBee R footprint makes your design futureproof Global options for devices deployed or moved anywhere in the world Description The NXP FRDM-K64F is the development board for the NXP Kinetis series, providing an affordable, flexible way to build prototypes. For applications requiring cellular connectivity, the NimbeLink Sensor Shield plugs into the FRDM-K64F development board and, in turn, accepts a plug-in NimbeLink Skywire end-device certified cellular modem, providing quick cellular access. This first-in-the-industry plug-in cellular solution is easier and more compact than USB or other modem connection options, and the pre-certified Skywire embedded modem eliminates the cost and complexity of obtaining carrier certifications. The NimbeLink shield comes with four integrated MEMS sensors for easy proof-of-concept development. Sensors include an accelerometer, a temperature sensor, an atmospheric pressure sensor, light sensor, a humidity sensor, an accelerometer and two pushbutton switches. The shield also provides headers similar to those on an Arduino board. These accept any of hundreds of compatible expansion boards allowing the addition of capabilities like GPS, screens, motor controllers, and more. The NimbeLink Sensor Shield requires 5-12vdc power and accepts a variety of antennas. Full Listing of Products/Components Note: For full listing or additional information for Products/Components used in this demo see "This Demo's IoT Highlights" in Left Column. Note: If you aren't looking at this demo in the IoT Solutions Center, please use below link to access NXP IoT Solutions Center: https://community.freescale.com/community/iot-center/demos/skywire-m2mmanager-demo What this Demo is All About Video Link : 4994 IoT Physical Components Gateways Boards/Modules: FRDM-K64F Software: ARM mbed End User Products: NimbeLink Sensor Shield and Skywire Modem Wireless Connectivity End-Device certified Skywire cellular modem Sensors MEMS accelerometer, temperature, humidity and pressure sensors. Light sensor, potentiometer and pushbutton switches. Cloud Infrastructure/Services Verizon ThingSpace IoT System Capabilities Cloud/App Communications/Interworking See the data from your Sensor Shield in the cloud using the Verizon ThingSpace portal on any connected device. IoT Development Capabilities Embedded Platforms NimbeLink can help you customize your cellular product design to take advantage of the latest NXP advances in technology. IoT Product Type Product/Component Vendor Research or Procure This Product/Component End User Hardware Skywire Sensor Shield Commercial Skywire Sensor Shield End User Hardware Skywire end-device certified cellular modem Commercial Skywire Modem
記事全体を表示
This post entry provides a detailed description of how a Bluetooth Low Energy (BLE) pairing solution via NFC was developed using two of our reference development boards: The NTAG I 2 C plus kit for Arduino pinout The Freedom KW41Z board. This document has been structured as follows: NFC for easy one-tap pairing solution NFC pairing is one popular feature you can find in cameras, speakers, printer, routers, wearables and many more. Just bringing two NFC-enabled devices close together is all it takes to create a connection. Just to mention a few of examples, with just a swipe you can: Connect your phone to a wireless speaker. Connect your new devices to the home network. Connect accessories to the control unit. In all these scenarios… NFC and Bluetooth are a perfect combination, since the pairing process with NFC becomes: Faster compared to the traditional pairing methods. Easier, reducing technical support More reliable, making sure you connect to the right device. The technical basis for this “tap to connect” process is provided in the NFC Connection Handover specification running atop the NFC Forum protocol stack. It defines a framework of messages and data containers that allow bootstrapping of alternative (i.e., other than NFC) carrier connections in a standardized way. For this reason, NFC pairing solution offers a unified user experience and interoperability across different manufacturers.  NFC solutions to implement secure simple pairing There are two types of solutions recommended to add NFC pairing functionality to designs: NFC static pairing with NTAG 213 The first solution is embedding an NTAG 213 NFC label. In such a case, the pairing credentials need to be previously loaded in to the tag memory as well as in the device MCU during manufacturing. NFC dynamic pairing with NTAG I2C plus The second solution is embedding an NTAG I 2 C plus tag. In such a case, the pairing credentials can be dynamically updated by the device MCU during the product lifetime. In addition, other features such as an automatic wake-up field detection signal are possible. Precisely, the combination of a passive NFC interface with a contact I2C interface allows the product to behave as a tag and be read via NFC and to connect to a host or application processor via  I 2 C. In addition, NDEF messages can be generated and updated by the host MCU depending on the application requirements. Later, these NDEF messages can be read by any NFC phone, including iOS devices with the latest OS version. Hardware setup Mapping the previous diagram to the demo hardware, we have: The NTAG I 2 C plus tag, using the Arduino pinout kit The MCU, using Kinetis KW41Z. The applicatiob logic, which updates the NDEF contents based on different use cases. Some details about the hardware used in the next sections: Kinetis KW41Z The Kinetis KW41Z is a high integrated chip with multi-protocol radio features enabling Bluetooth Low Energy (BLE) and 802.15.4 radio protocols such as Thread. KW41Z has as large memory of 512KB that can support multiple radio protocols running in a single application instace and implements nine low-power modes and a wide operating voltage range (0.9V/4.2V), for optimum current consumption. Finally, the software support package includes: BLE, Thread and 802.15.4 generic network stacks, several sample demo apps, support for RTOS and full integration in MCUXpresso. The Kinetis KW41Z evaluation is supported with the FRDM-KW41Z development board. The board main components are: a reference crystal, an accelerometer, an Arduino header, some LEDs and buttons, a JTAG and OpenSDA connectors,and an external flash memory. NTAG I2C plus kit for Arduino pinout The NTAG I 2 C plus Arduino kit consist of two PCBs stacked together: The upper PCB is the antenna board with the connected tag The lower PCB is an interface adaptor board to the Arduino pinout. This kit can be used to connect and evaluate the NTAG I 2 C plus  into many popular MCUs with Arduino compliant headers, for example:  Kinetis (e.g. KW41Z, i.MX (e.g. UDOO Neo, i.MX 6UL, i.MX 6 ULL, i.MX 7D) and LPC MCUs (e.g. LPCXpresso MAX, V2 and V3 boards). The kit support package includes several software examples, including the BT pairing example based on KW41Z.  The OM29110ARD is a generic interface board which offers support for connection to any PCB implementing Arduino connectors. It exposes: 3.3V and 5V power supply pins. I 2 C , SPI and UART host interfaces. Generic GPIOs (e.g. to be used for field detect, interrupts, reset pins or others) As such, it allows the NTAG I 2 C plus to be plugged into Arduino devices seamlessly. Once the NTAG I 2 C plus  board is stacked on the KW41Z, the pining routing between the two boards is as follows. It uses:  The  I 2 C  interface pins. The 3.3V supply pin. One GPIO is routed for the field detection pin. The Vout, for the energy harvesting pin. The ground reference. BLE pairing with NFC on KW41Z and NTAG I2C plus This section details how the Bluetooth Low Energy (BLE) pairing with NFC on KW41Z and NTAG I 2 C plus works. The following block diagram is a simplified representation of the demo that shows: The Bluetooth and NFC interfaces The buttons and LEDs involved in the process. Starting BLE advertising After SW4 is pressed: The application goes from IDLE to searching mode, advertising the BLE device The LED 3 starts blinking in RED color. Writing BLE pairing NDEF message Once the BLE advertising is activated, the next step is for the KW41 to write the pairing message into the NTAG I 2 C  plus memory. After SW3 is pressed: The KW41 uses the  I 2 C interface with the NTAG I 2 C plus to load a pre-defined NDEF message with the BLE pairing details. At the same time, the LED 4 is set to GREEN. Pairing with the BLE device While the LED 4 is set to green, the BLE pairing message is exposed through the NTAG I 2 C plus  RF interface. During this interval, any NFC-enabled device: Can read out the NDEF pairing message. Pass the BT credentials to the Android system or the host processor. And automatically create a Bluetooth link according to the exchanged network credentials. In case of an Android system, no third-party implementation is needed on this part as long as the pairing message follows the NFC Forum specifications. Writing default NDEF message Once the pairing information is read out of the NTAG I²C plus, the KW41Z removes the pairing content and turns back to normal operation mode. In addition, in this specific demo, the NDEF pairing message is programmed to remain in the NTAG I²C plus memory for only ten seconds. After these 10 seconds: The green LED is switched off. And the pairing NDEF message is overwritten by the default NDEF about the NTAG I²C plus demo app. Video The following video shows how the Bluetooth Low Energy (BLE) pairing with NFC on KW41Z and NTAG I 2 C plus works. How to integrate NTAG I2C plus into FRDM-KW41Z hid_device sample project In this section, we describe, step by step, how NFC is integrated in an existing default demo application taken from the KW41Z support package.   FRDM-KW41Z startup In the board website, there are very clear instructions on how to get started www.nxp.com/demoboard/FRDM-KW41Z. For instance: How to test KW41Z. How to get the tools, in our case: MCUXpresso, and the SDK for KW41Z. How to import, build and runn the examples included in the SDK for KW41Z, in our case: the ones inside the wireless_examples folder Importing FRDM-KW41Z SDK and hid_device sample project After that, we import the FRDM-KW41Z SDK and we import the sample project used as a basis for adding NTAG I 2 C plus support, this is the hid_device example located under the wireless/Bluetooth folder. Importing NTAG I2C plus middelware The NTAG I 2 C plus  middleware can be easily imported as a new folder in the project tree using the MCUXpresso File / Import menu. Once imported, the internal structure of the middleware should have this structure: HAL_I2C: The HAL_I2C files support access to the Kinetis I 2 C interface. HAL_ISR:  The HAL_ISR files support the interrupt handling and callback registration for the Kinetis MCU. HAL_NTAG: The HAL_NTAG source files provide an API that allow you to communicate with the NTAG chip and implements the NTAG command set to perform memory access operations from the I 2 C interface.  For instance, this API can be used to perform: Read / Write memory operations on EEPROM and SRAM (for example, to read data, you just need to indicate the memory address and length of the data to be read) Read / Write access to NTAG I 2 C plus registers (for example, you just need to indicate the register macro to be read). Functions for enabling the pass-through mode and handling the data exchange between interfaces (setting the data transfer direction is as easy as using this function). HAL_TMR: The HAL_TMR files support access to the timing hardware of the Kinetis MCU. Adding / changing GPIO pin settings All pin and GPIO settings are defined within the pin_mux.c file. For our application, the I 2 C pins need and a GPIO for the field detection need to be enabled.  Regarding the host interface: the I 2 C  pins for NTAG communication are configured using the BOARD_InitI2C() function, it sets the required I 2 C  port (port 0 for this MC) and set the right mode for the clock (SCL) and data (SDA) lines. Regarding the field detection: it is defined within the source code even though it is not used so far. It is left defined for future use. Within the pin_mux.c file, there are other functions which initialize; for instance, the buttons, LEDs, etc. These functions are called during the hardware initialization. NTAG I2C plus software and hardware initialization We move to the main_application, where some pieces of code need to be added. All code that has been added, is inside the #ifdef NTAG_I2C clause. First, we added: The I 2 C_driver and the ntag_app header files . The ntag_handle handler declaration. Then, the HW initialization is performed calling I2C_initDevice and the NFC_Initdevice() function is called to fill the  ntag_handle software handler. HID_device demo extensions The BLE demo application is written in the hid_device.c file and the whole behavior is handled in this file. The C-code printout in the blue box  below shows the content of the BleApp_HandleKeys() function, which handles the BLE activity and the changes made related to the NFC use case. Similarly, all new code additions are within the #ifdef NTAG_I2C clause. Mainly, the BleApp_HandleKeys() function function was extended to: Copy the pairing NDEF message to the NTAG I 2 C plus chip when the button SW3 is pressed. Set the LED 3 to green while the pairing NDEF message is available. Start a timer counter from the moment the SW3 button is pressed In addition, when the time counter is expired (expiration was defined to 10 seconds): The memory content of the NTAG I 2 C plus chip is overwritten by default NDEF message. The LED 3 is set to off. NDEF message for BLE pairing definition The last part missing to cover the NFC integration into the KW41Z refers to the files created within the application to declare the NDEF pairing and NDEF messages. The NFC Data Exchange Format (NDEF) is the NFC Forum specification defining an interoperable, common data format for information stored in NFC tags and NFC devices. The spec also details how to enable tags to deliver instructions to an NFC device so that the device will perform a specific action when a particular tag is read (open a browser, initiate a phone call, pairing, etc.). Every NDEF message can be automatically processed by any NFC device and execute the appropriate action without requiring the installation of any customized software / application and independently of the hardware manufacturer. There are several NDEF record formats that you can use in your implementation. Each NDEF record indicates to the application processor which kind of payload the message carries. In our demo app, the default NDEF message used belongs to a smart poster record and the NDEF pairing message, follows the protocol defined in the NFC Forum connection handover specification. Going to the source code, two application files for the NDEF handling were created: The app_ntag.h declares the two NDEF messages used in this demo. The app_ntag.c, implements a function which writes the NDEF message into the tag. As mentioned, the NDEF used for this BLE pairing was built according to the Connection Handover and BT secure simple pairing specifications and rules. On the image below, we copied the declaration of the NDEF pairing message. This is actually the hex bytes that are written into the tag memory. To highlight son relevant parts: We find the capability container and the NDEF TLV. These two fields are used by the NFC device to detect if the tag is loaded with NDEF formatted data into a Type 2 tag (like the NTAG I 2 C plus). After that, we find the record type name. This is the MIME type for the Bluetooth out of band pairing (written in its ASCII representation). It is followed by the device Bluetooth MAC address, and the complete local name (Freescale HID). The terminator TLV In case you are interested to know more about the NDEF message structure, you can check the NFC Forum specifications The data (MAC address 00:04:9F:00:00:04 & device name FSL_HID) read by the NFC device is sent to the Bluetooth controller to establish the Bluetooth connection. Default NDEF message definition  The NDEF used as thedefault_ndef message consist of two records: The first record was built according to the SmartPoster specification from the NFC Forum, which describe how to store a plain message followed by an URL. The second record is what is called Android Application record. On the image below, we copied the declaration of the NDEF default message. To highlight son relevant parts:   As the NDEF BLE message, the first data fields we find correspond to the container and the NDEF TLV structure for a Type 2 Tag. Then, we find the smart poster record, which includes a text field. In this example, it codes the text “NTAG I2C Explorer”  and a URI field which codes a the NTAG Explorer kit website URL. After that, we find the Android application record, which is used to automatically launch the app  or, if the app is not installed, redirect the user to Google Play. Finally, the terminator TLV. After 10 seconds, the application removes the BLE pairing NDEF and replaces it by the above described NDEF message. This can be easily demonstrated by tapping the phone after these 2 seconds, and validate that the NTAG I 2 C plus demo is automatically opened. Video recorded session   Available resources BLE pairing with NFC on KW41 and NTAG I 2 C plus source code www.nxp.com/downloads/en/snippets-boot-code-headers-monitors/SW4223.zip NTAG I 2 C plus kit for Arduino pinout www.nxp.com/demoboard/OM23221ARD FRDM-KW41Z board www.nxp.com/demoboard/FRDM-KW41Z
記事全体を表示
This demo shows the temperature monitor solution. We will show the logger ADK (starter kit) and various form factors from current customers (pcbs, labels). NHS3100 can be used for all goods where temperature control is essential for the quality guarantee: pharmaceuticals, medical goods, fruits, cut flowers, chemicals, fish and meat. Demo / product features Single chip solution for pharmaceutical and perishable temperature monitoring Easy integration into final design solution (NHS3100 + battery + NFC antenna) Accurate temperature sensors Large logging space NXP Recommends Temperature logger - NHS3100 Smart Pharma
記事全体を表示
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
記事全体を表示
    Features QorIQ Processing Platforms BSC9131 SoC based LTE small cell Zero intrusion by fitting in a lamppost’s existing photocell socket Avoids costly site acquisition and lengthy planning procedures Backhaul agnostic – Fiber, copper, PoE wireless P2P Trust architecture provides secure computing environment Block Diagram
記事全体を表示
Demo NXP has comprehensive solutions for USB Type-C that covers USB power delivery (USB PD), security, signal integrity, and protection.  The video below shows complete end-to-end solution covering super speed USB data and video combined with USB PD and authentication.  Demo / Product features Complete USB Type-C End to End Solution USB Power Delivery & Display Port Alternative Mode USB PD AC/DC charger with Authentication   NXP Recommends Check all products associated with USB Type-C on below link: http://www.nxp.com/usb-type-c Training Introduction to the Next-Generation USB Type-C Connector and NXP’s End-to-End Solution 
記事全体を表示
Demo Owner Juan Antonio Gutierrez Rosas   Watch as the 2D-ACE display controller allows responsive and eye-catching graphics and keeps the system costs, power consumption and board size low.   Features Display control unit - Hardware 2D animation and composition engine Rich set of capabilities that allow to build engaging graphical content with MINIMUM CPU intervention Featured NXP Products Vybrid QorIQ Links Introduction to the Vybrid Tower System  
記事全体を表示
Demo This demo shows how the FlexIO peripheral can be utilized to connect directly to an RGB TFT display to deliver a rich graphical display. The demo uses the versatile Tower ecosystem to connect the TWR-K80F150M MCU board to the display. The demo is well documented by an Application note and associated software.       Features: Dynamic Graphical LCD (480x272) with 16bt RGB interface Images stored in fast external Serial NOR flash           FlexIO utilized to generate 16bit interface to TFT display with minimal CPU intervention   _______________________________________________________________________________________________________     Featured NXP Products Product Link Kinetis® K8x Secure Microcontrollers (MCUs) based on Arm® Cortex®-M4 Core https://www.nxp.com/products/processors-and-microcontrollers/arm-microcontrollers/general-purpose-mcus/k-series-cortex-m4/k8x-secure:K8X-SCALABLE-SECURE-MCU?&cof=0&am=0 Tower® System Modular Development Board Platform https://www.nxp.com/design/development-boards/tower-development-boards:TOWER_HOME?&tid=vantower Kinetis® K80 MCU Tower® System Module TWR-K80F150M|Tower® System Board|Kinetis® MCUs | NXP    Application Notes AN5275.pdf AN5280.pdf AN5280SW.zip _______________________________________________________________________________________________________      
記事全体を表示
Description Near Field Communication (NFC) is used for real-time precision marketing based on time, local inventory and the individual when embedded in product displays or the products themselves. NFC is also becoming the preferred method for payment either in smartphones or smart payment cards. NXP secure MCUs and MPUs paired with our contact and contactless readers provide customers with state-of-the-art, comprehensive, pre-certified PCI and EMVCo payment acceptance capabilities that will ease the development process and speed time to market for payment solutions. SmartPOS will be the most important POS in the future. Customers can download authorized third-party software and connect to an acquiring system via cellular communication. It has both the security of traditional POS and the convenience of mPOS. Features Contact card interface (TDA8035) and contactless card interface (CLRC663) Supports the whole system to pass EMV Level 1/2 certification Magnetic Strip Card Reader (MSR) supports 1/2/3 tracker, which could be implemented by ADC module Tamper detection with more active pin pairs Integrated encryption module/accelerator High speed SPI interface to extend memory space Secure boot Code protection USB/UART/SPI communication ports, etc. Block Diagram Products Category Name 1 MCU and MPU Product URL 1 Arm Cortex-M4|Kinetis K21 120 MHz 32-bit USB MCUs | NXP  Product Description 1 The Kinetis K21 MCU features a hardware encryption coprocessor for secure data transfer and storage. Faster than software implementations and with minimal CPU loading. Supports a wide variety of algorithms - DES, 3DES, AES, MD5, SHA-1, SHA-256 Product URL 2 i.MX RT1170 Crossover MCU Family - First Ghz MCU with Arm® Cortex®-M7 and Cortex-M4 Cores | NXP  Product Description 2 i.MX RT1170 includes NXP’s EdgeLock™ 4A security subsystem, including secure boot and crypto engines Category Name 2 Card Reader Product URL 1 High integrated and low power smart card interface | NXP  Product Description 1 The TDA8035 is the cost efficient successor of the established integrated contact smart card reader IC TDA8024. It offers a high level of security for the card by performing current limitation, short-circuit detection, ESD protection as well as supply supervision. Product URL 2 CLRC663 plus | High-performance multi-protocol NFC frontend | NXP  Product Description 2 The CLRC663 plus is a high-performance NFC Frontend with low-power consumption. Is the perfect choice for NFC applications with high-performance requirements like access control, payment, gaming. Category Name 3 RTC Product URL 1 PCF2129 | NXP  Product Description 1 The PCF2129 is a CMOS Real Time Clock (RTC) and calendar with an integrated Temperature Compensated Crystal (Xtal) Oscillator (TCXO) and a 32.768 kHz quartz crystal optimized for very high accuracy and very low power consumption. Designs Products Links Linux Point of Sale (POS) Reader https://www.nxp.com/design/designs/linux-point-of-sale-pos-reader:SLN-POS-LRDR 
記事全体を表示
Demo Hexiwear platform combines the style and usability found in high-end consumer devices, with the functionality and expandability of sophisticated engineering development platforms, making Hexiwear the ideal form factor for the wearable market, as well as other edge-node IoT solutions. Completely open-source and developed by MikroElektronika in partnership with NXP, the Hexiwear hardware includes the low power, high performance Kinetis K6x Microcontroller based on ARM Cortex-M4 core, the Kinetis KW40Z multimode radio SoC, supporting BLE in Hexiwear. The Hardware features included 6 on-board sensors such as Optical Heart Rate Monitor, Accelerometer and Magnetometer, Gyroscope, Temperature, Humidity, light and Pressure sensor's. Hexiwear also includes Color OLED Display, Rechargeable battery and External flash memory. $49 NXP Hexiwear, IoT and Wearables development platform – ARMdevices.net   Hexiwear is supported with its own application for Android and iOS, so customers can connect the device to the cloud straight out of the box, without any additional software development. Hexiwear uses FreeRTOS, the Kinetis software development kit (SDK) and the Kinetis Design Studio IDE. The Hexiwear platform is also expandable with the option to add nearly 200 different, additional sensors through click boards™      Features •       Eye-catching small form factor (smaller than 2” by 2”) board with open source hardware with 7 NXP components and 8 sensors on-board. •       Designed for wearable applications with the onboard rechargeable battery, OLED screen and onboard sensors such as optical heart rate, accelerometer, magnetometer and gyroscope. •       Designed for IoT end node applications with the onboard sensor’s such as temperature, pressure, humidity and ambient light. •       Complete software solution with open source embedded software, cell phone apps and cloud connectivity. •       Flexibility to let you add the sensors of your choice from 180+ plug and play add on boards. NXP Products Recommended ARM Cortex-M4|Kinetis K64 120 MHz 32-bit MCUs|NXP  ARM Cortex-M0+|Kinetis KW40Z 2.4 GHz 32-bit MCUs|NXP  FXOS8700CQ Accelerometer and Magnetometer FXAS21002 Gyroscope MPL3115A2R1 Altimeter MC34671 Battery charger Other Links Kickstarter Hexiwear Design Files Hexiwear|NXP     News Module Targets Rapid IoT Development | Embedded content from Electronic Design  NXP Accelerates Smart Wearable Product Development | Business Wire  Mouser Stocking the Hexiwear Open Source IoT Platform from MikroElektronika and NXP | Electronics360  Contest Hexiwear: The Do-Anything Device! - Hackster.io  Hexiwear: Quickly Build Quality IoT Devices - HWTrek  http://www.rs-online.com/designspark/electronics/eng/blog/test-drive-hexiwear-the-wearable-iot-development-kit  Blogs https://www.linkedin.com/pulse/hexiwear-complete-iot-wearable-development-solution-powered-kedia?trk=prof-post  Introduction to Hexiwear – a wearable development kit for the IoT era – HWTrek Blog  Win an Oculus Rift! Hexiwear Design Contest | mbed  https://mcuoneclipse.com/2016/07/12/hexiwear-teardown-of-the-hackable-do-anything-device/  Freedom development platform: Hackster.io conte... | element14 Community  JavaScript mobile apps for your NXP Hexiwear BLE device | Evothings 
記事全体を表示
Android Open Accessory support allows external USB hardware (an Android USB accessory) to interact with an Android-powered device in a special accessory mode. When an Android-powered powered device is in accessory mode, the connected accessory acts as the USB host (powers the bus and enumerates devices) and the Android-powered device acts in the USB accessory role. This ADK library is based on NXP Kinetis Microcontroller KL26, It implements some functions to communicate with android phone.  
記事全体を表示
This post entry provides a detailed description of the OM29263ADK kit, a new antenna tuning development kit specially designed to facilitate the NFC antenna prototyping process. This document has been structured as follows: OM29263ADK kit contents This kit consists of a single PCB board that includes:  A pre-matched antenna of 2 turns and a size of 77 by 113 mm.  A second pre-matched antenna of 4 turns and a smaller size of 20 by 20 mm.  And, 8 extra boards to prepare the matching for custom antennas. As a result, this kit is a perfect resource for different purposes such as evaluating the RF performance of different antenna sizes and, for prototyping your custom antenna quickly. In addition, this NFC antenna development kit is compatible with our existing product support package. You can directly connect it to CLRC663 demoboards, as well as to PN5180 and PN7462 demoboards after a minor tuning. Using OM29263ADK kit with CLEV6630A or CLEV6630B The process is really straightforward… First, take one CLRC663 demoboard and separate the main PCB from the antenna & matching circuit. The board includes cut lines, so you can divide both sections easily by only using your hands. Second, break the kit OM29263ADK PCB so that you separate the pre-matched antenna from the other PCB parts. Then, it is just a matter of connecting the two parts together. The kit antenna includes pin male connectors while the CLRC663 board includes the corresponding female connectors. Therefore, hook up the antenna with the main board, solder the connectors and that’s all. We can observe that when we connect the kit large antenna to the reader PCB, the  impedance measured with our network analyzer shows that the tuning is adjusted to approximately, 19 Ohms. This is the result obtained without any hardware modification The same process applies for the smaller antenna: Similarly, we can observe that when we connect the kit small antenna to the reader PCB, the  impedance measured with our network analyzer shows that the tuning is adjusted to approximately, 36 Ohms. This is the result obtained without any hardware modification: Using OM29263ADK kit with PNEV5180B or PNEV7462C In case you are interested to connect the OM29263ADK kit antennas to the PNEV5180B or PNEV7462C boards, the preparation process is the following: First, separate the antenna and the matching section from the PN5180 or PN7462 demoboards, as before, using the cut lines. Then, take one kit sample, and separate the pre-matched antennas for the other PCB parts. And finally, adjust the EMC filter. The EMC filter adaptation is required because the kit antenna is prepared for asymmetric tuning while the PN5180 and PN7462 original antenna use a symmetrical tuning. The main difference between both types of tuning is the cut off frequency. The symmetric tuning uses a cutoff frequency around 15MHz, while the asymmetric can go up to 22 MHz. In practice, for this adaptation, we only need to change the value of the capacitor C0 in the main board. For instance, the existing 220 pF capacitor can be replaced for another one of 68 pF. Using OM29263ADK kit to connect your own antenna coil This section describes how to use the kit PCB boards for our custom antenna tuning. For this task, the list of material that we need is: A reader PCB board, in the example, we picked CLRC663 One of the PCBs for antenna matching included in the kit And, the any antenna to be matched  In our case, we have selected one sample antenna available in our lab. The following explanation will be guided using this antenna as a reference, but any antenna can be tune using the same process. The usual list of steps to tune a custom antenna are: First, we need to define target impedance and Q factor, as design parameters for our reader Then, we will characterize the antenna coil and find its parameters After that, we will design the EMC filter With this, we will calculate the matching components using an Excel sheet Afterwards, we will assemble the calculated components and measure the first results. We will take field measurements, which probably will show that it is not perfect, so we may need to adapt the matching values With these fine-tuned vales, we will re-assemble again And finally, we will design the receiver circuit. Define target impedance and Q-factor First, we start defining the target impedance and Q-factor. The target impedance is a design parameter, which needs to be chosen according to our needs whether we want to go for maximum field strength or minimum battery consumption or a trade-off in between. Typically, reasonable values are between 20 Ohms and 80. Another important design parameter is the Q factor. The Q factor is a dimensionless parameter indicating the performance of a resonant circuit. The higher the Q factor, the higher the read range. On the other hand, increasing the Q factor also reduces the bandwidth of the circuit. As a result, in practical implementation, Q-factor values below 30 are demonstrated to fit well for the ISO14443 wave form timing requirements and corresponding spectrum.  For our tuning exercise, the design parameters chosen are an impedance of 20 ohms and a Q factor of 25 Measure antenna coil Next step is to characterize the antenna coil. Any antenna coil has an input impedance. This input impedance is complex and consists of an inductance, capacitance as well as some losses represented by a resistance (R). The actual values depend, among others, on antenna material, thickness of conductor, distance between the windings, number of turns, etc.  The coil characterization needs to be done with a network analyzer. It could be a high end, such as Agilent or Rohde & Schwarz, which is powerful, accurate, easy to use, but expensive. Or we can also go for low end solutions, such as the miniVNA PRO, which is cheap compared with the previous ones, and accurate enough for our needs. In our case, the characterization of our lab antenna shows:  An inductance around 1.3 uH And a resistance of 2.5 Ohms Design EMC filter The next step is to design the EMC filter. As we are using CLRC663, we will go for an asymmetric antenna tuning. Good inductor values are between 330nH and 560nH. and 21MHz cutoff frequency is ideal for asymmetric tuning. Fixing this two parameters, we can easily calculate the required capacitor component for our EMC filter with the formula below. In our example, we need to use a capacitor of C= 122 pF. With this, we just pick up the closer commercial value from our components box Calculate matching circuit components We have characterized the antenna coil and completed the EMC filter. Now, we can calculate the matching network components. The matching components need to be calculated so that the maximum power from the reader is transmitted to the antenna. This happens when the equivalent impedance seen from the reader IC only has the real part, without the complex part. There are some complex calculation involved in the process. In order to avoid these cumbersome formulas, NXP provides a useful Antenna Tuning excel sheet that calculate the appropriate components for you. Below, you can see a screenshot of the Excel sheet in the slide. This sheet calculates C1 and C2 matching values according to the inputs expected from the user. These are The measured antenna coil parameters The EMC filter parameters. The target impedance and Q-factor of our design With these values, The Excel sheet calculates and outputs the value of the matching components: C0, C1, C2 and Rs. In our exercise, the output values calculated for the matching network by the Excel sheet are C1 around 43 pF and C2 around 144 pF Assemble and measure Typically, the calculated values do not match with commercial components. The easiest way is to add components in parallel to get as close as possible to the calculated values. If we take a closer look to the kit antenna matching PCB board, the pad location is the following: We have two slots for C0 – so we can have two capacitors in parallel to achieve a better accuracy on the capacitance value we need to achieve We also have two slots for C1, for the same purpose We have two more slots for C2 soldering We also have two slots for the dampening resistor, in case we need to reduce the Q-factor of our antenna. And finally, one slot for the receiver resistor circuit. After the first component assembly, it is worth performing a field measurement to find out how accurate our matching is in reality. Typically, the measured impedance is different than the impedance calculated in the simulation. Therefore, the calculated matching components were not 100% accurate. But we knew that in advance. We were aware that we were just getting a rough approximation to the antenna parameters. As a result, a good matching is achieved after a number of iterations according to the field measurements that we obtain. As a general rule,  C1 changes the magnitude of the matching impedance and C2 changes its imaginary part. In our exercise, after soldering the first components, the equivalent impedance is around 19 Ohms but it also has a significant imaginary part. As a result, it can be fine-tuned towards better performance. We modified C1 and C2 a couple of times until we found out the final values that work better. obtaining a impedance with only real part at 22 Ohms (C1= 36pF and C2=154 pF). Adjust receiver circuit The last step of tuning our antenna is to design the receiver circuit. The Rx circuit that consists of a voltage divider and a coupling capacitor connected from the output of the EMC filter to the RX pins of the NFC reader. The objective is to set the voltage level at the reception pins to achieve the compromise between a good sensitivity. For CLRC663 plus, the serial resistor is in the range of 7 and 15 kΩ. You can start with a 11 KOhm value, then, the resistor can be adjusted depending on the voltage measured in the Rx pins. If the voltage at Rx pin is higher than 1.7 V, it is recommended to increase the resistor value and if the voltage at Rx pin is below than 1.2 V, it is recommended to decrease the resistor value. Using OM29263ADK kit to evaluate the performance of different antenna shapes The section covers how you can use the antennas included in the kit for performance comparison. Please note that this lab exercise is shown only for illustrative purposes on how the kit can be used to evaluate the performance of different antenna shapes. As an example, we defined a sample scenario where we want to characterize how the field strength decreases with distance when using antennas of different size. For that, we used the following setup: A class 1 ISO14443 Reference PICC A scope A CLRC663 board connected to the small antenna A CLRC663 board connected to the large antenna A ruler to measure the distance The measurements were taken in this way: We tuned the large and small antennas to 20 Ohms We connected the board to the laptop, and we executed the NFC Cockpit tool to control the RF field. We measured with the scope the voltage level obtained by the ISO14443 Class 1 Reference PICC while we increased the distance. Background information Before actually showing you the results, it is worth it to review a couple of antenna design principles to properly understand the results. Coupling coefficient Before actually showing you the results, it is worth it to review a couple of antenna design principles to properly understand the results. The coupling coefficient is a parameter that indicates how much of the magnetic field generated by the reader is picked up by the card. The coupling coefficient takes a value between 0 and 1 If the coupling equals 1, it means we have a perfect coupling, all magnetic field lines are picked by the card If the coupling equals 0, it means we have no coupling at all, no magnetic field lines are picked by the card The key message is that the coupling coefficient is just a geometric quantity. It depends on: The reader and card antenna dimensions (both antenna radius) Their relative position (whether in parallel or perpendicular, they will pick a different amount of magnetic field lines) The distance between them And the magnetic properties of the medium Mutual inductance Very related to the coupling coefficient, we have the mutual inductance. The mutual inductance allows us to determine the voltage induced in the card antenna, that depends on: Coupling coefficient  Better coupling, higher the voltage Driver current  The higher the current we drive in the reader antenna, the stronger the magnetic field Antenna inductance Precisely, in this setup, we are going to measure the voltage perceived by the reference PICC when using two different antennas. Antenna tuning components used for the large antenna First, we prepared a tuning of 20 Ohms in the large antenna. This task was done using the process described above. As an example, we selected a low Q-factor of 10, which helped us to accommodate high bit rates for ISO14443. In the figure below, you can see the components we assembled to tune the large antenna near to 20 Ohms. Antenna tuning components used for the small antenna Second, we prepared a tuning of 20 Ohms in the small antenna so that the results are comparable. The same Q-factor and EMC filter values were used, but obviously, as the antenna size is different, we used different C1, C2 and Rs values to achieve the same equivalent impedance OM29263ADK large antenna vs small antenna The following graph shows the results we obtained: The blue line, represents the DC output voltage obtained from the Class 1 Reference PICC as we increase the distance from the reader using the large antenna… The green line, represents the DC output voltage obtained from the Class 1 Reference PICC but using the reader with the small antenna connected. As a result, what we see is that at close distance, both antennas are able to deliver the same field strength. However, as distance increases, the RF field of the small antenna starts to attenuate quickly from 2 cm distance of the reader while the RF field of the large antenna is more or less stable until 5 cm, after that, it starts to attenuate quickly as well. Potentially, what we can conclude is that for this setup, we might be able to get more reading distance with the large antenna. ISO/IEC14443 vs ISO/IEC15693 reader - Quality factor We need to bear in mind that our antenna is not only for energy transfer, but also it should match with the waveform requirements. Therefore, from the practical point of view, the Q factor of the system is limited by the bandwidth as if we increase the Q, we increase the field strength but we decrease the bandwidth. Our reader can be optimized whether we are designing a reader for ISO14443 or ISO15693 as the signals modulation and timing requirements of the rise and fall times for both RF protocols are different. Actually, in practice, ISO15693 allows us a higher Q factor because there is a lower bandwidth requirement as the waveform timings are more relaxed and, the power transfer requirement is lower than ISO14443. For such optimization, you can refer again to NXP antenna tuning excel sheet. If you recall, one of the input fields of the excel sheet is the Q-factor. Therefore, you can introduce here a value below 30 for ISO14443 readers or below 100 for ISO15693 readers. The excel will output reasonable matching values for the first components adjustment. After that, you can do a fine tuning according to the process I explained before. Further information You can find more information about NFC in: Our NFC everywhere portal: https://www.nxp.com/nfc You can ask your question in our technical community: https://community.nxp.com/community/identification-security/nfc You can look for design partners: https://nxp.surl.ms/NFC_AEC And you can check our recorded training: http://www.nxp.com/support/online-academy/nfc-webinars:NFC-WEBINARS Video recorded session On 21 June 2018, a live session explaining this topic. You can watch the recording here:
記事全体を表示
Demo Running on NXP’s i.MX 6QuadPlus applications processor, Crank Software’s Movie Kiosk demo is a rich 2D and 3D user interface for previewing movies, purchasing tickets and selecting seats        Features: Runs on the NXP i.MX 6QuadPlus applications processor with Linux® OS.  The i.MX 6QuadPlus delivers 50 percent improvement in both graphics processing & memory utilization. Created with Crank Software Storyboard Suite using direct Photoshop (PSD) and 3ds Max (FBX) content import. Full video background leveraging platform’s video codec and layer blending. Multi-stream-capable HD video engine delivering up to 1080p decode. Integrated 2D and 3D animated content guiding user interactions.  Independent graphics processing units: OpenGL® ES 3.0 3D graphics accelerator with four shaders, 2D graphics accelerator, and dedicated OpenVG™ 1.1 accelerator. 3D Model provides a 1:1 virtual to physical model for theater seat selection _________________________________________________________________________________________________________________________________________ Featured Products: Storyboard Suite | Crank Softwarehttp://www.nxp.com/products/microcontrollers-and-processors/arm-processors/i.mx-applications-processors/i.mx-6-processors/i.mx6qp/i.mx-6quadplus-processor-quad-core-high-performance-advanced-3d-graphics-hd-video-advanced-multimedia-arm-cortex-a9-core:i.MX6QP i.MX6QP|i.MX 6QuadPlus Processors|Quad Core|NXP i.MX6DP|i.MX 6DualPlus Processors|Dual Core|NXP SABRE Board Reference Design|NXP  (Evaluation / Reference board) 14-Channel Configurable Power Management IC|NXP _________________________________________________________________________________________________________________________________________ C53
記事全体を表示
NFC Tandem offers best of both worlds: An NFC reader and a passive connected tag sharing one antenna. A user can interact with the device when it is powered off (through the NTAG I²C plus); when the device is powered, it can interact with cards, P2P devices or other connected tags.                                                             NFC Tandem Uses Cases and Applications: One-touch pairing WiFi with phone, or card Bluetooth with phone, headset, speaker IoT network node commissioning User identification with badge or phone Authentication and configuration of consumable and accessory Zero-power parametrization Zero-power firmware update Zero-power diagnosis and maintenance NFC Tandem Demo: NFC Tandem concept is demonstrated using NFC Tandem reference board: The demo can run on either: UDOO Neo Download UDOO Neo demo image or Raspberry Pi Download Raspberry Pi demo image Video of the demo: <script src="https://players.brightcove.net/6153537070001/default_default/index.min.js"></script>(view in My Videos) NFC Tandem References: PN7150 High performance NFC controller, supporting all NFC Forum modes, with integrated firmware and NCI interface NTAG I²C plus NFC Forum Type 2 Tag with I²C interface NFC Tandem Documents: User Manual and reference schematics are attached to this document
記事全体を表示
Demo The NTAG21x family provides a particularly well suited portfolio for NFC enhanced smart consumer products, driving the integration between physical objects and the Internet of Things. These smart products enable deeper customer relationships, real-time customer service, brand protection, condition monitoring and much more. A simple tap with an NFC enabled phone on the product can connect the consumer to the brand (opening a webpage, starting an application, providing additional information) and show the authenticity of a product       Features: Fully NFC Forum tag type 2 compliant Multiple memory options from 48 – 888 Bytes to support simple, complex and multi-purpose applications 32-bit password authentication to protect data stored into the tag UID ASCII mirror, which maps the IC unique serial number as an ASCII encoded string to a stored NDEF message to simplify tag serialization A 24-bit NFC counter, along with an ASCII mirror to improve tag usage analytics Integrated originality signature to enable the detection of unauthorized NTAG copies (and hence of unauthorized products the tags are attached to) Fast read command to speed up tag registration in inline processes such as print media or product label manufacturing   _______________________________________________________________________________________________________   Featured NXP Products: NTAG|NXP UCODE|NXP ICODE|NXP _______________________________________________________________________________________________________
記事全体を表示