Integrating NFC with the NXP PN7150

Table of contents

image

View the PN7150 Webinar Recording: Enhance your application with NFC thanks to NXP’s PN7150

 

 

{tabbedtable} Tab LabelTab Content
About

This roadtest will explore the NXP PN7150 High performance NFC controller with integrated firmware, supporting all NFC Forum modes. If you have NFC develiopment experience or are interested in learning more about developing NFC apps with the PN7150, please enroll in this roadtest.

 

About the PN7150

The high-performance full NFC solution PN7150 is a full NFC controller solution with integrated firmware and NCI interface designed for contactless

communication at 13.56 MHz. It is compatible with NFC forum requirements.

PN7150 is designed based on previous NXP NFC device generation. It

is the ideal solution for rapidly integrating NFC technology in any application, especially those running O/S environment like Linux and Android, reducing Bill of Material (BOM)

 

PN7150 Features

  • Full NFC forum compliance with small form factor antenna
  • Embedded NFC firmware providing all NFC protocols as pre-integrated feature
  • Direct connection to the main host or microcontroller, by I2C-bus physical and NCI protocol
  • Ultra-low power consumption in polling loop mode
  • Highly efficient integrated power management unit (PMU) allowing direct supply from a battery
  • PN7150 embeds a new generation RF contactless front-end supporting various transmission modes according to NFCIP-1 and NFCIP-2, ISO/IEC 14443, ISO/IEC 15693, MIFARE Classic IC-based card and FeliCa card specifications. It embeds an ARM Cortex-M0 microcontroller core loaded with the integrated firmware supporting the NCI 1.0 host communication. It also allows to provide a higher output power by supplying the transmitter output stage from 3.0 V to 4.75 V.
  • The contactless front-end design brings a major performance step-up with on one hand a higher sensitivity and on the other hand the capability to work in active load modulation communication enabling the support of small antenna form factor.
  • Supported transmission modes are listed in Figure 1. For contactless card functionality, the PN7150 can act autonomously if previously configured by the host in such a manner. PN7150 integrated firmware provides an easy integration and validation cycle as all the NFC real-time constraints, protocols and device discovery (polling loop) are being taken care internally. In few NCI commands, host SW can configure the PN7150 to notify for card or peer detection and start communicating with them.

 

Kit Contents

image

PN7150 NFC controller SBC Kit-Arduino Compatible

image

FRDM-KW41Z

 

Other Features

  • Includes NXP ISO/IEC14443-A and Innovatron ISO/IEC14443-B intellectual property licensing rights
  • ARM Cortex-M0 microcontroller core
  • Highly integrated demodulator and decoder
  • Buffered output drivers to connect an antenna with minimum number of external components
  • Integrated RF level detector
  • Integrated Polling Loop for automatic device discovery
  • RF protocols supported – NFCIP-1, NFCIP-2 protocol (see [8] and [11]) – ISO/IEC 14443A, ISO/IEC 14443B PICC, NFC Forum T4T modes via host interface (see [3]) – NFC Forum T3T via host interface – ISO/IEC 14443A, ISO/IEC 14443B PCD designed according to NFC Forum digital protocol T4T platform and ISO-DEP (see [1]) – FeliCa PCD mode – MIFARE Classic PCD encryption mechanism (MIFARE Classic 1K/4K) – NFC Forum tag 1 to 5 (MIFARE Ultralight, Jewel, Open FeliCa tag, MIFARE DESFire) (see [1]) – ISO/IEC 15693/ICODE VCD mode
  • Supported host interfaces – NCI protocol interface according to NFC Forum standardization
  • I 2C-bus High-speed mode
  • Integrated power management unit – Direct connection to a battery (2.3 V to 5.5 V voltage supply range) – Support different Hard Power-Down/Standby states activated by firmware – Autonomous mode when host is shut down
  • Automatic wake-up via RF field, internal timer and I2C-bus interface
  • Integrated non-volatile memory to store data and executable code for customization

 

Additional Information

PN7150 Manual

Important Dates

Enrollment Begin: Jan 25 2018

Enrollment Ends: Feb 25  2019

RoadTesters Selected: Feb 27 2019

Product Shipped: Feb 28 2019

RoadTesting Begins: Mar 7 2019

Reminder/Update Email: Apr 7 2019*

Submit Reviews By: May 7 2019*

*The element14 RoadTest Staff will send this reminder/update email.

**If a RoadTester is unable to meet the deadline, please notify the RoadTest Program Lead, , as soon as possible before the deadline.

RoadTesters

Terms and Conditions

RoadTest

NXP PN7150 NFC Controller Dev Kit

