cancel
Showing results for 
Search instead for 
Did you mean: 

Programming STM32F405 in bootloader mode via stm32cube programmer command line interface at the address 0x08008000, the programming processes completes successfully but the controller does nothing afterwards I don't understand why?

TGhau.2088
Associate II

I am student developing an app that uses the STM32CubeProgrammer command line interface executable to program STM32F405.

The controller works as excepted if it is programmed at the address 0x08000000.

but sometimes the programming processes fails or stops halfway.

3 REPLIES 3

Going to be hard to guess. We know very little about the computers and boards envolved, if this is a custom board, or has secondary power, reset or watchdog issues. A design isn't going to get more reliable in bootloader mode.

USB DFU or UART mode?

Perhaps try using the original Flash Loader Demonstrator application, it should support UART mode on the F405 series, or one of the several open source apps based on the published UART protocol.

For DFU, try the DFU Manager / DfuSe Tool

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

Yes its a custom board.

The USB appears in bootloader mode.

I have already tried DfuSe Tool i was running into driver issues as the DfuSe tool wasn't able to detect the Microcontroller.

Plus I am using a ATtiny to controller the RST, Boot0 and boot1

command:

STM32_Programmer_CLI.exe -c port=USB1 -w C:/Users/Taha/Documents/MC_3W_HW1.0_SW4.02.bin 0x08000000

this is what I get while programming:

Warning: Wrong write command parameters: /c stm32_programmer_cli.exe

Memory Programming ...

Opening and parsing file: APP_3W_HW1.0_SW1.1_InductiveSensor.bin

File : APP_3W_HW1.0_SW1.1_InductiveSensor.bin

Size : 32620 Bytes

Address : 0x08000000

Erasing memory corresponding to segment 0:

Erasing internal memory sectors [0 1]

erasing sector 0000 @: 0x08000000 done

erasing sector 0001 @: 0x08004000 done

Download in Progress:

�������������������������������������������������� 0%

��� 6%��� 12%��� 18%��� 25%��� 31%��� 37%��� 43%���� 50%��� 56%��� 62%��� 68%��� 75%��� 81%��� 87%��� 93%���� 100%

File download complete

Time elapsed during download operation: 00:00:01.444