Skip to main content
Visitor II
March 2, 2021
Solved

SPI interface for STM32L476VG

  • March 2, 2021
  • 185 replies
  • 63548 views

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?

    This topic has been closed for replies.
    Best answer by Brian TIDAL

    Hi,

    X-CUBE-NFC5 package provides an NFC polling demo using the RFAL and running on NUCLEO-L476RG (MCU board) + X-NUCLEO-NFC05A1 (ST25R3911B expansion board). It can be a good starting point for a project based on SYM32L476VG.

    Rgds

    BT

    185 replies

    RShiv.1Author
    Visitor II
    May 20, 2021

    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

    Technical Moderator
    May 20, 2021

    Hi,

    the interrupt line is probably still connected to the onboard ST25R3911B and conflicting with the off board ST25R3911B ...

    Rgds

    BT

    RShiv.1Author
    Visitor II
    May 20, 2021

    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

    RShiv.1Author
    Visitor II
    May 20, 2021

    Hi BT,

    is it a S/w issue or Hardware...if its hardware..then where could be the issue..

    regards

    Ravi

    RShiv.1Author
    Visitor II
    May 20, 2021

    Hi BT,

    ALL SPI lines we are seeing CLK,MISO and MOSI properly no issues with that.

    Technical Moderator
    May 20, 2021

    HI,

    if the SPI is working properly, if you see proper responses from ST25R3911B on MISO, well, I would say it looks like either an HW issue (line being pulled up by another device) or the MCU GPIO is not properly configured (i.e. GPIO being in output pull up mode). Please provide a logic analyzer trace so I can check SPI communication is correct.

    Rgds

    BT

    RShiv.1Author
    Visitor II
    May 20, 2021

    Hi BT,

    Fine we will check this..but we do not have an analyser trace..we will share you the trace from scope(oscilloscope)..should be fine right.

    regards

    Ravi

    Technical Moderator
    May 20, 2021

    Hi,

    1/ can you confirm you see the following log message:

    • "Initialization succeeded..\r\n"
    • "SPI init passed..\r\n"?

    2/ disconnect the interrupt line from the ST25R3911B and connect the GPIO on 3V3 and then on Gnd: do you see the interrupt being triggered on MCU side?

    Rgds

    BT

    RShiv.1Author
    Visitor II
    May 20, 2021

    Hi BT,

    we are getting SPI

    • yes we are getting Initialization succeeded..\r\n"
    • "SPI init passed..\r\n"?

    we will answer the 2nd one for you shortly.

    regards

    Ravi

    RShiv.1Author
    Visitor II
    May 20, 2021

    Hi BT,

    we did the test for the 2nd point and still not seeing any result..I have also attached the ioc.file..can you confirm whether we need to configure PA3 as GPIO_EXTI3 or as GPIO_INPUT...let me know whether the configurations are correct..

    regards

    Ravi