Skip to main content
Topic: Bus Blaster v2 (Read 31363 times) previous topic - next topic

Bus Blaster v2

Updates:
*CPLD instead of logic chips
*EEPROM?
*mini dev board (program CPLD with second JTAG channel)
Got a question? Please ask in the forum for the fastest answers.

Re: Bus Blaster v2

Reply #1
*CLPD or FPGA? Which is better in this situation?
*If there is FPGA, definitely and EEPROM, otherwise is it needed?
* Even though it is not used normally, I would prefer a second JTAG channel for "hackability"

Re: Bus Blaster v2

Reply #2
This is a little to short, and follows up from my post in the other thread :)

CPLD:
super simple logic replacement.
only $1 is 1sies
existing reference designs
static design (FPGA usually has to load at startup, so a ROM or manual loader is needed)

It's pretty hard to bring out all the extra pins on a complex 2-layer board :) We'll do our best, but my current philosophy is to get the design done, and bring the extra stuff out on a revision. The CPLD will use the second JTAG channel to be reprogrammed as needed. That can also sub as a mini development board.
Got a question? Please ask in the forum for the fastest answers.

Re: Bus Blaster v2

Reply #3
 robots is volunteering for the v2 test/development :)
I have done some work with xc95xx and i would be happy to help with the design.

I would suggest to use the xillinx part, as people would not need to install another development IDE. (those people that already own OLS).

Re: Bus Blaster v2

Reply #4
You're the one who pointed this out :)

I'm using XC2C32A:
http://www.xilinx.com/support/documenta ... /ds310.pdf
Got a question? Please ask in the forum for the fastest answers.

Re: Bus Blaster v2

Reply #5
Here's a sketch.

What I like about this design--
*Cheap, and simple routing
*'better' translation than the buffer chips
*built in development board (for learning CPLD basics)
*uni-clone JTAG programmer

If we include the EEPROM for the FT2232 (settable USB IDs, device strings), then we can make it enumerate as *any* FT2232-based programmer :)

If we connect all (most) of the MSSPE1 port to the CPLD, then the CPLD can have a bitstream implementing a clone of any JTAG programmer interface :)

It can be a JTAGkey, OpenOCD, etc, etc. What fun!
Got a question? Please ask in the forum for the fastest answers.

Re: Bus Blaster v2

Reply #6
Here' the dia and png for it.

Re: Bus Blaster v2

Reply #7
I had to program a 50 attiny13's recently and my father brought me universal programmer from his workplace because it's easier than inserting every chip into dil8 and buspirate (I don't have any zif socket)... anyway I liked very much how it works and wanted to make suggestion for universal programmer project... but bus blaster v2 with zif socket daughter board is what it's all about :) . I opened programmer ant took pictures of it maybe you get some design idea...

http://www.transpapers.com/galep/DSC_4055_resize.JPG
http://www.transpapers.com/galep/DSC_4056_resize.JPG
http://www.transpapers.com/galep/DSC_4057_resize.JPG
http://www.transpapers.com/galep/DSC_4058_resize.JPG
http://www.transpapers.com/galep/DSC_4059_resize.JPG
http://www.transpapers.com/galep/DSC_4060_resize.JPG
http://www.transpapers.com/galep/DSC_4061_resize.JPG
http://www.transpapers.com/galep/DSC_4062_resize.JPG
http://www.transpapers.com/galep/DSC_4063_resize.JPG
http://www.transpapers.com/galep/DSC_4064_resize.JPG
http://www.transpapers.com/galep/DSC_4065_resize.JPG
http://www.transpapers.com/galep/DSC_4066_resize.JPG


I know it's offtopic but I liked zif so much and was thinking how nice it would be to have buspirate pic/avr zif board... I know avr is problematic and would need lot of jumpers just an idea...

Re: Bus Blaster v2

Reply #8
[quote author="ian"]
If we connect all (most) of the MSSPE1 port to the CPLD, then the CPLD can have a bitstream implementing a clone of any JTAG programmer interface :)
[/quote]

I would suggest connecting all of the portA of ft2232 to cpld bank x, and have all of the bank y pins broken out. This way we could use the FT2232 in any possible mode.

Re: Bus Blaster v2

Reply #9
@siklosi - we're working on it :) PiratePICprog is intended to do it for PICs on Bus Pirate and FT2232, and AVRs are easy to program.

@robots - thanks, good suggestion. I'll try to post an intro schematic tomorrow.
Got a question? Please ask in the forum for the fastest answers.

Re: Bus Blaster v2

Reply #10
Quote
@siklosi - we're working on it :) PiratePICprog is intended to do it for PICs on Bus Pirate and FT2232, and AVRs are easy to program.

I was thinking about simple board with 40pin ZIF socket and on the other side 2x5 connector for bp... no electronics just jumpers to select type of avr inserted that will lead right signals to pins of inserted avr


Re: Bus Blaster v2

Reply #12
Another suggestion is to use Bank 2 as the interface to ft2232, and route the TCK (probably also clkout) signal to one of those GCKx pins. These are global clocks, optimized for clock routing inside the cpld.


Re: Bus Blaster v2

Reply #14
I'm taking a look at the TI connections to get ideas. Maybe it is better to have RTCK as GCK?
Got a question? Please ask in the forum for the fastest answers.