Hey thanks for this video I'm busy learning about DFU and boot loaders for the STM32 your videos helped me alot I really appreciate the effort you put into this.
Thanks a lot for the video and I have shared with some Geek friends 😁 This is exactly what I was looking for but now I need to find out how to get .dfu files from my project output in Keil Uvision v5
I think I mentioned this in the video, and if not, then their is a small program that you need to use that converts from bin to DFU file. You can't output it directly from the compilers.
@@Weblearning1 Yes I am sorry you did explain it very well. I have just started with the STM32 and this video was a great help to get me going. I found another project to that uses some files and a batch script in Keil, so that when you build your code in Keil, it automatically converts it from hex to dfu and flashes it to your board all in one go. Here is the project page with some comments of what I found out to fix a small error in that batch file. hackaday.io/project/4139-stm32-dfu-file-converter/discussion-124728
Thank you so much man! Your video helped me a lot in my project. Keep up the good work, man. Cheers! I have one doubt though, I am using the STM32 NucIeo F446RE board as the usb-dfu target and I am using VDD to give HIGH to the BOOT0 pin but the partitions are not always visible on the DfuSe software. I connect the VDD to BOOT0 when STM is in normal mode, then I hit the reset button, then the STM leaves the normal mode and most probably enters the DFU mode but the partition doesn't show up many times, then I remove the wire from VDD. How to make the partitions visible on the software consistently when entering the bootloader mode? Is there something wrong in the procedure I am following? Thanks
Hi. it could be that there is some noise or voltage on the other peripherals and that holds the bootloader at the different peripheral then the dfu. Make sure that there is nothing connected to any of the peripherals, you can read an2606 about this. Also, check the timing. It could be that the PC is not answering fast enough and that can cause the bootloader also to hang.
Hello, Thanks for the Video! I am trying to make my own board, but the problem is that when I program the micro using the stlink, it dies (smoking!). The thing is that I've designed Boot0 and Boot1 to GND directly with no resistor, and the OSC32_IN to GND and the OSC32_OUT to sink the current from a pair resistor-led connected to the 3.3v. Idk why it is burning my stm32f103c8 when I program it. Could you help me?
It could be many things. 1. I would use a bench power supply and make sure not to have current about 50mA. If you dont have one, use a resistor ( depending on the voltage, you need to figure out the current ) or you can use a fuse. It could also be the programmer that you are using, or some other connection. Its hard to tell without seeing the schismatic design. Try measuring with DVM every connection that you have and see if you see Vdd when you should see GND, or GND when you need to see Vdd. That could be the reason.
How can one read the Stm32's Bootloader Version/ID? I understand not all chips support all bootloading peripherals (uart, spi, etc). For example, for the H74xxx devices, only the newest bootloader version 9 (0x90) supports FD-CAN, the previous versions 13.x (0xD2, 0xD3) don't! According to AN2606, "the bootloader ID is programmed in the last byte address - 1 of the device system memory and can be read by using the bootloader “Read memory” command or by direct access to the system memory via JTAG/SWD." But setting a pointer and reading from memory (0x1FF1E7FE) didn't work.. does it have to already be executing from the bootloader (BOOT0=3.3v)?
Hello. This is a very useful video thank you. I have a question. i trying to communicate with microcontroller but it is not board and i will program it first time but i cannot use dfu mode. it is seem as unknown device. what can i do ? firstly should i open usb botlooder ? if yes how can program it? how can i comminicate with microcontroller first time? thank you for answer.
As to the app note from ST, the F103 doesn't have DFU ( Table 3 ): www.st.com/content/ccc/resource/technical/document/application_note/b9/9b/16/3a/12/1e/40/0c/CD00167594.pdf/files/CD00167594.pdf/jcr:content/translations/en.CD00167594.pdf
@@Weblearning1 I cannot get into to DFU mode. What can be the possible reasons for this? Do I need to configure some stuff with code first? Also how can i debug betaflight onto board using cubemx?
![Blox Fruits Dragon Rework Update [Full Stream]](http://i.ytimg.com/vi/EqDAp8udhm0/mqdefault.jpg)
Hey thanks for this video I'm busy learning about DFU and boot loaders for the STM32 your videos helped me alot I really appreciate the effort you put into this.
Thanks. If you can, share them with others...
I will. I did. you deserve more views.
Thanks! This cleared up a lot :)
Thanks a lot for the video and I have shared with some Geek friends 😁 This is exactly what I was looking for but now I need to find out how to get .dfu files from my project output in Keil Uvision v5
I think I mentioned this in the video, and if not, then their is a small program that you need to use that converts from bin to DFU file. You can't output it directly from the compilers.
@@Weblearning1 Yes I am sorry you did explain it very well. I have just started with the STM32 and this video was a great help to get me going. I found another project to that uses some files and a batch script in Keil, so that when you build your code in Keil, it automatically converts it from hex to dfu and flashes it to your board all in one go. Here is the project page with some comments of what I found out to fix a small error in that batch file. hackaday.io/project/4139-stm32-dfu-file-converter/discussion-124728
Thanks for sharing
How do you change the option bytes? There's a dialog in STM's instructions, but it's not clear how to get to it
To what do you want to change the Option Bytes?
Have a look at this video: ruclips.net/video/CI1BcIN7qC4/видео.html
@@Weblearning1 Thank you! I'll check out that tool. Just want to do what I can to make sure someone can't dump my binary back out
Thank you so much man! Your video helped me a lot in my project. Keep up the good work, man. Cheers!
I have one doubt though, I am using the STM32 NucIeo F446RE board as the usb-dfu target and I am using VDD to give HIGH to the BOOT0 pin but the partitions are not always visible on the DfuSe software. I connect the VDD to BOOT0 when STM is in normal mode, then I hit the reset button, then the STM leaves the normal mode and most probably enters the DFU mode but the partition doesn't show up many times, then I remove the wire from VDD. How to make the partitions visible on the software consistently when entering the bootloader mode? Is there something wrong in the procedure I am following?
Thanks
Hi. it could be that there is some noise or voltage on the other peripherals and that holds the bootloader at the different peripheral then the dfu. Make sure that there is nothing connected to any of the peripherals, you can read an2606 about this. Also, check the timing. It could be that the PC is not answering fast enough and that can cause the bootloader also to hang.
Hello, Thanks for the Video! I am trying to make my own board, but the problem is that when I program the micro using the stlink, it dies (smoking!). The thing is that I've designed Boot0 and Boot1 to GND directly with no resistor, and the OSC32_IN to GND and the OSC32_OUT to sink the current from a pair resistor-led connected to the 3.3v. Idk why it is burning my stm32f103c8 when I program it. Could you help me?
It could be many things. 1. I would use a bench power supply and make sure not to have current about 50mA. If you dont have one, use a resistor ( depending on the voltage, you need to figure out the current ) or you can use a fuse. It could also be the programmer that you are using, or some other connection. Its hard to tell without seeing the schismatic design. Try measuring with DVM every connection that you have and see if you see Vdd when you should see GND, or GND when you need to see Vdd. That could be the reason.
what to do when pc dont recognize DFU mode? A request for the USB device descriptor failed.
What STM32 device are you using? Did you try also with the new CubeProgrammer?
@@Weblearning1 how we can made the leaveDFU witht the new cube programmer?
How can one read the Stm32's Bootloader Version/ID? I understand not all chips support all bootloading peripherals (uart, spi, etc). For example, for the H74xxx devices, only the newest bootloader version 9 (0x90) supports FD-CAN, the previous versions 13.x (0xD2, 0xD3) don't!
According to AN2606, "the bootloader ID is programmed in the last byte address - 1 of the device system memory and can be read by using the bootloader “Read memory” command or by direct access to the system memory via JTAG/SWD." But setting a pointer and reading from memory (0x1FF1E7FE) didn't work.. does it have to already be executing from the bootloader (BOOT0=3.3v)?
You can use the CuebProgrammer to read the memory address that is mentioned in AN2606 and then you can see what is the Ver.
Hello. This is a very useful video thank you. I have a question. i trying to communicate with microcontroller but it is not board and i will program it first time but i cannot use dfu mode. it is seem as unknown device. what can i do ? firstly should i open usb botlooder ? if yes how can program it? how can i comminicate with microcontroller first time? thank you for answer.
What is the part number of the device?
stm32f072c8
You have to follow my instruction on how to enter bootloader using the boot0 pin. If you don't have access to this pin, you can't enter the dfu mode.
Can I upload code to the same processor over and over again this way?
Yes.
can this work with the stm32f103c8 board
As to the app note from ST, the F103 doesn't have DFU ( Table 3 ):
www.st.com/content/ccc/resource/technical/document/application_note/b9/9b/16/3a/12/1e/40/0c/CD00167594.pdf/files/CD00167594.pdf/jcr:content/translations/en.CD00167594.pdf
Can anybody explain how can i use bootloader to flash betaflight firmware to nucleo f446re?
If you have the code and its for the F446, then you can use this video or the STM32CubeProgrammer.
@@Weblearning1 I cannot get into to DFU mode. What can be the possible reasons for this? Do I need to configure some stuff with code first?
Also how can i debug betaflight onto board using cubemx?
STM32 timed out programming : failed
How can I correct this
Its could be that you have something else connected to one of the bootloader pines.
@@Weblearning1 I have connected a mouse bro