OS Windows 7 - 64 bit
Files being used are in BusBlasterv3.zip from viewtopic.php?f=37&t=3993 (http://dangerousprototypes.com/forum/viewtopic.php?f=37&t=3993)
I have the power jumper in place but no target connected yet.
I struggled trying to use a downloaded version of urJTAG and then I discovered the modified one that's in the above zip file jtag-rev11.exe.
My problem appears to be that the bsdl file is not recognized. Here's what I can do....
UrJTAG 0.10 #1869
Copyright (C) 2002, 2003 ETC s.r.o.
Copyright (C) 2007, 2008, 2009 Kolja Waschk and the respective authors
UrJTAG is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
There is absolutely no warranty for UrJTAG.
jtag.c:518 main() Warning: UrJTAG may damage your hardware!
Type "quit" to exit, "help" for help.
jtag> cable ft2232 interface=1
Connected to libftd2xx driver.
jtag> detect
IR length: 8
Chain length: 1
Device Id: 00000110111000011100000010010011 (0x06E1C093)
Unable to open file 'c:tempurjtagdata/MANUFACTURERS'
Unknown manufacturer! (00001001001) (c:tempurjtagdata/MANUFACTURERS)
jtag>
I'm running the jtag-rev11.exe file as Admin from c:Tempurjtag and I've tried putting the xc2c32a_vq44.bsd into a sub directory and right now it's in the same directory. I've also tried...
jtag> bsdl path c:tempurjtag
with the file in the right directory but I always get the same as the code snippet above.
Any ideas?
Glad you found the patched version. As far as I know they have not released an updated windows compile with our second channel patch (which was accepted).
http://dangerousprototypes.com/docs/Bus ... _to_urJTAG (http://dangerousprototypes.com/docs/Bus_Blaster_urJTAG_guide#Adding_a_new_device_to_urJTAG)
Here is the process for talking to the onboard CPLD. The ID you're getting is correct.
jtag> bsdl path c:bsdl
Is needed for sure. What error message do you get when you detect after changing the path? still about data/manufacturers?
You might also try / instead of (path c:/bsdl)
OK, I got it working. For others following in my steps here's the check list. Remember my system is Windows 7-64 bit and I'm trying to make Bus Blaster V3c work with urJTAG.
1. Download urJTAG vn 0.10
2. Download BusblasterV3.zip download/file.php?id=7756 (http://dangerousprototypes.com/forum/download/file.php?id=7756)
3. Install urJTAG into default Program Files(x86) directory
4. Find file jtag-rev11.exe in zip file and copy it into the same directory that jtag.exe is in (as per step 3)
5. Use file explorer to fing jtag-rev11.exe, right click and chose 'run as administrator' - a command prompt should open with the JTAG start up messages.
6. At jtag> prompt, type 'cable jtagkey interface=0' - you should get a message about FT2232xx cable being used
7. With target connected, type 'detect' at jtag> prompt
FYI, I had problems trying to read blacfin devices using this version of urJTAG but the Bus Blaster seemed to work OK.
As a suggestion, it would help if there were lists of known working setups linked to all Bus Blaster device pages, the V3 seems particularly confusing from this perspective.
Thanks for the help
[quote author="Gandalf"]OK, I got it working. For others following in my steps here's the check list. Remember my system is Windows 7-64 bit and I'm trying to make Bus Blaster V3c work with urJTAG.
1. Download urJTAG vn 0.10
2. Download BusblasterV3.zip download/file.php?id=7756 (http://dangerousprototypes.com/forum/download/file.php?id=7756)
3. Install urJTAG into default Program Files(x86) directory
4. Find file jtag-rev11.exe in zip file and copy it into the same directory that jtag.exe is in (as per step 3)
5. Use file explorer to fing jtag-rev11.exe, right click and chose 'run as administrator' - a command prompt should open with the JTAG start up messages.
6. At jtag> prompt, type 'cable jtagkey interface=0' - you should get a message about FT2232xx cable being used
7. With target connected, type 'detect' at jtag> prompt
[/quote]
The above also functions for V4 under XP 32 bit, only issue is ensuring you have the 'multitude' of files scattered about for the part & an entry in 'parts' to ensure it decodes correctly.
UrJTAG 0.10 #1869
Copyright (C) 2002, 2003 ETC s.r.o.
Copyright (C) 2007, 2008, 2009 Kolja Waschk and the respective authors
UrJTAG is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
There is absolutely no warranty for UrJTAG.
jtag.c:518 main() Warning: UrJTAG may damage your hardware!
Type "quit" to exit, "help" for help.
jtag> cable jtagkey interface=0
Connected to libftd2xx driver.
jtag> detect
IR length: 10
Chain length: 1
Device Id: 01110010101011010110000010010011 (0x72AD6093)
Manufacturer: Xilinx (0x093)
Part(0): XC5VLX110T_FF1136 (0x2AD6)
Stepping: 0111
Filename: c:program filesurjtagdata/xilinx/XC5VLX110T_FF1136/XC5VLX110T
_FF1136
jtag> scan
IO_A14: 0 > 1
IO_A16: 0 > 1
IO_B17: 1 > 0
IO_C15: 0 > 1
IO_C17: 0 > 1
IO_D15: 1 > 0
IO_D17: 1 > 0
IO_D20: 0 > 1
IO_E19: 0 > 1
IO_M33: 1 > 0
IO_R28: 1 > 0
IO_R29: 1 > 0
IO_V32: 1 > 0
IO_V33: 0 > 1
IO_V34: 0 > 1
IO_W34: 1 > 0
IO_AE32: 1 > 0
IO_AE34: 1 > 0
IO_AF33: 1 > 0
IO_AH34: 0 > 1
IO_AJ14: 1 > 0
IO_AJ19: 1 > 0
IO_AJ34: 1 > 0
IO_AK19: 1 > 0
IO_AK24: 1 > 0
IO_AL23: 1 > 0
IO_AM15: 1 > 0
jtag> scan
IO_A14: 1 > 0
IO_A15: 0 > 1
IO_A16: 1 > 0
IO_C17: 1 > 0
IO_D15: 0 > 1
IO_D16: 0 > 1
IO_D17: 0 > 1
IO_D20: 1 > 0
IO_R28: 0 > 1
IO_R29: 0 > 1
jtag>
All in all, the setup is like being punched in the face with a brick, I had to do an exit of the program and a 'cable' 3 times before it finally detected correctly, but after that it was solid with no problems.
I suspect that it's one of those things where if everything is started fresh it is easier.
I had far better luck and setup with 'topjtag' which went straight in used the bus-blaster plus it only requires the FPGA BDSL file to work first time.
I would like to try and reprogram the V4 with the 'picotap' image (to test 'gojtag'), but there is no mention on this site if the 'picotap' image will work without modification on the V4 board or will crash and burn.
Is needed for sure. What error message do you get when you detect after changing the path? still about data/manufacturers????