Write orsc_fe_vmestream_echo_test and validate VMEStream

[ekfriis]

cc @dabelknap

This should sit on the oRSC FE, read a stream via VMEStream and echo it back. Will allow validation of VMEStream.

[ekfriis]

For reference from Mathias:

[9/25/13 9:07:21 PM] mathias blake: --MB READS, VME WRITES
--Address Range: 0x0000-0x07FF
[9/25/13 9:07:26 PM] mathias blake: --MB READS, VME WRITES
--Address Range: 0x0800-0x0FFF
[9/25/13 9:07:39 PM] mathias blake: --VME READS, MB WRITES
--Address Range: 0x1000-0x17FF
[9/25/13 9:07:47 PM] mathias blake: --VME READS, MB WRITES
--Address Range: 0x1800-0x1FFF

[dabelknap]

Ah, okay. uint16_t for the addresses, then?

[ekfriis]

I am not sure - that address range just refers to the size of the RAMS. i.e. there is a RAM at 0x0000, and it's size is 2048 words (almost positive they are words).

[dabelknap]

I mean, the addresses themselves are 16-bit. Otherwise it would be 0x00000000 - 0x000007FF instead, right?

[ekfriis]

They definitely fit in 16bit, but they may be 32bit. You should ask Mathias.

[ekfriis]

Note - at 904, the VME PC connected to the upper crate is l1ts-rct-02. You need to set

export CAEN_LINK=0
export VME_CONTROLLER=CAEN

for vmedia to work.