> Can you try the attached luminary.cfg to see if you can at
> least read the idcode?
In any case, it doesn't explain the hanging you mentioned. Did you
manage to get a debug log when it hanged?
There are a lot of variables here: OS, libusb version, adapter,
target. The following configuration seems to be very stable for me:
Ubuntu 10.04
Libusb 1.0.6 (in Ubuntu repo)
Jtagkey-Tiny, Olimex ARM-USB-OCD and Olimex ARM-USB-OCD-H
STM32F100 and STM32F103
If you or anyone can test configurations with only one or two
differences at a time it would be very helpful to locate the
problem(s).
I've done performance testing with the following openocd.cfg:
---
source [find interface/ftdi/jtagkey.cfg]
#source [find interface/jtagkey.cfg]
#source [find interface/ftdi/olimex-arm-usb-ocd-h.cfg]
#source [find interface/olimex-arm-usb-ocd-h.cfg]
#source [find interface/rlink.cfg]
source [find target/stm32f1x.cfg]
#source [find board/stm32f4discovery.cfg]
#source [find board/stm32vldiscovery.cfg]
$_TARGETNAME configure -event reset-start {
adapter_khz 1000
}
$_TARGETNAME configure -event reset-init {
mww 0x40022000 0x32
mww 0x40021004 0x3c0400
mww 0x40021000 0x01000883
sleep 10
mww 0x40021004 0x3c0402
sleep 10
adapter_khz 8000
}
init
reset init
poll off
stm32f1x mass_erase 0
flash write_image test.bin 0x08000000
verify_image test.bin 0x08000000
dump_image dump.bin 0x08000000 131072
load_image dump.bin 0x20000000 bin 0x20000000 20480
shutdown
---
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel