How to debug EVAL-ST95HF board using STM32F103RGT6 with atollic or KEIL uvision5

[abarr.10]

Hello Everybody, I've a big problem to debug my EVAL-ST95HF board, i tried two ways to fix that:

• the first one: i unzipped the source folder getting EVAL-ST95HF_FW_V3.7.0 that i used with keil uvision5, when i build i get this error message and i've seen this file doesn't exist within the indicated directory and tried to install a previous version e.g keil uvision4.74 i've no managed to open project with the last one

Rebuild started: Project: DEMO_BOARD_ST95HF

*** Using Compiler 'V5.06 update 6 (build 750)', folder: 'C:\Keil_v5\ARM\ARMCC\Bin'

Rebuild target 'DEMO_BOARD_ST95HF'

compiling Firmware_Saving.c...

compiling menu_writer.c...

compiling menu_Tagemul.c...

compiling menu_cardemul.c...

compiling menu_reader.c...

compiling main.c...

compiling common.c...

compiling hw_config.c...

compiling menu_auto.c...

compiling menu.c...

compiling stm32f10x_it.c...

compiling PongExample.c...

compiling proprietary_p2p.c...

compiling drv_spi.c...

compiling drv_95HF.c...

compiling drv_interrupt.c...

compiling drv_uart.c...

compiling lib_nfctype1pcd.c...

compiling lib_nfctype2pcd.c...

compiling lib_nfctype3pcd.c...

compiling lib_nfctype4pcd.c...

compiling lib_iso7816pcd.c...

compiling lib_nfctype5pcd.c...

compiling lib_iso14443Apcd.c...

compiling lib_iso14443Bpcd.c...

compiling lib_iso18092pcd.c...

compiling lib_iso15693pcd.c...

compiling lib_PCD.c...

compiling lib_nfctype2picc.c...

compiling lib_PICCemulator.c...

compiling lib_nfctype4picc.c...

compiling lib_iso7816picc.c...

compiling lib_cardemul.c...

compiling lib_iso14443Apicc.c...

compiling lib_PICC.c...

compiling lib_flash_ndef.c...

compiling lib_proprietaryP2P.c...

compiling lib_NDEF_AAR.c...

compiling lib_NDEF.c...

compiling lib_ConfigManager.c...

compiling lib_NDEF_Email.c...

compiling lib_NDEF_Geo.c...

compiling lib_NDEF_SMS.c...

compiling lib_NDEF_URI.c...

compiling lib_NDEF_Text.c...

compiling lib_NDEF_Vcard.c...

compiling misc.c...

compiling lib_95HF_wrapper.c...

compiling stm32f10x_crc.c...

compiling stm32f10x_exti.c...

compiling stm32f10x_dma.c...

compiling stm32f10x_gpio.c...

compiling stm32f10x_spi.c...

compiling stm32f10x_rcc.c...

compiling stm32f10x_flash.c...

compiling stm32f10x_tim.c...

compiling drv_LED.c...

compiling stm32f10x_usart.c...

compiling drv_lcdspi_ili9341.c...

compiling usb_init.c...

compiling usb_int.c...

compiling usb_core.c...

compiling usb_mem.c...

compiling usb_desc.c...

compiling usb_sil.c...

compiling usb_regs.c...

compiling usb_endp.c...

compiling usb_istr.c...

compiling mass_mal.c...

compiling memory.c...

compiling msd_rw.c...

compiling nand_if.c...

compiling scsi_data.c...

compiling usb_hid.c...

compiling usb_bot.c...

compiling usb_scsi.c...

assembling startup_stm32f10x_xl.s...

compiling usb_prop.c...

compiling core_cm3.c...

compiling usb_pwr.c...

compiling system_stm32f10x.c...

linking...

.\Obj\DEMO_BOARD_ST95HF.axf: error: L6050U: The code size of this image (72548 bytes) exceeds the maximum allowed for this version of the linker.

Finished: 0 information, 0 warning, 0 error and 1 fatal error messages.

".\Obj\DEMO_BOARD_ST95HF.axf" - 1 Error(s), 0 Warning(s).

Target not created.

Build Time Elapsed: 00:00:06

• the second way, i installed STM32CubeProgrammer, i've managed to program my EVAL-ST95HF but not debugging

I've even tried with Atollic using ST-Link embed into nucleo board , nothing works

can you help me please? Which methode must i use to debug my board

[abarr.10]

Hi Brian, I've tested the program that i I've imported from EVAL-ST95HF_FW8V3.7.0 into Atollic, everything works except Tag Emultalor mode (TT2 & TT4) and Tag Detect WU mode, but when i use ST'Link utility with the software(EVAL-ST95HF_FW8V3.7.0) provided by ST it works fine and I've got multiple warning when i build, can you help me please?

look at below

[Brian TIDAL]

Hi,

Thanks for reporting us these issues.

in Tag Detect WU mode menu, there is a while loop on KEYPress flag. As this flag is not declared as volatile, the compiler may have optimized the code and not read the updated value of the flag after the interrupt callback. You can either compile with optimization level -Oo (None) or add the volatile qualifier for KEYPress.

You will need as well to fix SELECT_BUFFER_SIZE in lib_PCD.h (should be 9 instead of 6) to avoid a potential buffer overflow.

No issue seen on my side with Tag emulator TT2 or TT4 when compiling in -O0

Rgds

BT

[abarr.10]

Hi Brian,

thank you for your reply, its ok for me, everything works,

i'am looking for a small board for only ST95HF Transceiver, because I had already done a big part of my project on another STM32 board(NUCLEO F103RB), my idea is running 95HF with this board, How can i find ST95Hf expansion board? or I have to do PCB for that?

[Brian TIDAL]

​Hi

if you need only card reader feature, you can use the PLUG-CR95HF-B development board or the X-NUCLEO-NFC03A1 expansion board for STM32. I would suggest you use the ST25R95 RFAL library from X-CUBE-NFC3. This library provides common interface between each reader of the ST25R family.

Rgds

BT

[abarr.10]

I need Tag hunting and tag emulator from ST95HF beacause inTag reading i can't read RFID tag and can't realize tag emulator on CR95HF.

[Brian TIDAL · Accepted solution]

​Hi,

for new development, it is recommended to use the ST25R95 IC which supports reader mode and Card Emulation mode over SPI with the same set of commands as the ST95HF. The X-NUCLEO-NFC03A1 is also the expansion board for the ST25R95.

Rgds

BT

[abarr.10]

Brian,

I really need reader mode and tag emulator(TT2 or TT4 ) not card emulator in card emulation mode. the only eval board that can do that is Eval ST95HF, our Idéa was to to take NFC03A1 and then adding M24LR to get 2 features (reader mode and tag allowing a smartphone to read information without card emulator or P2P) like Tag hunting and tag emulator in ST95HF