card emulation with PN7150

[Tadashi_1]

Hello, 

I would like to implement card emulation using the PN7150.

Since we are programming without an OS like Linux on the microcontroller,

we are directly sending NCI commands from the microcontroller to the PN7150 without using an API.

Commands sent:

CORE_RESET_CMD

CORE_INIT_CMD

RF_DISCOVER_MAP_CMD

  Only the following payload is set:

  04: PROTOCOL_ISO_DEP

  03: RF protocol is mapped to both Listen and Poll for RF interface.

  02: ISO-DEP RF Interface

  STATUS_OK is returned.

CORE_SET_CONFIG_CMD

  The following parameters are set in the payload:

  {30, 01, 01} = {LA_BIT_FRAME_SDD, L=1 byte, Param=01}

  {31, 01, 03} = {LA_PLATFORM_CONFIG, L=1 byte, Param=03}

  {32, 01, 20} = {LA_SEL_INFO, L=1 byte, Param=20}

  {33, 04, 01, 02, 03, 04} = {LA_NFCID1, L=4 bytes, "01, 02, 03, 04"}

  STATUS_OK is returned.

RF_DISCOVER_CMD

  The following parameters are set in the payload:

  0x01, 0x80, 0x01

  Using 0x80, NFC_A_PASSIVE_LISTEN_MODE is requested.

After these command communications, when I bring a smartphone running the TagInfo app close, an RF_FIELD_INFO_NTF(0x01) is received, but immediately after that, an RF_FIELD_INFO_NTF(0x00) is received.

According to an RF checker, the signal seems to be emitted.

Afterward, RF_INTF_ACTIVATED_NTF does not arrive.

From these observations, it appears that card emulation is not being activated.

Could anyone please help me understand what might be causing the card emulation to fail to activate?

[Tadashi_1]

Dear Fabian, 

The issue has been resolved, and it has been confirmed that the evaluation board connects to the PC via VCOM.

It seems that the settings in MCUXpresso IDE were not configured correctly. After tinkering with various options in the Debug Configuration screen, the connection suddenly started working. However, since I was randomly trying different things, I can't pinpoint which specific change fixed the issue.

For now, I have confirmed that the evaluation board operates in card emulation mode. I am currently analyzing the sample code to better understand it so that I can port it to another microcontroller and make it work.

Thank you for your support.

Best Regards

[Fabian_R]

Hello sir,
I would be great to know what might the issue be.
But at least it has been resolved, we will check it also from our side to discard any problems in our configurations and software.
Thank you very much for letting us know this.

[Fabian_R]

Hello sir,

We don't recommend the use of PN7150 for new designs, if you are in an early stage of development please explore the possibility of using PN7160 for a new design since, the support for PN7150 is very limited.

Regarding your issue, have you tried our PN7150 example (SW4325) this is an example that provides the possibility of emulate a T4T and, can be read by the TagInfo App.

For further information please take a look at AN11990

[Tadashi_1]

Hello Sir,

Thank you for your response.
Then I will consider using the PN7160.
Could you please provide the datasheet and sample code for the PN7160 to replace the PN7150's AN11990 and sample code?
Additionally, although I assume it may be mentioned in the datasheet, could you let me know the most recommended combination of microcontroller board and NFC controller board?

Best Regards,

Tadashi

[Fabian_R]

Hello sir,

The application note for running the software can be found in the following link:

I can also be found in the PN7160 link, scrolling down to the Documentation section and looking for AN13288

The software can be found in the PN710 site but, in the Software section as SW6705

The recommended MCUs are mentioned in AN13288 but they are: LPC82x,  LPC55S6x and  i.MX RT1170.

[Tadashi_1]

Hello, 

Based on AN13288, I have purchased the following items:

- OM13071 LPCXpresso824-MAX board
- NFC controller board (OM27160A1HN)
- Arduino interface board (OM29110ARD-B)

Following the instructions in Section 2.1 (LPC82x) of AN13288, I completed the hardware setup, ensuring the above three components are correctly connected.

As per Section 3 (SW setup), I installed MCUXpresso IDE and imported the project.

Following the instructions, "Click on the 'dark blue bug' icon to build the project," I selected NXP-NCI2.0_LCP82x_examples<RWandCE_Debug> in the Project Explorer and clicked on the dark blue bug icon.

However, the following Error(A) appeared below.
Then appeard Error(B).

What steps should I take to resolve these errors (A) and (B), to successfully build the project to start debugging?

/////////////////////////////////////////////////////////////////////////////////////////////////

Error(A):
ERROR: Could not connect to target.
SEGGER J-Link GDB Server V8.10 Command Line Version
JLinkARM.dll V8.10 (DLL compiled Sep 26 2024 08:37:48)
Command line: -SettingsFile C:\Users\DENKISEKKEI03\Desktop\SVN_2(2)\SW6705\NXP-NCI2.0_MCUXpresso_examples\NXP-NCI2.0_LPC82x_examples\RWandCE_Debug\NXP-NCI2.0_LPC82x_examples JLink RWandCE_Debug SettingsFile.jlink -nosilent -swoport 2332 -select USB=600102279 -telnetport 2333 -singlerun -endian little -noir -speed 4000 -port 2331 -vd -device LPC824M201 -if SWD -halt -reportuseraction
-----GDB Server start settings-----
GDBInit file: none
GDB Server Listening port: 2331
SWO raw output listening port: 2332
Terminal I/O port: 2333
Accept remote connection: localhost only
Generate logfile: off
Verify download: on
Init regs on start: off
Silent mode: off
Single run mode: on
Target connection timeout: 0 ms
------J-Link related settings------
J-Link Host interface: USB
J-Link script: none
J-Link settings file: C:\Users\DENKISEKKEI03\Desktop\SVN_2(2)\SW6705\NXP-NCI2.0_MCUXpresso_examples\NXP-NCI2.0_LPC82x_examples\RWandCE_Debug\NXP-NCI2.0_LPC82x_examples JLink RWandCE_Debug SettingsFile.jlink
------Target related settings------
Target device: LPC824M201
Target device parameters: none
Target interface: SWD
Target interface speed: 4000kHz
Target endian: little
Connecting to J-Link...
J-Link is connected.
Device "LPC824M201" selected.
Firmware: J-Link V10 compiled Jan 30 2023 11:28:07
Hardware: V10.10
S/N: 600102279
Feature(s): RDI, FlashBP, FlashDL, JFlash, GDB
Checking target voltage...
Target voltage: 3.31 V
Listening on TCP/IP port 2331
Connecting to target...
Found SW-DP with ID 0x2BA01477
DPIDR: 0x2BA01477
CoreSight SoC-400 or earlier
Scanning AP map to find all available APs
AP[0]: Stopped AP scan as end of AP map has been reached
Iterating through AP map to find AHB-AP to use
Attach to CPU failed. Executing connect under reset.
DPIDR: 0x2BA01477
CoreSight SoC-400 or earlier
Scanning AP map to find all available APs
AP[0]: Stopped AP scan as end of AP map has been reached
Iterating through AP map to find AHB-AP to use
Could not find core in Coresight setup
Found SW-DP with ID 0x2BA01477
DPIDR: 0x2BA01477
CoreSight SoC-400 or earlier
Scanning AP map to find all available APs
AP[0]: Stopped AP scan as end of AP map has been reached
Iterating through AP map to find AHB-AP to use
Attach to CPU failed. Executing connect under reset.
DPIDR: 0x2BA01477
CoreSight SoC-400 or earlier
Scanning AP map to find all available APs
AP[0]: Stopped AP scan as end of AP map has been reached
Iterating through AP map to find AHB-AP to use
Could not find core in Coresight setup
ERROR: Could not connect to target.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 

Error(B):
Error in final launch sequence:

Failed to execute MI command:
-target-select remote localhost:2331

Error message from debugger back end:
localhost:2331: Connection timed out.
Failed to execute MI command:
-target-select remote localhost:2331

Error message from debugger back end:
localhost:2331: Connection timed out.
localhost:2331: Connection timed out.

[Fabian_R]

Hello,

Could you please clarify that you have installed the LPC82x SDK? This has to be downloaded in the following site: https://mcuxpresso.nxp.com/en/select by searching the board's name: LPCXpresso824MAX

The full guide is in the following link: https://www.nxp.com/webapp/Download?colCode=UM10830

My recommendation would be to please test the board by flashing one of the examples from the SDK and then, follow AN13288.

In case the issue is still persistent, please make sure you are using the latest MCUXpresso and, NCI-example software version from the PN7160 site.