PN5180 Quick Start Guide Datasheet by NXP USA Inc.

View All Related Products | Download PDF Datasheet
UM10954
PN5180 SW Quick start guide
Rev. 1.67 May 2018
345816
User manual
COMPANY PUBLIC
Document information
Info
Keywords
Abstract
Evaluation board, which are related to the installation of the SW sample
projects as well as the re-installation of the original LPC firmware to run
the NFC Cockpit. It describes the steps to be done to become acquainted
with the demo reader especially for SW development.
UM10954 hng://www.nxg.com .a 32
NXP Semiconductors
UM10954
PN5180 SW Quick start guide
UM10954
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2018. All rights reserved.
User manual
COMPANY PUBLIC
1.67 May 2018
345816
2 of 32
Contact information
For more information, please visit:
http://www.nxp.com
Revision history
Rev
Date
Description
1.6
20180507
Editorial updates
1.5
20170511
MCUXpresso IDE description added
1.4
20170117
Updated description how to flash FW for the NFC Cockpit tool.
1.3
20170105
Updated examples descriptions, reworked firmware update
1.2
20161124
Updated examples descriptions
1.1
20160803
Note in section 5 regarding the LPCXpresso version added
HCE, NFC Forum and MIFARE DESFire added to the Associated projects
Cockpit version changed from 2.2 to 2.3
Required LPCXpresso version changed from 7.9 to 8.1.4
RTOS options added
1.0
20151126
Initial version
UM10954 m 32
NXP Semiconductors
UM10954
PN5180 SW Quick start guide
UM10954
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2018. All rights reserved.
User manual
COMPANY PUBLIC
1.67 May 2018
345816
3 of 32
1. Introduction
This document is the continuation of the “AN11744 - PN5180 Quick start guide” and
describes the installation procedures of the SW development environment and handling
SW example projects using the NFC Reader Library prepared for the PN5180 evaluation
board.
It also describes how to re-install the original LPC firmware binary to use the NFC
Cockpit again.
In this document the term „MIFARE Classic card“ refers to a MIFARE Classic IC-based
contactless card, the term “MIFARE DESFire card” refers to a MIFARE DESFire IC-
based contactless card, the term “MIFARE Ultralight card” refers to a MIFARE Ultralight
IC-based contactless card.
Projects used and explained in this documentation are:
Table 1. Example projects
Example projects delivered with the NFC Reader Library
Example
Description
NfcrdlilbEx1_Basic
DiscoveryLoop
Explains how to poll for different technologies (Tag, P2P, HCE),
detect and report them. Default configuration parameters are used.
NfcrdlilbEx2_AdvancedDi
scoveryLoop
Explains how to poll for different technologies (Tag, P2P, HCE),
detect and report them. All configuration parameters are used and
explained.
NfcrdlilbEx3_
NFCForum
Explains how to configure the NFC Reader Library for different P2P
modes such as Active Mode, Target Mode, Initiator Mode and SNEP
Client/Server.
NfcrdlilbEx4_MIFARE
Classic
Explains the usage of MIFARE Classic card commands.
NfcrdlilbEx5_
ISO15693
Explains the usage of this technology and provides an overview
about the most common commands.
NfcrdlilbEx7_
EMVCo_Polling
Explains polling for EMVCo payment cards.
NfcrdlilbEx8_
HCE_T4T
Explains how to emulate a NFC Forum Type 4 Tag supporting read
and write operations.
NfcrdlilbEx9_
NTagI2C
Explains NTAG-I2C specific commands.
NfcrdlilbEx10_
MIFAREDESFire
Explains the usage of MIFARE DESFire cards. (This example is
delivered with the NFC Reader Library version available via NXP
DocStore)
NfcrdlibEx11_ISO10373_
PCD
Example is used to perform ISO 10373-6 PCD compliance
validation.
Nfcrdlib_SimplifiedAPI
EMVCo
EMVCo loopback application with simplified API, which can be used
for EMVCo level 1 digital certification.
Nfcrdlib_SimplifiedAPI
EMVCo_Analog
Application is used to perform EMVCo2.6(L1) Analog compliance
validation.
Nfcrdlib_SimplifiedAPI
ISO
Explains how to use simplified API with different types of cards.
UM10954 m 32
NXP Semiconductors
UM10954
PN5180 SW Quick start guide
UM10954
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2018. All rights reserved.
User manual
COMPANY PUBLIC
1.67 May 2018
345816
4 of 32
2. Managing the PN5180 SW projects with MCUXpresso IDE
The PN5180 SW projects are delivered in a zip package and can be extracted, edited,
compiled and linked with MCUXpresso IDE.
The MCUXpresso IDE is a low-cost highly integrated software development environment
for NXP's LPC microcontrollers and includes all the tools necessary to develop high-
quality software solutions in a timely and cost-effective fashion. MCUXpresso IDE is
based on Eclipse and has many enhancements to simplify development with NXP LPC
microcontrollers. It also features the industry-standard GNU tool chain, with a choice of a
proprietary optimized C library or the standard “Newlib” library. The MCUXpresso IDE
can build an executable of any size with full code optimization.
Designed for simplicity and ease of use, the MCUXpresso IDE provides software
engineers a quick and easy way to develop their applications.
This tool can freely be downloaded from the MCUXpresso website [1]. Before one can
download the software, it is necessary to create an account. Creating an account is free.
2.1 Development environment
To use PN5180 prepared software package all components listed in the Table 2 are
required.
Table 2. Development Environment
Item
Version
Description
PN5180EV5180B
1.0 or higher
PN5180 Customer Evaluation board (hardware)
LPC-Link 2
1.0
Standalone debug adaptor (hardware)
MCUXpresso IDE
10.0.0 or higher
Development IDE (PC software)
2.2 Installation procedure of the MCUXpresso IDE
The MCUXpresso IDE is installed into a single directory, of your choice. Unlike many
software packages, the MCUXpresso IDE does not install or use any keys in the
Windows Registry, or use or modify any environment variables (including PATH),
resulting in a very clean installation that does not interfere with anything else on your PC.
Should you wish to use the command-line tools, a command file is provided to set up the
path for the local command window.
Multiple versions can be installed simultaneously without any issues.
The installation starts after double-clicking the installer file.
UM10954 e .SmuprMGJXpmlDE E. \ E1 \ 22 mu: My Mum m Th5: mm are rammed when my the deb”! Woks land hem mmmmmmmmmmmurmm. m‘mmmmwmm,pzmu,msmxwug m uwmmmammmmuhlmm. 17‘ NXP mam mm; mm: m m mm mm, mm fl em;:v"m=‘mw"“m“~" .m “Mkmwmwwm WW m 32
NXP Semiconductors
UM10954
PN5180 SW Quick start guide
UM10954
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2018. All rights reserved.
User manual
COMPANY PUBLIC
1.67 May 2018
345816
5 of 32
Fig 1. Check box for NXP debug drivers
Make sure, the checkbox for installing the NXP debug drivers is activated.
During the installation, the user will be asked to install some required drivers. The
installation of these drivers shall be accepted.
Fig 2. Windows security dialog
After the setup wizard, has finished, the newly installed IDE can be launched.
UM10954 e comnldinn the HCllXaresso [DE smun Wizard W7“?2’"J"1"‘”“”‘fl": 3.32:”; 1. mm m unmmwmmm 1 ummwrm mnmn « Dummy.“ mmmmm v Mum...» WWW: mum". Mummy“ [TE m 32
NXP Semiconductors
UM10954
PN5180 SW Quick start guide
UM10954
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2018. All rights reserved.
User manual
COMPANY PUBLIC
1.67 May 2018
345816
6 of 32
Fig 3. MCUXpresso IDE
2.3 Importing provided SW example projects
The use of quick start panel provides rapid access to the most commonly used features
of the MCUXpresso IDE. Quickstart panel allows easy import projects, create new
projects, build and debug projects.
The sequence of installing the software projects is indicated:
Start the MCUXpresso IDE.
Open new or dedicated workspace
Select the option “Import project(s)” (see picture below).
Browse the zip archive.
MCUXpresso IDE unzips the software package.
The software package is ready for use.
UM10954 e Uchks v u g MCUXpressoiDE (Free Edition) . sun m. I New men I Import SDK examvveli). : lmpnrl Wm) hen Me my“ :‘3 (ma Senmgs >> Eund ail Wm u )lnpofl FM) mm file system. sum m mm»; armwe me m mm um»: (mm mm Mm (mm Wale "mm mm a 6":an 5.1m yum mam mam: av m mildew m m (m, D" II: mil m: wen we Dmiecuyau mm mm». mm yrs 4mm, PWilmmfimmopmam wag-q Barnum-Ive mm mm 3K7”: w m... prom 4mm [unmdrtdl m .1”:me am mom meow. 5m: mummm (can has: luvamaM mm m uvc Mm‘xamml‘ers Mcuxum m mm m: mum thgaxwhknun Ix Impound dummy vy premng m: Mm bum-m mm: PmJKt mm up) mm above, and rumgilm m m. hawks/Woven «mm Mummy, p15 0.. mm Debut m am m. mm webs“! in! ms. mum RM women lax-11mm: mm m 32
NXP Semiconductors
UM10954
PN5180 SW Quick start guide
UM10954
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2018. All rights reserved.
User manual
COMPANY PUBLIC
1.67 May 2018
345816
7 of 32
Fig 4. Importing project (1)
In the Quickstart panel on the left-hand side, choose “Import projects(s)”.
Fig 5. Importing project (2)
Browse the desired package and click “Next”.
UM10954 e .hwmmrxymmmam, memmwflm . B WNW..MWmam A m, NW A SW. 1 mm , mwmw ‘_1W J'Ip: mmm‘mm nsénp‘ wnmpwwpvzsm nag/3 Miran \ v m..M..Wm WWW,” 4mmmmmuwww.mmmw V WWW”. w ‘ m- [flow .6 32
NXP Semiconductors
UM10954
PN5180 SW Quick start guide
UM10954
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2018. All rights reserved.
User manual
COMPANY PUBLIC
1.67 May 2018
345816
8 of 32
Fig 6. Importing project (3)
For a working demo project, you need to import at least four sub projects. One example
project, the NFC Reader Library, FreeRTOS, one chip library and one board library.
When the import process has finished one can start browsing the code.
2.4 Building projects
Building projects in a workspace is a simple case of using the Quickstart Panel - ‘Build all
projects’. Alternatively, a single project can be selected in the “Project Explorer View” and
built separately. Note that building a single project may also trigger a build of any
associated library projects.
The project can be built as shown in the Fig 7.
UM10954 [E Projed Explmel :3 E" Periphecalu llll Regina's E Symbol Vie l» E ApiDatumemallon l» B DAL l 9 FleeR'lOS l is lp¢_noam_nxp,lpcxplesso_17s9 l. E lpc,cnlp,175x,6x ,SanlmedAPLEMVCn New > 60 [me Open in New Window l BNkmlihE D Copy CM+C l B NlcrdlihE Vasle CIlI¢V X Delele Delete Source » Move Rename. F2 m Import. m Expon. Build Plojm Clean Project Relresn F5 1% Pulled Explorer :3 g. Petiphevalso llll Regimrs lESyrnbol , a FleeRTOS , alpc,mard,nxp,lpcxpresso,1769 » a Ipc_cmp_175x_6x » a Nfcldllb_SlmplifiedAPLEMVCa , B NkldlibESimplifiedAPLEMVCaiAnalog , B Nlcmlibjmplil mpuso A 6 NfudllexLBasIchscoveryLoop . u' Binaries l> aw Nkmlleleasichscovelytoop.axf - [arm/la] , @ IMlndes . a DAL ~ 6 DebugLPC1769 m 32
NXP Semiconductors
UM10954
PN5180 SW Quick start guide
UM10954
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2018. All rights reserved.
User manual
COMPANY PUBLIC
1.67 May 2018
345816
9 of 32
Fig 7. Building the project
As a part of the build output, the binary for the “User Flash” file is created. This binary file
can be later also used to update LPC1769 Flash memory via USB mass storage
interface.
Fig 8. List of projects in “Project Explorer view
UM10954
NXP Semiconductors
UM10954
PN5180 SW Quick start guide
UM10954
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2018. All rights reserved.
User manual
COMPANY PUBLIC
1.67 May 2018
345816
10 of 32
The project settings, compiler and link flags can be changed in the project properties
dialog. To open the project properties dialog, select appropriate project in the “Project
Explorer View” and click “Edit ‘selected-project’ project settings”.
2.5 Running and debugging a project
This description shows how to run the “NfcrdlibEx1_basicDiscoveryLoop” example
application for the PN5180 evaluation development board. The same basic principles will
apply for all other examples. In cases where example will need additional configuration
this will be detailed described in the example description.
PN5180 evaluation board should be connected to the computer via LPC-Link 2, as
shown in Fig 9.
LP C-LINK2
S WD -c on ne ct or
Fig 9. PNEV5180B with LPC-Link 2
When debug is started, the program is automatically downloaded to the target and it´s
programmed to the LPC1769 flash memory; a default breakpoint is set on the first
instruction in main (), the application is started (by simulating a processor reset), and
code is executed until the default breakpoint is hit.
To start debugging your application on the PN5180, simply highlight the project in the
Project Explorer and then in the Quickstart Panel click Debug, as shown in Fig 10. The
MCUXpresso IDE will first build application, flash application binary and then will start
with debugging.
Before running the project, please ensure that the correct microcontroller and the correct
build configurations are chosen. Information about how to do this can be found in the Fig
23 and chapter 6.3.
UM10954 e mecmanvana r: «mommamm ‘ '/a’\amss - weak; E MCUXpresso lDE (Free Edltion) . scan hate I New ploject I Impan SDK example(s) .. S. Imfiun Urojectfi) fmm ME 516mm" ‘i Build 'NfcrdlIDBLstchlscm/eryloop' [DebugLPEUfiB] I (lean N(ch‘bmjasmmscomymop [chuglPC1769] at Debug NfcvdlwbEleastwscox/elymov [Debugwmeal umm gm Dumpmm Etumme ‘L mm.” [1 Manny ‘lnmmm 1m .LSWDnamcmmg nmmeML u r: DGE ,‘nt HI navnv (gillmmCame[mamlblxljnmmxuvemml , , , "mm mm mmnnmjnsmum—Mann“ Inunkinfl mm mm armrnanrreabi'nc runstdlib , mmm‘y rtzmn um 5m Ram Sm fig: usm mums mm a 511 u; um Kama; 35m 3 31 xx mm: awn: v n (.3 :2 a max mama mum: mm. mm]mmaamnnwmymp.axe Sn5\nxflnslflmcmrmswvxmzssuIDEJU.9.BJMVWkspacejlfliflwupgd‘ m. rrmrprimrdimzmry ”527mm Parfnrminx pnsbkwild my; irmrnuntrtabi Sim ‘McrdlibExLBasirDiscWWluuvvaxf' ; arrnwzreabirabiwvy 70 binary “McrdlibExLBasicDi um um hss an: m mg...“ mm x: 3m mm 1am: Inf:rvdliBExljasi:Diumwmnvraxf u 55 15 mum nmm (lack 235.9A2-s) m 32
NXP Semiconductors
UM10954
PN5180 SW Quick start guide
UM10954
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2018. All rights reserved.
User manual
COMPANY PUBLIC
1.67 May 2018
345816
11 of 32
Fig 10. Launch debug session
Fig 11. Successful compile
Select “LPC-Link 2” as a debug probe.
UM10954 e lummum \ .= /—\m r—m mm m .29.: mom 1 mm «mm mm m: pvabe m m Ava able aflached puns L mm: WWW» w wmm mg WW I LK mm 0495 mwsm Dzszllxw “an Wiemx Noanwp swam mm nun/um In mug/mm) IV mewmms mgr-«mm CMSIS mum-m \v m: Mam pm \v swan Hmk Dvnbu pm km Dmnns v Mums-w«mommummmm @ UK can Im..:..m3mmu,rummrmmmmwmwww.m‘wwww.mmr m. m M. mm" mm. W" a...” m Fromm mm mm ‘54.; «o~o~‘~m\w l.‘3-\\ @ . V m_-;n,«¢zja4.m¢ru <2“ka m="" ,="" n="" 4:="" 0mg="" »="" a="" n-="" u="" ,="" .="" .g="" mmmmmjmrmsumrvlm="" m="" mx="" m="" mama»="" .="" mm..-="" -="" 4="" a...“="" 1="" (finance!="" mm="" mm»="" .="" m="" "m="" a.="" www="" mwnan‘mn="" mw="" v="" e="" ”mm-mewh="" viwehmrv:="" a="" nkmuhnljacunwmwlvlunnt="" ._="n" ,="" mnflhbhljaurmmrymx'="" a:="" an="" ,="" a="" u="" -="" u="" an="" m="" n."="" mm;="" w="" [="" m="" m="" i="" mcuxprlm="" in!="" (r...="" w="" (="" 92="" mm»...="" m="" thfzubjutult="" dwsums.="" '="" lummm="" ‘="" v="" ‘="" .="" lxmummwum="" '="" w="" ‘="" ‘="" a="" ‘="" u="" u="" o="" _="" r="" ‘="" n="" 1="" “www,“w="" nlmluuh="" -="" x="" ).="" a.="" n="" .="" 5="" p="">< e="" -="" a="" -="" ‘="" m="" m="" md,="" wdww‘="" "mum;="" bus-(wawmupmbwmnsa="" mo="" ,="" mxx-="" swmmm="" mummmx="" mummiu="" mam="" ,="" m"="" mnmm'mmmm="" muxam“="" mmmnr="" mm="" rmsnle="" var="" mmmhm="" haurmvwrrvlorm="" npmrlwimu="" a="" in,“="" nkmh="" h="" mum”="" 1="" ww="" m="" m="" mm="" mm="" iv="" um="" mummu="" ,3“)="" al'mwuvv‘="" ‘="" ~="" .="" ‘="" m="" ‘="" ,="" .="" m="" '="" w="" w="" mimwmhbm="" hwy-«1.40m="" wm“="" 5mm="" 32="">
NXP Semiconductors
UM10954
PN5180 SW Quick start guide
UM10954
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2018. All rights reserved.
User manual
COMPANY PUBLIC
1.67 May 2018
345816
12 of 32
Fig 12. Select the launch configuration
After successful software upload, the execution of the project starts immediately, but
might halt at the initial breakpoint. To resume execution, click the resume button.
Fig 13. Debug project
UM10954 e m m K h-HoElCanmlE. “an. .mz» .m. ummmmmmmmmuguacnmMuwxmmmaum-ww Av ram:ummsxummmmww: [WUXDressa Semihnstinz mm console an Mnd]ihEyLflasicDiscweryLnop IkbugLPKNfiE named on pm 3331] K-sumscauvylnm 2mm» Card danced and activated sumssmly... Yzzhmlug m. A Cam- 1 um m 5; 56 m :1 29 pm sax . ma Wylie: Typ: 2 m '9)? .a 32
NXP Semiconductors
UM10954
PN5180 SW Quick start guide
UM10954
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2018. All rights reserved.
User manual
COMPANY PUBLIC
1.67 May 2018
345816
13 of 32
In the console window application debug outputs of the execution can be seen.
Fig 14. Application printouts in Console window
After the execution has reached the end of the main function please click the Terminate
button to stop the execution. Otherwise rerun of the project will be possible.
Buttons in the debug toolbar provide next functionalities:
Run the program.
Step over C/C++ line.
Step into a function.
Stop the debugger.
Pause execution of the running
program.
Instruction stepping mode
(disassembly).
Fig 15. Debug Buttons
3. Managing the PN5180 SW projects with Linux and Kinetis platform
Detailed description and guideline, how to import and manage NFC NXP Reader Library
projects for Linux and Kinetis platform, check:
- AN11802 - NFC Reader Library for Linux Installation Guidelines
- AN11908 - NFC Reader Library for FRDM-K82F Installation Guidelines
UM10954 //::define NXPBUILD_PHHAL_HW_RC553 m 32
NXP Semiconductors
UM10954
PN5180 SW Quick start guide
UM10954
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2018. All rights reserved.
User manual
COMPANY PUBLIC
1.67 May 2018
345816
14 of 32
4. Associated projects
All example projects are available for download at the PN5180 product page in the
documents section and are being distributed in one single file.
All projects are packaged into a single installer file. After downloading the zip file, extract
it and run the installer. The installer makes a copy of all documents and SW on the hard
disk.
By default, the projects are preconfigured to be run on the PNEV5180B development
board. This is defined by preprocessor directive PHDRIVER_LPC1769PN5180_BOARD
(properties-> settings->preprocessor) and by macro in “../intfs/ph_NxpBuild_App.h”.
//#define NXPBUILD__PHHAL_HW_RC663
#define NXPBUILD__PHHAL_HW_PN5180
Running the projects with, or without FreeRTOS
All projects described in the following sub chapters can be configured to run with or
without FreeRTOS operating system. To enable/disable FreeRTOS support, define
preprocessor directive (properties-> settings->preprocessor) PH_OSAL_FREERTOS or
PH_OSAL_NULLOS.
4.1 Example 1 Basic Discovery Loop
The Discovery Loop can be seen as the entry point when starting to communicate with
an NFC tag or device. It scans the close environment for tags and devices of different
technologies.
Example is implemented to work in POLL and LISTEN mode of the discovery loop.
Information (like UID, SAK, and product type of MIFARE IC) of the detected tags are
printed out and it also prints information when it gets activated as a target by an external
initiator/reader. Whenever multiple technologies are detected, example select first
detected technology and resolve it.
In passive poll mode, Low Power Card Detection (LPCD) is enabled.
UM10954 e Discovely Loop Poll Moth — Slate and Ennr (bdes mews mm_mn_mm mm_m_mmvm ran- a.- nacj-awjuui m m mun W4 lulu-aw): m m avg—zoo- u Jajl‘an 51m Yunnan" Damned mu,wwov,cuuna,~m,vou,smz . pmjsuoo vowsumumcnnu, amummumm.‘nw,m:_nscmon,mm_mm,vuu mmmcmmjmwmflugm . mamom,mu,u.u,canw,~m.um Nlln mam mar-d > 1 .hazmsdmannulmrdlhdlszloop, nag-4pc, ngmm; 5mm dam: Amvmd or Ermr means m_m»g_nsw;-fvmm m m”“m"“°o:%;mf§ fm" rau- can: may-annulu- m 32
NXP Semiconductors
UM10954
PN5180 SW Quick start guide
UM10954
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2018. All rights reserved.
User manual
COMPANY PUBLIC
1.67 May 2018
345816
15 of 32
Fig 16. Discovery Loop in Poll mode
The core function of this example is “BasicDiscoveryLoop_Demo()”, where initialization of
the NFC Reader library and polling for NFC technologies is implemented. After each
polling loop, application is checking polling result and printout information about the
detected tags or devices.
This example is using default DiscoveryLoop configuration, which enables all supported
technologies and it is limited to one device for each technology.
Table 3. Supported technologies
ISO14443P3A
ISO15693- SLI
FeliCa
TYPEF_TARGET_PASSIVE
ISO14443P4A
ISO18000P3M3
TYPEA_TARGET_PASSIVE
TYPEF_TARGET_ACTIVE
ISO18092MPI
ISO14443P3B
TYPEA_TARGET_ACTIVE
UM10954 m 32
NXP Semiconductors
UM10954
PN5180 SW Quick start guide
UM10954
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2018. All rights reserved.
User manual
COMPANY PUBLIC
1.67 May 2018
345816
16 of 32
4.2 Example 2 Advanced Discovery Loop
Additionally to Example 1 the Advanced Discovery Loop example explains the different
configuration options of the Discovery Loop and configure DiscoveryLoop with default
values based on the interested profile, NFC or EMVCo.
The configuration of the “DiscoveryLoop” is implemented in "LoadProfile()” function.
4.3 Example 3 NFC Forum
Explains how to configure the NFC Reader Library for different P2P modes such as
Active Mode, Target Mode, Initiator Mode and SNEP Client/Server.
In SNEP Server mode the example waits for a connection from a SNEP Client. When the
connection between client and server is establish, client send a data and server read it.
The application displays read data in the console window of the LPCXpresso IDE.
In SNEP Client mode, the application tries to connect to a SNEP Server. Once the
connection is established, it transmits an NDEF message to the server.
4.4 Example 4 MIFARE Classic card communication
This example demonstrates how to configure “DiscoveryLoop” to poll for only one
technology and how to resolve detected card, in this example MIFARE Classic is used.
Once MIFARE Classic card is activated, application printout information like UID, ATQA
and SAK and perform the authentication with MIFARE Classic card default key. After
successful authentication, basic read/write operations are implemented.
This example is good start in case of working with only one card or to see how to
manage MIFARE Classic cards.
4.5 Example 5 - ISO15693
Similar to the previous example, this one is also using only one technology, in that case
ISO15693. DiscoveryLoop” is configured to resolve only one device and in the example
it is shown how to change Tx Guard Time for T5T cards, this is implemented in
phApp_Init()” function.
Once ICODE SLI is resolved and activated, application printout card information like type
of the card and UID, and it will read and write from/to the memory block.
This example is good start in case of working with only one card or to see how to
manage ISO15693 type of the cards.
For a much more extensive example, demonstrating the use of ISO/IEC 15693 and
ISE/IEC 18000-3 Mode 3 tags (ICODE SLI and ICODE ILT). In order to assure ICODE
SLI and ILT detection please check HAL digital delay define settings as described in
chapter 4.
UM10954 www.nxg.com .a 32
NXP Semiconductors
UM10954
PN5180 SW Quick start guide
UM10954
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2018. All rights reserved.
User manual
COMPANY PUBLIC
1.67 May 2018
345816
17 of 32
4.6 Example 7 EMVCo Polling
The EMVCo Polling example it is demonstrated how to configure NFC Reader Library as
specified by EMVCo specifications and starts polling for EMVCo cards.
Once an EMVCo compatible card is resolved and activated, it demonstrates the
exchange of APDU commands. This example shall help the developers getting started
more quickly when working with EMVCo cards.
4.7 Example 8 HCE T4T
Example 8 implements a Type 4 Tag card emulation according to NFC Forum Type 4
Tag specification. The example supports all specified commands such as Select,
ReadBinary, UpdateBinary.
With this example our reader is in card emulation mode (HCE) and it support reading and
writing data. Default data is configured as an NDEF message as a url www.nxp.com.
The maximum NDEF length the reader can write is limited by NDEF file size used in
example (default configured as 1024 bytes).
4.8 Example 9 NTAG-I2C
The NTAG-I2C example demonstrates the use of special features which are supported
by NTAG-I2C. By using POLL mode of the discovery loop, example detect the NTag I2C
cards and displays detected tag information like UID, ATQA, SAK, Version info and
performPage Read and “PageWrite” commands.
For more details about the NTAG-I2C and its functionalities please consult the related
product page [2]
4.9 Example 10 MIFARE DESFire card communication
The MIFARE DESFire example demonstrates how to use MIFARE DESFire EV1 cards.
Once MIFARE DESFire card is resolved and activated, it displays MIFARE DESFire
applications created by this example previously and it displays 32bit signed integer which
is incremented after each successful detection of tag.
In case no application is present on the tag, new application will be created with two new
files to hold NXPNFCRDLIB version used to create this application and another file to
hold 32bit signed integer.
Note: This example including the required modules of the NFC Reader Library is only
available via NXP Docstore.
4.10 Example 11 ISO10373 PCD
This example is used to perform ISO 10373-6 PCD compliance validation. This example
has to be executed in the DUT which has an ISO 14443 based PCD implementation. The
ISO 10373-6 test methods verifies the compliance to the ISO 14443 protocols. An
UM10954 m 32
NXP Semiconductors
UM10954
PN5180 SW Quick start guide
UM10954
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2018. All rights reserved.
User manual
COMPANY PUBLIC
1.67 May 2018
345816
18 of 32
external tool like Micropross MP300 implements the test methods for the ISO 10373-6
and is used as the counterpart for this testing.
4.11 Simplified API EMVCo
This application will configure Reader Library as per EMVCo specification and start
EMVCo polling. This loop back application will send SELECT_PPSE command and is
used to test EMVCo.3.1a(L1) digital compliance. Simplified approach, after library
initialization, is using only three commands:
- phNfcLib_Activate()
- phNfcLib_Transmit()
- phNfcLib_Receive()
4.12 Simplified API EMVCo Analog
This example provides command line interface so user can choose one of three
operation modes as below.
- EMVCo LoopBack Application
- Trans send Type A application
- Trans send Type B application
Above Application modes are used to perform EMVCo2.6(L1) Analog compliance
validation.
4.13 Simplified API ISO
This example is a reference application to demonstrate the usage of Simplified API with
ISO profile. Application contains example of Type A Layer 4, Type B Layer 4,
ISO/IEC15693 and ISO/IEC180003m3 and MIFARE DESFire card, MIFARE Ultralight
card and MIFARE Classic card communication.
Example demonstrates how to use simplified API, which require, after successful library
initialization, only three commands:
- phNfcLib_Activate()
- phNfcLib_Transmit()
- phNfcLib_Receive()
UM10954
NXP Semiconductors
UM10954
PN5180 SW Quick start guide
UM10954
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2018. All rights reserved.
User manual
COMPANY PUBLIC
1.67 May 2018
345816
19 of 32
5. Flashing Firmware on the LPC1769
Flashing VCOM firmware is the procedure needed to prepare PN5180 evaluation board
to be used with the Cockpit tool. The Cockpit tool is software design tool for prototyping
NXP NFC card reader applications.
VCOM firmware which needs to be flashed on the LPC1769 is provided with the installer
package of the NXP NFC Cockpit application and it can be found in
“\NxpNfcCockpit_v3.10.0.0\firmware\Secondary_PN5180” folder.
This folder contains several binaries which can be used as VCOM firmware application:
• BootLoader_And_Nfcrdlib_SimplifiedAPI_EMVCo_Secondary.bin
• BootLoader_And_phRfOnOff_Secondary.bin
• BootLoader_And_phUcBal_Secondary.bin
Steps required to flash VCOM application:
Connect the LPC-LINK2 debugger to the PN5180 board as shown in the Fig 17.
LP C-LINK2
S WD -c on ne ct or
(1) Use an LPC-Link 2 debugger and make the connections with PN5180 board
Fig 17. LPC-Link 2 - PN5180 board connection
UM10954 e ‘I mkwgmnm , mm , Mt s.mp‘.nm,mm.wmmm , Mcuxwm m me mm "mm Search mm m mm; mm», Help .avw wvrsvgzalwvovmvmzu p.“ i , 33 u» an ‘. 1. ‘ ‘ .a ougaa Mmm a. g Pellpheval. Mister; bsymboWL. = El 4 WzlLum: E N L dh , ILBasLD “mm,“ E E@ « 37 ; :Qfifmemn I “mm“ m Mme, m ,_ E FveeRTCVS Program Flash using nus—um: cuss—n» V5.11: ‘ a 'Pehoa'dNPJWPW Program met um “>an mxp {Puma} % . a lympflsux / a McmllbjlmpllhchPLE Ions _ a urcmlm,s.mplmmng a" » B NtcrdllbjlmpllhedAPL E Dlsvlzv Dreams: ‘09 C Wu an comma-wr- / H NfcldllhExLBuxKDl J Repeaton complenon L Run'lasn mmmam and copy in cupboard ,- % NfcmllexLLlSOmSB, » E NtcrdllexLMvancedDI . B MkvdllexLNFCFumm Cannmlnn Options / fl Mcmllex‘LMlFARECIa - a NfcmlIbEXSJSOfifiQZ » B NkrdllexlEMVCoJ’ull Mdmum‘ “Pm“; / I3 NfcrdlIbExILHCLTM ,- % Nfcmllex‘JVNTangC » E urcmlmmujumzl . a WWW, — / 2 pm. mm mm. chnsusujlzm v Came. Jug mpyllash mmmand m (\Ipbuzrd L mm.“ znmmand heft": meaning J use ATM menace Lmiscrverwnnm scum v mouse. 1 nasn Dvmr 9392 flash memory 52m file C’\nxp\NXDNf(OxkaLV3 100.U\llrmward v mm. Base addrm 0m 7‘ Reset iavget an mmplznan base onions g MN erase 9‘ Base only Vulmred setters emu wQulds. 'Gmua m 32
NXP Semiconductors
UM10954
PN5180 SW Quick start guide
UM10954
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2018. All rights reserved.
User manual
COMPANY PUBLIC
1.67 May 2018
345816
20 of 32
Use the MCUXpresso Program Flash utility flash to flash bootloader binary to the MCU.
(2) Create (or Open an existing MCUXpresso project) and set the MCU type to LPC1769
(3) Chose “Program flash” from menu bar
(4) Select bootloader binary, e.g.
‘NxpNfcCockpit_v3.10.0.0\firmware\Secondary_PN5180\BootLoader_And_Nfcrdlib_SimplifiedAPI
_EMVCo_Secondary.bin’
(5) Set base address to 0x00
(6) Press “OK” button and flash the bootloader
Fig 18. Flashing Bootloader.bin
Flash the binary on the PNEV5180B and ensure that the process succeeds.
UM10954 e I Mcuxmm ll)! ms...“ nun nLemu,mmdlwk Mamba MT upwwfixmp‘m100mmmm:muna:rnys1manImmmkmlnjmpmumwkumawIm' IE! grrmnugzrmmmm mom um mm mommkdmmu mnausnmknanmwinsmsuum m- aw/wm w 015 WM 5599: m m mm: - w clam-q m dmr mmumm m- m. wm Dane m- Imflefl mam m m mm: humans/s} m um um (my OO .. « WWW“ » BMW m. m. m m m mm mm ; v o ‘ Unspec‘fied (D ‘ 4! 13 .wmm mm“ Hm. . 32
NXP Semiconductors
UM10954
PN5180 SW Quick start guide
UM10954
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2018. All rights reserved.
User manual
COMPANY PUBLIC
1.67 May 2018
345816
21 of 32
(7) Inspect program flash output
Fig 19. Flash report
Disconnect the USB cable, remove LPC-Link 2 connection and reset the board.
The board appears as a VCOM device:
Fig 20. PN5180 Board Correctly installed
The PN5180 based evaluation board is ready now to be used with the NXP NFC Cockpit
tool.
UM10954 m 32
NXP Semiconductors
UM10954
PN5180 SW Quick start guide
UM10954
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2018. All rights reserved.
User manual
COMPANY PUBLIC
1.67 May 2018
345816
22 of 32
6. Supplementary Notes
6.1 General Software Architecture
The software of the reference reader is based on the NFC Reader Library Fig 21. It
intends to be simple, modular, easily readable and quickly portable by all the customers.
This philosophy is reflected in its architecture which is divided into 4 layers:
BAL (Bus Abstraction Layer),
HAL (Hardware Abstraction Layer)
PAL (Protocol Abstraction Layer)
AL (Abstraction Layer)
Fig 21. Architecture of the NFC Reader Library
6.1.1 Bus abstraction layer
This layer offers functions to abstract the hardware parts of the LPC1XXX
microcontroller.
These functions use the specific libraries available for the LPC1XXX family
microcontroller. Based on these stacks, the communication routines for the relevant
physical media I2C/SPI can be easily designed. These drivers are specific for the
LPC1XXX family and therefore cannot be ported to other microcontrollers.
6.1.2 Hardware abstraction layer
This layer offers functions to abstract the hardware parts of the transceiver CLRC663.
6.1.3 Protocol abstraction layer
Every PAL function is a low-level function realizing a single functionality. It is
encapsulated in a module which is independent from the others. The user can easily
design his application by doing a drag-and-drop of the relevant module.
UM10954 m 32
NXP Semiconductors
UM10954
PN5180 SW Quick start guide
UM10954
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2018. All rights reserved.
User manual
COMPANY PUBLIC
1.67 May 2018
345816
23 of 32
The following PAL modules are available in this software package:
ISO/IEC 14443-3A,
ISO/IEC 14443-3B,
ISO/IEC 14443-4A/B,
MIFARE products
FeliCa
NFC Initiator
NFC Target
6.1.4 Application layer
Lying on the previous software layers, the application layer is on top of the reader
software package. It combines elements of the previous three parts into high level
functionalities.
6.2 Build configuration
All the projects mentioned in Chapter 0 are available in debug configuration. Additionally,
the Polling project comprises the release configuration.
Debug configuration
This configuration is mainly used when the target board is attached to the PC with
the JTAG debugger. It allows the display of debug messages in the console window,
which is useful in the early stage of the project.
Release configuration
Once the project is debugged and mature, it might be interesting to use the release
configuration, to use the hardware stand alone. No debug messages are displayed in
the console window.
The build configuration can be selected as follows:
Click on the project in the project window of the MCUXpresso IDE,
Right click of the mouse Select Build Configuration,
Set active DebugLPC1769 build (or ReleaseLPC1769 build) for LPC1769.
UM10954 e New an 1m Opcn In new Wmdow Capy hue Dem Smart: Mme Rename. mwm Boom mm quen clean Project Mm. Clme Pm‘m Close Unvelzmd moms 3qu Cunflgmalm Build Tzrgms lmex Run A: Debug As Pwme es cum rm‘v Dclclc r2 rs 44 45 This mample contains three mode nf Wzratians within itsE 46 (Imus: as balm. 4/ 42 LEM-K0 LDapBack Applinalion 49 59 2.1mm 32nd 1'qu A applitalion m > 52 3.1m": send Type a applitalion ‘n 54 Above Application modes are used to per-far. EM02.6(LJ) m a: validation. The (Pu heuuency mnneured for the Host (on' SD shuuld b2 sufficient ennflzh to leg! EMU lining rmuiramew :7 as no; Rastridinns nn llfzrdlih plifizflAPI EMn Analng (:2 , MFcr'dlibisilplifiedAPIifl'NcoiAnalaz is restricted (a he I 63 awards/Ks mantiuned in SEzlioanM. VA in m mg“ m .H a .r > Smklm > V chbuglPCUéS (DEM bmld lot [PC1769] , Mirage, 2R2Ius=lPCI769 (Release hmldlurLPCl‘lGS] , pm . raulur "x . . PM A" The default used mu type is lP(1769. whew > mean»: ' Bum Se‘ecmd , [<— wmsuu,="" the="" mu="" type="" has="" to="" be="" changed="" iw="" m="" 32="">
NXP Semiconductors
UM10954
PN5180 SW Quick start guide
UM10954
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2018. All rights reserved.
User manual
COMPANY PUBLIC
1.67 May 2018
345816
24 of 32
Fig 22. Select the build configuration
6.3 Setting the MCU
There are many LPC microcontrollers supported by the MCUXpresso IDE build in
compiler. Before compiling a project, the correct MCU need to be set.
Right click the project choose properties (at the bottom)
C/C++ build MCU settings expand desired LPC700 MCU group choose the
correct microcontroller click OK
UM10954 e \ we mler 1m \ Mcu mm: b v K, v v > Rescues Builder: I Ava Iahle parts . CICH Build Emld Vznables r snK MCU: Enmmmem Logging v Plelnsvalkd MCUs MCU mum MCUS from prelrlslalled LP( and gene": Corteer pan swoon mums NXP LPC1769 . Tool (ham Editor LPC1765 . qcu Geneval chuee > Code Analysis mm” Documentation ch1753 n" Types mums ”Wm“ » LPC177xjx "Km" » LPClExx 7 Language Mapplm m.“ and Symbol, 127991 zrchitaclura cmtewn} m 32
NXP Semiconductors
UM10954
PN5180 SW Quick start guide
UM10954
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2018. All rights reserved.
User manual
COMPANY PUBLIC
1.67 May 2018
345816
25 of 32
Fig 23. Selection of the LPC1769 MCU
UM10954 e I Propemes'ov Nfcvduh s mpll mnmjmvcunalog [M Settings : Resume: Bundec ‘ C/Co c Bulld Bum Vanab‘es . 5 mm ceampuey Environment a” mum mggmg w Preploml MCU semngs e lndudeg Semng: w owmaum Tool Chain mm: a” Debuggmg C/C+O General F Wammgs mm Mame: w Musccuam Run/Debug 5mm; w Amman": - s Mcu Asemblev 3 General w Avmvhsmlre :1 Heads: . 5 MC“ lmkev ‘u‘£\fil czvfivv a) TuoIScttmgs » amid new: 9 Build Amian Ia Emery Panels 0 ElmrP-ilsels ovumlmon chcl Mane 100) ' Omevoptlmlzauonllags inurcommon F Enab‘c Lmkrhmc ommuzallun Hm) nlllc chlcds rm Mo uneasy m 32
NXP Semiconductors
UM10954
PN5180 SW Quick start guide
UM10954
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2018. All rights reserved.
User manual
COMPANY PUBLIC
1.67 May 2018
345816
26 of 32
6.4 Level of compiler optimization
When the code size at the current compiler level overloads the FLASH size of the target
board (512K for the ARM-based microcontroller LPC1769), a higher compiler
optimization level can be selected to reduce the code size of the project.
The following steps can be followed to select a level of compiler optimization:
Click on the application project in the project window of the LPCXpresso IDE,
Right click of the mouse Select properties Select C/C++ build,
Select Settings Optimization,
Choose the desired level in the combo box.
Fig 24. Select the level of optimization
6.4.1 Optimization issues
When optimization is enabled, it will reorder code. What this means is that the code from
multiple C lines will be intermingled. In addition, assignments and initializations might be
pulled out of loops so they are only executed once. Changes like these will make the
code confusing to debug. Some symptoms one might see are breakpoints that only work
the first time through, or seeing the debugger’s current line indicator fail to advance or
even move backwards when clicking step. It is best to always use O0 for debugging.
6.5 Removing the initial breakpoint on debug startup
When the debugger starts, it automatically sets a breakpoint at the first statement in the
main()function. One can remove this breakpoint as follows:
1. Right click on the project and choose Launch Configurations Edit current…
UM10954 e Hm! ¢ has annual: X )YDDEY ' ’ \dCcnsoHMkvdln NMZaJuaghxk] ‘ ‘9'" ' "rlnrprintrfliramry pustrbuild cmvm » "an, pagan-u mp; WMWM_ unnaunne WMJMXEWCLM: hum».9un«.g....1m r » :m..m.. mm mm » i mm min » a Mama-H. 31.5) Yank » » Manny! 3y mucwuwu,‘ as Ddsnlme-fgntnn mum l Axum .mnugmgumm cm, manage, ma nm mnfigunflnns 15‘ :VE“F“‘>' ‘Iype «he. am 9 . mxp Semiwndumvs] Mm A delmExLBastwxavcryW [ mmummjasmmmmp u :.. an :.. mm. m Appllmllcn :.. Pusmwmgm mum. :.. Renate Appllmuun )5 Hardware Deb-499mg >5 PEMKm 1mm magma ya Senna [Menace nemaamg my. mama ‘ m \ » mm marmad n m 11 mm Mm: McIdlIbEK] kWCDMmWWDEb‘AQLPC1769 e um“: Cnmnnn it Debuggei .Iymm 35mm. mum mm Few: mm“ bleakpmm . Dengue: 0mm»: Igdmnflglmmn Mam Gnaaenuggcr avmrmntmbvgdb GDB command me: Mama Some mmam‘k m IDIS III: mzy mum mm "It :hflnv a: exampie nm 1 7 Norman mode (Mme “Emma: mm? GDH) [name Revem Debuggmg amanun um: Wave mam Debi v ® m 32
NXP Semiconductors
UM10954
PN5180 SW Quick start guide
UM10954
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2018. All rights reserved.
User manual
COMPANY PUBLIC
1.67 May 2018
345816
27 of 32
Fig 25. Edit Launch Configurations
Uncheck “Stop on startup at main” option.
Fig 26. Disable break point at main()
UM10954 hup://www.nxp.com/products/schwarerandriooIs/runrt‘wmersoflware/mcuxoressor softwarerandrtools:MCUXPRESSO hnD://www.nxD.com/products/ident‘wfication and securitv/nfc and reader ics/conne cted tag solutions/series/NT3H1101 NT3H1201.htm| www.nxg.cum www.nxg.ccm .a 32
NXP Semiconductors
UM10954
PN5180 SW Quick start guide
UM10954
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2018. All rights reserved.
User manual
COMPANY PUBLIC
1.67 May 2018
345816
28 of 32
7. References
[1] MCUXpresso download website
http://www.nxp.com/products/software-and-tools/run-time-software/mcuxpresso-
software-and-tools:MCUXPRESSO
[2] NTAG-I2C
http://www.nxp.com/products/identification_and_security/nfc_and_reader_ics/conne
cted_tag_solutions/series/NT3H1101_NT3H1201.html
[3] AN11744 PN5180 evaluation board quick start guide, www.nxp.com
[4] AN11742 PN5180 Dynamic Power Control, www.nxp.com
UM10954 m 32
NXP Semiconductors
UM10954
PN5180 SW Quick start guide
UM10954
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2018. All rights reserved.
User manual
COMPANY PUBLIC
1.67 May 2018
345816
29 of 32
8. Legal information
8.1 Definitions
DraftThe document is a draft version only. The content is still under
internal review and subject to formal approval, which may result in
modifications or additions. NXP Semiconductors does not give any
representations or warranties as to the accuracy or completeness of
information included herein and shall have no liability for the consequences
of use of such information.
8.2 Disclaimers
Limited warranty and liabilityInformation in this document is believed to
be accurate and reliable. However, NXP Semiconductors does not give any
representations or warranties, expressed or implied, as to the accuracy or
completeness of such information and shall have no liability for the
consequences of use of such information.
In no event shall NXP Semiconductors be liable for any indirect, incidental,
punitive, special or consequential damages (including - without limitation -
lost profits, lost savings, business interruption, costs related to the removal
or replacement of any products or rework charges) whether or not such
damages are based on tort (including negligence), warranty, breach of
contract or any other legal theory.
Notwithstanding any damages that customer might incur for any reason
whatsoever, NXP Semiconductors’ aggregate and cumulative liability
towards customer for the products described herein shall be limited in
accordance with the Terms and conditions of commercial sale of NXP
Semiconductors.
Right to make changesNXP Semiconductors reserves the right to make
changes to information published in this document, including without
limitation specifications and product descriptions, at any time and without
notice. This document supersedes and replaces all information supplied prior
to the publication hereof.
Suitability for useNXP Semiconductors products are not designed,
authorized or warranted to be suitable for use in life support, life-critical or
safety-critical systems or equipment, nor in applications where failure or
malfunction of an NXP Semiconductors product can reasonably be expected
to result in personal injury, death or severe property or environmental
damage. NXP Semiconductors accepts no liability for inclusion and/or use of
NXP Semiconductors products in such equipment or applications and
therefore such inclusion and/or use is at the customer’s own risk.
ApplicationsApplications that are described herein for any of these
products are for illustrative purposes only. NXP Semiconductors makes no
representation or warranty that such applications will be suitable for the
specified use without further testing or modification.
Customers are responsible for the design and operation of their applications
and products using NXP Semiconductors products, and NXP
Semiconductors accepts no liability for any assistance with applications or
customer product design. It is customer’s sole responsibility to determine
whether the NXP Semiconductors product is suitable and fit for the
customer’s applications and products planned, as well as for the planned
application and use of customer’s third party customer(s). Customers should
provide appropriate design and operating safeguards to minimize the risks
associated with their applications and products.
NXP Semiconductors does not accept any liability related to any default,
damage, costs or problem which is based on any weakness or default in the
customer’s applications or products, or the application or use by customer’s
third party customer(s). Customer is responsible for doing all necessary
testing for the customer’s applications and products using NXP
Semiconductors products in order to avoid a default of the applications and
the products or of the application or use by customer’s third party
customer(s). NXP does not accept any liability in this respect.
Export controlThis document as well as the item(s) described herein
may be subject to export control regulations. Export might require a prior
authorization from competent authorities.
Evaluation productsThis product is provided on an “as is” and “with all
faults” basis for evaluation purposes only. NXP Semiconductors, its affiliates
and their suppliers expressly disclaim all warranties, whether express,
implied or statutory, including but not limited to the implied warranties of non-
infringement, merchantability and fitness for a particular purpose. The entire
risk as to the quality, or arising out of the use or performance, of this product
remains with customer.
In no event shall NXP Semiconductors, its affiliates or their suppliers be
liable to customer for any special, indirect, consequential, punitive or
incidental damages (including without limitation damages for loss of
business, business interruption, loss of use, loss of data or information, and
the like) arising out the use of or inability to use the product, whether or not
based on tort (including negligence), strict liability, breach of contract, breach
of warranty or any other theory, even if advised of the possibility of such
damages.
Notwithstanding any damages that customer might incur for any reason
whatsoever (including without limitation, all damages referenced above and
all direct or general damages), the entire liability of NXP Semiconductors, its
affiliates and their suppliers and customer’s exclusive remedy for all of the
foregoing shall be limited to actual damages incurred by customer based on
reasonable reliance up to the greater of the amount actually paid by
customer for the product or five dollars (US$5.00). The foregoing limitations,
exclusions and disclaimers shall apply to the maximum extent permitted by
applicable law, even if any remedy fails of its essential purpose.
8.3 Licenses
Purchase of NXP ICs with NFC technology
Purchase of an NXP Semiconductors IC that complies with one of the Near
Field Communication (NFC) standards ISO/IEC 18092 and ISO/IEC 21481
does not convey an implied license under any patent right infringed by
implementation of any of those standards. Purchase of NXP
Semiconductors IC does not include a license to any NXP patent (or other
IP right) covering combinations of those products with other products,
whether hardware or software.
8.4 Trademarks
Notice: All referenced brands, product names, service names and
trademarks are property of their respective owners.
MIFARE is a trademark of NXP B.V.
MIFARE Classic is a trademark of NXP B.V.
MIFARE Ultralight is a trademark of NXP B.V.
DESFire is a trademark of NXP B.V
ICODE is a trademark of NXP B.V
Kinetis is a trademark of NXP B.V
UM10954 m 32
NXP Semiconductors
UM10954
PN5180 SW Quick start guide
UM10954
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2018. All rights reserved.
User manual
COMPANY PUBLIC
1.67 May 2018
345816
30 of 32
9. List of figures
Fig 1. Check box for NXP debug drivers ..................... 5
Fig 2. Windows security dialog ................................... 5
Fig 3. MCUXpresso IDE .............................................. 6
Fig 4. Importing project (1) .......................................... 7
Fig 5. Importing project (2) .......................................... 7
Fig 6. Importing project (3) .......................................... 8
Fig 7. Building the project ........................................... 9
Fig 8. List of projects in “Project Explorer view ........... 9
Fig 9. PNEV5180B with LPC-Link 2 .......................... 10
Fig 10. Launch debug session .................................... 11
Fig 11. Successful compile ......................................... 11
Fig 12. Select the launch configuration ....................... 12
Fig 13. Debug project .................................................. 12
Fig 14. Application printouts in Console window ......... 13
Fig 15. Debug Buttons ................................................ 13
Fig 16. Discovery Loop in Poll mode........................... 15
Fig 17. LPC-Link 2 - PN5180 board connection .......... 19
Fig 18. Flashing Bootloader.bin .................................. 20
Fig 19. Flash report ..................................................... 21
Fig 20. PN5180 Board Correctly installed ................... 21
Fig 21. Architecture of the NFC Reader Library .......... 22
Fig 22. Select the build configuration .......................... 24
Fig 23. Selection of the LPC1769 MCU ...................... 25
Fig 24. Select the level of optimization ........................ 26
Fig 25. Edit Launch Configurations ............................. 27
Fig 26. Disable break point at main() .......................... 27
UM10954 m 32
NXP Semiconductors
UM10954
PN5180 SW Quick start guide
UM10954
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2018. All rights reserved.
User manual
COMPANY PUBLIC
1.67 May 2018
345816
31 of 32
10. List of tables
Table 1. Example projects .............................................. 3
Table 2. Development Environment ................................ 4
Table 3. Supported technologies .................................. 15
UM10954
NXP Semiconductors
UM10954
PN5180 SW Quick start guide
Please be aware that important
notices concerning this document and the product(s)
described herein, have been included in the section 'Legal information'.
© NXP B.V. 2018. All rights reserved.
For more information, please visit:
http://www.nxp.com
For sales office addresses, please send an email to: salesaddresses@nxp.com
Date of release: 7 May 2018
345816
Document identifier:
UM10954
11. Contents
1. Introduction ......................................................... 3
2. Managing the PN5180 SW projects with
MCUXpresso IDE ................................................. 4
2.1 Development environment ................................. 4
2.2 Installation procedure of the MCUXpresso IDE .. 4
2.3 Importing provided SW example projects ........... 6
2.4 Building projects ................................................. 8
2.5 Running and debugging a project .................... 10
3. Managing the PN5180 SW projects with Linux
and Kinetis platform .......................................... 13
4. Associated projects .......................................... 14
4.1 Example 1 Basic Discovery Loop .................. 14
4.2 Example 2 Advanced Discovery Loop ........... 16
4.3 Example 3 NFC Forum.................................. 16
4.4 Example 4 MIFARE Classic card
communication ................................................. 16
4.5 Example 5 - ISO15693 ..................................... 16
4.6 Example 7 EMVCo Polling ............................ 17
4.7 Example 8 HCE T4T ..................................... 17
4.8 Example 9 NTAG-I2C ................................... 17
4.9 Example 10 MIFARE DESFire card
communication ................................................. 17
4.10 Example 11 ISO10373 PCD .......................... 17
4.11 Simplified API EMVCo ..................................... 18
4.12 Simplified API EMVCo Analog ......................... 18
4.13 Simplified API ISO ............................................ 18
5. Flashing Firmware on the LPC1769 ................. 19
6. Supplementary Notes ....................................... 22
6.1 General Software Architecture ......................... 22
6.1.1 Bus abstraction layer ........................................ 22
6.1.2 Hardware abstraction layer .............................. 22
6.1.3 Protocol abstraction layer ................................. 22
6.1.4 Application layer ............................................... 23
6.2 Build configuration ............................................ 23
6.3 Setting the MCU ............................................... 24
6.4 Level of compiler optimization .......................... 26
6.4.1 Optimization issues .......................................... 26
6.5 Removing the initial breakpoint on debug
startup ............................................................. 26
7. References ......................................................... 28
8. Legal information .............................................. 29
8.1 Definitions ......................................................... 29
8.2 Disclaimers ....................................................... 29
8.3 Licenses ........................................................... 29
8.4 Trademarks ...................................................... 29
9. List of figures ..................................................... 30
10. List of tables ...................................................... 31
11. Contents ............................................................. 32

Products related to this Datasheet

PN5180 NFC FRONTEND DEV KIT
PN5180 DEVELOPMENT BOARD