1
Bus Blaster JTAG debugger / Re: New BusBlaster owner here!
Regrads,
tornado@dd-wrt.com
Messages
This section allows you to view all Messages made by this member. Note that you can only see Messages made in areas you currently have access to.
Messages - tjtag
Regrads,
tornado@dd-wrt.com
2
Bus Blaster JTAG debugger / Re: New BusBlaster owner here!
I do not usually use OpenOcd except for IXP targets, but I did connect a WRT54Gv4, just to test with IAN's Ft2232H breakout board, the BBv1 pinout may be a little different, I honestly have not looked. Anyway, here is the opnocd-5352.cfg file I'm using with the current trunk:
Code: [Select]
telnet_port 4444
gdb_port 2001
#interface
interface ft2232
ft2232_device_desc "TJTAG-PRO USB FT2232H A"
ft2232_layout "jtagkey"
ft2232_vid_pid 0x0403 0x8a98
jtag_khz 1500
#jtag scan chain
# format L IRC IRCM IDCODE (Length, IR Capture, IR Capture Mask, IDCODE)
#jtag_device 8 0x01 0x7f 0x1e
if { [info exists CHIPNAME] } {
set _CHIPNAME $CHIPNAME
} else {
set _CHIPNAME bcm5352
}
if { [info exists ENDIAN] } {
set _ENDIAN $ENDIAN
} else {
set _ENDIAN little
}
if { [info exists CPUTAPID ] } {
set _CPUTAPID $CPUTAPID
} else {
# force an error till we get a good number
set _CPUTAPID 0x0535217F
}
gdb_memory_map enable
gdb_flash_program enable
#jtag_nsrst_delay 250
#jtag_ntrst_delay 250
#use combined on interfaces or targets that can't set TRST/SRST separately
reset_config srst_only
#reset_config srst_only srst_pulls_trst
#reset_config trst_and_srst separate
#reset_config trst_and_srst srst_pulls_trst
#reset_config trst_and_srst separate trst_push_pull srst_push_pull
#reset_config trst_and_srst separate
#jtag scan chain
#format L IRC IRCM IDCODE (Length, IR Capture, IR Capture Mask, IDCODE)
jtag newtap $_CHIPNAME cpu -irlen 8 -ircapture 0x1 -irmask 0x7f -enable -expected-id $_CPUTAPID
set _TARGETNAME [format "%s.cpu" $_CHIPNAME]
target create $_TARGETNAME mips_m4k -endian $_ENDIAN -chain-position $_TARGETNAME
#$_TARGETNAME configure -work-area-virt 0 -work-area-phys 0x80300000 -work-area-size 0x40000 -work-area-backup 0
#flash bank <driver> <base> <size> <chip_width> <bus_width>
flash bank 0 cfi 0x1fc00000 0x200000 2 2 0
#$_TARGETNAME configure -event halted { script bcm5352.script }
and this is my output, I have not tried flashing with this yet.
Code: [Select]
openocd -f openocd-ftdi-5352.cfg
Open On-Chip Debugger 0.5.0-dev-00808-g68bd107 (2011-03-28-19:00)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.berlios.de/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
1500 kHz
srst_only separate srst_gates_jtag srst_open_drain
Warn : use 'bcm5352.cpu' as target identifier, not '0'
Info : max TCK change to: 30000 kHz
Info : clock speed 1500 kHz
Info : JTAG tap: bcm5352.cpu tap/device found: 0x0535217f (mfg: 0x0bf, part: 0x5352, ver: 0x0)
You will need to change vid/pid and also set _CPUTAPID 0x0535217F in the .cfg file.
P.S. also need to change ft2232_device_desc "TJTAG-PRO USB FT2232H A"
Hope this helps a little.
Regards,
Tornado
3
Bus Blaster JTAG debugger / Re: Re: Compiling urjtag on windows
Great info, please keep us informed !!
4
Bus Blaster JTAG debugger / Re: Compiling urjtag on windows
Also, I have built my own multilib toolchain with mingw64, it helps alot on multiple target builds on the linux side for windows x32/x64 builds
Thanks
5
Bus Blaster JTAG debugger / Re: Compiling urjtag on windows
6
Bus Blaster JTAG debugger / Re: urJTAG for Bus Blaster v2 JTAG B
svn co http://urjtag.svn.sourceforge.net/svnroot/urjtag/trunk urjtag-current
gives us svn verison 1869, I think
7
Bus Blaster JTAG debugger / Re: urJTAG for Bus Blaster v2 JTAG B
8
Bus Blaster JTAG debugger / Re: urJTAG for Bus Blaster v2 JTAG B
if(devInfo.ID == USBID && strstr(devInfo.Description," A")>0)
{
ftStatus = _FT_Open(0, &ftHandle);
ii=0;
break;
}
only needs to be:
if(devInfo.ID == USBID && strstr(devInfo.Description," B")>0)
{
ftStatus = _FT_Open(1, &ftHandle);
ii=0;
break;
}
but this is my src code, I will look at urjtag's
Ian, just found this in urjtag's src
#endif
/* try various methods to open a FTDI device */
if (p->serial)
{
/* serial number/description is specified */
/* first try to match against the serial string */
status = FT_OpenEx (p->serial, FT_OPEN_BY_SERIAL_NUMBER, &p->fc);
if (status != FT_OK)
/* then try to match against the description string */
status = FT_OpenEx (p->serial, FT_OPEN_BY_DESCRIPTION, &p->fc);
}
else
/* give it a plain try */
status = FT_Open (0, &p->fc);
Changed status = FT_Open (0, &p->fc); to status = FT_Open (1, &p->fc);
sending via e-mail now
Regards
9
Bus Blaster JTAG debugger / Re: Compiling urjtag on windows
Check your e-mail, I have sent you a new build with patches to test.
Regards
10
Bus Blaster JTAG debugger / Re: FT2232H EEPROM needed?
The answer to this question is NO, to be more exact, the eeprom allows the configuration of different available modes of the FT2232H chip. Some modes can only be entered into, by programming the eeprom chip. See page 44 od DS_FT2232H.
Does that answer your question more specifically ?
11
Bus Blaster JTAG debugger / Re: urJTAG for Bus Blaster v2 JTAG B
Thanks for the reply,
Actually I write my own software, but it's mostly mips/and atheros based. I use urjtag and openocd for arm targets mostly. I'm adding ft2232h to my software, and looks like this board would do the job.
Regards,
Tornado
12
Bus Blaster JTAG debugger / Re: urJTAG for Bus Blaster v2 JTAG B
Just joined the list, I like what your doing here and am interested in helping/testing.
I'm pretty familiar with urjtag/openocd, etc... I program mostly on the linux side, but have been known to produce a few, win32/win 7 x64 apps.
Let me know if I can help...
I will try to find a link now to get your board.
P.S. Could not find a way to get this board online, could you please contact me via e-mail, or your chioce on how I might get my hands on one of these ?
Regards,
Tornado