Terms and Conditions

These are the terms and conditions which govern the  NXP PN7150 NFC Controller Dev Kit contest. This Contest requires participants to submit an application indicating their previous experience with this type of equipment/component, information on what they would do to test the equipment/component, and the applicant’s desire to post a thorough review of their experience with images, photos, or other supplemental materials. Participants will be required to meet the Conditions for Participation.  The winners of this RoadTest will receive the item(s) listed below. RoadTest Reviews are due no later than 60 days after the receipt of the item(s). No other prizes are offered.

The Principal terms of the Competition:

The following words and phrases are used in these terms and conditions and have the meanings given to them below.

(RoadTest or Contest)

Key dates:

Applications Close: midnight (GMT) on Feb 25 2019

Announcement of Winner (estimated): Feb 28 2019

Prize:  NXP PN7150 NFC Controller Dev Kit

Additional Prizes: none

Competition Site: https://www.element14.com/community/groups/roadtest?ICID=menubar_resources_roadtest

Site or element14 Community: www.element14.com/community

Judges: members of the element14 community team chosen at the Organiser’s discretion.

Judging Criteria, All of the following which will have equal weighting:

· Demonstrated competence with the technologies including links or descriptions of past projects

· Qualifications as indicated by current job role and/or schooling/vocational training;

· A thorough description of how the prize would be tested;

· Likelihood that the Applicant will blog about the prize and provide a review on element14.com;

· Originality;

· Innovation.

Organiser: Premier Farnell plc (registered in England and Wales under company number 876412) whose registered office is at Farnell House, Forge Lane, Leeds, UK

Conditions for Qualification: in addition to meeting the requirements of these terms, all persons applying to take part in the Contest (each one an Applicant) must:

· Provide a RoadTest application describing what he/she would do if awarded the Prize including similar previous projects, product experience and qualifications

Terms: these terms and conditions which govern the Competition and to which the Organiser reserves the right to make changes from time to time and the latest version of these Terms from time to time will be posted to the Site.

  1. Eligibility
  2. Applications:
  3. Selecting Winners:
  4. Liability:
  5. General:

1.1 Save as set out in these Terms, the Contest is open to any natural or legal person, firm or company or group of natural persons or unincorporated body.

1.2 All Applicants must be aged at least 18 at the time of their application.

1.3 Applicants must not enter the RoadTest if doing so or taking part may:

1.3.1 cause the Organiser and/or themselves to be in breach of any agreement (including but not limited to any contract of employment) to which they are a party or in breach of any law, regulation or rule having the force of law to which the Organiser or the Applicant may be subject or any policy of the Organiser or the Sponsor;

1.3.2 Require the Organiser to obtain any licence, authorisation or permission to deal with the Applicant; or

1.3.3 Be in breach of any policy or practice of their employer. Some employers prohibit or restrict their employees from taking part in competitions such as these or receiving prizes under them and the Organiser respects those policies and practices.

The Organiser reserves the right to disqualify any Application made in breach of these Terms and to reject any Application which it reasonably believes may be or become in breach. The Organiser reserves the right to require evidence in such form as the Organiser may reasonably require of any Applicant’s compliance with any of these Terms and to disqualify any Applicant or Participant who cannot provide such evidence reasonably promptly.

1.4 Multiple applications are not permitted.

1.5 Applications may not be submitted by an agent whether acting on behalf of an undisclosed principal or otherwise.

1.6 The Contest is NOT open to:

1.6.1 Any person or entity who is a resident or national of any country which is subject to sanctions, embargoes or national trade restrictions of the United States of America, the European Union or the United Kingdom;

1.6.2 Any employee, director, member, shareholder (as appropriate) or any of their direct families (parents, siblings, spouse, partner, children) (“Direct Families”) of the Organiser and Sponsors; or

2.1 Each Applicant must fully complete and submit a RoadTest Application by the Application Close.

2.2 By submitting a Registration Form, each Applicant:

2.2.1 Authorises the Organiser to use his or her personal data (as defined in the Data Protection Act 1998) for the purposes of running and promoting the RoadTest;

2.2.2 Authorises the Organizer to copy, reproduce and publish their application should they be accepted as a Participant;

2.2.3 Will be deemed to have read, accepted and agree to be bound by these Terms. Applicants are advised to print and keep safe these Terms;

2.2.4 Authorises the Organiser to copy, reproduce and use the Application and/or Review for the purposes of the RoadTest and as otherwise contemplated by these Terms. The Organiser will not be responsible for any inaccuracy, error or omission contained in any reproduction or use of the Project Blogs.

