[Openocd-development] couldn't read enough bytes from FT2232 device (0 81)
This problem again. I see plenty of e-mails in the past supposedly addressing it, but none worked for me. I'm trying to use a TI/Blackhawk USB100v2, which I think is supposed to be identical to an XDS100v2, so I am using the interface/xds100v2.cfg file. I'm using Freddie's OpenOCD 0.5.0 build under Windows 7. Debug: 231 123 ft2232.c:2469 ft2232_init(): ft2232 interface using shortest path jtag state transitions Debug: 232 123 ft2232.c:2342 ft2232_init_libftdi(): 'ft2232' interface using libftdi with 'xds100v2' layout (0403:a6d0) Debug: 233 129 ft2232.c:2389 ft2232_init_libftdi(): current latency timer: 2 Debug: 234 130 ft2232.c:2400 ft2232_init_libftdi(): FTDI chip type: 4 2232H Debug: 235 131 ft2232.c:2426 ft2232_set_data_bits_low_byte(): 80 3a 7b Debug: 236 131 ft2232.c:2446 ft2232_set_data_bits_high_byte(): 82 00 59 Debug: 237 132 ft2232.c:2446 ft2232_set_data_bits_high_byte(): 82 86 59 Info : 238 132 ft2232.c:647 ft2232h_ft4232h_clk_divide_by_5(): max TCK change to: 3 kHz Debug: 239 134 core.c:1602 adapter_khz_to_speed(): convert khz to interface specific speed value Debug: 240 134 core.c:1606 adapter_khz_to_speed(): have interface set up Debug: 241 135 ft2232.c:615 ft2232h_ft4232h_adaptive_clocking(): 96 Debug: 242 135 core.c:1602 adapter_khz_to_speed(): convert khz to interface specific speed value Debug: 243 136 core.c:1606 adapter_khz_to_speed(): have interface set up Info : 244 136 core.c:1424 adapter_init(): RCLK (adaptive clock speed) Debug: 245 137 openocd.c:137 handle_init_command(): Debug Adapter init complete Debug: 246 137 command.c:151 script_debug(): command - ocd_command ocd_command type ocd_transport init Debug: 247 138 command.c:151 script_debug(): command - ocd_transport ocd_transport init Debug: 249 138 transport.c:255 handle_transport_init(): handle_transport_init Debug: 250 139 ft2232.c:1749 xds100v2_reset(): trst: 0, srst: 0, high_output: 0x96, high_direction: 0x59 Debug: 251 139 core.c:713 jtag_add_reset(): SRST line released Debug: 252 140 core.c:737 jtag_add_reset(): TRST line released Debug: 253 140 core.c:329 jtag_call_event_callbacks(): jtag event: TAP reset Debug: 254 141 command.c:151 script_debug(): command - ocd_command ocd_command type ocd_jtag arp_init Debug: 255 141 command.c:151 script_debug(): command - ocd_jtag ocd_jtag arp_init Debug: 256 142 core.c:1435 jtag_init_inner(): Init JTAG chain Debug: 257 142 core.c:329 jtag_call_event_callbacks(): jtag event: TAP reset Debug: 258 143 core.c:1055 jtag_examine_chain(): DR scan interrogation for IDCODE/BYPASS Debug: 259 143 core.c:329 jtag_call_event_callbacks(): jtag event: TAP reset Error: 260 4140 ft2232.c:590 ft2232_read(): couldn't read enough bytes from FT2232 device (0 81) Error: 261 4140 ft2232.c:845 ft2232_send_and_recv(): couldn't read from FT2232 Error: 262 4141 core.c:1479 jtag_init_inner(): Trying to use configured scan chain anyway... Debug: 263 4141 core.c:1219 jtag_validate_ircapture(): IR capture validation scan Error: 264 8140 ft2232.c:590 ft2232_read(): couldn't read enough bytes from FT2232 device (0 2) Error: 265 8140 ft2232.c:845 ft2232_send_and_recv(): couldn't read from FT2232 Debug: 266 8141 core.c:329 jtag_call_event_callbacks(): jtag event: TAP reset Warn : 267 8141 core.c:1503 jtag_init_inner(): Bypassing JTAG setup events due to errors Debug: 268 8142 openocd.c:150 handle_init_command(): Examining targets... Debug: 269 8142 command.c:151 script_debug(): command - ocd_command ocd_command type ocd_flash init Debug: 270 8143 command.c:151 script_debug(): command - ocd_flash ocd_flash init Debug: 271 8143 log.c:437 keep_alive(): keep_alive() was not invoked in the 1000ms timelimit (8143). This may cause trouble with GDB connections. Debug: 274 8144 tcl.c:912 handle_flash_init_command(): Initializing flash devices... Debug: 275 8145 command.c:151 script_debug(): command - ocd_command ocd_command type ocd_mflash init Debug: 276 8145 command.c:151 script_debug(): command - ocd_mflash ocd_mflash init Debug: 278 8146 mflash.c:1331 handle_mflash_init_command(): Initializing mflash devices... Debug: 279 8146 command.c:151 script_debug(): command - ocd_command ocd_command type ocd_nand init Debug: 280 8147 command.c:151 script_debug(): command - ocd_nand ocd_nand init Debug: 282 8147 tcl.c:521 handle_nand_init_command(): Initializing NAND devices... Debug: 283 8148 command.c:151 script_debug(): command - ocd_command ocd_command type ocd_pld init Debug: 284 8149 command.c:151 script_debug(): command - ocd_pld ocd_pld init Debug: 286 8149 pld.c:232 handle_pld_init_command(): Initializing PLDs... 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.zipcan=2q=). I get the same result. Anybody have any hints?
Re: [Openocd-development] couldn't read enough bytes from FT2232 device (0 81)
On Tue, Aug 16, 2011 at 9:18 AM, Eric Wetzel thewet...@gmail.com wrote: This problem again. I see plenty of e-mails in the past supposedly addressing it, but none worked for me. I'm trying to use a TI/Blackhawk USB100v2, which I think is supposed to be identical to an XDS100v2, so I am using the interface/xds100v2.cfg file. I'm using Freddie's OpenOCD 0.5.0 build under Windows 7. Debug: 231 123 ft2232.c:2469 ft2232_init(): ft2232 interface using shortest path jtag state transitions Debug: 232 123 ft2232.c:2342 ft2232_init_libftdi(): 'ft2232' interface using libftdi with 'xds100v2' layout (0403:a6d0) Debug: 233 129 ft2232.c:2389 ft2232_init_libftdi(): current latency timer: 2 Debug: 234 130 ft2232.c:2400 ft2232_init_libftdi(): FTDI chip type: 4 2232H Debug: 235 131 ft2232.c:2426 ft2232_set_data_bits_low_byte(): 80 3a 7b Debug: 236 131 ft2232.c:2446 ft2232_set_data_bits_high_byte(): 82 00 59 Debug: 237 132 ft2232.c:2446 ft2232_set_data_bits_high_byte(): 82 86 59 Info : 238 132 ft2232.c:647 ft2232h_ft4232h_clk_divide_by_5(): max TCK change to: 3 kHz Debug: 239 134 core.c:1602 adapter_khz_to_speed(): convert khz to interface specific speed value Debug: 240 134 core.c:1606 adapter_khz_to_speed(): have interface set up Debug: 241 135 ft2232.c:615 ft2232h_ft4232h_adaptive_clocking(): 96 Debug: 242 135 core.c:1602 adapter_khz_to_speed(): convert khz to interface specific speed value Debug: 243 136 core.c:1606 adapter_khz_to_speed(): have interface set up Info : 244 136 core.c:1424 adapter_init(): RCLK (adaptive clock speed) Debug: 245 137 openocd.c:137 handle_init_command(): Debug Adapter init complete Debug: 246 137 command.c:151 script_debug(): command - ocd_command ocd_command type ocd_transport init Debug: 247 138 command.c:151 script_debug(): command - ocd_transport ocd_transport init Debug: 249 138 transport.c:255 handle_transport_init(): handle_transport_init Debug: 250 139 ft2232.c:1749 xds100v2_reset(): trst: 0, srst: 0, high_output: 0x96, high_direction: 0x59 Debug: 251 139 core.c:713 jtag_add_reset(): SRST line released Debug: 252 140 core.c:737 jtag_add_reset(): TRST line released Debug: 253 140 core.c:329 jtag_call_event_callbacks(): jtag event: TAP reset Debug: 254 141 command.c:151 script_debug(): command - ocd_command ocd_command type ocd_jtag arp_init Debug: 255 141 command.c:151 script_debug(): command - ocd_jtag ocd_jtag arp_init Debug: 256 142 core.c:1435 jtag_init_inner(): Init JTAG chain Debug: 257 142 core.c:329 jtag_call_event_callbacks(): jtag event: TAP reset Debug: 258 143 core.c:1055 jtag_examine_chain(): DR scan interrogation for IDCODE/BYPASS Debug: 259 143 core.c:329 jtag_call_event_callbacks(): jtag event: TAP reset Error: 260 4140 ft2232.c:590 ft2232_read(): couldn't read enough bytes from FT2232 device (0 81) Error: 261 4140 ft2232.c:845 ft2232_send_and_recv(): couldn't read from FT2232 Error: 262 4141 core.c:1479 jtag_init_inner(): Trying to use configured scan chain anyway... Debug: 263 4141 core.c:1219 jtag_validate_ircapture(): IR capture validation scan Error: 264 8140 ft2232.c:590 ft2232_read(): couldn't read enough bytes from FT2232 device (0 2) Error: 265 8140 ft2232.c:845 ft2232_send_and_recv(): couldn't read from FT2232 Debug: 266 8141 core.c:329 jtag_call_event_callbacks(): jtag event: TAP reset Warn : 267 8141 core.c:1503 jtag_init_inner(): Bypassing JTAG setup events due to errors Debug: 268 8142 openocd.c:150 handle_init_command(): Examining targets... Debug: 269 8142 command.c:151 script_debug(): command - ocd_command ocd_command type ocd_flash init Debug: 270 8143 command.c:151 script_debug(): command - ocd_flash ocd_flash init Debug: 271 8143 log.c:437 keep_alive(): keep_alive() was not invoked in the 1000ms timelimit (8143). This may cause trouble with GDB connections. Debug: 274 8144 tcl.c:912 handle_flash_init_command(): Initializing flash devices... Debug: 275 8145 command.c:151 script_debug(): command - ocd_command ocd_command type ocd_mflash init Debug: 276 8145 command.c:151 script_debug(): command - ocd_mflash ocd_mflash init Debug: 278 8146 mflash.c:1331 handle_mflash_init_command(): Initializing mflash devices... Debug: 279 8146 command.c:151 script_debug(): command - ocd_command ocd_command type ocd_nand init Debug: 280 8147 command.c:151 script_debug(): command - ocd_nand ocd_nand init Debug: 282 8147 tcl.c:521 handle_nand_init_command(): Initializing NAND devices... Debug: 283 8148 command.c:151 script_debug(): command - ocd_command ocd_command type ocd_pld init Debug: 284 8149 command.c:151 script_debug(): command - ocd_pld ocd_pld init Debug: 286 8149 pld.c:232 handle_pld_init_command(): Initializing PLDs... 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
Re: [Openocd-development] couldn't read enough bytes from FT2232 device (0 81)
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.zipcan=2q=). 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. -- Xiaofan ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] couldn't read enough bytes from FT2232 device (0 81)
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.zipcan=2q=). 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: 3 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
