Bus Blaster v2 manufacturing resources

From DP

Revision as of 11:32, 19 February 2013 by Ian (Talk | contribs)
Jump to: navigation , search

Contents

Setup

Download and install the drivers:

Download and install urJTAG:

Download the CPLD implementation:

Bus_Blaster_v3_manufacturing_resources

Programming the CPLD with urJTAG

Bus Blaster v3 can program the CPLD itself using our patched version of urJTAG. Hopefully our patches will be included in an official release soon.

Patched urJTAG

We patched urJTAG to allow the Bus Blaster v2 to self-program. Follow these steps to setup:

  1. Download and install UrJTAG
  2. Copy the patched .exe file (urjtag-revXX.exe) to the install location (C:\Program Files\UrJTAG)
  3. Copy in.txt to the UrJTAG install location (C:\Program Files\UrJTAG)
  4. Copy \bsdl and \svf to c:\

Program

Run the patched version of UrJTAG (urjtag-revXX.exe) 

jtag> include ./in.txt
Connected to libftd2xx driver.
IR length: 8
Chain length: 1
Device Id: 00000110111000011100000010010011 (0x06E1C093)
 Filename:     c:/bsdl/xc2c32a_vq44.bsd
Parsing    660/664 ( 99%)
Scanned device output matched expected TDO values.
jtag>

At the UrJTAG command prompt type include ./in.txt to run the in.txt script and program the Bus Blaster.

Hardware selftest

Bbv2-manufacturing-test-self-test.png

The hardware self test is part of the factory jtagkey-compatible buffer shipped with the Bus Blaster v2. This mode allows testing all the connections between the FT2232 and CPLD, and CPLD to pin header. 

Warning!!!
Ensure Bus Blaster is in test mode before running the test
Conflicting pin directions during the test could fry a chip
Test connections
PinA PinB
TRST TDI
TMS TCK
RTCK TDO
TSRST DBGRQ
P28/IO09GND
JP4JP4


  1. Unplug the Bus Blaster!
  2. Place a jumper on JP4. This powers the buffer from the main power supply
  3. Connect the pin headers as shown in the table. The P28/IO09 connection activates the test buffer
  4. Plug in the Bus Blaster
  5. Pin P19/IO15 will measure 3.3volts if the test mode is active
  6. Run the test utility .bat file
  7. The test reports success or fail
  8. Unplug the Bus Blaster before removing the connections 
We highly recommend users upgrade to a non-selftest buffer immediately.
Retrieved from "http://dangerousprototypes.com/docs/Bus_Blaster_v2_manufacturing_resources"