2.2.5 Licenses the Organiser to use the intellectual property in the Project (IP) for the purposes of this Contest. As between the Applicant and the Organiser the IP remains owned by the Applicant.

2.2.6 Grants the Organiser the right to use his or her likeness, photographs, logos, trademarks, audio or video recordings without restriction for the purposes of Contest or the promotion of it or the Site;

2.2.7 Agrees to participate positively in all publicity surrounding the Contest;

2.2.8 Agrees to be responsible for all expenses and costs incurred by him or her in preparing for, entering and participating in the Contest (save for any expenses expressly agreed by the Organiser to be borne by it in these Terms);

2.2.9 Confirms that he or she owns all IP used in his or her application or Project or Blogs and indemnifies the Organiser from any claim by a third party that use of any material provided by an Applicant to the Organiser infringes the intellectual property rights of any third party;

2.2.10 Agrees not to act in any way or fail to act in any way or be associated with any cause or group which would have a negative impact on the reputation of the Organiser and/or the RoadTest.

2.3 All applications submitted to this RoadTest must meet the following criteria:

2.3.1 Applicants must be the author, creator and owner of the proposed review idea. Applicants must not submit someone else’s idea;

2.3.2 The proposed application must be reasonably achievable by the within the time constraints of the Contest;

2.3.3 Applications must not include or propose any of the following, the inclusion of which shall render any proposed application ineligible:

(a) Applications which relate to socially taboo topics, such as illicit drug use or sexual gratification;

(b) Applications that are or could reasonably be considered to be illegal, immoral, discriminatory or offensive as determined by the Organiser;

(c) Applications in relation to them which if accepted would infringe or breach any of the policies or terms of access or use of the Site.

2.4 No Application may contain any of the hazardous substances identified by Article 4 of Directive 2002/95/EC of the European Parliament on the Restrictions on the Use of Substances in Electronic and Electrical Equipment ("the Directive") or the use of such hazardous substances in the in any such Project must not exceed the maximum concentration values set out in the Directive.

3.1 Winners will be selected by the Organiser on the basis of the quality of his or her application and its adherence to these Terms.

3.2 The total number of Winners selected will be at least the minimum number set out above but the actual number is at the sole discretion of the Organizer and/or the Sponsor, if applicable.

3.3 The Organiser will use all reasonable efforts to announce the Winners via an update to the RoadTest page by the date listed above.

3.4 Winners agree to take part in all publicity which the Organiser or the Sponsor wishes to use to promote the RoadTest, the Products featured or other Contests with which the Organiser may be connected from time to time.

3.5 Details of the Winners may also be published in the media.

3.6 Winners are responsible for all applicable taxes, duties or other charges payable in relation to any prize.

3.7

4.1 The Organiser hereby excludes all and any Liability arising out of the Contest or the acceptance, use, quality, condition, suitability or performance of any Prize, even where that Liability may arise from the Organiser’s negligence.

4.2 Nothing in these Terms will affect any Liability of the Organiser for death or personal injury arising from its negligence, for breach of Part II of the Consumer Protection Act 1987 (in the event that any entrant is entitled to claim rights under the Consumer Protection Act 1987) or for any matter in relation to which it would be illegal for the Organiser to exclude or to attempt to exclude its Liability.

4.3 Subject to 4.2, neither the Organiser, any parent company nor any subsidiary of the Organiser or such parent company or any of their directors, officers and employees (together referred to in these terms and the ‘Associates’) makes any guarantee, warranty or representation of any kind, express or implied, with respect to this Competition or the Prizes potentially available under it. Neither the Organiser nor any of its Associates shall be responsible for any Liability that may arise out of or in connection with person’s participation in this Competition, the claiming, redemption or value of any prizes under it, the use or enjoyment of such prizes or any events or circumstances arising out of or in connection with any of them. Any implied warranties of condition, merchantability or suitability or fitness for purpose of any of them are hereby expressly excluded. Wherever used in these Terms, ‘Liability’ shall mean any and all costs, expenses, claims, damages, actions, proceedings, demands, losses and other liabilities (including legal fees and costs on a full indemnity basis) arising directly or indirectly out of or in connection with the matter concerned.

5.1 The RoadTest is organised and sponsored by the Organiser. The Organiser reserves the right to delegate all or any of its powers, rights and obligations arising in relation to the RoadTest to any Associate and certain such rights and powers are assumed by the Organiser on behalf of itself and each Associate. Reference to “Organiser” shall be deemed to include reference to each Associate.

