Vadim Kaushan

@martonmiklos, no, the newer official firmware (V3J6M2) locks the chip to the protection level 2, effectively preventing SWD from working. With such a locked chip you can still update (and...

And yes, I successfully uploaded my own firmware and dumped the bootloader via UART. 1. Build your firmware with `0x08020000` base address. 2. Convert it to binary and encrypt with...

@martonmiklos I think that the answer is flash layout: the sectors have different sizes and they are used to store 4 different things and should be erased separately. The bootloader...

@UweBonnes it is still possible to reprogram the chip with the ST bootloader (unless you erase it by accident). At least that's what I'm doing :) Additionally, I confirmed that...

@martonmiklos yes, but... you can use one of the previous versions of the firmware without this code

Here is the relevant part if you want to patch the firmware: ``` ROM:080298A4 CMP R2, #0xCC ROM:080298A6 BEQ loc_80298CE ``` Jumping to this label skips the locking process. Firmware...

Can confirm that firmware versions V3J2 to V3J5 (inclusive) do not touch option bytes, that is, do not enable any protection levels.

@RadioOperator 1. I suppose yes. At least if booted at least once, and this happens right after fw upgrade. 2. You can upload your CMSIS-DAP firmware via the same update...

Is it stated anywhere apart from this comment?

This may not work well on Cortex-M0 microcontrollers when you have to relocate vector table to the start of the RAM. For example, when you have a bootloader at the...