Skip to main content
Visitor II
September 14, 2017
Question

ST-LINK CLI (v3) cannot connect with LPM option

  • September 14, 2017
  • 3 replies
  • 2929 views
Posted on September 14, 2017 at 11:02

Hi everybody!

Just I want read a some memory area from my F4-DISCO for monitoring values.

So, first I start 

ST-LINK CLI with following arguments:

ST-LINK_CLI.exe -c SWD HOTPLUG -r8 0x20018000 0x100

and this works (i.e. read data) fine, but processor gets the stop-state during data read and runs again after.

Second, I trying to run CLI with additional LPM option, like this:

ST-LINK_CLI.exe -c SWD HOTPLUG LPM -r8 0x20018000 0x100

But the ST-LINK CLI returns a error:

[LPM]: Unknown debug protocol or option!

I tried a different options and it different order in command line, but not success.

Who can explain what's going on with CLI and how I can resolve this issue?

Thanks!

#lpm #st-link-cli
    This topic has been closed for replies.

    3 replies

    nvkokorinAuthor
    Visitor II
    October 10, 2017
    Posted on October 10, 2017 at 08:51

    hey developers! Is anyone here?

    Visitor II
    June 28, 2018
    Posted on June 28, 2018 at 17:04

    Did you ever get a solution to this? The manual still says '-c LPM' is a valid option. I'm trying it today and getting the same error you got.

    Technical Moderator
    June 28, 2018
    Posted on June 28, 2018 at 18:06

    Hello 

    mtaylor

     

    Which version of STLink Utility is used ?

    Can you please check if you use the latest version 4.2.0!

    With Regards,

    Imen

    Visitor II
    June 28, 2018
    Posted on June 28, 2018 at 18:55

    STM32 ST-LINK CLI v3.0.0.0

    On Thu, Jun 28, 2018 at 12:07 PM, Imen D <st-microelectronics@jiveon.com>

    ________________

    Attachments :

    image.png : https://st--c.eu10.content.force.com/sfc/dist/version/download/?oid=00Db0000000YtG6&ids=0680X000006HxSd&d=%2Fa%2F0X0000000ayK%2FdHByI7M3t2yam_QqxMTneCiqC3CTEkq6ybr4B80FLx0&asPdf=false
    Technical Moderator
    October 12, 2018

    Hello,

    This issue will be fixed with the next version of STM32 ST-LINK Utility (V4.3.0).

    Kind Regards,

    Imen