Do you have a question? Post it now! No Registration Necessary
Subject
- Posted on
VHDL for FPGA VME Slave
- 08-15-2003

Re: VHDL for FPGA VME Slave

Be very, very afraid.
VME was defined as an *asynchronous* protocol to keep it
independent of any CPU's clock. Consequently, any VME
interface needs to be sensitive to EDGES on several different
strobe signals (*DS0, *DS1, *AS and several others). I think
you can do a reasonable job if you are prepared to oversample
all the strobes with a clock of about 80MHz or faster, but
a direct (asynch) implementation in FPGA would be horrible.
Once you've coped with that asynch-strobes nonsense, the main
remaining problem is performance. Given that you're only
accessing a few registers, speed may not be a major problem.
If this is so, the rest of the task is comparatively easy -
just a matter of reading the fine print carefully, so that
you don't get confused about address modifiers, word
widths and burst transfers.
Finally, be careful about electrical specs. VME was defined
around a particular set of LSTTL devices (74LS641-1 bidi
buffers, and a few others). Output drivers need to be able
to sink 64mA, and be 5V-tolerant, to meet the specs. 74F543
bidi latch/buffer chips are your friends here, if you can
still get 'em.
Enjoy!
--
Jonathan Bromley, Consultant
DOULOS - Developing Design Know-how
Jonathan Bromley, Consultant
DOULOS - Developing Design Know-how
We've slightly trimmed the long signature. Click to see the full one.
Site Timeline
- » Which software from Xilinx
- — Next thread in » Field-Programmable Gate Arrays
-
- » Problem with Modelsim Lisence server...
- — Previous thread in » Field-Programmable Gate Arrays
-
- » Division Algorithms
- — Newest thread in » Field-Programmable Gate Arrays
-
- » Replacement for 741
- — The site's Newest Thread. Posted in » Electronics Design
-