SPI Comm Between FRDM-MCXW71 and a PN7160 Module

[S_Salam555]

I am attempting to establish SPI communication between the FRDM-MCXW71 and a PN7160 module. At the moment, the PN7160 does not respond over SPI. I have verified the basic hardware connections (SPI signals, IRQ, VEN, and RESET), but the device remains unresponsive.

For firmware reference, I am following the NXP PN7160 NFC Reader firmware example originally provided for LPC microcontrollers, and I am in the process of porting and adapting it to the MCXW71 platform. Despite configuring the SPI peripheral according to the PN7160 documentation, communication is not established.

I suspect the issue may be related to:

• SPI timing or mode configuration differences between LPC and MCXW platforms

• PN7160 VEN / RESET / IRQ handling sequence

• Required delays or power-up initialization specific to PN7160

• Any platform-specific considerations when using PN7160 over SPI

• Correct configuration and adaptation of the tml.c (Transport Mapping Layer) file, particularly SPI initialization parameters, IRQ handling, and low-level read/write implementation for the MCXW71 platform  

I have attached the project I am currently working on for your reference. Any guidance, recommended configuration changes, or reference material specific to PN7160 with MCX-series MCUs would be greatly appreciated.

[Shakir555]

Hi Roman,

I just wanted to follow up as the SPI communication issue between the FRDM-MCXW71 and PN7160 is still ongoing.

Best regards,
Shakir Salam

[RomanVR]

Hi @S_Salam555, sorry for the late reply.

From the changes that you have implemented in your project, would you please share with me the captured SPI traces? This will allow me to better analyze the behavior that you are observing, and if possible, please try to obtain the SPI traces using a logic analyzer.

[RomanVR]

Hi @S_Salam555, hope you are doing well.

Since you are doing a porting work for the MCXW71, I would suggest to take as reference any of the available SPI examples within the MCXW's SDK to avoid any peripheral configuration issues, especially regarding clock initialization and pin muxing and configuration parameters, ensuring that the configured instance is consistent with the interface instance.

After doing the configurations based on the SPI example, please let me know your findings. If the issue persists, share with me the traces of the SPI communication.

[S_Salam555]

Hi Roman,

I hope you’re doing well.

I was away for some time and recently resumed testing the FRDM-MCXW71 with the PN7160 module, with assistance from Jimmy Chan and Fabian on the hardware wiring and configuration. However, I am still encountering issues on the firmware side.

Jimmy mentioned that the problem might be related to the IRQ pin configuration, and I would appreciate it if you could help review my firmware to identify any potential issues or improvements.

I have attached the project files and relevant images for your reference.

Thank you very much for your support.

Best regards,
Shakir Salam

[RomanVR]

Hello @S_Salam555, sorry for the late reply

While reviewing your project I was able to notice that you are using LPSPI1 peripheral for interface with the PN7160 in your TML file, however you are initializing pins of LPSPI0 instance, please try by modifying this initialization and use a single LPSPI instance for your project.

Please let me know if applying these changes you can enable the SPI communication.

[S_Salam555]

Hello @RomanVR,

I hope you are doing well. Great to see you back.

I have updated the LPSPI0 instance, but the output remains the same. Could you please try running the software on your side to verify?

I’ve attached my current project, where I modified the LPSPI0 instance in board.h. Kindly help to review and experiment on your side and let me know your findings.

Thanks in advance.

Best regards,
Shakir Salam

 

[S_Salam555]

Hi Roman,

I hope you're doing well.

Additionally, could you please help double-check the SPI0 pin peripheral initialization. For your reference, I’ve attached a screenshot of pin_mux.c below.

Thank you in advance for your support.

 

  

Best regards,
Shakir Salam

[RomanVR]

Hello @S_Salam555.

From the changes you have done to the project I have noticed that you are missing to initialize the IRQ, VEN and DWL pins, please do so just as you have done it for the SPI pins and make sure that the initialization is consistent with the GPIOs configured in the TML.

Additionally, please confirm if now you are able to see SPI frames in the corresponding terminals, preferably with a logic analyzer.

[S_Salam555]

Hi,

Thank you for your suggestion.

I have already based my implementation on the SPI examples available in the MCXW SDK, ensuring that the clock initialization, pin muxing, and configuration parameters are aligned with the reference design.

As requested, I have shared the SPI communication waveform along with the complete project folder for your review.

Please let me know your findings or if any additional information is required.

Best regards,
Shakir Salam

 

[RomanVR]

Hello @S_Salam555.

Please check that the SPI and GPIO instances and pins initialized match the ones used in your TML.

Also, avoid enabling more than once the clocks of the peripherals and ensure to be properly clocking all of the used ports required by the pins used to communicate with the PN7160.

Regarding your SPI communication capture, is the MCXW71 not sending any SPI frame?

[S_Salam555]

Hi Roman,

I hope you're doing well.

It appears there are differences between the PC55S6X and MCXW71 configurations. The PC55S6X uses four parameters, whereas the MCXW71 only has three. I have already made the necessary adjustments accordingly, but the results remain the same.

Could you please help verify whether the pin and port configurations for IRQ, VEN, and DWL on the MCXW71 are correct? I would also appreciate your guidance or recommendations on the correct pinout for these three signals.

I have attached an image below highlighting the differences between the MCXW71 and LPC55S6X for your reference.

Thank you in advance for your support.

MCXW71

[board.h]

[tml.c]

LPC55S6X

[board.h]

[tml.c]

Terminal Output

FRDM-MCXW71 View

Best regards,
Shakir Salam

[S_Salam555]

Hi Roman,

Here some quick update.

I have updated the pin configuration according to the MCXW71 and PN7160 pinout. However, the result remains the same.

Could you please advise if there are any additional checks or recommendations I should consider?

Thank you in advance for your support.

Best regards,
Shakir Salam

[S_Salam555]

Hi Roman,

I hope you’re doing well.

Could you please advise whether I should start by importing the NXP-NCI examples from LPC, or proceed directly with importing the lpspi_interrupt_b2b_master example and test it with the PN7160?

Best regards,
Shakir Salam

[S_Salam555]

Hi Roman,

I have conducted tests based on the provided examples; however, it appears that the PN7160 is unable to detect the FRDM-MCXW71. I have included all relevant details in the attachment for your reference. Can you help me double check the hardware wiring as well. thanks. 

Best regards,
Shakir Salam

[RomanVR]

Hello @S_Salam555.

Sorry if my earlier suggestion was unclear. The lpspi_interrupt_b2b_master example is not expected to work directly with the PN7160. Instead, it is meant to serve as a baseline to help you add the required MCXW71 LPSPI configurations into the Transport Mapping Layer of the LPC reference example, and to replace the LPC initializations with the corresponding MCXW71 ones.

The intention is to make the porting process easier and to help avoid configuration issues while adapting the LPC example to the MCXW71.

[S_Salam555]

Hi Roman,

Nice to meet you! I’m planning to work with SPI on the MCU and wanted to ask which SDK components you would recommend using as a template. Would FlexIO SPI, LPSPI, or LPSPI with EDMA be the best choice?

Thanks for your guidance!

Best regards,
Shakir Salam

[RomanVR]

Hello @S_Salam555!

I would suggest to take as reference the lpspi_interrupt_b2b_master example as it is intended to configure the board as an SPI master to communicate with other board which is a closer approach to your expected functionality and it is a good base to see the required and proper initializations needed for the LPSPI peripheral.

Please let me know if this helps.