Re: [casper] Roach2 Tutorial 4 Troubles (Can't Compile .slx or Upload .fpg)

2016-12-02 Thread Alec Josaitis
Dear Jack, I just wanted to follow-up with my last message, about the broken "shared bram" connections. Any new suggestions? I hope we're close to resolve this issue, as there are no other errors displayed by MATLAB. Thanks for all the help you've given, and any more that you may be able to

[casper] Appropriate Clock input

2016-12-02 Thread Miller, Eric H.
??Hi All, I'm using a ROACH1 board with the ADC6x1000-12 DAQ card. I would like to use an external clock, but am having trouble finding what input settings (voltage, pedestal) to use for the clock signal. Can anybody suggest the right input settings? Thanks, Eric SDSM

Re: [casper] Problem reading DRAM in ROACH2

2016-12-02 Thread Franco
No, I'm using the tutorial version. That might be the problem. However I'm reluctant to update since this might cause incompatibilities with my previous models. I suppose that if I what to use the DRAM I don't have other choice. Do you have any suggestions? Many thanks, Franco Jason

Re: [casper] Problem reading DRAM in ROACH2

2016-12-02 Thread Jason Manley
Are you running the latest version of the toolflow? Earlier versions did not include the CPU interface to the DRAM. Jason On 02 Dec 2016, at 15:30, Franco wrote: > The register is not present in the bitstream. I thought that the register was > inside the dram yellow

Re: [casper] Problem reading DRAM in ROACH2

2016-12-02 Thread Franco
The register is not present in the bitstream. I thought that the register was inside the dram yellow block though. I have to add it manually or something? Here is the listdev just in case: ['acc_len', 'adc5g_controller', 'cnt_rst', 'dout0_0', 'dout0_1', 'dout0_2', 'dout0_3', 'dout1_0',

Re: [casper] Problem reading DRAM in ROACH2

2016-12-02 Thread Marc Welz
Then there is no bitstream programmed or the particular bitstream doesn't contain that register. Type ?listdev on that connection to find out regards marc On Fri, Dec 2, 2016 at 12:52 PM, Franco wrote: > It says: #log error 1018802834854 raw >