Products > Test Equipment
HP/Agilent 1675x logic analyzer card memory up-hack
MarkL:
--- Quote from: DogP on February 05, 2022, 07:54:05 pm ---...
Edit: I just looked at the cards, and the one difference that jumps out at me is that the 'A' uses XCV300 FPGAs, and the 'B' uses XCV300E FPGAs. The Virtex-E is a 1.8V FPGA instead of 2.5V of the original Virtex. Additionally, while the part number sounds like they'd be basically the same FPGA, the 300E has more logic resources than the 300, so they almost certainly require different bit files, which the mainframe would need to be aware of. So, I'd guess the 'A' to 'B' was simply a change to the Virtex-E due to the original Virtex going obsolete.
--- End quote ---
I think you're exactly right on Virtex vs. Virtex-E.
In /usr/sprockets/tools/instrument/16700/16718/, there are two different versions of bit files, yari.rbt and yari_rev2.rbt. The header of yari.rbt:
Xilinx ASCII Bitstream
Created by Bitstream D.27
Design name: yari_g.ncd
Architecture: virtex
Part: v300bg352
Date: Wed Oct 03 08:50:00 2001
Bits: 1751808
The header of yari_rev2.rbt:
Xilinx ASCII Bitstream
Created by Bitstream D.27
Design name: yari_g.ncd
Architecture: virtexe
Part: v300ebg352
Date: Fri Oct 05 09:19:46 2001
Bits: 1875648
The driver is /usr/sprockets/tools/instrument/16700/16718/lib16718.sl and covers the 16718A, 16719A, 16740A, 16741A, 16742A, 16750A, 16750B, 16751A, 16751B, 16752A, and 16752B. This is where the above two bit files are referenced. That family of cards is called "yari" and they all have the same basic architecture. The A and B versions probably operate identically after being loaded with their respective bit files.
Thanks for solving the mystery of A vs. B! That's been bothering me for a long time.
DogP:
Very cool... nice analysis. I've got a lot to learn about this system... I've had a 16500A for ~20 years, and figured it was time to upgrade. :)
DogP
DogP:
Sorta "up-hack" related... has anyone made an adapter to use older logic analyzer cables with the newer units?
I've got a 16550A card in my 16500A, with a bunch of cables, but no cables for my 16750A/Bs. They both go to the standard 40-pin connector, and the 16550A supports up to 500 MHz timing, so it seems a simple adapter to go from the 60-pin to the 50-pin connector would at least be somewhat usable. Is the connector type and/or pinout documented anywhere?
Though maybe with the cost of connectors, it just make sense to find the right cables. If that's the case, any recommendations for sourcing these cables? Is buying cards with cables and scrapping the cards the best way?
Thanks,
DogP
gslick:
--- Quote from: DogP on February 06, 2022, 07:30:28 pm ---Though maybe with the cost of connectors, it just make sense to find the right cables. If that's the case, any recommendations for sourcing these cables? Is buying cards with cables and scrapping the cards the best way?
--- End quote ---
Might be easiest to just buy "for parts" modules that include the cables.
For example, maybe try making offers on something like these. Maybe they would consider lower offers for just the pod cables, and make shipping cheaper too.
16716A https://www.ebay.com/itm/223464547231
16715A https://www.ebay.com/itm/202701121599
16715A https://www.ebay.com/itm/173876217896
Could try an eBay search like this for modules with compatible pod cables:
(hp, hewlett, agilent, keysight) (16715a, 16716a, 16717a, 16718a, 16719a, 16740a, 16741a, 16742a, 16750a, 16751a, 16752a, 16750b, 16751b, 16752b, 16910a, 16911a)
Or maybe other members here have modules which have failed and they might consider selling the pod cables.
DogP:
Thanks... yeah, I'll probably just end up making an offer on a set.
DogP
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version