2021-03-01 11:32 PM
STM32L476VG is the MCU we are interfacing with ST25R3911B using SPI.
what we have understood from some search is that we need RFAL (abstraction layer) to interface with RF HAL.
Then once we integrate RFAL and RF HAL in our system workbench(ac6) project we need to build the integration then use SPI calls to read the register from RFID reader ST25R3911B
we wanted to use ISO-14443A standard to be configured and read the values.
where do we get the basic RFAL work space or code flow so that we shall use in our current project?
Kindly guide us and let us know are we in right path?
Solved! Go to Solution.
2021-05-19 08:22 AM
2021-05-19 08:34 AM
Hi,
the HAL_Delay(2000); in the while(1) in main.c:142 is probably the cause for your issue. This prevents from having real time processing. I would suggest to comment lines 140 to 142.
I believe you are now close to fix your issue
Rgds
BT
2021-05-20 01:20 AM
Hi BT,
we tried even doing this..but no luck still not seeing any RFID value...neither we are seeing return code 4 also..we have put a print there in rfalNfcaPollerCheckPresence function...do not understand from where to debug this...kindly let us know hoq to move on from here..
thanks and regards
Ravi
2021-05-20 01:30 AM
Hi,
I would suggest to check that the ST25R3911B interrupt pin from the X-NUCLEO-NFC05A1is properly connected to your custom board and that other existing connection to the IRQ_3911 GPIO does no conflict with the ST25R3911B interrupt pin.
To investigate further, please connect a logic analyzer on the ST25R3911B IRQ pin + SPI pins (CLK, MOSI, MISO, CS) and provide a logic analyzer trace
Rgds
BT
2021-05-20 01:36 AM
HI BT,
Here we have connected X-NUCLEO-NFC05A1 to discovery board STM32L476VG...we are trying with discovery there also same issue...we are trying to give you logs.
thanks and regards
Ravi
2021-05-20 04:30 AM
Hi BT,
As you told we probed the Interrupt line in ST25R3911B to STM32L476VG and we are seeing no activity here...any guess on what could be the problem and how we can
solve this?..kindly let us know.
regards
Ravi
2021-05-20 04:37 AM
Hi,
the interrupt line is probably still connected to the onboard ST25R3911B and conflicting with the off board ST25R3911B ...
Rgds
BT
2021-05-20 04:48 AM
Hi BT,
we are using X-NUCLEO-NFC05A1 connected discovery board STM32L476VG(not our customized board)...so where is the conflict here..also ensured no other lines are
connected ...any directions here..
regards
Ravi
2021-05-20 04:53 AM
Hi BT,
is it a S/w issue or Hardware...if its hardware..then where could be the issue..
regards
Ravi
2021-05-20 04:59 AM
Hi BT,
ALL SPI lines we are seeing CLK,MISO and MOSI properly no issues with that.