STM32 ARM Microcontroller Bootloaders / Dfuse / ST link / Serial Flashloader 

Unbelievably clear and concise explanation … finally moving into the world of stm32 programming and this is one of the most direct and easy to understand vids yet!! Thank you!

Thank you very much. That video helped me to figure out that I was missing the JP1 jumper - without that jumper the main MCU won't get power at all. I was basically doing everything right which your video confirmed me.

Very clean presentation, really appreciated! The discovery board was just sitting on my desk for days , now I know where to start at least.

Thanks for explaning. The video is so much useful to upload my source code to stm32 mcu.

Very clear and strait forward. Thanks for making this so easy.

Hi To suppose that connection between a fpga and mcu and display and amplifier’s ic and all of them are connected to cpu. This is a media player package. 1-what is mcu duty? 2-where is save mcu’s program ? 3-at this case, mcu is controller or i/o ? Thanks 🙏🏼

This is super useful. I was always trying to use the mbed drag and drop method on my nucleo board. But this seems to be the way to go. Thanks

Why do we program the microcontroller using bootloader when we have an ST-Link on board to do the same thing ?

So resetting with the BOOT0 pin, enables *BOTH* programming ports... USART3 (Flash Loader Demonstrator) *AND* via usb-otg (DfuSe Demo v3.0.5)? Are there any times when the built-in bootloader should be used versus the St-Link/SWD? For example, can St-Link program the micropython .dfu/.bin file? Also, any thoughts on writing a custom bootloader like 'stm32duino bootloader' or 'STM32_HID_bootloader'? For example, if you want to update the application in-system via the user usb-otg but without changing jumpers... can you the flash the area that it's currently running from? Or would you have to allocate the new bootloder at the reset address (0x8000000) and place the user application elsewhere..i.e. so that it can be flashed from the custom bootloader?

Hey 0033mer, I watched Andreas Spies's recent upload about Micropython, and was talking about forth yesterday with a few people. I was given a reference to Mecrisp Forth and JeeLabs as a way to play with forth on ARM hardware. I've skimmed the basics and know that Mecrisp was originally intended for the MSP430's, is open source, and has been ported to the STM32 as well. Is there a difference between Mecrisp and the Forth software your using on different microcontrollers? Also, I am under the impression you don't use the Arduino IDE. One alternative that several people seem to prefer is the PlatformIO extension w/Atom text editor (if you can still call Atom a text editor at this point). I was also told about "GEANY" as a better environment for using the newer Ardy IDE CLI option with GCC and AVRdude. I haven't looked into it yet but I'm curious if you use other more up to date and feature rich platforms like these or are you using forth for all/most of your projects? Lastly, I came across another reference yesterday that got me to start a new playlist on Forth that I named IDE Forth, (because of my personal alphabetical indexing even though it isn't an IDE). That upload I mentioned was based on Mecrisp Forth and the bluepill. He went into how Forth dictionaries work and how words can be "stacked" and built upon to create more complex code functions. He also covers a bit of information about initial setup of registers for IO as opposed to how the Arduino IDE automatically configures these. Later he uses the hardware level info to demonstrate the basics of Forth code optimization by disassembling a section of code. You do a great job of introducing your audience to Forth and it's interpretation features. I had a basic grasp of the potential of Forth from watching your uploads, but I didn't understand the dictionary and stack like I do after watching the aforementioned reference. I'll go find the link to his upload and post it as a reply to this message to avoid the main YT auto-spam filter. I have followed your links to more info about forth, but after reading a good bit I had to put this on my list of things to do as a dedicated project, as I need to spend a lot more time dedicated to the task in order to follow detailed instructions. By seeing a bit more of the inner workings "under the hood" I have a much better grasp of where I can go with this, and I can play with this as a side project until I have more time and am ready to go into depth more I just wanted to share that last one because your kinda the Forth Guru on YT ;) Thanks for the upload and introduction to Forth. -Jake

As usual just what I needed. : = }}

best explanation yet I came across

Excellent stuff! Clarifies many things. Thanks.

Sir how can i program hex file using bluetooth , GSM module or WIFI module please tell any one of them

You are great , thank you very much .

I have tried to use "Flash Loader Demonstrator" for a new STM32F051R8. In the MCU have no firmware to initial USART peripheral. It didn't work in this case.

Thanks for the great video. With DFU Demo 3.0.5 from DFuSe, I am having an issue that the tool said the upgrade is successful but the transferred data size is 0KB of 0KB. Thus the upgrade was actually not successful. Details as follows: When I generate a DFU file from a Hex/S19/BIN file with "DFU File Manager", I think I must input the information below: 1.Target ID 2.VID 3.PID 4.Version 5.Target Name 6. Starting address (if binary file is the file to generate DFU file) I have studied and compared many sources and here is something I want to try again shortly (I only put.VID: 0x0483 previously) 1.Target ID: 0x00 2.VID: 0x0483 3.PID: 0xDF11 4.Version: 0x011A 5.Target Name: Internal Flash 6. Starting address (if binary file is the file to generate DFU file): 0x0800 3000 Could you comment whether they are correct or important?

Hello, Is it possible to do that over half duplex rs485 line? Thanks for your answer...

Thank you for the excellent video tutorial ! I would please like to ask: you mentioned that the video "cover three boot-loaders", but isn't it more correct to say that the 3 host tools are all using one bootloader ? (as far as I know there is only one bootloader in rom from ST) Thanks!

bin or hex file, are they same? can upload to stm32f4 using stm32 utility?

If programming using the STlink via the SWD, does boot0 still needs to be pulled to high?

Thanks. Can I use the Arduino IDE and USB as well?

i am using STEVAL-STLCX01V1. It is not recognized in my computer. how do i make it recognize? (i am using windows 7 as my os)

There is another way, using another bootloader stored in regular program flash, like when using with arduino ide and wanting to upload sketches via the other USB connector.

thank you.can i use a another usart like usart2 ?? or just usart1 and usart3

My STM32F103C8 bluepill is not getting recognized. how do i fix this problem? I cannot update any driver into it too...

Thanks 0033mer, for the useful video. You have a nice way explaining that makes it easy to understand. I have been using PIC 8-bit microcontrollers for more than a decade, but am new to STM32 uCs. I have a Blue Pill board with STM32F103C8T6 uC and 64K flash. I have replaced the R10 (10K) with a 1.5K resistor, successfully uploaded the boot loader file from GitHub (generic_boot20_pc13.bin) through ST Link-V2 and installed the required drivers. But when I connect to the USB port, I always get the message "USB Device Not Recognized". My OS is Windows 7. Can you offer some help?

perfect nice job

When the "DFU file manager" is used with a Hex file as the input, the data address 0x0800 0000 is inserted into the generated DFU file automatically followed by the data size (compliant with DFU file spec named UM0391) When a binary file is used for generating a DFU file, a default address 0x0000 0000 is inserted into the DFU file unless I manually change something like 0x0800 3000 in the GUI. Should I ensure the address of 0x0800 3000 (or something else) be inside a DFU file, in the field of wElementAddress (starting address of the data)? Or, the USB driver will take care of the actual internal flash address of the STM boardto write onto ?

Helpful