ST25RU3993 HPEV UART Comminication between STM MCU and Host

[SPraj.1]

I have development board of ST25RU3993 HPEV. I am testing TAG detection uising GUI application -provided by STM.

As this application works using USB interface between STM MCU and HOST. Instead of USB interface I want to check UART communication with HOST.

Can you plese ket us know how can i check UART communication and where to take wires and what changes are required in hardware.

Also I need some informatrion of protocol because we need to develop a application on UART to read tag information

[Nick K]

Hello SPraj1.

• can you confirm that the CP2102 is able to operate at 3MBit/sec ? - No it is operatable upto 1Mbit/sec
  • The stock FW operates at 3Mbit/sec. If CP2102 operates with max 1Mbit/sec communication can not work. Please use a USB-UART converted which is able to work with 3Mbit/sec.

• just to be sure, did you also connected DTR/RTS lines between the HPEV and the CP2102 ? as explained, they are needed to bring the STM32L4 into bootloader mode, if you want to upgrade the FW. DTR/RTS lines are also used by the GUI during connect and when starting the upgrade process. If DTR and RTS are not proper configured the board will not boot from User code nor enter bootloader. - No RTS and DTR lines are not connected between CP2102 and STM32l4. Already latest firmware is downloaded previously then also it asks for firmware upgrade while UART is connected.
  • RTS and DTR lines are needed to define boot-behavior of the STM32L4. If DTR and RST are not configured correct the board will not boot. Neither into bootloader code nor into user code. Please connect them as the GUI controls them to boot the board.

• could you send a picture with your wiring between the board and the CP2102 ? - Images are attached.
  • Thanks for the picture, but the connections on the CP2102 side is not visible, the cable for GND connection is not visible and the DTR, RTS pins are not connected.

• could you send traces of the DTR, RTS, Rx, Tx lines when trying to connect the GUI with the board ? - Did not get your question. what you want waveforms?
  • Yes, waveform captured at the DTR, RTS, Rx, Tx wires to check the communication on the wires, if it can be assumed that all wires are connected correct and communication still not work

[SPraj.1]

Point#1: Currently we are not having UAB-UART bridge that support 3 Mbit/sec. So I will order it but till now What if I change the firmware baud rate to lower? in our final application STM32L4 will connect to BLE thorugh and UART and it receives command so we need to change the baud rate. So is it good to change the baudrate?

Point#2: You mean to say that RTS and DTR lines are connected to CP2102? If it is connected to CP2102 then how it can be configured by GUI application?

Point#3: GND is connedcted to another side of board so it is not visible. BLUE - Tx, GREEN - RX and BLACK -GND.

Point#4: Give me some I will ask my hardware engineer to capture the waveforms and send it to you.

[SPraj.1]

Hello Nick,

As ou said we have changed the USB UART converter and connect RTS and DTR. But still we are getting same result. I am attaching all the images for your reference.

[Nick K]

Hello,

let me summarize, based on the discussion, how to replace the ST25RU3993 EVAL/HPEV onboard FT231 IC

• Unsolder U13 or put U13 (onboard FT231) into reset mode by remove R6 and short C33
• Connect your own USB-UART converter at J7 by using RX, TX, DTR and RTS pins.
• IMPORTANT: To avoid FW changes a USB-UART convert IC supporting 3MB is required.
• IMPORTANT: DTR and RTS pins are used to control RST and BOOT0 pins of onboard STM32L4 and needed for proper board booting
• Use ST25RU3993 Reader Suite GUI and connect to the board through your own UART-USB converter
• Alternative: Develop your own UHF Host application. For this it is recommended to have a look at the STUHFL_demo source code example and follow the connection procedure.
  • Connect to COMxx with 8N1 and 3MBit/sec
  • set DTR high, to force STM32L4 start from user code
  • toggle RTS (high -> low), to restart the board
  • Wait ~400ms to give board time to boot

BR