2020-04-02 04:28 AM
2020-04-02 04:58 AM
Try reviewing application note AN2606
2020-04-02 06:40 AM
The bootloader does not support debugging. It is meant for programming. The SWD interface (ST-Link) is meant for the usual programming/debugging.
2020-04-02 10:26 AM
The ROM loader comes on the parts as delivered.
The most critical hardware consideration is NOT to generate noise on interfaces other than the one(s) you want to use. For example don't connect a GPS receiver to a USART the loader is looking for.
Use an interface you expose. If you have a RS232 port on product, connect the boot loader USART to that, so you can program in factory or field.
If you don't normally provide a USART port, expose one to pin headers or test points for factory use.
2020-04-02 10:27 PM
The document explains connection for uart and DFU USB,can i have some circuit example for Boot pin and how to set and reset nBoot1 bit.
2020-04-02 11:26 PM
For normal operation BOOT0 should be pulled low externally. If using a BOOT button logic would be reverse that of the RESET
Sure there is an Option Byte programming example in HAL libraries, shouldn't need to change.
2020-04-03 12:12 AM
Thanks ,but just for clarification
When i make BOOT pin high and program booloader using UART,then making Boot pin low will run this latest program from flash ,and i don't need to make boot pin high forever till i again need to reprogram.
2020-04-03 12:22 AM
BOOT0 pin just needs to be high across reset. Many boards, like flight controllers, have two buttons, you press the BOOT button, press and release RESET, then release BOOT, chip starts in ROM based system loader, connects via serial, or USB/DFU device.
BOOT pin latched at reset.
Must not let it float, will run into startup issues if supply slow to rise, internal core running at 1.2V, VIL/VIH thresholds a bit sketchy at that point.
2020-04-03 03:08 AM
once this is done ,program will be in flash memory ?