cancel
Showing results for 
Search instead for 
Did you mean: 

Pinout to read stm32F103zet6 using ST-LINK

tomero
Associate II

Hi,

I want to know pinout to read flash from CHIP stm32F103zet6 using ST-LINK.

Can someone provide it, im new on STM32 chip.

 

Thanks.

14 REPLIES 14
Andrew Neil
Super User

The pinout of the chip will be in its datasheet.

The pinout of the ST-Link will be in its User Manual.

 

If the STM32 is already programmed by someone else, it might be read-protected...

 


@tomero wrote:

I'm new on STM32 chip.


Are you familiar with any other microcontroller(s) ?

 

Here are some getting started tips:

https://community.st.com/t5/stm32-mcus-products/for-better-learning-stm32-programming-and-debugging/m-p/719485/highlight/true#M260696

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

Im very stuck to reading pinout from datasheet, but I try configuration like this:

tomero_0-1750425733666.png

But still not connected. Btw, I just want to connect it for read flash test.

avinash_elec
Associate III

Is your STM32 on a development board? or a bare chip? If its on a board then tell us about the board like its name and make. Other wise if you are using bare chips, it still need few more connection in order to work. Like there are so many VCC pins but you have connected only one of them. Proper level on RESET and boot pins also required and decoupling capacitors also.


@tomero wrote:

Im very stuck to reading pinout from datasheet


It's all in Table 5:

AndrewNeil_1-1750429328113.png

https://www.st.com/resource/en/datasheet/stm32f103ze.pdf#page=35

via: https://www.st.com/en/microcontrollers-microprocessors/stm32f103ze.html#documentation

 

Note that this is not a genuine ST-Link - it's a clone:

AndrewNeil_0-1750428736722.png

See How to recognize a genuine ST-LINK/V2 versus a cloned one; in particular, this comment.

Double-check that you have the pinout correct for the actual clone you have - as noted in the above comment.

 

You need to connect:

  • SWDIO pin from the ST-Link to the SWDIO pin on the STM32;
  • SWCLK pin from the ST-Link to the SWCLK pin on the STM32;
  • RST pin from the ST-Link to the NRST pin on the STM32.

Plus 3.3V and GND

As @avinash_elec said, the STM32 needs to be in a functional circuit.

 


@tomero wrote:

I just want to connect it for read flash test.


Why do you need to do that?

I hope you're not trying to steal someone's code ... ?

 

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

SWDIO = PA13

SWCLK = PA14

NRESET = NRST

GND = VSS (All), VSSA, VREF-

3V3 = VDD (All), VDDA, VREF+

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..

Yeah, it looks like you're just randomly picking pins hoping for a connection.

The SWDIO and SWCLK are on the other side of the chip

KarlYamashita_0-1750466295176.png

 

I was told that if a devices starts to smoke, put the smoke back in. I guess I never got all the smoke because the device never worked afterwards.
Don't worry, I won't byte.
TimerCallback tutorial! | UART and DMA Idle tutorial!

If you find my solution useful, please click the Accept as Solution so others see the solution.

Thank you for your response and good explain. I will try it.

 


@Andrew Neil wrote:

Why do you need to do that?


I have buy device with broken chip and its too slow response for the support, so I want to buy new one and backup the firmware for next repair.


@tomero wrote:

Thank you for your response and good explain. I will try it.

 


@Andrew Neil wrote:

Why do you need to do that?


I have buy device with broken chip and its too slow response for the support, so I want to buy new one and backup the firmware for next repair.


Well, you better hope the other STM32 isn't code protected. If it is, you're not going to be able to read the memory and save it. 

I was told that if a devices starts to smoke, put the smoke back in. I guess I never got all the smoke because the device never worked afterwards.
Don't worry, I won't byte.
TimerCallback tutorial! | UART and DMA Idle tutorial!

If you find my solution useful, please click the Accept as Solution so others see the solution.

This is to the point, I will try this one.

tomero_0-1750467724216.png

Thank you.