Demo These state-of-the-art devices are single-chip solutions for contact, contactless, and NFC operation, and can be loaded with fully-custom applications. Optimized antenna operation and low-power modes enable best-in-class performance. This NFC & BLE hospitality demo showcases a physical access scenario in hospitality with ultimate contactless connectivity through NXP NFC and BLE solutions and superior security with MIFARE DESFire on cards, mobile and wearables Product Features • Total interoperability with smart devices – NFC/BLE • Ultimate contactless connectivity through NXP NFC and BLE solutions • Superior contactless experience and security with MIFARE DESFire on cards, mobile and wearables NXP Recommends PN746X_736X_SERIES|NXP  Ultra low power Bluetooth LE system-on-chip solutio|NXP 

This post entry provides a detailed description of how to port the NFC Reader Library to Kinetis K64F MCU. It is used a real porting example exercise to show the steps required to adapt the NFC Reader Library to a sample target MCU. The goal of this post is to serve as a guide for software developers requiring to port the NFC Reader Library to their MCU of choice for their designs. NFC Reader Library overview The NFC Reader Library is a software stack for creating and developing contactless applications for NXP’s NFC frontends and NFC controllers with customizable firmware. This library provides an API facilitates the most common operations required in NFC applications such as: reading or writing data into contactless cards, exchanging data with other NFC-enabled devices or emulating cards. The NFC Reader Library: It is based on a modular approach It has been designed with a flexible and multilayered architecture It is written in ANSI-C programming language It is supported in multiple design environments and platforms and it has been developed with a strong focus on portability. It is available for free download. The NFC Reader Library v5.02.00 currently supports: All our NFC frontends (CLRC663 plus PN5180) and PN7462 NFC controller. Their corresponding development boards, used as NXP reference HW (CLEV6630B, PNEV5180B, PNEV7662B) And built-in MCU support for LPC1769, LPC11U68, FRDM-K82F and Raspberry Pi. In addition, the release includes several examples to get familiar with the library and which can be used as reference for your developments and, it is also included an HTLM-based API documentation for all the components, which is generated from source-code annotations. NFC Reader Library architecture The NFC Reader Library is encapsulated into layers, differentiated by colors, and components, differentiated in boxes. From top to bottom, we have: The Application Layer (AL), which implements the command sets to interact with MIFARE cards and NFC tags. The NFC activity, which implements a configurable Discovery loop for the detection of contactless cards, NFC tags or other NFC devices. Next to it, the HCE and P2P components, for the emulation of Type 4 tags and P2P data exchange respectively. The protocol abstraction layer (PAL), which contains the RF protocol implementation of the ISO14443, Felica, vicinity and NFC standards. One level down, the hardware abstraction layer (HAL), which implements the drivers for controlling the NFC frontends RF interface and capabilities. Below, the Driver Abstraction Layer (DAL), newly introduced in the latest release, which implements the GPIO pinning, the timer configuration and the physical interface (BAL) between the host MCU and the reader IC. Finally, the OSAL module, in charge of abstracting the OS or RTOS specifics (handles tasks such as timers, events, semaphores and threads) This layered architecture is helpful for several reasons: The eleven software examples, the Application Layer (AL) and the Protocol Abstraction Layer (PAL) are HW-independent, so that can be used on top of any NFC frontend. The the Application Layer (AL), the Protocol Abstraction Layer (PAL) and the Hardware Abstraction Layer (HAL) are platform-independent, so that can run in any MCU without any additional change. In case the reader MCU is part of the built-in support, the examples can be directly imported and executed straight forward. On the other hand, in case the reader MCU is not supported by default, the major advantage is that only adaptations in the DAL and OSAL layers are required, while the rest of the layers can be used without any modification. The NFC Reader Library structure can be seen more clearly when imported in the MCUXpresso development environment. After completing the import wizard, all projects are listed in the “Project Explorer” window. As can be seen in the screenshot, it contains different folders: API documentation folder Driver Abstraction Layer FreeRTOS support The platform support (in the screenshot, corresponding to the LPC support) The software examples (11) The Reader Library implementation And the OS abstraction layer NFC Reader Library porting to FRDM-K64F steps In the existing NFC Reader Library v5.02.00 release there is no native support for Kinetis K64F. However, it is included a pre-compiled package for Kinetis K82F MCU. We use the K82F NFC Reader Library package as a reference project to start the porting to K64F MCU. This package can be downloaded from www.nxp.com/pages/:NFC-READER-LIBRARY. The steps required to port the library to Kinetis K64F are: Prearing the HW (i.e the pining between the Kinetis and the NFC reader board). Setting up the development environment (i.e workspace). Perfoming some changes in project configuration settings Performing some code modifications in the DAL and application code for adding Kinetis K64F support. NFC Reader Library porting to FRDM-K64F - Preparing the hardware The hardware used for this porting exercise is: A CLEV6630B board (CLRC663 plus) as an NFC transceiver  A FRDM-K64F board (Kinetis K64F) as host MCU, used to load and run the application logic. The CLRC663 plus evaluation board is connected by default to an LPC1769 µC via SPI. However, the board is made in such a way that the LPC1769 MCU can be bypassed to connect an external MCU easily. For doing so: Six resistors from the board need to be removed. These are highlighted in red. Use the SPI pin connectors available on the left hand side, on the board edge. Next, to connect the two boards together, the pining routing was done as follows: We use the Kinetis K64F jumper 2 pin line for the MOSI, MISO, chip select and clock lines of the SPI communication. The IRQ, interface selection and reset pins of CLRC663 plus are connected in jumper 1 pin line. And, one ground pin used for reference. Therefore no complex HW manipulation was required since all interfaces are easily accessible via dedicated headers or test points. NFC Reader Library porting to FRDM-K64F - Setting up the development environment Once the HW connection is prepared, we can move to setting up the development environment and workspace. Get the latest NFC Reader Library release From the software perspective, first we need to download the latest NFC Reader Library package. To do so: Go to NXP dot com slash pages slash NFC Reader Library (www.nxp.com/pages/:NFC-READER-LIBRARY) Go to the Downloads tab and click on the download button Click download on the NFC Reader Library for Kinetis K82Fpackage. Generate a downloadable SDK package for FRDM-K64F board As part of the NXP support, an SDK with drivers, middleware, RTOS demos and more is available for any of its Kinetis and LPC micros.We need to build the corresponding one to K64F SDK. For that: Navigate to www.mcuxpresso.nxp.com and select SDK builder option. Then, use the drop-down menus to customize your SDK configuration, middleware and optional software components be included in the package. Select Request build. In a few minutes, you will receive an email with a link to download the SDK package, very similar to the one showed in the figure below. Import the NFC Reader Library into MCUXpresso workspace Next step to configure the development environment is to import the library package in the workspace. The easiest way is to use the Quick Start Panel on the left hand side. Click on Import project from file system Then, browse the library package in your file system. Click Finish to import it all to your workspace. Install and link FRDM-K64F SDK into MCUXpresso workspace The last step is to import the K64F customized SDK we configured from the MCUXpresso tools. To do so: Just drag and drop the SDK into the installed SDKs tab of the MCUXpresso IDE. (It will appear in the bottom part, in the center) Import the SDK into the workspace and link it with the software examples. It will appear as another folder in the project explorer window. If the K64F SDK has been properly imported in the workspace, we should see a new drop-down menu for K64F. From there, we should select K64F and click Apply so that the memory details for K64F are set to the project example NFC Reader Library porting to FRDM-K64F - Project configuration changes At this point we have the hardware and the workspace for software development ready. In this step, we will start porting the NfcrdlibEx1_BasicDiscoveryLoop  software example provided as part of the NFC Reader Library release. Select FRDM-K64F SDK in the project MCU settings One of the first configurations to be changed is the project MCU settings. These settings indicate which target host device is running the application code. These settings can be found if: You right click on the project example > Properties In the left-hand list of the Properties window, open “C++ build” and select “MCU settings” In the right-hand panel, we can observe the corresponding settings for K82F micro. The left figure indicates the project configuration settings used by the default SW example prepared for K82F while the right figure indicates the final project configuration settings used by the SW example ported to K64F. Define FRDM-K64F SDK preprocessor symbols in the project After that, we need to change the compiler preprocessor settings, which can be found in C++Build > Settings. In the project examples of the NFC Reader Library, the conditional directives like #ifdef and #ifndef are used to include or exclude portions of the code from the actual compilation. The conditional codes are included in the program compilation only if the MACROs are defined in the project compiler preprocessor settings. In the left side we can see the defined macros for the original project. Among them, includes one which defines that the HW used is PN518 and K82F board. Therefore, in the ported project, we need to replace the macros corresponding to K82F with the new ones corresponding to K64F.  For instance, the PHDRIVER_K64_CLRC663 macro includes in the compilation the files related to the new HW used in the ported project (for the board pin and GPIO config, SPI settings or timers). Precisely, these files are included inside BoardSelection.h file in the Driver Abstraction Layer (DAL). Add include paths for FRDM-K64F SDK files When including header files into our project, the compiler must be told which directories must be searched to find those files. To do this: Open the project properties. In the left-hand list, open “C++ Build” and Select “Settings”. In the right-hand pane, choose the “Includes” section. Click the “Add icon”. In the left figure, we see the compiler include paths for the K82F SDK of the original example. In the ported example, the K64F SDK sources will not yet compile since we did not tell the compiler about all the new include paths. Therefore, we need to add the new include paths pointing to the K64F SDK and put them into the MCUXpresso IDE project. In the right figure, you can see the paths we included for this purpose. Mainly, these paths reference to the board system init, board drivers, CMSIS files and debug utils. Add include path for FRDM-K64F MCU assembler The last MCUXpresso settings to be changed is in the MCU Assembler. This can be found in the right-hand panel, choose the “MCU Assembler” and select “General”. In the original source code, a path is used to the K82F SDK. In the ported example, we just need to remove the previous include path and replace it with the corresponding one pointing to the K64F SDK in our workspace. NFC Reader Library porting to FRDM-K64F - Code changes So far, we have the HW, the development environment prepared and the project configuration settings changed. At this point, there are only a few code changes to be done before the porting is completed and the software example can be run in K64F. DAL driver adaptation for FRDM-K64F The layered architecture of the NFC Reader Library makes porting easier since only the lower drivers need to be adapted. This driver includes functions for: The physical link connection establishment between the CLRC663 plus and K64F The init functions for timers and interrupts so they are correctly used by the application layer. Going to the NfcrdlibEx1-BasicDiscovery loop project structure, it contains several folders. If we open the DAL > board folder, we can observe one source file per each supported platform (LPC with PN5180 and CLRC663, and the same for Raspberry Pi and Kinetis K82F). Our task for the porting would be to create an equivalent source file for the new supported board, the K64F together with the CLRC663 (e.g. Board_FRDM_K64FRc663.h). This file includes The related board pin and GPIO configurations The SPI configuration The timer configuration In addition, we need to include the board, pin_mux and clock config files. Use SDK examples to get FRDM-K64F board specific configuration Implementing these board specific files, in some cases, could be time consuming and may require experience. However, you do not need to do so but rather use the existing source files. For that, you can use any of the existing SDK software examples. You can easily import one SDK example by: Clicking the “Import SDK” example in the quick start menu > select the FRDM-K64F board. Selecting the demo example. Each example application has its own unique copy of the board, pin mux, and clock config files that you can reuse for the porting (Note: this process could be different depending on the MCU used). Add FRDM-K64F macro definitions in the source code Next, along the project tree, we need to add the #ifdef directives, indicating that K64F board files that need to be compiled. This is the case for: The BoardSelection.h file The ph_NxpBuild_App.h, which links the board with the reader IC by enabling the CLRC663 plus module in the HAL layer. The ph_AppInit.h so that the board is initialized when the reader device boots. Add FRDM-K64F CPU initialization code The ph_AppInit.h  file takes care of the code initialization and code specific to the HW used to run the example. As part of this ph_AppInit.h file, there is a function in charge of initialization the host MCU. Here, we need to implement the corresponding function for the K64F init, based on the SDK example source code selected earlier. If we look within this routine, we actually find functions for: Configuring the MCU clocks. Configuring the MCU pins. Configuring the interrupts (PIT). NFC Reader Library porting to FRDM-K64F: NfcrdlibEx1_BasicDiscoveryLoop execution After following the previous steps, the source code is succesfully ported to K64F. The following video demonstrates the correct execution of the NfcrdlibEx1_BasicDiscoveryLoop example in FRDM-K64F host MCU connected to CLRC663 plus NFC frontend (CLEV6630B). The video includes a webcam, which records the HW, including all the witing wiring between the K64F and the CLRC663 plus antenna. After the code is built and compiled, the video shows how some tags are tapped to validate that the example is working as expected (tag's UIDs are displayed in the MCUXpresso console). . General considerations to port the NFC Reader Library to your target MCU Overall, the general steps required to port the NFC Reader Library to your target MCU are: Adapt the MCU drivers to the DAL layer in the NFC Reader Library. This typically includes: timers, interrupts, pining and host interface configuration between the NFC reader and host MCU sides. Adapt the OS layer (i.e. you might need to port the FreeRTOS or to your target OS platform). Adapt the source code examples: project settings (macros, include paths, MCU configuration) and perform the required code modifications (Code for HW initialization, board files, etc). Available resources NFC Reader Library:  www.nxp.com/pages/:NFC-READER-LIBRARY CLRC663 plus: www.nxp.com/products/:CLRC66303HN CLRC663 plus development kit: www.nxp.com/demoboard/OM26630 FRDM-K64F board: www.nxp.com/demoboard/FRDM-K64F Video recorded session

