Stm32cubeprogrammer

[AAkin.1]

Hi,

​I just got a PCB with integrated stm32f0... Chip, which can be flash though ISP,usart, UART, Swd..

​

​

But I downloaded the stm32cubeprogrammer to flash the chip as the hex and bin file was sent to me I keep getting the error o the bootloader stuff,

​

decide to follow online steps to install the stm32bootloader.bat from DFU driver via the command line, and although the command prompt is correct and the directory file but the driver didn't install. Please what is the issue I am using Window 10 Os.

​

Thanks.

​

[MM..1]

You dont write how connection you plan to use or have onboard, but system bootloader support basicaly only one way designed for PC. UART.

When your f0.. have USB FS then second way exist DFU over USB. Only this one need driver in Windows10.

?

[AAkin.1]

Thanks alot for your prompt response, let me just be clear enough.

​

I​ got a customized PCB with the stm32f070CBT6 chip on it

And on the datasheet of the PCB, it can be flashed through

1. SPI interface

2. UART interface

3. SWD interface.

​​I also got the hex file to flash the chip,

But when I install stm32cubeprogrammer and flashloader I couldn't flash the MCU with the programmer I have,

>> USBasp(using the SPI interface as recommended in the datasheet)

​

>> FTDI programmer (using the UART interface)

​

But every time I to connect I get the error

" Error: Activating device:KO. Please, very the boot mode configuration and check the serial Port configuration. Reset your device "

​

I​ guess it was the stm32 bootloader that have not been installed to connect and communicate with the external programmer, I follow an online step to install the stm33bootloader by executing the file stm33bootloader.bat, during this execution the DFU_Driver was unable to be initialise, and the stm32 bootloader was not installed s well, during the execution I I'll see a window comes up like that of CMD prompt and dissapear Sharply with nothing been done.

​

So I was wondering what might be wrong, although i

Don't have the defuse driver install.

​

So my problem is I cant install the bootloader for the stm32 through the command line executing stm32bootloader.bat from the directory folder. And I can connect the stm32 MCU with the stm32cubeprogrammer.

​

I​ am using Window 10 Os what do you think might be wrong.

​

Thanks in advance​

[AAkin.1]

*stm32bootloader and stm32bootloader.bat not stm33bootloader typographical error.

​

​

Thanks :folded_hands:​

[MM..1]

I mean first choice is defined by schematics of your custom PCB. Here you have an pinout for programming, and this define how interface use.

As primary for develop is used SWD . This dont need bootloaders and you flash over it hex directly with utility.

Then you need check and write how you realy do.

[AAkin.1]

Yes, you are right!

But the pins of the SWD interface required a special connector please see attached, which I don't have currently, I was wondering how to use the SPI and UART interface I have.

​

Thanks​

​

[MM..1]

OK then you need read application note about howto start system bootloader, because this is first step to support SPI and-or UART.

Too appnote define only some uart or spi for using. Simply you need start power your board in special BOOT mode and on your image i dont see boot pin for this, then you need read docs.

Only after this you need PC and can try FTDI ...

[TDK]

> ​decide to follow online steps to install the stm32bootloader.bat from DFU driver via the command line

> I was wondering how to use the SPI and UART interface I have.

DFU is specific to USB. Do you have USB connected?

If not, you'll need a USB to UART converter and hook that up to USART1, assuming those are hooked up to supported pins per AN2606. Then put the chip in bootloader mode (hold BOOT0=3.3V during reset) and upload.

[AAkin.1]

​Hi thanks for your response but I tried it with usb to uart converter cp2102, but the error is thesame

​" Error: Activating device:KO. Please, verify the boot mode configuration and check the serial Port configuration. Reset your device..and try again "

​