Struggling with x-NUCLEO-NFC12A1

[SnoZek]

Hello,

I'm having trouble deploying the middleware for the X-NUCLEO-NFC12A1 demo board.
I have an x-NUCLEO-NFC12A1 and a NUCLEO-WBA65RI.

I connected the two boards together, wired the pins correctly, and tried to use the X-CUBE-NFC12 middleware package. However, when I generate the project, it only includes the ST25R500 driver under Drivers/BSP/Components/.

How can I get a proper starting point to develop with the ST25R300? Is there a specific package or example project available for it?

My goal is simple: I want to use it to enable and operate a WLC with a PTX30W.

Thanks a lot for your help,

Yvan

[Brian TIDAL]

Hi Yvan,

make sure to follow the X-CUBE-NFC12_GettingStarted.pdf located in <yourHomeDir>\STM32Cube\Repository\Packs\STMicroelectronics\X-CUBE-NFC12\1.0.0\Documentation.

It provides the step-by-step instructions to properly configure the project.

Feel free to share your ioc project file and I will check it.

Rgds

BT

[SnoZek]

Hello Brian,

Thank you for your reply.

I followed the getting started documentation. After building the project and running it, I noticed that the ST25R500 component is still present in the component files.

At first, I encountered an error related to PendingCallback, which I replaced with RisingCallback since I am using the WBA board (a more recent version).

I also observed that the ST25R500 is still referenced throughout the source files.

However, I was able to start the demo code and successfully detect a tag, so I assume that everything is working correctly.

[Brian TIDAL · Accepted solution]

Hi Yvan,

Great job: the demo is functional.

The ST25R500 and the ST25R300 share the same drivers. The ST25R500 is an automotive version of the ST25R300. Thus, the drivers refer to ST25R500.

PendingCallback versus RisingCallback is a bug that will be fixed in the next version of the package.

Feel free to share more information in private about your use case.

Rgds

BT