User Activity

They certainly appear on the Windows one, usually at a .0 version e.g. 1.15.0 and then 1.15.1 fixes it.Problem is that the Cube IDE versions stored on the ST website are provided only in 1.xx.0 versions so if you don't archive the 1.xx.1 when it was ...
Is this the right way? if (FLASH_OB_GetRDP() != OB_RDP_LEVEL_2) { HAL_FLASH_Unlock(); // Unlock the flash memory HAL_FLASH_OB_Unlock(); // Unlock the option bytes *(__IO uint8_t*) OPTCR_BYTE1_ADDRESS = OB_RDP_LEVEL_2; // Set RDP2 HAL_FL...
Thissuggests that one cannot execute code from SRAM. Is that really correct?Also there is ambiguity on whether the OTP area (512 bytes plus the control block) is readable in RDP2. Why say "512 bytes" and not just all-OTP?The OTP area must remain usab...
It seems perfectly possible, under Level 2, to have a "boot block" which accepts a firmware block (say via USB MSC or via HTTP), encrypted with a key stored in the boot block, and you have a product whose firmware can be upgraded but can't be extract...
Currently the Cube SWV ITM debug console does not receive the data unless you have built the project using the build+debug option F11.This is a problem sometimes, when running code which contains the debug statements but which wasn't loaded from Cube...
Kudos given to