What’s it like to sit in a state-of-the art eCockpit? Put on a virtual reality headset and find out! Here, the virtual world meets the real world as live video content from 4 displays -- a HUD, cluster, infotainment and rear seat entertainment systems – is processed and streamed realtime from a single i.MX 8 applications processor.  i.MX 8 series will transform interactions in ways you’ve never imagined   NXP product recommended i.MX 8 ARMCortex-A53 Processor|NXP 

Demo This development board for RF power products is now available from Richardson, one of NXPs distributors Demo / product features This next generation board provides RF design engineers with best efficiency, a range of frequencies and voltage. Richardson has a combined depth of real-world RF technical experience and a solid partnership with NXP that enables us to serve the unique needs of the RF design engineer. Richardson and NXP serve customers across a similar set of vertical markets, including aerospace and defense, military, wireless infrastructure, mobile, broadcast and ISM. Links RF | NXP Richardson RFPD - NXP Semiconductors

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 

The quadcopter drone is a very popular design for an unmanned aerial vehicle (UAV). It consists of a flight controller and four electronic speed controllers (ESCs), one for each motor. The flight controller is equipped with a radio to receive flight commands provided by the pilot and the inertial measurement unit (IMU). The IMU provides information (such as velocity and orientation) that are necessary for autonomous stabilization of the vehicle, using the internal accelerometer, gyroscope, and sometimes the magnetometer and GPS receiver.   Resources Quadcopter Drone Reference Design   Drone Examples - powered by NXP 3DR Drone Spiri Programmable Flying Robot  DJI Phantom 3 Advanced

