Skip to main content
Math86
Associate II
Jun 2, 2021 10:18 AM UTC
Question

Help connecting to STM32 on Cube Programmer

Hello everyone,

I have a PCB with an embedded STM32F103 on it. The PCB provides access to some ports on the side. Those are linked to VDD, PA9, PA10, PA13, PA14 and GND.

0693W00000BZseOQAT.jpgI tried connecting to it with Cube Programmer using a FT232RL as pictured below :

0693W00000BZsfRQAT.jpg 

The connections are :

3.3 v -- VDD

GND -- GND

RX -- PA10

TX -- PA9

When I try to connect with Cube Programmer it shows an error :

0693W00000BZsdqQAD.pngI tried all baud rates as I have no idea which one I should use but still no luck.

On the PCB it looks like pin boot 0 is connected to a resistance which is connected straight to ground and same for pin PB2.

Any idea on what I am doing wrong ? (I'm fairly new to this so it might be a stupid mistake)

Thanks in advance !

This topic has been closed for replies.

8 replies

Tomas SIRUCEK
Visitor II
Jun 2, 2021 12:23 PM UTC

Hi,

If You need to connect to MCU using UART, You need to first enter embedded bootloader. To do so, You need to connect BOOT0 pin to VDD and then reset MCU. Then it should be possible to connect to MCU from CubeProgrammer.

Have a nice day,

Tomas

Math86
Math86Author
Associate II
Jun 2, 2021 1:19 PM UTC

Would it be the same procedure if I tried with a ST link ?​

Tomas SIRUCEK
Visitor II
Jun 2, 2021 1:24 PM UTC

Using ST Link and SWD interface (SWDIO and SWCLK pins), You do not need to pull BOOT pin high. If it will not connect, try to use reset pin as well and use option "Connect Under Reset".

Tesla DeLorean
Guru
Jun 2, 2021 1:11 PM UTC

Given the effort to obfuscate the part number,and lock the device to a specific vehicle or VIN#, I'd imagine the part is locked down so you can't read out the firmware.

Tips, Buy me a coffee, or three.. PayPal Venmo (See Profile) Up vote any posts that you find helpful, it shows what's working..
Math86
Math86Author
Associate II
Jun 2, 2021 1:18 PM UTC

Fair point, I think so too. ​Would the error mean that the MCU is locked ?