LPC55s28 PN5190 NFC Read Library porting

[RadoslawTomasik]

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

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

Thank you!

[RadoslawTomasik]

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

[EduardoZamora]

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.

[RadoslawTomasik]

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

[EduardoZamora]

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.

[RadoslawTomasik]

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

[RadoslawTomasik]

@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

[EduardoZamora]

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.

[RadoslawTomasik]

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

[Emiel]

Hello,

Were you able to figure out how the library can be ported? I keep getting stuck at rewriting the DAL because the SDK and NFC-library structure were changed quite significantly.

I tried to base my code of off this guide with included source code . However this NFC-library version does not include the PN5190 drivers. When the PN5190 was added quite a few significant changes were added to the library which causes a lot of errors when I tried to just replace the NfcRdLib, phOsal and intfs folders. I also ran into a couple of errors that were caused by the newer SDK version so I basically don't really know what to do now. Especially because the recommended guides 1 & 2 are not up-to-date anymore.

Thanks in advance! 

[RadoslawTomasik]

Hi Emiel,

Are you using the same hardware combination (LPC55xx + PN5190)?

Basically, you can use the existing porting guides as a reference, even though there is no official LPC55S28 + PN5190 project. I would recommend downloading the latest NxpNfcRdLib_PN5190 package and importing it into MCUXpresso. As a starting point, create a new project from an LPC55xx SDK example (for example, hello_world) and port the NFC Reader Library manually.

The approach that worked for me was:

• Copy the DAL, intfs, NxpNfcRdLib, and phOsal folders directly into the LPC55S28 project so everything is part of the project structure.
• Manually configure all required include paths, preprocessor symbols, and source locations.
• Rewrite the DAL for the LPC55xx platform (SPI, GPIO, IRQ handling, timing, etc.).
• Enable any missing MCU drivers through Manage SDK Components in MCUXpresso and adapt the DAL to use those drivers.

Regarding the drivers you mentioned as missing: which ones are they exactly? If you can list the missing modules or post the compiler errors, it will be much easier to identify what still needs to be ported.

The errors caused by the newer SDK may also depend on the exact LPC device and SDK version you're using. I would first verify that you're using the latest SDK available for your MCU from NXP and make sure it matches the version expected by your project.

From your description I can only make an educated guess, but if you can share:

• the exact LPC55xx device,
• the SDK version,
• the NFC Reader Library version, and
• a few of the compilation errors,

I'd be happy to help identify the required changes. I went through a similar manual port, so I may be able to point you in the right direction.

I hope this helps you move a bit further.

[Emiel]

Hello,

Thank you for your reply! It's greatly appreciated. I'm using the LPC55S69-EVK  + PNEV5190BP.

I have downloaded the latest NxpNfcRdLib (NxpNfcRdLib_PN5190_v07.16.00_PUB) and SDK (SDK_26_06_00_LPCXpresso55S69) from the website.

At first I imported the DiscoveryLoop example from the NxpNfcLib made for the K82F microcontroller. This was not a great success because there are a lot of micrcocontroller specific settings that were interfering with that process. 

I then found the LPC porting guide mentioned earlier in this thread. This was also not a success because the SDK and Nfc lib versions were basically too old to properly use.

I then did what you already mentioned. I imported the lpcxpresso55s69_lpc_gpio_led_output_cm33_core0 example from the newest SDK and added the DAL, intfs, NxpNfcRdLib, and phOsal folders directly to the project. Then I configured the paths, preprocessor and source locations. The I added the missing SDK components.

I tried to modify the DAL but because there were quite a few differences between the DAL that worked for the old Nfc lib and the new lib I was not able to pull this off. It actually compiles but it gets stuck in the hardfault handler on the SPI_MasterInit function caled bij phbalReg_Init(). 

I think this is mostly because I'm quite new to using NXP products. I'll include a zip file of the project. Maybe there are things that I did wrong or maybe I missed something.

[RadoslawTomasik]

Hi Emiel,

From your description, the first thing I would double-check is your pin configuration (pin_mux) and verify that the correct Flexcomm instance is configured for SPI. A mismatch there can easily cause the code to end up in the HardFault handler during SPI_MasterInit().

Additionally, make sure that the spi_master_config structure is properly initialized before calling SPI_MasterInit(). It's also worth reviewing the Exchange function to ensure that both the WRITE and READ phases are implemented correctly, as the newer Reader Library expects slightly different behavior than the older versions.

I've attached my files for reference. They may help you compare your implementation with a working example, but I can't guarantee they'll work without modification since they were created for a different setup.

Hopefully this points you in the right direction.

[Emiel]

Thank you very much. I'm not entirely sure how I should configure the pin_mux and clocks. I did it via the pin configuration tool though but I'm not sure if I have done it correctly. But I also don't quite understand why I would have to do it like this because these settings seem to be overwritten in the phbalReg_LpcOpenSpi.c file anyway. 

I did find out that in phbalReg_Init(), I think it was, I needed to change the way the clock frequency was selected because this had been changed some time ago. 

I then was able to compile and download the code to the microcontroller. However, nothing works except the debug text :(. I took a look at your code however, I ran into more problems. The library version I have expects the interrupt handler to be like this: PH_DRIVER_LPC_TIMER_IRQ_HANDLER(uint32_t flags); while literally every example I have found thus far uses your define: PH_DRIVER_LPC_TIMER_IRQ_HANDLER(void);

This results in the following error: 

../DAL/src/LPCOpen/phDriver_LPCOpen.c:42:47: error: initialization of 'void (*)(uint32_t)' {aka 'void (*)(unsigned int)'} from incompatible pointer type 'void (*)(void)' [-Wincompatible-pointer-types]

42 | ctimer_callback_t ctimer_callback_table[] = { PH_DRIVER_LPC_TIMER_IRQ_HANDLER, NULL, NULL, NULL, NULL, NULL, NULL, NULL};

| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Your help has been very helpful thus far. Would it be possible to include the phDriver_LPCOpen.c file or a zip of the entire project?

Thanks in advance!

[Emiel]

EDIT: I managed to "fix" this error by adding uint32_t flags instead of void to the definitions of PH_DRIVER_LPC_TIMER_IRQ_HANDLER. Still doesn't work though