On 10/06/13 14:59, Stuart Longland (VK4MSL) wrote: >> Measure the SRST voltage and make sure it's >> > at Vdd level. [...] If you find a problem with the dongle, you may simply >> > disconnect the reset line since in many cases you can manage without it >> > (and the default is to not use it anyway).
> I just had a crack at this again... my multimeter measures 3.3V on that > pin with the dongle disconnected, 0.7V with it connected. [...] > > I'll see what I can do about the ribbon. If need be, I'll cut the > offending wire in the ribbon cable and wire in a toggle switch (so I can > re-connect SRST if needed). Okay, I located pin 15 on the ribbon, scored either side with a scalpel, then cut it neatly with a pair of side cutters. I also managed to get my openocd built with the 'ftdi' driver... the other driver I was thinking of was 'ftd2xx' which is the proprietary. Under Gentoo with the live git ebuild, I had to add in a line to the ./configure: > econf \ > $(use_enable dummy) \ > $(use_enable ftdi ft2232_libftdi) \ Add this here: $(use_enable ftdi ftdi) \ > $(use_enable ftd2xx ft2232_ftd2xx) \ > [...] That gave me both the ft2232 and the new ftdi drivers. I now get this: > $ openocd -f interface/ftdi/olimex-arm-usb-tiny-h.cfg -f target/stm32f1x.cfg > Open On-Chip Debugger 0.8.0-dev-00024-g08d4411-dirty (2013-06-10-16:06) > Licensed under GNU GPL v2 > For bug reports, read > http://openocd.sourceforge.net/doc/doxygen/bugs.html > WARNING! > This file was not tested with real interface, but is assumed to work as this > interface uses the same layout as configs that were verified. Please report > your > experience with this file to openocd-devel mailing list, so it could be marked > as working or fixed. > Info : only one transport option; autoselect 'jtag' > adapter speed: 1000 kHz > adapter_nsrst_delay: 100 > jtag_ntrst_delay: 100 > cortex_m3 reset_config sysresetreq > Info : clock speed 1000 kHz > Info : JTAG tap: stm32f1x.cpu tap/device found: 0x3ba00477 (mfg: 0x23b, part: > 0xba00, ver: 0x3) > Info : JTAG tap: stm32f1x.bs tap/device found: 0x06414041 (mfg: 0x020, part: > 0x6414, ver: 0x0) > Info : stm32f1x.cpu: hardware has 6 breakpoints, 4 watchpoints > Info : accepting 'telnet' connection from 4444 > Info : JTAG tap: stm32f1x.cpu tap/device found: 0x3ba00477 (mfg: 0x23b, part: > 0xba00, ver: 0x3) > Info : JTAG tap: stm32f1x.bs tap/device found: 0x06414041 (mfg: 0x020, part: > 0x6414, ver: 0x0) > target state: halted > target halted due to debug-request, current mode: Thread > xPSR: 0x01000000 pc: 0x00010100 msp: 0x464c457c > Info : device id = 0x10016414 > Info : flash size = 512kbytes > stm32x mass erase complete > wrote 60184 bytes from file sd-adc-ant-debug.elf in 1.899734s (30.938 KiB/s) > Info : JTAG tap: stm32f1x.cpu tap/device found: 0x3ba00477 (mfg: 0x23b, part: > 0xba00, ver: 0x3) > Info : JTAG tap: stm32f1x.bs tap/device found: 0x06414041 (mfg: 0x020, part: > 0x6414, ver: 0x0) and my STM32 is happily running the new code now. Thank-you all for your assistance, and for this tool. :-) Regards, -- Stuart Longland (aka Redhatter, VK4MSL) I haven't lost my mind... ...it's backed up on a tape somewhere. ------------------------------------------------------------------------------ How ServiceNow helps IT people transform IT departments: 1. A cloud service to automate IT design, transition and operations 2. Dashboards that offer high-level views of enterprise services 3. A single system of record for all IT processes http://p.sf.net/sfu/servicenow-d2d-j _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel