AnsweredAssumed Answered

ST-LINK fails when launching debugger if there is external memory assigned.

Question asked by oz.kurt on Jul 23, 2014
Latest reply on Oct 25, 2014 by Clive One
I have an application created for an STM32F429 target. I have been using ST-LINK/v2 debugger in an Virtual Box environment (Ubuntu). I use eclipse GNU ARM tools to compile and debug  my applications. When there is no data assigned to external SRAM, the debugger launches successfully and I can debug my code without any problem. When I add external data and change my linker files as described below then my debugger launch fails with the following messages:

929,472 15load /home/user/projects/myproject/blink-led/Debug/blink-led.elf 
929,552 13^done,groups=[{id="i1",type="process",pid="42000"}]
929,552 (gdb) 
929,552 14^error,msg="Can not fetch data now."
929,553 (gdb) 
929,553 &"load /home/user/projects/myproject/blink-led/Debug/blink-led.elf \n"
929,553 ~"Loading section .eb0data, size 0x4 lma 0x64000000\n"
929,553 &"Load failed\n"
929,553 15^error,msg="Load failed"
929,553 (gdb) 
929,553 &"\n"
929,553 ^done


Linker file settings:

(mem.ld):
MEMORY { ..
EXTMEMB0 (xrw) : ORIGIN = 0x64000000, LENGTH = 262K}

and (sections.ld)
  /* EXTMEM Bank0 */
    .eb0text :
    {
        *(.eb0text)                   /* remaining code */
        *(.eb0rodata)                 /* read-only data (constants) */
        *(.eb0rodata.*)
    } >EXTMEMB0
    
    .eb0data :
    {
        *(.eb0data)                   /* remaining data */
    } >EXTMEMB0

My st-util connection parameters are:
$ st-util
2014-07-23T09:45:07 INFO src/stlink-common.c: Loading device parameters....
2014-07-23T09:45:07 INFO src/stlink-common.c: Device connected is: F42x and F43x device, id 0x10036419
2014-07-23T09:45:07 INFO src/stlink-common.c: SRAM size: 0x30000 bytes (192 KiB), Flash: 0x200000 bytes (2048 KiB) in pages of 16384 bytes
Chip ID is 00000419, Core ID is  2ba01477.
Target voltage is 3211 mV.
Listening at *:4242...
GDB connected.

Is this problem an ST-LINK external memory access timing issue, or could it be linker file setting?
Does anyone come cross with this problem before?
Thanks...

Outcomes