Skip to main content
yingxia feng
Associate II
August 17, 2017
Question

Auto update version

  • August 17, 2017
  • 7 replies
  • 2554 views
Posted on August 17, 2017 at 10:18

Hello.

      I am a test engineer in ABB of China. Now I need help .

     My chip is  STM32F051R8T6 in our target.  After my company's R&D check in their codes, then build one version about the STM32F051R8T6 ,I need auto update this version on my target by the

http://www.baidu.com/link?url=PkwGw4t4cI3d-bIFXUt-salx0xSksWwM3ERWHzIrF9eBFH0I8EEZdYvsz1482L0IZxfMgluUBPiGEe84vMFNH-SwNO48-B-qxvU2IibTH2E60iFZXKLEusqn1baTwED22FvH1_lWqODRhXkcdRWsmMmEYTrn1iUqEn0GkoeCQS_

,how can I do ?

      Whether the ST-LINK utility supports command line mode or not?

Thank you! 

    This topic has been closed for replies.

    7 replies

    Tesla DeLorean
    Guru
    August 17, 2017
    Posted on August 17, 2017 at 16:41

    Thought it provided a CLI, there is also STVP programming tool kit.

    Other JTAG/SWD pods vendors also have programming libraries and APIs if those suit your needs.

    Tips, Buy me a coffee, or three.. PayPal VenmoUp vote any posts that you find helpful, it shows what's working..
    RomainR.
    ST Employee
    August 17, 2017
    Posted on August 17, 2017 at 16:57

    Hi  yingxia feng,

    I can advise you to look at the STLink Utility User Manual at 

    http://bit.ly/2uTT8IG

     

    And especially Chapter 3.5 Device Programming. If you have an executable .bin or .hex.

    Chapter 4 covers the command line interface (CLI)

    You also need a ST-LINK / V2 in-circuit debugger / programmer in SWD mode here 

    http://bit.ly/2x80V6q

    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.
    yingxia feng
    Associate II
    August 18, 2017
    Posted on August 18, 2017 at 09:04

    Hello,

         I learn and try.

    when I input

    -c SN=56FF72065080525021540987 SWD UR LPM Hrst

    -w32 -P C:\Users\tiandf\Desktop\HDI06_Alarm_V1.02_20160907_PP_STM32F051R8T6.hex 0x08000000

    the Stlink tool doesn't work and quit the ST_LINK_CLI

    RomainR.
    ST Employee
    August 18, 2017
    Posted on August 18, 2017 at 09:30

    Hello,

    It seems that you are working under Windows OS.

    What type of debugger do you use? STLink stand-Alone?

    Which version ?

    Can you give more information (picture or schematic) concerning your Hardware setup ?

    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.
    yingxia feng
    Associate II
    August 18, 2017
    Posted on August 18, 2017 at 09:55

    0690X00000607x4QAA.png
    yingxia feng
    Associate II
    August 18, 2017
    Posted on August 18, 2017 at 09:56

    0690X00000607vEQAQ.png
    RomainR.
    ST Employee
    August 18, 2017
    Posted on August 18, 2017 at 10:10

    Ok great, your STLink probe is detected and also your STM32F0 target.

    Now it should ready for Erase or write Flash operation.

    Without using CLI mode but using .exe are you able to read memory of device and make a Flash erase ?

    If yes you can download your .hex in Flash start 0x08000000 by using Target -> Program or shortcut below

    0690X00000607qJQAQ.png

    Make sure Flash write protection is disabled (Option Byte Read Out Protection field)

    Let me know.

    BR

    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.
    yingxia feng
    Associate II
    August 18, 2017
    Posted on August 18, 2017 at 10:43

    0690X00000607xJQAQ.png

    Thank you !

    Useing .exe is ok ,but  CLI  mode is failed.

    I think I need to work CLI mode .because 

    RomainR.
    ST Employee
    August 18, 2017
    Posted on August 18, 2017 at 10:52

    You can try 2 things.

    Try reducing the length of the file. <HDI06_Alarm_V1.02_20160907_PP_STM32F051R8T6.hex>

    At the same time, enable the log with the -log option to see if an error is reported

    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.
    nvkokorin
    Associate
    February 5, 2018
    Posted on February 05, 2018 at 08:25

    Hi,

    I have asimilar question about STLink-CLI.So, in short, when I use the LPM option in CLI gets the error:

    [LPM]: Unknown debug protocol or option!

    After this any other CLI commands are failed (need reconnect USB).

    I use the F4-DISCO and NUCLEO-H743 boards;

    ST_LINK utility v.4.2.0.0 with CLIv3.2.0.0;

    My earlier topic here

    https://community.st.com/0D50X00009XkXI7SAN

    May be someone here knows the solution? or where is the mistake.

    Thanks!