5.2 The RoadTest may be terminated at any time if there are, in the sole opinion of the Organiser, an insufficient number of entries, or if the Applications are not of an appropriate standard for a competition of this nature. The Organiser has the right to cancel or suspend the RoadTest at any time due to circumstances outside its reasonable control.

5.3 The Organiser shall have the sole discretion to disqualify (without correspondence or right of appeal) any Applicant it considers to be adversely affecting the process or the operation of the RoadTest or to be in breach of these Terms or to be acting in a disruptive manner or with intent to annoy, abuse, threaten or harass any other Applicant or Participant.

5.4 The Organiser has the right to amend or add to these Terms from time to time. Revised Terms and Conditions will be posted on the Contest Site and it is a condition of entry to the RoadTest that Applicants agree to comply with these Terms and, if appropriate, such Terms as amended from time to time.

5.5 Headings are for convenience only and do not affect the interpretation or construction of these Terms and Conditions.

5.6 These Terms and the operation of the Contest shall be governed by and construed in accordance with English Law and any claim or matter arising under these Terms shall be subject to the exclusive jurisdiction of the English courts.

Comment List
Anonymous
  • I think that the B0 version on the box is a a red herring.   I think the board is a A3 based on the A3 sticker on the board itself.  So assume these boards are A3.  Clearly NXP needs to do a better job of describing what version a board is since it keeps changing the hardware.

     

    I have done much testing with the PTA0/PTA1 pins and have determined  that they CONFLICT with SWD .

  • I contacted NXP, seeking technical support.

     

    Randall

  • I've published my road test. Maybe that might help you get further with yours.

     

    For what it's worth, I found schematics for the B and C revisions of the KW41Z on the Tools tab on the NXP site. You'll find the older A revision schematic on the Getting started tab.

  • image

     

    I did a continuity test with a multimeter and J2[1] (which is the pin that is used by IRQ) is connected to J13 which is used by openSDA - I know as I cut the trace on J13 to see what happens and could not get connectivity when debugging. Similarly, J1[8] (used by VEN) is connected to J12/J14 etc.

     

    I also just spotted a tiny sticker on my board which says I actually have revision A2. This differs to the box which says revision B0.

     

    So I have an A board after all.

  • Well, I have to say it is rather odd that if they were hoping for us to showcase the FRDM-KW41Z as part of the PN7150 road test review then having the old incompatible version has not really helped at all. I think I will search again to see what sort of change notice NXP have for the new version as I must have missed it.

  • That's exactly the problem I have with my version A boards. Your version B boards should have different pins (PTB5 and PTC0 from memory) in those positions. The quick start guide still had the pinouts for the older version, but later schematics exist on the NXP site if you can find them. The documentation is a real mess!

     

    I'm away for the weekend so can't dig out the details right now. Maybe I should publish my draft road test so the info is out there for you and the other road testers.

  • I've been endeavouring to get to know the FRDM-KW41Z board via the MCUXpresso IDE and have encountered problems when using pins PTA0 and PTA1. It turns out that these pins are used by the MCUXpresso openSDA debugger. These two pins are also assigned to IRQ and VEN on the PN7150 Arduino shield. I believe the debugger clock line is then tied to the PN7150 reset (VEN) line. So in essence the shield is not compatible with the FRDM-KW41Z, as is, and thus requires the trace lines to be cut and manually rewired.

  • I never ever received the pop up when clicking on the blue debug button, but after much trial and error and a MCUXpresso reinstall I have just solved the problem.

     

    I had to do the following:

     

    The first thing I had to do was go to Windows menu, select preferences and the J-Link Options under MCUXpresso IDE category.

     

    Then for the J-Link Server executable I chose browse and selected the "JLinkRegistration.exe" file for the "J-Link Server executable" then "Apply and Close".

     

    Then when I choose DEBUG it throws up a SEGGER registration screen. I filled in the details etc. and sent these off.

     

    Now I return to Windows preference options and now choose the "JLinkGDBServerCL.exe" file and "Apply and Close"

     

    Now when I choose DEBUG it finds the serial number and I enter the debug session.

     

    Happier now...

  • I see I too have a version B0 and for some reason my MCUXpresso version doesn't like the OpenSDA driver as it keeps telling me it is incompatible with the 32bit MCUXpresso version I have installed. Anyway it's pulling me in the right direction learning the ins and outs of this IDE.

     

    Also, I found that the interface board has no pull-up resistors on the SDA and SCL lines and so if you are not planning to solder in pull-ups then you must ensure in the pin MUX config tool for the KW41Z that you have pull-ups enabled on these pins otherwise it will not communicate... not that I've got that far...

  • My investigation suggests just B is needed, but I can't be sure. My revision A boards are 2016.