Re: [OpenOCD-devel] STM32W108 fails with STlink V2

Fri, 26 Jul 2013 16:42:41 -0700

Title: suretronic_labs_sig.html
Hi Spen, Andreas

Ok, it looks like it was me being stupid with the modified .cfg permissions, which had changed due to an edit from root.

This seems to be working with the 256K chip:

/home/ron/Dev/openocd# Info : This adapter doesn't support configurable speed
> Info : STLINK v2 JTAG v15 API v2 SWIM v4 VID 0x0483 PID 0x3748
> Info : Target voltage: 3.250952
> Info : stm32w108.cpu: hardware has 6 breakpoints, 4 watchpoints

with a target .cfg of

#
# STM32W108xx stlink pseudo target
#

if { [info exists CHIPNAME] == 0 } {
   set CHIPNAME stm32w108
}

if { [info exists CPUTAPID] == 0 } {
   set CPUTAPID 0x1ba01477
}

if { [info exists WORKAREASIZE] == 0 } {
   # 4k -- This should work for all chips, though perhaps not optimally
   set WORKAREASIZE 0x1000
}

source [find target/stm32_stlink.cfg]

# Use the flash driver from the EM357
set _FLASHNAME $_CHIPNAME.flash
# 256k (0x40000) of flash
flash bank $_FLASHNAME em357 0x08000000 0x40000 0 0 $_TARGETNAME

Using this I've flashed a verified image to the chip.

Apologies for the false 'bug'. At least operation with an stm32w108CC 256K chip is now partially tested.

Cheers, Ron
Wellington, NZ



On 26/07/2013 10:00 p.m., Spencer Oliver wrote:
On 26/07/13 03:46, Ron Segal wrote:
Openocd version 0.7.0 current
ST-LINK/V2 usb dongle

Hi Folks

The current release works ok with an STM32W108CB version with 128K
Flash.  A Rexense wireless module on a development board with JTag.
With exactly the same setup it throws the following with an STM32W108CC
version with 256K Flash.

/openocd# ./openocd -f interface/stlink-v2.cfg -f
target/stm32w108_stlink.cfg
Open On-Chip Debugger 0.7.0 (2013-07-26-13:57)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.sourceforge.net/doc/doxygen/bugs.html
Info : This adapter doesn't support configurable speed
Info : STLINK v2 JTAG v15 API v2 SWIM v4 VID 0x0483 PID 0x3748
Info : Target voltage: 3.245115
Error: init mode failed
in procedure 'transport'
in procedure 'init'

I have tried various changes to the stm32w108_stlink.cfg file but to no
avail.

I have tried with different STM32W hardware (development board and
STM32W module) in case there was a problem there.

A fix or workaround would be appreciated.


Are you saying your are using JTAG mode with the stlink?
If you are I would suggest you use SWD as it is currently more reliable - http://sourceforge.net/apps/trac/openocd/ticket/61. I am working on the fix.

One other issue is that the stlink uses the TAPID to determine supported targets, this changes a lot more with JTAG mode than it does with SWD.

Also show us what your current cfg looks like.

Cheers
Spen



--

R o n   S e g a l MSc, CEng, ITCP
suretronic labs
Wellington, New Zealand
Tel: 64 4 5288806 Cell: 64 21 678009

This e-mail message and any attachments are confidential to the addressee(s).  If you are not the intended addressee, please notify me as soon as possible and immediately delete the e-mail, including any attachments.  Thank you.
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to