topic Re: LPC55s28 PN5190 NFC Read Library porting in NFC

LPC55s28 PN5190 NFC Read Library porting

RadoslawTomasik — Thu, 22 Jan 2026 08:46:46 GMT

Hello Community,
hello NXP-Team

I'm looking for LPC55S28 ↔ PN5190 connection details (Host SW + DAL / BAL layer)

I already have the PN5190 NFC Reader Library and would like to connect the LPC55S28 MCU to the PN5190 NFC frontend.

I have reviewed the article “Using NFC Reader Library with LPC55S69”, but I am looking specifically for an LPC55S28‑compatible setup.

Questions

Is there an existing DAL/BAL (Driver Abstraction Layer) implementation for connecting the LPC55S28 to the PN5190?
Has anyone successfully connected LPC55xx (LPC55S16 / LPC55S28 / LPC55S69) to a PN5190 using the NFC Reader Library?
Is there a ready solution, reference project, or recommended starting point for the LPC55S28 + PN5190 combination?
If not, is the LPC55S69 guide the correct and closest reference to follow for porting?

Thank you!

Re: LPC55s28 PN5190 NFC Read Library porting

EduardoZamora — Thu, 22 Jan 2026 18:08:59 GMT

Hello @RadoslawTomasik

My apologies, there is no specific documentation or guide for PN5190 + LPC55S28.

However, as you mention, you can refer to the following guides:

- Using NFC Reader Library with LPC55S69

- NFC Reader Library Porting FRDM_K64F

- NFC Reader Library Porting to i.MX RT1050 - NXP Community

Those guides can be a good starting point.

Regards,
Eduardo.

Re: LPC55s28 PN5190 NFC Read Library porting

RadoslawTomasik — Fri, 23 Jan 2026 09:03:23 GMT

Hello @EduardoZamora,

Thank you for your response.

The guides you referenced are already much more helpful than what I initially found on the NXP website, so thank you for pointing them out.

While reviewing these guides, I noticed that many of them include preconfigured folders or ready-to-use packages for specific processors or boards. These packages typically integrate the NFC Reader Library together with the control processor setup and, in some cases, DiscoveryLoop examples, which makes it much easier to get started.

Would it be possible to provide a similar reference package or project (for example, importable into MCUXpresso) for the LPC55S28 + PN5190 combination, or at least for the closest supported LPC55xx configuration? Having such a project as a starting point would be extremely helpful for porting and validation.

Thank you in advance for your support.

Best regards,
Radoslaw Tomasik

Re: LPC55s28 PN5190 NFC Read Library porting

RadoslawTomasik — Fri, 23 Jan 2026 13:54:32 GMT

@EduardoZamora

When following the guide below:
https://community.nxp.com/t5/NFC-Knowledge-Base/NFC-Reader-Library-Porting-FRDM-K64F/ta-p/1117798

I am able to successfully perform the described steps:

Add the NFC Reader Libraries
Create a project for LPC55Sxx
Copy the DiscoveryLoop files into the LPC project

However, when performing the same steps for PN5190 (using NxpNfcRdLib_PN5190_v07.14.00_Pub), I am able to:

Add the libraries
Create the LPC55Sxx project

but when attempting to copy the DiscoveryLoop files, I encounter the following error:

Problem occurred while copying resources.
Cannot create linked resource.

Could you please check this on your side and let me know whether this is a known limitation, or if there is a recommended workaround for PN5190 with LPC55Sxx?

Thank you for your support.

Best regards,
Radoslaw Tomasik

Re: LPC55s28 PN5190 NFC Read Library porting

RadoslawTomasik — Fri, 23 Jan 2026 15:19:49 GMT

Hello @EduardoZamora ,

As a follow-up, I found that the original “Cannot create linked resource” error was caused by an excessively long file path. After shortening the path, this specific issue was resolved.

However, a related problem still persists when adding the NFC Reader Libraries to the workspace with the “Copy projects into workspace” option enabled (see attached screenshot).

Several documents (e.g. AN13425) explicitly recommend not selecting this option. When I follow this recommendation, copying the DiscoveryLoop files into the LPC55Sxx project works correctly.
The downside is that, in this case, linking the NFC Reader Libraries is no longer possible, because the workspace does not contain any NFC example projects.

As a result, it is not possible to link the following folders from NfcrdlibEx1_BasicDiscoveryLoop into the lpc55sxx_basic_discovery_loop project:

