texane/stlink — Issue #41: gdbserver does not recognize correct CHIPID for F4DISCOVERY
Author: andrea-rockt
Created: 2011-12-23 14:05:58+00:00
State: open

stlink gdbserver does not correctly recognize the chipid for the mcu mounted on my F4DISCOVERY board returning a wrong memory map to gdb, here is the log from st-util:

```
andrea@andrea-HP-Pavilion-dv6-Notebook-PC:~/st-link/stlink.git/gdbserver$ ./st-util
Chip ID is 00000000, Core ID is 00000000.
KARL - should read back as 0x03, not 60 02 00 00
init watchpoints
Listening at *:4242...
GDB connected.
recv: qSupported:multiprocess+;qRelocInsn+
query: Supported;multiprocess+;qRelocInsn+
send: PacketSize=3fff;qXfer:memory-map:read+
recv: !
send: OK
recv: Hg0
send:
recv: ?
send: S05
recv: Hc-1
send:
recv: qC
send:
recv: qAttached
query: Attached;
send:
recv: qOffsets
query: Offsets;
send:
recv: g
send: 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000220ffffffff30040008
recv: qXfer:memory-map:read::0,fff
query: Xfer;memory-map:read::0,fff
Xfer: type:memory-map;op:read;annex:;addr:0;length:4095
send: m 0x0
recv: qXfer:memory-map:read::26c,d93
query: Xfer;memory-map:read::26c,d93
Xfer: type:memory-map;op:read;annex:;addr:620;length:3475
send: l
recv: m8000430,4
send: 002103e0
recv: m0,40
send: 0000022031040008d5030008e1030008e9030008f1030008f903000800000000000000000000000000000000010400080d040008000000001904000825040008
recv: qSymbol::
query: Symbol;:
send:
recv: qTStatus
query: TStatus;
send:
```

Neither flash loading nor sram loading works in this conditions