Demo Features: Based on latest SOM Colibri i.MX7D 512 MB from Toradex Heterogeneous architecture: Qt on top of Linux on ARM® Cortex®-A7 core Realtime control loop on FreeRTOS on ARM® Cortex®–M4  Balancing control loop and mechanics by Antmicro  Face emotions using Qt 5.6 beta done by The Qt Company ______________________________________________________________________________________________________________________ NXP Featured Products: NXP i.MX 7 - Computer | System on Modules ______________________________________________________________________________________________________________________ C78

The purpose of this project is the control of a RGB LED panel using the FlexIO peripheral included in the Kinetis K82 microcontroller. The FlexIO peripheral offers a great advantage, unloading the CPU in the process of refreshing the LED color and brightness information, comparing with other control methods using GPIO bit-banging or PWM + DMA. I will use different method. The panel will use LED stripes with the WS2812B controller. We will also have a simulation platform for developing the applications. Hardware: 30 x16 LED WS2812B Panel Multiplexer board FRDM-K82 Uctronics QVGA display Software: IAR Workbench 7.50.1 SDK 1.3 for the Kinetis K82 FreeRTOS eGUI graphic library You can watch the video with the LED panel working: Video Link : 4707 Part 1: Building the LED Panel Part 2: LED control method using the FlexIO Part 3: Software for LED Panel emulation Part 4: Software for panel control

