I find out the problem was in an old firmware in ST-Link:

> Info : STLINK v2 JTAG v14 API v2 SWIM v0 VID 0x0483 PID 0x3748
Updated firmware

Info : STLINK v2 JTAG v21 API v2 SWIM v0 VID 0x0483 PID 0x3748

is OK. It is mentioned in doc. My fault that I did not notice.

Tom

On 9.2.2015 12:32, Uwe Bonnes wrote:
>>>>>> "Andreas" == Andreas Fritiofson <andreas.fritiof...@gmail.com> writes:
>      Andreas> On Wed, Feb 4, 2015 at 6:02 PM, Tomas Vanek
>      Andreas> <tom_...@users.sourceforge.net> wrote:
>
>      Andreas>     time to time I encounter an error reading a configuration
>      Andreas> register using ST-Link V2.
>
>      Andreas>
>
>      >> mdh 0x40048010 2
>      Andreas>     0x40048010: 0000 0000
>
>      Andreas> It probably doesn't affect your issue but be aware that the
>      Andreas> ST-Link doesn't support 16-bit accesses. I think OpenOCD maps
>      Andreas> it to two 8-bit accesses, which of course may fail when dealing
>
> On STM32 all 16 bit registers are on a 32-bit boundary, so 16-bit should
> better ba accessed as 32-bit.
>
>      Andreas> with peripheral registers. IMO we should fail them instead.
>
>      Andreas> Also, if things haven't improved since I used it last time,
>      Andreas> read failures do not propagate to OpenOCD so if you read bogus
>      Andreas> addresses (or use unsupported access sizes) you get bogus data,
>      Andreas> instead of failure. ST-Link really isn't the best tool to use
>      Andreas> for low level debug and I don't get why people insist on using
>      Andreas> it for that.
>
> The ST-Link is abundant and is part of the Nucleo and Discovery boards. So
> not using the STlink would be strange.


------------------------------------------------------------------------------
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
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to