FAQs
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

CubeProgrammer 2.16 CLI problem - warning

TDJ
Lead

‎2024-04-04 11:27 PM - edited ‎2024-04-05 02:02 AM

After upgrading CubeProgrammer to new release 2.16 CLI commands started to fail during verification phase when changing option bytes on STM32U5A5. Sample command which fails:

STM32_Programmer_CLI -c port=SWD mode=UR --hardRst -ob WRP1A_PSTRT=0xff WRP1A_PEND=0

The same operation performed from GUI works correctly. I had to go back to release 2.15

Labels:
0 Kudos
1 REPLY 1
STTwo-32
ST Employee

‎2024-04-05 02:20 AM - edited ‎2024-04-05 02:21 AM

Hello @TDJ 

I've tested using the NUCLEO-U5AZJ-Q:

STTwo32_0-1712308071982.png

The default value of the WRP1A_PSTRT and WRP1A_PEND are 0xFF and 0x0:

STTwo32_1-1712308209835.png

Then, using the command " STM32_Programmer_CLI -c port=SWD mode=UR --hardRst -ob WRP1A_PSTRT=0xaf WRP1A_PEND=1 ",I've been able to set the WRP1A_PSTRT and the WRP1A_PEND to 0xAF and 0x1:

STTwo32_2-1712308476181.png

and Finally I've executed the command " STM32_Programmer_CLI -c port=SWD mode=UR --hardRst -ob WRP1A_PSTRT=0xff WRP1A_PEND=0 " which take back the WRP1A_PSTRT and the WRP1A_PEND to 0xFF and 0x0:

STTwo32_3-1712308813082.png

Can you add more details about your issue (screenshot,...).

Best Regards.

STTwo-32

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

0 Kudos
Top