LPC54114 Audio and Voice Recognition Kit The LPC54114 Audio and Voice Recognition Kit provides a complete hardware and software platform for developers to evaluate and prototype with the LPC54114 processor family. It has been developed by NXP® to provide all that you need to develop an always-on low power voice triggering product. Features: LPCXpresso54114 (OM13089) development board with: LPC54114 dual-core (M4F and dual M0) MCU running at up to 100 MHz in LQFP64 package. Hi-speed USB based debug probe with CMSIS-DAP and SEGGER J-Link OB protocol options. Connectivity for external debug probes. Micro USB connector for LPC54114 USB device operation. Tri-color LED. Target Reset, ISP and interrupt/user buttons. On-board 1.8 V / 3.3 V or external power supply options. 8 Mb Macronix MX25R SPI flash. FTDI UART connector and built-in UART to USB bridge options. Built-in MCU power consumption and supply voltage measurement for LPC54114 device. UART, I²C and SPI port bridging from LPC54114 target to USB via Link2 device. FTDI UART connector. Digital Mic/Audio codec/OLED display (“MAO”) shield with: Knowles SPH0641LM4H digital microphone. Cirrus Logic (Wolfson) WM8904 audio codec with stereo line in/out sockets. Monochrome OLED display (160 x160 pixels). Demos: Include USB/I2S audio demo, as well as voice recognition demos leveraging partner technology (Malaspina and Sensory) http://cache.nxp.com/documents/application_note/AN11855.zip Videos: These videos showcase the NXP’s LPC54114 MCU in a kit designed for customers to evaluate its capabilities for audio and voice processing _______________________________________________________________________________________________________ Featured NXP Products: Product Link LPC54000 Series LPC54000|Power Efficient 32-bit Microcontrollers (MCUs)|Cortex®-M4 Core | NXP  LPC54114 Audio and Voice Recognition Kit https://www.nxp.com/design/microcontrollers-developer-resources/lpcxpresso-boards/lpc54114-audio-and-voice-recognition-kit:OM13090?&fsrch=1&sr=1&pageNum=1 _______________________________________________________________________________________________________

Wind River's Ka Kay Achacoso demonstrates VxWorks 7 with graphics on the i.MX6 series applications processor. Features Demonstration of Graphics using VXWorks 7 The drivers are taking advantage of the i.MX processor's GPU to render hardware accelerated 3D graphics Using the accelerometer to show the orientation of the board The display shows a 3D view of how the board is being positioned taking into consideration perspectives and lighting shadows Featured NXP Products ARM® Cortex®-A9 Cores: i.MX 6 Series Multicore Processors Links NXP Connect - Wind River

Demo NXP, the number one supplier of high power RF power transistors, has a new 5G cellular base station concept alongside many other innovative cellular infrastructure solutions and technologies that is being shown at industry events. Product innovations from NXP are in the areas of 5G, from Gigabit LTE leading up to 5G using GaN and silicon LDMOS for macro and small cell base stations. Learn more about the steps that NXP is taking toward enabling the 5G wave Features Smaller footprint to reduce installation costs Network infrastructure evolution Active antenna rise Power consumption Multiple standards to support with 3G, 4G to 5G Link  5G Infrastructure|NXP 

Demo Owner Mike Stanley     Features Measuring the output from sensors, then computing the orientation of the device with the KL25 Kinetis Microcontrollers using advanced filtering techniques such as: Kalman filtering, Indirect Kalman filtering Built a representation of the current orientation of the device, linear acceleration Fusion software incorporated in standard OS systems Windows, iOS, Android Software library, visualization tools and full development suite are available for customers Featured NXP Products FXOS8700CQ (6- Axis Accelerometer + Magnetometer) FXAS21002 (3-Axis Gyroscope) Development Hardware Used FRDM- KL25Zhttps://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fwww.nxp.com%2Fproducts%2Fsoftware-and-tools%2Fhardware-development-tools%2Ffreedom-development-boards%2Ffreedom-development-platform-for-kinetis-kl14-kl15-kl24-kl25-mcus%3AFRDM-KL25Z FRDM-FXS-MULTI Design Resources Sensor Fusion Library for Kinetis MCUs Sensor Fusion Toolbox for Android Sensor Fusion Toolbox for Windows Training Hands on Workshop: Sensor Fusion Library for Kinetis MCUs Links Sensor Fusion NXP Community: Sensors Best of Sensors Expo (2014 Sensor's Expo)  

Classic board games with a touch of magic. NFC adds extra functionality to familiar fun. Interact more intuitively, speed up gameplay, and easily pick up where you left off. Experience board game immersions like you never have before. NFC helps bringing the 2-D board game experience to life. Players move their NFC-equipped pieces across the board as usual, but they can now be electronically tracked. The game processor uses this tracking data - coupled with information about the piece itself that can also be stored in the tag, creating an exciting gaming environment that's alive with action. It also enables new gameplay dimensions like on-line and interactive play scenarios.   Features enabled by NXP •Detection of up to 40 RFID Objects on large surface powered by single RFID reader •Direction detection of the game pieces •Connectivity to host system via USB or BLE   Recommended Products SLRC 610 – High perfromance RFIDreader Icode SLIx – Ultra low power RFID tag LPC11uxx – Microcontroler with embeded FS USB 74HCxxx – Ultra thin Analog Switches   Resources More information about NFC gaming: http://www.nxp.com/solutions/portable-wearable/gaming.html

Demo Ricardo Anguiano describes a memory game demo built by Mentor Graphics for their Embedded Systems Division's 20th Anniversary. The game uses 36 FRDM-K64F boards with Adafruit 2.8" capacitive touchscreens in a 6 x 6 grid. The FRDM-K64F boards run the Nucleus RTOS from Mentor Graphics. The FRDM-K64F boards are connected over Ethernet to a touchscreen-driven Boundary Devices BD-SL-i.MX6 (formerly the SABRE Lite board) game controller which also runs the Nucleus RTOS. Players start the game by viewing and studying the position of all 36 digital cards, the cards are flipped and the player must touch matching pairs for points before time expires. The memory game generated lots of interest with players coming back multiple times. It was a great way to introduce the ARM TechCon crowd to the Nucleus RTOS, which enjoys wide success in a number of vertical markets and product categories like industrial, medical, IoT, wearables and automotive. The safety-certified version, Nucleus SafetyCert has been verified and documented to meet the certification requirements for device manufacturers developing safety related software for avionics requiring DO-178C Level A, industrial requiring IEC 61508 SIL 3, medical requiring IEC 62304 Class C, and automotive requiring ISO 26262 ASIL B. Features • A fun memory game built on Mentor Graphics' Nucleus RTOS, deployed on over 3 billion devices worldwide. • NXP FRDM-K64F and i.MX6 based hardware NXP products ARM Cortex-M4|Kinetis K64 120 MHz 32-bit MCUs i.MX6Q|i.MX 6Quad Processors|Quad Core Tools FRDM-K64F|Freedom Development Platform|Kinetis MCUs https://boundarydevices.com/product/sabre-lite-imx6-sbc/  Mentor Graphics Links https://www.mentor.com/embedded-software/nucleus/ https://www.mentor.com/embedded-software/nucleus/safety https://blogs.mentor.com/embedded/blog/2016/10/31/testing-your-memory-at-arm-techcon/ 

Demo See what FlexIO Does _______________________________________________________________________________________________________ KL28Z FlexIO Camera Demo FRDM-KL28Z board connects with a camera device module via FLexIO interface. The FlexIO peripheral emulates camera interface to capture raw image data. And the real-time images are displayed on a TFT LCD. Features: The FlexIO peripheral emulates camera interface. Captures 320x240 QVGA images via 8-bit width data bus. Displays real-time images on a TFT LCD. The sample rate is up to 15fps. _______________________________________________________________________________________________________ KL28Z FlexIO LCD Demo TWR-KL28Z board drives a TFT LCD panel via FlexIO emulated 8080 interface. Features: The FlexIO peripheral emulates 8080 parallel interface with full writing and reading functions. Drives a 320x240 resolution TFT LCD via the interface. Bus width could be 8 bits or 16 bits. The refresh rate is up to 128 fps with 16-bit width data bus and 48MHz core clock. Featured NXP Products: Flex Your Mind with Kinetis FlexIO projects - Hackster.io ARM Cortex-M4 Cores|Kinetis K8x MCUs|NXP K8X Freedom Development Platform|NXP  QRDEMOUG.pdf _______________________________________________________________________________________ USB Video Camera This demo shows how the FRDM-K82F board along with an OV7670 Camera module can be utilized to create a USB web camera application. The demo application software is delivered as part of the KSDK software enablement. The FS USB video class demonstration can deliver images to PCs or tablets. Demo / product features USB Video device class demonstration application included in Kinetis SDK Easy connection to PC or tablet  display and process video captured from the device     FlexIO camera driver utilized to interface to OV7670 camera module NXP Recommends http://www.nxp.com/products/microcontrollers-and-processors/arm-processors/kinetis-cortex-m-mcus/k-series/k8x-scalable-secure-mcus:K8X-SCALABLE-SECURE-MCU?cof=0&am=0 AN5275: Using FlexIO for parallel Camera Interfacehttp://cache.nxp.com/files/microcontrollers/doc/app_note/AN5275.pdf?fsrch=1&sr=1&pageNum=1 AN5280: Using Kinetis FlexIO to drive a Graphical LCD Training C25

Combining NXP's wireless MCU with NFC controller allows to build a BLE-NFC bridge. It allows demonstrating transmission of NFC data over BLE, acting then as a king of Magic NFC remote. This demonstrator is built assembling the OM5578: Development Kits for PN7150 Plug’n Play NFC Controller (OM5578/PN7150ARD version including Arduino compatible connectors). on top of the FRDM-KW41Z: Freedom Development Kit for Kinetis ® KW41Z/31Z/21Z MCUs (minimum version B1 since previous versions have a pin conflict on the Arduino connector) Alternatively the Rigado R41Z Eval Board can be used as replacement to the FRDM-KW41Z To complete the demonstration, an android phone is used as BLE counterpart. It shall run the modified version of Kinetis BLE Toolbox android application including the NFC demo part. This dedicated version of the Kinetis BLE Toolbox android application is available for download from the files attached to this document. Below is a video of the demo. As shown, it demonstrate capabilities to control the NFC discovery remotely (via BLE) from the phone. Then, if tapping a card on the bridge, the related information including the content is conveyed through BLE to the phone and get displayed by the app. Additionally, the app can configure a message to be shared whenever an NFC reader (e.g. NFC phone) tap the bridge. The K41Z firmware of this demo is built based on the wireless UART example from MCUXpresso Software Development Kit (SDK), and updated with the porting of the NXP-NCI MCUXpresso example. The complete MCUXpresso project is given in source code in the attached files. To replicate the demo, just import it in an MCUXpresso workspace by selecting "Existing Projects into Workspace", then browsing to the BLE-NFC_bridge_MCUXpressoProject.zip file. Select the frdmkw41z_BLE-NFC_bridge from the "Project Explorer" view, and click on the blue bug icon to build, flash and debug the program.

