cancel
Showing results for 
Search instead for 
Did you mean: 

Programming header and Debug Header for STM32L073 micro?

amass.9
Associate II

Hi,

I am laying out  aboard with STM32L073. I would like to add a debug header and a programming header. Do you know which pins i should connect  these headers to?

 

I see that PA13 and PA14 are involved in debugging, but which other pins do i also need to include in the header?

6 REPLIES 6

VCC and GND

NRST to allow for controlled startup

On CM3,4,7 consider PB3 / SWO, but not supported on CM0(+) parts

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

Thanks, by CM3, CM4, CM7, do you mean the Cortex-M thing?

How would i know if i have a CM3 say?

The part number is

STM32L073CBU6 (LQFP48)


@amass.9 wrote:

How would i know if i have a CM3 say?


It would certainly be stated in the datasheet.

Most likely even in the marketing material; eg,

https://www.st.com/en/microcontrollers-microprocessors/stm32l0-series.html 

STM32L0 is Cortex-M0+ 

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.

@Tesla DeLorean wrote:

VCC and GND


@amass.9 Note that, for many debug probes (including ST-Link), they need this VCC connection to sense the power on the Target - not supply power to the target.

 

In addition to the basic GND, VCC, SWDIO, SWCLK, NRST, you might also consider providing a UART pin - especially on a part with no SWO ...

 

Be sure to study Application note AN4467Getting started with STM32L0xx hardware development:

https://www.st.com/resource/en/application_note/an4467-getting-started-with-stm32l0xx-hardware-development-stmicroelectronics.pdf

And, of course, the datasheet.

Also, take a look at the ST board designs (Discovery, Nucleo, whatever).

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.

Thanks, due to your kind replies,  i now know that for debugging on STM32L073 we need  GND, VCC, SWDIO, SWCLK, NRST,  and a UART pin in the header.

Do you know what pins are needed for programming?

It does seem that you are lacking some rather basic understandings to be laying out a PCB!

I suggest that you spend some (more?) time with a Nucleo (or similar) board get familiar with the product before getting into custom PCB design.

 


@amass.9 wrote:

for debugging on STM32L073 we need  GND, VCC, SWDIO, SWCLK, NRST,  and a UART pin in the header.


Well, you don't strictly need a UART - but it comes in very handy!

 


@amass.9 wrote:

Do you know what pins are needed for programming?


The SWD connection is used for both programming and debugging.

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.