> -----Original Message-----
> From: openocd-development-boun...@lists.berlios.de 
> [mailto:openocd-development-boun...@lists.berlios.de] On 
> Behalf Of Michael Jäntsch
> Sent: 10 March 2009 17:46
> To: openocd-development@lists.berlios.de
> Subject: Re: [Openocd-development] ST32-PerformanceStick
> 
> That is pretty much what I was thinking.
> The 500kHz is set by the target file that comes with openocd 
> $OPENOCD_DIR$/target/stm32stick.cfg . I tried to set it to a 
> different speed, but that was basically just guessing. I 
> thought that the jtag_khz in the target file would work for me.
> 
> I attached the debug output with -d 3
> 
> Michael
> 
> 

Its hard to say what is causing the problem
The ST32-PerformanceStick works find for me on both win32/linux
I am using the ftdi's own driver in linux, however libftdi also works fine.

Just for info, do you have v1 or v2 - they may have differant vid/pid's -
run lsusb to find out.
http://www.hitex.com/index.php?id=340
http://www.hitex.com/index.php?id=1506

here is my working config:

# debug options
debug_level 3
#log_output openocd.log

# daemon configuration
telnet_port 4000
gdb_port 2000

jtag_khz 500

# comstick ftdi device
interface ft2232
ft2232_layout stm32stick
#ft2232_device_desc "STM32-PerformanceStick A"  # for win32
ft2232_device_desc "STM32-PerformanceStick"
ft2232_vid_pid 0x0640 0x002d    # required for linux

jtag_nsrst_delay 100
jtag_ntrst_delay 100

# use combined on interfaces or targets that can't set TRST/SRST separately
reset_config trst_and_srst

# stm32 stick
jtag newtap stm32 cpu -irlen 4 -ircapture 0x1 -irmask 0xf
jtag newtap stm32 bs -irlen 5 -ircapture 0x1 -irmask 0x1
jtag newtap str750 unknown -irlen 4 -ircapture 0x1 -irmask 0x0f
target create stm32.cpu cortex_m3 -endian little -chain-position stm32.cpu

# working area
stm32.cpu configure -work-area-virt 0 -work-area-phys 0x20000000
-work-area-size 0x4000 -work-area-backup 0

# flash stuff
flash bank stm32x 0 0 0 0 0

init
reset halt

Cheers
Spen

_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to