This demo shows how to load the different demo codes for the kit FRDM-K64 with FRDM-FXS-MULT2B boards, to access the different sensors included in the card and use it to create your own applications. This demo runs on a K64 freedom board and uses the MCUXpresso IDE, the FRDM-K64 with MULT2B SDK and a serial terminal, in this case TeraTerm. Video: Software Links: Driver FRDM-K64: http://developer.mbed.org/media/downloads/drivers/mbedWinSerial_16466.exe MCUXpresso (requires NXP account): https://www.nxp.com/design/software/development-software/mcuxpresso-software-and-tools/mcuxpresso-integrated-development-environment-ide:MCUXpresso-IDE SDK Builder (requires NXP account): https://mcuxpresso.nxp.com/en/select_config_tools_data TeraTerm: https://osdn.net/projects/ttssh2/releases/ NXP Product Link Freedom Development Platform for Kinetis® K64, K63, and K24 MCUs FRDM-K64F Platform|Freedom Development Board|Kinetis MCUs | NXP  Freedom Development Platform for NXP® Sensors with Bluetooth®. Freedom Development Platform Bluetooth® | NXP 

Description    NXP’s Personal Network Attached Storage (NAS) solution enables portable personal storage to be shared through an internal protocol (IP) or Wireless network allowing users to share photos, data, stream music or videos, backup and recovery of data over the local area network in a completely secure environment. In addition, the solution can support gateway features such as packet forwarding, cloud connectivity via Ethernet, Wi-Fi or LTE. This NAS solution offers significant advantages to consumer and SMB environments, including: Hardware-accelerated Raid for data parity and recovery, a reduced bill of materials (BOM) and ease-of-use associated with an IP network that most business and consumers already find familiar. Based on the QorIQ Layerscape LS1012A processor and the Network Attached Storage Application Solution Kit (ASK), the personal/consumer NAS solution offered by NXP allows developers to easily build storage applications leveraging the highly-optimized and feature rich ASK software stack along with the small form factor, low-power consumption and packet processing capabilities enabled by LS1012A processor. NXP provides an integrated platform solution (SW and HW) helping the customer to reduce his time to market, increase security and increase performance by leveraging the packet accelerators within the QorIQ® Layerscape LS1012A processor while delivering high NAS performance and IP forwarding applications with reduced load on the Arm® core. In addition, NXP LS1012ARDB supports a full set of popular interfaces such as SATA, USB 3.0, PCIe and 2.5/1Gigabit Ethernet for LAN and WAN, allowing customers and operators to securely connect storage devices with the cloud. Features Integrated Platform Solution Commercial Market Proven Software Solution Hardware Offloading Popular Connectivity Flexible and Optimized Software Architecture Use Cases Personal Storage Consumer Network Attached Storage (NAS) Consumer Direct Attached Storage (DAS) Battery Powered Portable NAS Wireless Personal Storage Media Gateway Chip on Drive Wi-Fi SSD and Small/Portable Drive Ethernet Drives Block Diagram Products Category Name MPU Product URL Layerscape LS1012A Communication Processor for the IoT | NXP  Product Description The QorIQ® LS1012A processor, optimized for battery-backed or USB-powered, space-constrained networking and IoT applications Category Name DC Regulator Product URL MC34VR500 | Multi-Output DC/DC Regulator | NXP  Product Description The NXP® MC34VR500 power management solution for network processor systems is a high-efficiency, quad buck regulator with up to 4.5 A output and five user-programmable LDOs. Tools Product URL QorIQ® LS1012A Development Board QorIQ® LS1012A Development Board | NXP  Layerscape FRWY-LS1012A board FRWY-LS1012A Development Platform | NXP 

