Skip to main content ↑ ↓

Topics

This section allows you to view all Topics made by this member. Note that you can only see Topics made in areas you currently have access to.

Topics - tormod

1
Bus Blaster JTAG debugger / Bus Blaster V3 TDO stuck at 1 Continued...
I finally got some time to look at this issue again.

In order to verify my setup I invested in a Flyswatter.

. Linux 64 bit, 12.04 LTS
. Latest SVN of urjtag
. Make sure usbserial.ko will not load.
. Configured urjtag: ./configure  --without-ftd2xx
. Connected to my target using the Flyswatter all good, chain detected.

Note:
I could not get the urjtag to properly detect my target if I used the official ftd2xx (1.2) library.

Started investigating the Bus Blaster again.

. Compiled some libftdi examples, verified that I could read out the correct chip type on the BB V3
. Created a cable suitable for my target
. Connected all together still get:

> cable ft2232 pid=0x6010 vid=0x403 interface=0
> detect
warning: TDO seems to be stuck at 1

. Installed the SVF file (bbv3.zip) that Will posted in the previous thread, same result.

Questions:
. Is the BB V3 compatible with the V2 ?
. What is the correct bitstream to use for the V3 board ?
. If the BB is JTAGKey or KT-Link compatible why does it have to be detected as a generic ft2232 ?
. When will you create a proper package for BB V3 like the one which exists for V2 ?
2
Bus Blaster JTAG debugger / Bus Blaster V3 TDO stuck at 1
I recently bought a bus blaster v3. My operating system is: Ubuntu 12.04 64 bit.

I have pulled the latest version of urjtag from the SVN configured with: --with-ftd2xx --without-libftdi

The bus blaster is not powering the target, the jumper is open.

If I connect the bus blaster to my machine without any target connected I get this:

Code: [Select]
jtag> cable ft2232 pid=0x6010 vid=0x403 interface=1
Connected to libftd2xx driver.
jtag> detect
IR length: 8
Chain length: 1
Device Id: 00000110111000011100000010010011 (0x06E1C093)
  Manufacturer: Xilinx (0x093)
  Part(0):      xc2c32a-vq44 (0x6E1C)
  Stepping:     0
  Filename:     /usr/local/share/urjtag/xilinx/xc2c32a-vq44/xc2c32a-vq44

I am assuming that channel 1 goes to the CPLD itself and channel 0 is for access to the JTAG header.

Connect the cables to my target and power on target:

Code: [Select]
jtag> cable ft2232 pid=0x6010 vid=0x403 interface=0
Connected to libftd2xx driver.
jtag> detect
warning: TDO seems to be stuck at 1
jtag> detect

Now I get: TDO seems stuck at 1.

The most baffling part is that this works with an Altera byteblaster using urjtag.

Anyone have any suggestions to what I might be doing wrong ?

( ! ) Fatal error: Uncaught exception 'Elk_Exception' with message 'Please try again. If you come back to this error screen, report the error to an administrator.' in /var/www/dangerousprototypes/forum/sources/database/Db-mysql.class.php on line 696
( ! ) Elk_Exception: Please try again. If you come back to this error screen, report the error to an administrator. in /var/www/dangerousprototypes/forum/sources/database/Db-mysql.class.php on line 696
Call Stack
#TimeMemoryFunctionLocation
10.04112280072session_write_close ( )...(null):0
20.04142411672ElkArte\sources\subs\SessionHandler\DatabaseHandler->write( )...(null):0
30.04142412448Database_MySQL->query( ).../DatabaseHandler.php:119
40.08602551184Database_MySQL->error( ).../Db-mysql.class.php:273