Skip to main content
Topic: busblaster 4.1V and OpenOCD (Read 52 times) previous topic - next topic

busblaster 4.1V and OpenOCD

Hi I have a 4.1 that I got years back when it was recently released. I am trying to get it up again now and I keep getting errors from OpenOCD.

The following is what I get when I use the instructions in your manual. What changes should I be making if any to the cfg file now that ft2232 is depreciated for ftdi?

openocd -f busblaster.cfg
Open On-Chip Debugger 0.10.0
Licensed under GNU GPL v2
For bug reports, read
   http://openocd.org/doc/doxygen/bugs.html
Error: The specified debug interface was not found (ft2232)
The following debug interfaces are available:
1: ftdi
2: usb_blaster
3: amt_jtagaccel
4: gw16012
5: presto
6: usbprog
7: openjtag
8: jlink
9: vsllink
10: rlink
11: ulink
12: arm-jtag-ew
13: buspirate
14: hla
15: osbdm
16: opendous
17: sysfsgpio
18: aice
19: cmsis-dap

 

Re: busblaster 4.1V and OpenOCD

Reply #1
Never mind I found most of it here. https://gist.github.com/kevinmehall/71db7951c7538541eee2

Please update the wiki page.

###### Bus Blaster

interface ftdi
ftdi_device_desc "Dual RS232-HS"
ftdi_vid_pid 0x0403 0x6010

ftdi_layout_init 0x0c08 0x0f1b
ftdi_layout_signal nTRST -data 0x0100 -noe 0x0400
ftdi_layout_signal nSRST -data 0x0200 -noe 0x0800

adapter_khz 1000

reset_config srst_only

transport select jtag
#the other option is swd - this bit I had to look up