Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Releases: Cipulot/tinyuf2

0.1.3_DISABLE_WRITE_PROTECTION

05 Dec 13:28
ddd10ca

Choose a tag to compare

Pre-release

Introduction

Initial release of a collection of UF2 bootloaders for the STMF4x1 family of MCU.

MCU size specific bootloaders are available and it's strongly advised to use the correct one that matches your MCU. While using other bootloaders that share the same family might work, I have not investigated the behavior and therefore I DO NOT encourage it.

HSE specific versions for each MCU are available too. Here it's a MUST to use the correct one based on your HSE clock.
8MHz, 16MHz and 25MHZ( files named blackpill) are available.

Install and update process

First install

For the first time install the *.bin file with the matching characteristics to your use case. This will install the bootloader by flashing it into the early sectors of the flash.

At this point, the board will reboot and a mass storage device named Cipulot_UF2 will appear.

πŸŽ‰ Congrats! You're ready to upload your firmware using the UF2 format. πŸŽ‰

Update

In case you already have the bootloader installed and you want to update it with the latest one simply upload the *.uf2 file with the matching characteristics to your use case.

Aaaaaand, you're done. You can now proceed as usual.

Changes from the 0.1.2 tag

The changes include the recompilation of all the targets with the addition of the #define TINYUF2_PROTECT_BOOTLOADER 0 directive. This directive prevents TinyUF2 from enabling the write protection bits for the first 2 sectors of the MCU flash.
The goal here was to make it easier for the user to remove TinyUF2 through a MASS ERASE command, since at times the user might want to remove TinyUF2 but it is blocked by either a stall in the un-set of the protection bits when in DFU through STM32CubeProgrammer, having to resort to SWD or other external programming method that directly manipulate the bits. This mode isn't very user-friendly and requires additional tools, although it is almost 100% guaranteed to work since the erase is achieved through the protection mechanism that the MCU has when manipulating protection bits.

Notes

Note that if you notice that the date in the INFO_UF2.txt didn't change then it's is likely that the auto-update through UF2 upload didn't work properly.

Fix

To fix this you may need to MASS ERASE the flash, either through DFU or with an external programmer.
To do that in DFU mode (using something like STM32Cube Programmer) you need to first disable the write protection bits for the 2 sectors and then erase the chip. If either the bit set or the mass erases fail or you notice that they didn't perform correctly even with a positive result (aka STM32CubeProgrammer says operation completed but you see the flash is still populated) then you need to use an external programmer and erase the chip. This erase forces the MCU to self-erase since you are gonna tamper with the security bits.

0.1.2

21 Nov 18:14

Choose a tag to compare

0.1.2 Pre-release
Pre-release

Introduction

Initial release of a collection of UF2 bootloaders for the STMF4x1 family of MCU.

MCU size specific bootloaders are available and it's strongly advised to use the correct one that matches your MCU. While using other bootloaders that share the same family might work, I have not investigated the behavior and therefore I DO NOT encourage it.

HSE specific versions for each MCU are available too. Here it's a MUST to use the correct one based on your HSE clock.
8MHz, 16MHz and 25MHZ( files named blackpill) are available.

Install and update process

First install

For first time install flash the *.bin file with the matching characteristics to your use case. This will install the bootloader by flashing it into the early sectors of the flash.

At this point the board will reboot and a mass storage device named Cipulot_UF2 will appear.

πŸŽ‰ Congrats! You're ready to upload your firmwares using the UF2 format. πŸŽ‰

Update

In case you already have the bootloader installed and you want to update it with the latest one simply upload the *.uf2 file with the matching characteristics to your use case.

Aaaaaand, you're done. You can now proceed as usual.

Changes form the 0.1.1 tag

The changes include the recompilation of all the targets with updated INDEX_URL now pointing to my website and alignment to the master code.

0.1.1

20 Jan 17:05

Choose a tag to compare

0.1.1 Pre-release
Pre-release

Introduction

Initial release of a collection of UF2 bootloaders for the STMF4x1 family of MCU.

MCU size specific bootloaders are available and it's strongly advised to use the correct one that matches your MCU. While using other bootloaders that share the same family might work, I have not investigated the behavior and therefore I DO NOT encourage it.

HSE specific versions for each MCU are available too. Here it's a MUST to use the correct one based on your HSE clock.
8MHz, 16MHz and 25MHZ( files named blackpill) are available.

Install and update process

First install

For first time install flash the *.bin file with the matching characteristics to your use case. This will install the bootloader by flashing it into the early sectors of the flash.

At this point the board will reboot and a mass storage device named Cipulot_UF2 will appear.

πŸŽ‰ Congrats! You're ready to upload your firmwares using the UF2 format. πŸŽ‰

Update

In case you already have the bootloader installed and you want to update it with the latest one simply upload the *.uf2 file with the matching characteristics to your use case.

Aaaaaand, you're done. You can now proceed as usual.