Add config header

[crvux]

Config header allows customize some bootloader parameters like USB
Device Descriptor fields in user_config.h file.

[davidgfnet]

Hey! You still up for merge? :P

[crvux]

Yes! :)

[davidgfnet]

Left a comment (review) in the code for you to reply

[crvux]

Sorry, but I couldn't find your review. Can you post review URL?

[davidgfnet]

Comments get inlined in the code in github, it's a matter of going to the "Files changed" tab to see them.

[Ralim]

Hello 👋🏼
Don't want to butt in, but what was the comment?
Would be keen to see config headers :)
Can't see any comments (not sure if deleted or not submitted?)

[Y-e-Quit]

Got a question. I use CubeProgrammer and want to flash the Bootlaoder onto my own custom board. Also Using an Stm32F103 microprocessor. Which File do I need to choose for the upload?

[gaspacio]

Got a question. I use CubeProgrammer and want to flash the Bootlaoder onto my own custom board. Also Using an Stm32F103 microprocessor. Which File do I need to choose for the upload?

You probably want to use the .elf or .hex files as they already contain the metadata necessary for the programmer to know where to write the firmware. You may also use the .bin file but you'll have to write the starting address of the flash (0x08000000). Below are instructions to flash the bootloader using either Cube's GUI or CLI (both are bundled in the official software package by ST).

GUI

Note: the following instructions rely on the GUI released in version 2.13.0 and may be subject to change.

1. in Cube Programmer, click the 'Connect' button in the top right corner
   

2. click on the top left three bars icon to expand the side menu
   

3. select 'Erasing and programming'
   

4. click on 'Browse' button in the center-middle and select the .elf or .hex file
   

5. for .bin files, make sure to set the 'Start address' field to 0x08000000
   

6. make sure 'Skip flash erase before programming' is left unchecked
   

7. click on Start programming
   

CLI

The connection interface may vary, but assuming you're using an SWD it would be something like:
STM32_Programmer_CLI --connect port=SWD -w bootloader-dfu-fw.elf -v -rst

[thienandangthanh]

Hi @davidgfnet, we don't see you review comments in the "Files changed" section.
Did you submit your review?

You can have a look at this GitHub article.
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request#submitting-your-review