Skip to main content
Amahm.2142
Associate
December 8, 2019
Question

STM32G030C6t6 Problem in Flash Loader (v2.8)

  • December 8, 2019
  • 10 replies
  • 1842 views

Hi

I made the processor STM32G030C6t6 , STM32G030K6t6 because it will be 

cheap in the future and have a lot of use for it.

I use the Flash Loder Dmonstrator program for the STM32 processor program.

Due to the high number of daily programs and I have my own automatic programmer working with port COM.

The program identifies Flash Loder (v2.8) find processors but does not 

have program addresses and does not work.

Please prepare a new edit to fix this issue.

Thanks

This topic has been closed for replies.

10 replies

Amel NASRI
ST Technical Moderator
December 19, 2019

Hello @Amahm.2142​ ,

STM32G0 is a new product that is not supported in FlashLoader.

You need to use STM32CubeProgrammer.

-Amel

To give better visibility on the answered topics, please click on "Best Answer" on the reply which solved your issue or answered your question.
Amahm.2142
Associate
December 31, 2019

Hi@Amel

I know that but the program (STM32CubeProgrammer)design for

programing chip one by one by user.

As I said before, maybe flash 8k chip in someday.

And this is by simulation Flash Loader.

Thanks for your comment.

Tesla DeLorean
Guru
December 19, 2019

The NEW part is not explicitly supported in OLD software. Wouldn't expect a lot of updates on it.

The underlying protocol should remain the same, if you write your own programmer software against the USART loader protocol you won't be beholden to ST's priorities to move to the newer STM32 Cube Programmer.

Tips, Buy me a coffee, or three.. PayPal Venmo (See Profile) Up vote any posts that you find helpful, it shows what's working..
Amahm.2142
Associate
December 31, 2019

Hi@clive1

You are right.

but it is so hard to Changes it.

Thanks for your comment and your time.

Tesla DeLorean
Guru
December 31, 2019

On the scale of complexity of the things I've had to write/build over the years, this honestly is fairly simple.

Segger historically had programming libraries and stand-alone programmers. As the STM32 families have gotten more popular more people have built/sold standalone programmers.

If you want something that scales to high volumes you might want to build your own test fixturing, perhaps using another STM32 to program one or many devices at once.

Tips, Buy me a coffee, or three.. PayPal Venmo (See Profile) Up vote any posts that you find helpful, it shows what's working..
Samira Foroughi
Associate II
March 11, 2020

Hi

I too have this problem.

I used the cube programmer for the stm32G03 micro-series but there is a problem:

According to stm company video tutorial I first programmed the micro by st link. Then by changing the option byte, I put the micro into boot mode.

To do this, I set the nboo0 checkbox to unselected and apply.

Then I expected to detect the micro in uart mode after placing the board in boot mode, without the st link being connected. Just like the first time it was empty. But unfortunately it only connects if the st link is connected.

Is there a way to re-program the micro in uart mode without stlink, just like the first time it was empty?

In addition, I'm also requesting an update to the flash loader program to support the new micro.

Thankful

Amahm.2142
Associate
March 14, 2020

Hi@Samira

I had previously created a programmer that could program many processors at the same time as a serial port and I can program them repeatedly.

 But with a problem with the new G030 series, rewriting must be programmed option byte (nboo0)to zero by another port !!!

These are weird forms and I don't know why they didn't think of them.

This problem can no longer be easily programmed with the serial port.

This problem reminds me of years ago when I used the AVR family. One Registry had an oscillator control input frequency to the processor 

if you had an external crystal and this register on the input oscillator would no longer pass through the data processor. 

The working month changed the value of the registry automatically, and we hardly attached an external oscillator and then programmed that registry.

Then you could re-program it.

I hope ST company does something about this problem.

Good luck.