[SOLVED]Cortex-M3 External RAM not recognized by GDBServer 4.2 Eval Version

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

  • [SOLVED]Cortex-M3 External RAM not recognized by GDBServer 4.2 Eval Version

    I am trying to debug STM32F103 ZE microcontroller code. The Segger JLink GDBServer detects the processor core - Cortex-M3 correctly. I can set the breakpoint on internal RAM addresses but for external RAM addresses it says fllowing:

    0x00000224 in ?? ()
    Ignoring packet error, continuing...
    Reply contains invalid hex digit 116
    (gdb) b XE_Slot_Task
    Breakpoint 1 at 0x6000ffbc
    (gdb) c
    Warning:
    Cannot insert breakpoint 1.
    Error accessing memory address 0x6000ffbc: Unknown error 4294967295.

    on GDBServer it says:

    Setting breakpoint @ address 0x6000FFBC, Size = 2, BPHandle = 0x0000
    WARNING: No more breakpoint resources left



    I am able to connect and debug STR7 processor and every memory area - introm, intram, extram etc. are detected fine.

    Following are the details of JLink I am using:

    JLinkARM.dll V4.20h (DLL compiled Oct 5 2010 19:11:41)

    Listening on TCP/IP port 2331

    J-Link connected
    Firmware: J-Link ARM V7 compiled Sep 6 2010 10:43:31
    Hardware: V7.00
    S/N: 57000492
    Feature(s): JFlash



    Thanks in advance for Help.

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

  • Hi Sheel,

    did you verify that the external RAM has been initialized correctly?
    For the J-Link itself it does not really make a difference if you are accessing the internal or external RAM.


    Best regards
    Alex
    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.
  • Thanx Alex for responding.



    Yes, the RAM is initialized since I am able to execute the program without GDB. Also, When I used a licensed version of GDBServer with JLink6.0, it seems it is able to write to the external RAM, because it says Verify OK on each write. However, the setting of breakpoints on external RAM has the same problem with the licensed version as well.



    BTW, the external RAM on STR7 works without any problem with the same GDBServer/Jlink.



    Any help is appreciated.



    Thanks

    Sheel