2025-05-12 3:30 AM
Hello,
I have purchased the "STEVAL-25R200SA – Discovery Kit for the ST25R200 high-performance NFC device" and attempted to run the sample application STSW-ST25R020 (Firmware for STEVAL-25R200 kit) available on the portal.
I was able to build and flash the code successfully; however, the reader is unable to detect the tag when it is presented. Additionally, I do not see any output (Even with USE_LOGGER=LOGGER_ON) on the Tera Term terminal.
Interestingly, when I use the same firmware along with the ST25R200 Eval GUI PC application, the reader appears to wake up, detect tags, and return to sleep mode as expected but no output on the Tera Term terminal.
Could anyone assist me in identifying the issue and provide guidance on how to resolve it?
Thanks & Regards,
Tanuj
Solved! Go to Solution.
2025-05-13 2:26 AM
Hi,
I would suggest to base you development on the X-CUBE-NFC10 package. Just reuse the STEVAL-25R200-STM32G0B1.ioc from the STSW-ST25R020 package and start STM32CubeMX with this file. Install the X-CUBE-NFC10 component in STM32CubeMX and then follow the documentation from STMicroelectronics.X-CUBE-NFC10_GettingStarted.pdf (in STM32Cube\Repository\Packs\STMicroelectronics\X-CUBE-NFC10\1.0.0\Documentation folder). Map the various IPs (SPI, UART, LEDs) on the ones already defined in the STEVAL-25R200-STM32G0B1.ioc. You may need to define a fake GPIO_EXTI for the push button. Then generate the application. This should provide a ready to use pollingTagDetect application. This application polls for different technologies (NFC-A, NFC-B and NFC-V) and displays the tag UID once a tag is present in the operating volume. You can then customize this application for your own needs.
Rgds
BT
2025-05-12 4:09 AM
Even though USE_LOGGER=LOGGER_ON is set, the UART pins and baud rate must match.
Confirm that Tera Term is set to 115200 bps, 8N1.
Ensure that you're connected to the correct virtual COM port exposed by the ST-Link (typically called “STMicroelectronics STLink Virtual COM Port”).
Check if the firmware is using USART1 or another peripheral. On STM32, UART TX/RX might be routed differently (e.g., alternate function pins).
2025-05-12 4:28 AM
Hi,
the STSW-ST25R020 is intended to be used with the ST25R200 Eval GUI PC application through the STLink Virtual Com Port (VCP). As the STLink VCP is used for the communication between the STEVAL-25R200A board and the PC, it cannot be used for printf traces. A DLL is provided on PC side with the various exported API for the development of custom PC applications.
The ST25R200 Eval GUI PC application can be used to set the STEVAL-25R200A board in a standalone demo mode (see the "Reader + Tag demo" tab). In this mode, the behavior of the LEDs can be customized by the user. See section 3.2 Reader+Tag Demo tab in the User Manual UM3364 for more information.
Rgds
BT
2025-05-12 5:58 AM
Hello Brian,
Thank you for the quick response and for confirming that the STSW-ST25R020 firmware is intended to work with the ST25R200 Eval GUI.
I am planning to develop an application using the NFC functionality. Could you please advise if there is any sample application available that can be used as a starting point? Having such a reference would help save time during development.
Best regards,
Tanuj
2025-05-12 8:18 AM
Hi Tanuj
Do you plan to develop an embedded application (i.e. fully running on the STM32G0 MCU of the STEVAL-25R200A board) or a PC application communicating with the STEVAL-25R200A board through the STLink VCP?
Rgds
BT
2025-05-12 8:29 AM
Hello Brian,
Yes, I have a plan to develop an embedded application running on the STM32G0 MCU.
Best Regards,
Tanuj
2025-05-13 2:26 AM
Hi,
I would suggest to base you development on the X-CUBE-NFC10 package. Just reuse the STEVAL-25R200-STM32G0B1.ioc from the STSW-ST25R020 package and start STM32CubeMX with this file. Install the X-CUBE-NFC10 component in STM32CubeMX and then follow the documentation from STMicroelectronics.X-CUBE-NFC10_GettingStarted.pdf (in STM32Cube\Repository\Packs\STMicroelectronics\X-CUBE-NFC10\1.0.0\Documentation folder). Map the various IPs (SPI, UART, LEDs) on the ones already defined in the STEVAL-25R200-STM32G0B1.ioc. You may need to define a fake GPIO_EXTI for the push button. Then generate the application. This should provide a ready to use pollingTagDetect application. This application polls for different technologies (NFC-A, NFC-B and NFC-V) and displays the tag UID once a tag is present in the operating volume. You can then customize this application for your own needs.
Rgds
BT
2025-05-19 3:45 AM
Hello Brian,
Thank you so much for your help. I followed your instructions and able to port and test the sample application for STEVAL-25R200 dev kit. However, i needed to struggle a little to resolve build errors due to the updated folder directory for generated files. For example, "Inc" and "Src" folder are placed together inside the "Core" folder.
I would like to know, if there is any document that can help me understand the NFC RFAL library.
Regards,
Tanuj
2025-05-19 4:00 AM
Hi,
The RFAL is documented inside the RF/NFC abstraction layer (RFAL) User Manual (UM2890 ).
Rgds
BT