About FArdi.1

FArdi.1 · 2024-02-13

Using latest STM32CubeProgrammer v2.15.0Register name and description don't match (rising register, but falling description, and vice versa).Which one is correct?

FArdi.1 · 2024-01-10

I need to write option bytes using HEX file, but so far can't work on STM32C0. It was working well in STM32L0.Any solution?Updating the option bytes using "-ob [OptByte=<value>]" is working, but I prefer using the HEX file. STM32C031STM32CubeProgramm...

FArdi.1 · 2021-09-28

Using ST-link V3.MCU: STM32L031First programming was ok. After disconnecting and reconnect with second device, nothing happen.Using same set of hardware, but changed software to ST-LINK Utility.Result: ok. Automatically programmed the second device.

FArdi.1 · 2021-09-27

MCU is STM32L0.The file I use to program has option bytes added with read-protection turned ON. :020000041FF8E3 :0C0000000000FFFF7A80857FFF0000FFFA :00000001FFUsing ST-link V3, I'm having this error: (see attached screenshot) Command line:stm32_prog...

FArdi.1 · 2024-03-19

Description is unchanged with new v2.16.0. Still wrong, not match with Reference Manual.But the release history said otherwise. See attached.

FArdi.1 · 2024-03-19

Just an update:Problem is still there using new version STM32CubeProgrammer v2.16.0. After installing, the program is not responding after I click OK button. See attached pic. I need to force close from task manager. The next time I run the CubeProgr...

FArdi.1 · 2024-02-13

@TDK Thanks for the answer & the link to old issue.At least for now the address location is correct for -ob BOR_EN=0x1 BORF_LEV=0x3 BORR_LEV=0x0Only descriptions inside GUI need to be swapped.

FArdi.1 · 2024-01-25

This means my boards are unrecoverable because I never prepare to access DBG_SWEN register in my application.I'm expecting this information to be mentioned near the BOOT_LOCK . My understanding of "debug capability disable" was unable to debug during...

FArdi.1 · 2024-01-24

Hi @bvd , so sorry the hear that, after so many months without solution I think ST should be able to duplicate the problem since we're using same NUCLEO-C031C6 board.Just now I tried on my own PCBA with STM32C031K6. Same thing happen. All possible co...

User statistics

User Activity

BOR level description is confusing

Writing Option Bytes using HEX file is failed on STM32C0, but successful on STM32L0

STM32CubeProgrammer 2.8.0 Automatic mode is not working

With ST-link V3, is there an option to verify while programming like in ST-link V2?

Re: BOR level description is confusing

Re: Installation Issues - Infinite Loop

Re: BOR level description is confusing

Re: after change the RDP of FLASH from lv0 to lv1, the target could not be detected on NUCLEO-C031C6

Re: after change the RDP of FLASH from lv0 to lv1, the target could not be detected on NUCLEO-C031C6