2025-05-13 1:43 AM
Hello,
I would like to develop a system using the NFC chip ST25R200 and the microcontroller STM32F303. The main idea is to be able to read an NFC tag, specifically the ST25DV64KC.
As a first step, I plan to test this using the prototyping board NUCLEO-F303 and the NFC expansion board X-NUCLEO-NFC10A1. I'm using CubeIDE.
I'm sure that ST has prepared everything for a simple and smooth integration. Because of that, I'm confused about what I'm doing wrong.
After configuring the pins and integrating the middleware/software in STM32CubeMX, I get errors when I try to compile the code (I haven't changed anything in the generated code).
Here is picture with Pins defined:
here is Middleware/software package included and set:
SPI1, Interrupt, GPIO configure:
After generating code I go to main.c where I want to compile generated code and get a lot of errors:
Can you please help me understand what I'm doing wrong?
In the past, I worked with the ST25R3912, so I have some experience.
If you need more information, feel free to ask.
Solved! Go to Solution.
2025-05-13 5:41 AM
Hi,
make sure to select an RFAL configuration. It seems not selected in your case:
This should be something like:
See attached ioc file as an example.
Rgds
BT
2025-05-13 5:41 AM
Hi,
make sure to select an RFAL configuration. It seems not selected in your case:
This should be something like:
See attached ioc file as an example.
Rgds
BT
2025-05-13 6:09 AM - edited 2025-05-13 6:25 AM
That solved my problem.
Thank you very much.
If I want to use NFC-V and allowed energy harvesting for tag (ST25DV64KC)...
1. what is the minimum of the functions I need to use?
2. what of these options I need to use:
I'm a bit sceptical with time spending using all that functions.
Thank you and best regards,
2025-05-13 9:08 AM
Hi,
in a perfect world, you should choose Custom_config for the RFAL and then select RFAL_FEATURE_NFCV and RFAL_FEATURE_ST25xV and regenerate. In that case the project also defines RFAL_ANALOG_CONFIG_CUSTOM whereas no custom analog config are provided, so #define RFAL_ANALOG_CONFIG_CUSTOM needs to be manually commented in the nfc_conf.h.
Unselected technologies are then not used in the discovery loop and the linker removes the unused part of the code.
Rgds
BT
2025-05-13 11:45 PM
Thank you.
So I did the following 4 steps:
Is this enaugh or I need to uncheck some other things? thank you very much
If I do this 4 steps and compile code I get no errors.
Best regards,
2025-05-14 12:39 AM
Hi,
this should be fine: only NFC-V technology plus support of ST25TV/ST25DV API are selected.
Rgds
BT
2025-05-14 12:46 AM - edited 2025-05-14 1:13 AM
Okey, but with this configuration I don't need to insert #define RFAL_ANALOG_CONFIG_CUSTOM like you said.
If I check RAM, FLASH usage are in both cases the same:
I have a feelings like nothing changes.
Should I uncheck what the bottom red arrow shows or anything else?
thank you and best regards,
2025-05-14 6:15 AM
Hi,
Sorry for the confusion about RFAL_ANALOG_CONFIG_CUSTOM, I was using a pre-release version of the FW package.
Regarding RAM/FLASH usage
Default:
Custom:
Make sure to use the following compiler settings:
and the following linker setting:
Check the map file for the custom build vs the default build: functions such as rfalNfcaPollerInitialize should be absent in the custom build map file.
Also adjust the compiler optimization level according to your needs.
Rgds
BT
We’re moving the ST Community to a new platform to give you a better and more reliable community experience.