DAL
NxpNfcRdLib
phOsal
intfs

Could you please advise whether this is a known limitation for PN5190 with LPC55Sxx, or if there is a recommended workaround?
Also, is a preconfigured LPC55Sxx + PN5190 project available, similar to those referenced in other NFC Reader Library guides?

Best regards,
Radoslaw

Re: LPC55s28 PN5190 NFC Read Library porting

EduardoZamora — Fri, 23 Jan 2026 21:00:51 GMT

Hi,

Unfortunately, there is no reference project for this specific setup. The NFC Reader Library for PN5190 includes support for LPC1769 and Kinetis K82; support for any other Host MCU must be implemented by the user.

When you mention that linking the NFC Reader Libraries is no longer possible, does it mean that you are getting an error message when trying to link the folders? What is the procedure you are following? You should be able to link the folder by following the steps listed in NFC Reader Library Porting FRDM_K64F, "Link the NFC Reader Library" section. Also, linked resources should appear in Project Properties > Resource > Linked Resources.

Regards,
Eduardo.

Re: LPC55s28 PN5190 NFC Read Library porting

RadoslawTomasik — Mon, 26 Jan 2026 15:06:07 GMT

Hello @EduardoZamora ,

thank you for your reply and for the clarification.

I understand that there is no reference project for the LPC55S28 + PN5190 combination, and I am prepared to implement the SPI DAL myself. My intention is to follow the NFC Reader Library Porting FRDM_K64F procedure as closely as possible, but I am encountering some differences when working with the PN5190 package.

Here is the current status and the open questions:

Importing an LPC55S28 SDK example (e.g. hello_world) works without any issues.
Link the NFC Reader Library:
- The NxpNfcRdLib and phOsal folders can be linked to the LPC55S28 project and are visible under
  Project Properties → Resource → Linked Resources.
- However, these linked folders do not appear in the project structure as shown in the porting guide.
The DAL and intfs folders are part of the DiscoveryLoop example and cannot be linked independently.
- Should these folders be copied from the DiscoveryLoop project into the LPC55S28 project instead of being linked?
- If so, which parts are considered platform-specific and expected to be modified by the user?
Include paths can be configured manually, but it is unclear:
- Which include directories should be taken from the NxpNfcRdLib / phOsal libraries
- Which ones should come from the DiscoveryLoop example

Since the libraries differ depending on the host MCU, and the integration procedure seems to vary from project to project, I would appreciate your guidance on the recommended setup for this configuration.

This is fully within NXP platforms; I already have both evaluation boards connected and would like to proceed with basic driver and connection tests.

Best regards,
Radoslaw

Re: LPC55s28 PN5190 NFC Read Library porting

EduardoZamora — Mon, 26 Jan 2026 21:51:06 GMT

Hi,

Could you please kindly clarify what you mean with "the DAL and intfs folders are part of the DiscoveryLoop example and cannot be linked independently"? You should not face any restriction when trying to link these folders to your project.

You can either copy the folders to the workspace and link them or link the folders directly from the path where the Library was extracted; how they are shown in the project structure may depend on the method used.

Relevant paths that need to be included are shown in "Add include paths" section from NFC Reader Library Porting FRDM_K64F after linking the folders.

Regards,
Eduardo.

Re: LPC55s28 PN5190 NFC Read Library porting

RadoslawTomasik — Fri, 30 Jan 2026 11:31:46 GMT

Hi Eduardo,

thank you for your reply.

To clarify what I meant: the issue is how the DiscoveryLoop example project is structured and imported.

When importing the DiscoveryLoop project into MCUXpresso, it cannot be added to the workspace using the “Copy files into workspace” option. As a result, the project remains outside the MCU workspace directory and the DAL and intfs folders are therefore not visible within the workspace file system. Because of this, they cannot be linked independently in a practical way, as described in the FRDM_K64F porting guide.

Due to this, I proceeded with a manual port:

Copied the required DAL, intfs, NxpNfcRdLib, and phOsal folders directly into the LPC55S28 project so that they are fully visible in the project structure.
Manually added all required include paths, preprocessor symbols, and source locations.
Modified the DAL implementation to match the LPC55S16/LPC55S28 platform (SPI, GPIO, IRQ handling, timing, etc.).

With this approach, the project builds and the structure is now consistent and transparent inside the MCU workspace.

Regards,
Radoslaw