Demo Kinetis KW4x MCU is an ultra low power, highly integrated single-chip device that enables Bluetooth low energy (BLE) connectivity for portable, extremely low-power embedded systems.     Features iBeacon Location-based Messages The KW4x is an ultra low power, highly integrated single-chip device that enables Bluetooth low energy (BLE) or IEEE Std. 802.15.4/ZigBee RF connectivity for portable, extremely low-power embedded systems. Applications include portable health care devices, wearable sports and fitness devices, AV remote controls, computer keyboards and mice, gaming controllers, access control, security systems, smart energy and home area networks.  The KW4x SoC integrates a radio transceiver operating in the 2.36GHz to 2.48GHz range supporting a range of FSK/GFSK and O-QPSK modulations, an ARM Cortex-M0+ CPU, 160KB Flash and 20KB SRAM, BLE Link Layer hardware, 802.15.4 packet processor hardware and peripherals optimized to meet the requirements of the target applications.  The KW4x’s radio frequency transceiver is compliant with Bluetooth version 4.1 for Low Energy (aka Bluetooth Smart), and the IEEE 802.15.4-2011 standard using O-QPSK in the 2.4 GHz ISM band and the IEEE 802.15.4j MBAN frequency range spanning from 2.36 GHz to 2.40 GHz. In addition, the KW4x allows the Bluetooth Low Energy protocol to be used in the MBAN frequency range for proprietary applications. Enabled by Kinetis KW4x MCUs Discover location-based context A Bluetooth® Smart low-power application   Bluetooth Smart and 802.15.4 Dual Mode Communication BLE heart rate sensor on a KW40Z connecting, pairing and exchanging data with an iPod while the 802.15.4 end device (on the same KW40Z chip) associates and exchanges data with a coordinator. The OTA packets are displayed in sniffer applications on a Windows PC.  The KW4x is an ultra low power, highly integrated single-chip device that enables Bluetooth low energy (BLE) or IEEE Std. 802.15.4/ZigBee RF connectivity for portable, extremely low-power embedded systems. Applications include portable health care devices, wearable sports and fitness devices, AV remote controls, computer keyboards and mice, gaming controllers, access control, security systems, smart energy and home area networks.  The KW4x SoC integrates a radio transceiver operating in the 2.36GHz to 2.48GHz range supporting a range of FSK/GFSK and O-QPSK modulations, an ARM Cortex-M0+ CPU, 160KB Flash and 20KB SRAM, BLE Link Layer hardware, 802.15.4 packet processor hardware and peripherals optimized to meet the requirements of the target applications.  The KW4x’s radio frequency transceiver is compliant with Bluetooth version 4.1 for Low Energy (aka Bluetooth Smart), and the IEEE 802.15.4-2011 standard using O-QPSK in the 2.4 GHz ISM band and the IEEE 802.15.4j MBAN frequency range spanning from 2.36 GHz to 2.40 GHz. In addition, the KW4x allows the Bluetooth Low Energy protocol to be used in the MBAN frequency range for proprietary applications. Concurrent communication on BLE and 802.15.4 Suited for configuring 802.15.4 devices from your smart phone Automatic synchronization completely transparent to the application   BLE-enabled Smart Zumo Robot The Smart Zumo Robot is powered by the new Kinetis KW40X MCU and is enabled by Bluetooth Low Energy (BLE) technology. Low-power, Bluetooth Low Energy (BLE) application Running simple control implementation over BLE to interact and control with the robot Highly-integrated radio solution with scalable memory options   Featured NXP Products   Product Link Bluetooth Low Energy/IEEE® 802.15.4 Packet Sniffer USB Dongle for Kinetis® KW40Z/30Z/20Z MCUs Bluetooth Low Energy/IEEE® 802.15.4 Packet Sniffer USB Dongle for Kinetis® KW40Z/30Z/20Z MCUs | NXP      Development Hardware Used   Freedom Development Platform for Kit Bluetooth Low Energy/IEEE® 802.15.4 Pack

Based on Continua Health Alliance standards for healthcare devices, a Kinetis MCU encapsulates the data using the IEEE® 11073 standard. In this example, a Freedom development platform operates as the near field communication board that bridges between the NFC antenna and the manager. Features Emulation of blood glucose module Low Power  technologies specific for healthcare NFC reading from blood glucose monitor Continua compliant demo (IEEE 11073) Featured NXP Products Product Link Kinetis® L Series Kinetis L Series Microcontrollers - Arm® Cortex™-M0+ Core | NXP  Freedom Development Platform for the Kinetis® KL05 and KL04 MCUs FRDM-KL05Z|Freedom Development Platform|Kinetis® MCU | NXP