On 7.2.2015 11:19, Andreas Fritiofson wrote:
On Wed, Feb 4, 2015 at 6:02 PM, Tomas Vanek
<[email protected] <mailto:[email protected]>>
wrote:
time to time I encounter an error reading a configuration register
using
ST-Link V2.
> mdh 0x40048010 2
0x40048010: 0000 0000
It probably doesn't affect your issue but be aware that the ST-Link
doesn't support 16-bit accesses. I think OpenOCD maps it to two 8-bit
accesses, which of course may fail when dealing with peripheral
registers. IMO we should fail them instead.
Also, if things haven't improved since I used it last time, read
failures do not propagate to OpenOCD so if you read bogus addresses
(or use unsupported access sizes) you get bogus data, instead of
failure. ST-Link really isn't the best tool to use for low level debug
and I don't get why people insist on using it for that.
AFAIK reading from a bogus address is reported in fresh OpenOCD and
ST-Link V2. Just message is not too informative, just "in procedure 'mdw'"
In case of delayed error I'm afraid that OpenOCD starts reconnection
process too early. It would be worth to retry memory read once (even if
it can clear some flags...).
Otherwise I agree that there are better tools. I do not insist on using
ST-Link ;-)
Tomas
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
