Skip to main content
JPehl.1
Associate III
October 27, 2020
Solved

STM32F070CBT6TR does not run

  • October 27, 2020
  • 6 replies
  • 1334 views

Hi.

I am using MCU STM32F070CBT6TR on my custom board, I do use ST-LINK/V2 as hardware tool, and I have configured the boot options according to this:

0693W0000059Uu7QAE.jpg0693W0000059UuRQAU.jpg 

But in fact the MCU is not running the code, it keeps in lockup state, and then I am not able to debug the code on Utility nor in the IDE, because the MCU doesn't even run. 

Pin 44 (BOOT0) is connected directly to GND.

Pin 7 (NRST) have a pull-up of 4.7K and is measuring 3.3V

What I am doing wrong?

This topic has been closed for replies.
Best answer by JPehl.1

Hi.

Problem solved...

We changed the lib used to generate the binaries.

6 replies

MM..1
Super User
October 27, 2020

Maybe Note 1 is active , have you realy loaded code to start ADDR flash.?

JPehl.1
JPehl.1Author
Associate III
October 27, 2020

Hi.

What you mean with "Note 1"? I don't know what is this.

Yes, we can read the binary that we downloaded to its memory.

MM..1
Super User
October 27, 2020

Note 1 is under your table on image about boot modes. And you can load and read binary, but on bad address.

Too try uncheck nBoot1

JPehl.1
JPehl.1Author
Associate III
October 27, 2020

Hi.

unchecking "nBoot1" makes no difference.

Theoretically the binary is being put at the correct memory address, and the empty check was validated, and we should consider that the content is at address 0x0800 0000

0693W0000059Wq2QAE.jpg 

Is there any other detail that could still make the system boot at system memory and not on flash memory?

MM..1
Super User
October 27, 2020

Hmm possible is two problems when you use bin. Maybe code need be loaded to other address and on start need bootloader code.

Too your 0 vector 2000C000 isnt as i see standart, but when i good rememmber start prog is +4 and this seems be ok.

I recommend debug code, because here we stucks.

JPehl.1
JPehl.1AuthorBest answer
Associate III
October 27, 2020

Hi.

Problem solved...

We changed the lib used to generate the binaries.