Still lots of snow here. So now I am stuck at home with lots of time to play with the BBv4. For some reason I was not able to replicate the previous success anymore. I have a feeling it is something related to the driver or maybe even UrJtag being messed up. Today I was going to test the svf programming, but it detected the device one time and then not anymore. I am not sure why. This is the output I am having consistently today:
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> bsdl path d:bsdl jtag> cable jtagkey pid=0x6010 vid=0x0403 Connected to libftd2xx driver. jtag> detect Error: parse.c:208 urj_parse_file() no error: Cannot open file 'C:UsersMockba/ .jtag/rc' to parse jtag>
I was able to detect the device once and the not anymore. Right now I am using the buffer code provided by Joe previously, which is the one that was able to detect before also. I have also tried loading back the original buffer code and no success there either. I am not sure how to use the bbv4-passthrough buffer code Joe provided, do I am back at square one again.
When trying to repeat different versions of the command and also combine different parameters I ended up forgetting to add the interface=0, and this seems to have solved the problem. 2 out of 3 times it will detect the device correctly, so I can consider this a big advance. I didn't try to write a svf stream to it yet, gotta go outside to some sow shoveling, but I will certainly do it later today.
Thanks a lot for insisting on my, it was a big help.
jtag> cable jtagkey interface=0 pid=0x6010 vid=0x0403 driver=ftdi-mpsse Couldn't connect to suitable USB device. Error: parse.c:208 urj_parse_file() no error: Cannot open file 'C:UsersMockba/.jtag/rc' to parse jtag>
At this point I am not sure anymore if I made the right decision when purchasing the latest BusBlaster. Maybe I should have purchased the v2.x. Or none at all. I basically see no support from Dangerous Prototypes other than occasional answers to my eMails from Ian that he doesn't tend to follow up afterwards. Maybe he's too busy to deal with this, maybe the product doesn't work at all, I don't know. After all nobody replied to my post asking if anyone else was using the same version as I am. Maybe no one is. Other than some valuable help like I am getting from you here, there's nothing else. Maybe I will just throw this device on my "old boards" box and leave it there to scavenge for parts. My mistake buying it without researching first.
Anyways, thanks a lot for helping with all this. I am still believing that this issue may be caused by some simple mistake that I am making or some simple incompatibility that could be easily solved if Dangerous Prototypes spent some time troubleshooting it. I think that when a company sells a prototype as a product they must understand that we stop being fellow experimenters and start being regular customers, which need some level of support or guidance from the people who develop it.
Sorry for venting out on a reply to you, but I needed to vend out to someone who is at least listening to me :)
Again, thanks a lot for the ideas. Let me know if you have any other that may help get this to work.
I have loaded your bbv4-jtagkey.svf stream into the internal buffer and made the following connections:
BBv4 -> OLS VTG -> 2v5 GND -> GND TDI -> TDI TMS -> TMS TDO -> TDO TCK -> TCK Left the JP4 open, meaning the target is self-powered. The yellow(ish) LED blinks and then stays lit until I connect to the driver. I have the following results:
UrJTAG 0.10 #1869 ... jtag> cable jtagkey pid=0x6010 vid=0x0403 interface=0 Connected to libftd2xx driver. (yellow LED turns off here) jtag> bsdl path D:/bsdl jtag> detect Error: parse.c:208 urj_parse_file() no error: Cannot open file 'C:UsersMockba/ .jtag/rc' to parse jtag>
I don't know what this .jtag/rc file should be. Not sure if this is an improvement or not. If I use the ft2232 cable instead of jtagkey I get the "stuck at 0" message before the .jtag/rc one.
You seem to have solved the same problem I am having on my 4.1a ... is there any chance you can share the before/after files with me so I can try the same change on my 4.1a code? I have been trying for support here so far with no results, so maybe your solution will drag me out of the swamp.
Yes, I've used the patched urjtag version provided in the forum. So far I believe I am doing everything correctly. I must be missing some stupid detail. Thanks immensely for the help.
Please don't see this as a rant post, even though it may be a little. I am wondering: does anybody here have a working Bus Blaster 4.1a (Jul 2012)? If so, please share the details of what you did to make it work. I have been trying to operate mine under Windows 7 - 64 bits with no luck so far. I have installed/reinstalled the latest FTDI drivers. Used the latest urJTAG with the modded (v11) version for the interface=0/1 option. It passes self-test consistently, it always programs the internal buffer normally (with BBv4-JTAGkey-selftest-v1.1.svf), but that's it. Once I get it connected to a target it gets TDO either stuck at 1 or 0, depending on which target I connect. I am at the point of giving up and start using it as a simple CPLD prototype board (to which I don't have any use). So, please, if anybody is using this specific device successfully, share the details of your setup. Which O.S., which driver, cable setup, etc. I will be much appreciated. Please answer only if you are using the v4.1a, as it seems people is being able to use the v2 successfully.
Good point. I will give it a try on a 32bit Windows XP I still have here. It is still strange for me that the self test passes all the time. Meaning the signals are reaching the JTAG connector and coming back. However a test on a 32 bit will definitely give some better clue or help rule out driver issues. Good idea. I will test it and report back.
I am having, I believe, the same problem as you. Please see my post: viewtopic.php?t=6058&p=55865 My board passes self-test and also programs the internal buffer normally, so I am not sure where to look anymore. If you could share some of the "voodoo rituals" you used I would be grateful.
An update ... still no success. I have tried completely cleaning up the FTDI drivers from my computer and reinstalling them after a reboot ... no success. I have tried again to read the FPGA from my Open Logic Sniffer, no success either. The connection from my BB4.1a to my Open Logic Sniffer are: VTG -> 2V5 GND -> GND TDI -> TDI TMS -> TMS TCK -> TCK TDO -> TDO Both boards plugged to USB ports on my laptop
I ran the self test again on the BB4 board just to make sure I was not seeing things, but the test still passes with zero errors and I am still able to "see" the internal CPLD buffer by selecting interface=1 when in "Update Buffer" mode. I have simulated errors by taking jumpers out of the test and saw that the test fails accordingly. So I still have no clue of what is going on.
