Skip to main content
Visitor II
February 9, 2021
Question

ST-Link Can't Read Memory

  • February 9, 2021
  • 2 replies
  • 4791 views

Hi everybody, I recently bought a STM32F103RBTx and it worked perfectly at the first run.

Today I tried to use it again and I meet a lot of problems.

When I launch the ST-Link Utility, I have a message saying " Can not read memory! Disable Read Out Protection and retry."

Then I go to Target > Option Bytes and I set "Read Out Protection" to "Disabled". When I press apply I have this error again: "Could not set Option bytes! Please reset the target and retry." I close the message and the following one appears: "Can not connect the device".

I really don't understand... I'm a beginner with STM32, I did a lot of researches but nothing helped me...

I would be grateful if you could help me...

Edgar

    This topic has been closed for replies.

    2 replies

    Technical Moderator
    February 9, 2021

    Hello @ESchu.2​ and welcome to the STM32 Community =)

    Check the USB cable and try to upgrade the ST-Link firwmare through ST-Link utility (go to ST-LINK>firmware update) or this Link STSW-LINK009.

    Maybe you can try with the STM32CubeProgrammer and check if that recognizes it.

    Please tell me if that solve the issue.

    Imen

    ESchu.2Author
    Visitor II
    February 9, 2021

    I already changed my cable et upgraded the firmware. The CubeIDE say this when I try to debug:

    "Error in final launch sequence:

    Failed to execute MI command:

    target remote localhost:61234

    Error message from debugger back end:

    Remote failure reply: E31

    Failed to execute MI command:

    target remote localhost:61234

    Error message from debugger back end:

    Remote failure reply: E31

    Remote failure reply: E31"

    Graduate II
    February 9, 2021

    STM32 Cube Programmer, not CubeMX or CubeIDE

    Graduate II
    February 9, 2021

    Some custom board? NRST connected to debugger?

    Can you try with BOOT0 pulled high?​

    ESchu.2Author
    Visitor II
    February 9, 2021

    Not a custom board and I don't know if NRST is connected to debugger...

    I saw that a lot, what is BOOT0 pulled high and how do I do that ?