On Tue, Aug 16, 2011 at 9:23 AM, Xiaofan Chen <xiaof...@gmail.com> wrote:
> On Tue, Aug 16, 2011 at 9:18 PM, Eric Wetzel <thewet...@gmail.com> wrote:
>
>> I'm not sure if Freddie's OpenOCD is built using libftdi-1.0, which
>> previous e-mails indicate may solve this problem. As a last-ditch
>> effort to try libftdi-1.0, I replaced the libfti.dll in Freddie's bin
>> directory with the libftdi.dll from Xiaofan's build
>> (http://code.google.com/p/picusb/downloads/detail?name=libftdi1_17July2011_mingw32_mingw64.zip&can=2&q=).
>> I get the same result.
>
> Hmm, interesting to know that would work.
>
> Freddie's OpenOCD binary and my binary are both using libftdi-0.19
> and libusb-win32.
>
>> Anybody have any hints? Is anybody else successfully using a Blackhawk
>> USB100v2? I don't really think it's the interface itself because I get
>> the same failure on a completely different target board using OpenOCD
>> built from git on Linux at home... I think.
>
> From the past history, it seems that ftd2xx may help. So you may want to
> build with FTDI's latest D2xx library to see if that helps.
>
Strangely, I am having the same problem with FTD2XX, but the timeouts
are taking much longer:
Debug: 236 158 ft2232.c:2478 ft2232_init(): ft2232 interface using
shortest path jtag state transitions
Debug: 237 158 ft2232.c:2158 ft2232_init_ftd2xx(): 'ft2232' interface
using FTD2XX with 'xds100v2' layout (0403:a6d0)
Debug: 238 194 ft2232.c:2285 ft2232_init_ftd2xx(): current latency timer: 2
Info : 239 194 ft2232.c:2315 ft2232_init_ftd2xx(): device: 6 "2232H"
Info : 240 194 ft2232.c:2316 ft2232_init_ftd2xx(): deviceID: 67348176
Info : 241 194 ft2232.c:2317 ft2232_init_ftd2xx(): SerialNumber: USB100V2A
Info : 242 195 ft2232.c:2318 ft2232_init_ftd2xx(): Description: Texas
Instruments Inc.XDS100 Ver 2.0 A
Debug: 243 195 ft2232.c:2435 ft2232_set_data_bits_low_byte(): 80 3a 7b
Debug: 244 195 ft2232.c:2455 ft2232_set_data_bits_high_byte(): 82 00 59
Debug: 245 195 ft2232.c:2455 ft2232_set_data_bits_high_byte(): 82 86 59
Info : 246 196 ft2232.c:648 ft2232h_ft4232h_clk_divide_by_5(): max TCK
change to: 30000 kHz
Debug: 247 197 core.c:1602 adapter_khz_to_speed(): convert khz to
interface specific speed value
Debug: 248 197 core.c:1606 adapter_khz_to_speed(): have interface set up
Debug: 249 197 ft2232.c:616 ft2232h_ft4232h_adaptive_clocking(): 96
Debug: 250 197 core.c:1602 adapter_khz_to_speed(): convert khz to
interface specific speed value
Debug: 251 197 core.c:1606 adapter_khz_to_speed(): have interface set up
Info : 252 197 core.c:1424 adapter_init(): RCLK (adaptive clock speed)
Debug: 253 197 openocd.c:137 handle_init_command(): Debug Adapter init complete
Debug: 254 197 command.c:151 script_debug(): command - ocd_command
ocd_command type ocd_transport init
Debug: 255 198 command.c:151 script_debug(): command - ocd_transport
ocd_transport init
Debug: 257 198 transport.c:255 handle_transport_init(): handle_transport_init
Debug: 258 198 ft2232.c:1750 xds100v2_reset(): trst: 0, srst: 0,
high_output: 0x96, high_direction: 0x59
Debug: 259 198 ft2232.c:816 ft2232_send_and_recv(): write buffer (size 3):
Debug: 260 198 ft2232.c:797 ft2232_debug_dump_buffer(): 82 96 59
Debug: 261 198 core.c:713 jtag_add_reset(): SRST line released
Debug: 262 198 core.c:737 jtag_add_reset(): TRST line released
Debug: 263 198 core.c:329 jtag_call_event_callbacks(): jtag event: TAP reset
Debug: 264 199 command.c:151 script_debug(): command - ocd_command
ocd_command type ocd_jtag arp_init
Debug: 265 199 command.c:151 script_debug(): command - ocd_jtag
ocd_jtag arp_init
Debug: 266 199 core.c:1435 jtag_init_inner(): Init JTAG chain
Debug: 267 199 core.c:329 jtag_call_event_callbacks(): jtag event: TAP reset
Debug: 268 199 ft2232.c:816 ft2232_send_and_recv(): write buffer (size 3):
Debug: 269 199 ft2232.c:797 ft2232_debug_dump_buffer(): 4b 04 1f
Debug: 270 199 core.c:1055 jtag_examine_chain(): DR scan interrogation
for IDCODE/BYPASS
Debug: 271 199 core.c:329 jtag_call_event_callbacks(): jtag event: TAP reset
Debug: 272 199 ft2232.c:816 ft2232_send_and_recv(): write buffer (size 94):
Debug: 273 200 ft2232.c:791 ft2232_debug_dump_buffer(): 4b 06 17 39 4e
00 ff 00 00 00 ff 00 00 00 ff 00
Debug: 274 200 ft2232.c:791 ft2232_debug_dump_buffer(): 00 00 ff 00 00
00 ff 00 00 00 ff 00 00 00 ff 00
Debug: 275 200 ft2232.c:791 ft2232_debug_dump_buffer(): 00 00 ff 00 00
00 ff 00 00 00 ff 00 00 00 ff 00
Debug: 276 200 ft2232.c:791 ft2232_debug_dump_buffer(): 00 00 ff 00 00
00 ff 00 00 00 ff 00 00 00 ff 00
Debug: 277 200 ft2232.c:791 ft2232_debug_dump_buffer(): 00 00 ff 00 00
00 ff 00 00 00 ff 00 00 00 ff 00
Debug: 278 200 ft2232.c:797 ft2232_debug_dump_buffer(): 00 00 ff 00 00
3b 06 00 6b 01 01 4b 04 1f
Error: 279 25203 ft2232.c:591 ft2232_read(): couldn't read enough
bytes from FT2232 device (0 < 81)
Error: 280 25203 ft2232.c:846 ft2232_send_and_recv(): couldn't read from FT2232
Error: 281 25203 core.c:1479 jtag_init_inner(): Trying to use
configured scan chain anyway...
Debug: 282 25203 core.c:1219 jtag_validate_ircapture(): IR capture
validation scan
Debug: 283 25203 ft2232.c:816 ft2232_send_and_recv(): write buffer (size 12):
Debug: 284 25203 ft2232.c:797 ft2232_debug_dump_buffer(): 4b 06 1b 3b
06 ff 6b 01 81 4b 02 03
Error: 285 50206 ft2232.c:591 ft2232_read(): couldn't read enough
bytes from FT2232 device (0 < 2)
Error: 286 50206 ft2232.c:846 ft2232_send_and_recv(): couldn't read from FT2232
Debug: 287 50206 core.c:329 jtag_call_event_callbacks(): jtag event: TAP reset
Debug: 288 50206 ft2232.c:816 ft2232_send_and_recv(): write buffer (size 3):
Debug: 289 50206 ft2232.c:797 ft2232_debug_dump_buffer(): 4b 04 1f
Warn : 290 50206 core.c:1503 jtag_init_inner(): Bypassing JTAG setup
events due to errors
Debug: 291 50206 openocd.c:150 handle_init_command(): Examining targets...
Debug: 292 50206 command.c:151 script_debug(): command - ocd_command
ocd_command type ocd_flash init
Debug: 293 50206 command.c:151 script_debug(): command - ocd_flash
ocd_flash init
Debug: 294 50207 log.c:437 keep_alive(): keep_alive() was not invoked
in the 1000ms timelimit (50207). This may cause trouble with GDB
connections.
Debug: 297 50207 tcl.c:912 handle_flash_init_command(): Initializing
flash devices...
Debug: 298 50207 command.c:151 script_debug(): command - ocd_command
ocd_command type ocd_mflash init
Debug: 299 50207 command.c:151 script_debug(): command - ocd_mflash
ocd_mflash init
Debug: 301 50207 mflash.c:1331 handle_mflash_init_command():
Initializing mflash devices...
Debug: 302 50207 command.c:151 script_debug(): command - ocd_command
ocd_command type ocd_nand init
Debug: 303 50207 command.c:151 script_debug(): command - ocd_nand ocd_nand init
Debug: 305 50207 tcl.c:521 handle_nand_init_command(): Initializing
NAND devices...
Debug: 306 50207 command.c:151 script_debug(): command - ocd_command
ocd_command type ocd_pld init
Debug: 307 50208 command.c:151 script_debug(): command - ocd_pld ocd_pld init
Debug: 309 50208 pld.c:232 handle_pld_init_command(): Initializing PLDs...
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to