cancel
Showing results for 
Search instead for 
Did you mean: 

STM32U5 + ST2525R3916B

biopunk101
Associate II

I am currently using STM32U5 + ST25R3196B with STM32CubeMX and X-CUBE-NFC6.

The program is based on the documentation from X-CUBE-NFC6.

Previously, I tested the example on the STM32F4 series, and it worked correctly. However, after migrating to STM32U5, the program does not function as expected.

After tracing, I found that execution stops at the following segment:

截圖 2025-03-11 11.18.21.png

 

Additionally, "BSP_NFC0XCOMM_IRQ_Callback()" is not triggered as expected.

I am aware that EXTI configurations differ between STM32U5 and STM32F4, so I modified the settings as follows:

image (2).png

 

The SPI initialization appears to be correct, but the issue persists. Could you help check if there are any potential issues? Thank you.

This discussion is locked. Please start a new topic to ask your question.
1 ACCEPTED SOLUTION

Accepted Solutions
biopunk101
Associate II

Thank you all for your replies.

I have confirmed that the issue was due to an incorrect CS pin configuration. The NUCLEO-L476 and NUCLEO-U545 actually have differences in their pin assignments.

Below is the correct configuration, which can be used for NUCLEO-U545 + ST25R3916B (X-NUCLEO-NFC08A1).

截圖 2025-03-13 11.09.17.png

 

View solution in original post

5 REPLIES 5
Ulysses HERNIOSUS
ST Employee

Hi biopunk101,

which NUCLEO board are you using? To which pins are the button and the IRQ of ST25R3916 connected. I propose you inspect which settings are currently applied on your project vs the actual HW connection.

I find integrate-nfc08a1-expansion-board-with-stm32-u575zi-q which addresses at least the user button problem.

BR, Ulysses

Andrew Neil
Super User

Please see How to insert source code - not as images.

 


@biopunk101 wrote:

After tracing, I found that execution stops at the following segment:

截圖 2025-03-11 11.18.21.png


Where, exactly, in that segment?

This line:

AndrewNeil_0-1741698643172.png

That's waiting for the pin to go high - so have you checked (eg, with a voltmeter) if the pin ever does go high?

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

 

Thanks for your reply and reminder.

Now, I understand that the button configuration on STM32U5 and F4 is different. I am using the  NUCLEO-U545 to test.

I also referred to the NUCLEO-L476RG, where the interrupt (INT) is connected to PA0, and I believe it should be the same for NUCLEO-U545.

However, the ISR is still not working. My current settings are as follows:

biopunk101_0-1741756435595.png

 

biopunk101_0-1741764501148.png


Is there anything else I need to check or modify? Any suggestions would be greatly appreciated.

biopunk101
Associate II

Thank you all for your replies.

I have confirmed that the issue was due to an incorrect CS pin configuration. The NUCLEO-L476 and NUCLEO-U545 actually have differences in their pin assignments.

Below is the correct configuration, which can be used for NUCLEO-U545 + ST25R3916B (X-NUCLEO-NFC08A1).

截圖 2025-03-13 11.09.17.png

 

If that's answered your question, please mark the solution:

https://community.st.com/t5/community-guidelines/help-others-to-solve-their-issues/ta-p/575256

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.