[SOLVED] Reading STM32F4 SRAM with JLink/ST-Link

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • [SOLVED] Reading STM32F4 SRAM with JLink/ST-Link

    Hi,

    I have setup a little Demo Project for our STM32F469 Disco Board. I use the JLink Firmware on the ST-Link Module on the Board. I use Keil as Debug IDE (Target Build runs over Make & GCC)...
    When I stop my target I want to read some Parts of the SRAM with the debugger. But that does not work. I don't get any content. When I do this with our actual Project I can read SRAM on Break. For our Project we use an JLink Pro connected over SWD.

    If I try to read a SRAM Region with the JLink Commander on both Targets (Demo Board & Project Board) I cannot read any SRAM Region on both Targets, independent of JLink Debugger.

    Are there any Registers in the STM32F4 series or in Keil uVision which need to be set to enable reading from SRAM?

    Kind regards
    Andreas

  • Hello Andreas,

    Thank you for your inquiry.
    Such an issue is not known to us.
    We suspect that RAM access is not available with your application under certain circumstances.
    Could you provide a J-Link log of such a session?
    wiki.segger.com/Enable_J-Link_log_file

    Best regards,
    Nino
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • Hello Nino,
    thanks for your help.
    I've attached a Log File.
    As mentioned, I use a STM32F469 Dicovery Board with JLink Reflash FW. So I hope this is no limitation.

    Kind regards
    Andreas
    Files

    • JLinkLog.txt

      (261.03 kB, downloaded 285 times, last: )

    The post was edited 1 time, last by duderino65 ().

  • Hello Andreas,

    Thank you for providing the log file.
    I assume this log is from a Keil MDK session?
    According to the log memory reads to address space around 0x02010100 is constantly failing.
    That does not look like a valid memory area of the STM32F4 device.
    RAM for that device starts at 0x20000000.
    Make sure to access only valid memory areas. When accessing invalid memory areas unexpected behaviour can be the result.

    Best regards,
    Nino
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • Hello Nino,
    thanks for your help!

    I checked that and noticed that I mixed up RAM address with Flash addresses which start with 0x08XXXXXX. Of course RAM starts at 0x20000000. So no Zero at the beginning...
    Bad mistake!

    Kind regards
    Andreas

  • Hello Andreas,

    Great to hear that you are up and running again.
    We will consider this thread as solved now.

    Best regards,
    Nino
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.