NXP Designs Knowledge Base

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

NXP Designs Knowledge Base

Discussions

Sort by:
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 
View full article
Demo Running NXP’s i.MX6SX application processor, Earthquake warning system proof of concept is able to warn citizen about Earthquake. Data are gathered from local sensor, remote sensors based on K64F NXP’s controllers and seismology servers from Internet. Features: Give citizens warning against Earthquakes Runs on the NXP i.MX6SX application processor with Linux® OS. Presents i.MX6SX asymmetrical architecture features, where data are measured locally by Cortex-M4 with FreeRTOS and displayed and presented by Cortex-A9 core with Linux® OS. Cortex-M4 can measure in real-time and monitor Linux part. Cortex-A9 can sleep to save power and be waked up by the quake detected by Cortex-M4. Communication between cores via RPMsg. Remote sensor’s accelerometer data are measured running K64F microcontrollers Seismology server’s data are displayed and analysed ___________________________________________________________________________________________________________________________ Featured NXP Products: Product Link Freedom Development Platform for Kinetis® K64, K63, and K24 MCUs FRDM-K64F Platform|Freedom Development Board|Kinetis MCUs | NXP  i.MX 6SoloX Processors - Heterogeneous Processing with Arm® Cortex®-A9 and Cortex-M4 cores i.MX 6SoloX Applications Processors | Arm® Cortex®-A9, Cortex-M4 | NXP  __________________________________________________________________________________________________________________________
View full article
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:
View full article
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
View full article
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
View full article
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 _______________________________________________________________________________________________________
View full article
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 
View full article
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
View full article
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 
View full article
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
View full article
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 
View full article
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
View full article
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
View full article
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 _______________________________________________________________________________________________________
View full article
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
View full article
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 
View full article
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)  
View full article
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
View full article
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/ 
View full article
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
View full article