Yeah read_dram should work just fine! Jason
On 02 Aug 2016, at 18:18, Franco <francocuro...@gmail.com> wrote: > Thank you Jason, > > > Do you know if the "read_dram()" function would work as well, or should I > stick to read()? > > > Franco > > > On 02/08/16 05:46, Jason Manley wrote: >> Hi Franco >> >> You've uncovered a weirdness with the tools: unlike most other blocks, for >> QDR and DRAM the memory names are static, regardless of design hierarchy or >> block names. And as you've discovered, the standard snapshot function >> expects to retrieve the captured data from a contained bram memory. >> >> For now, you'll probably want to manually read the dram memory with the >> normal read() function. And you'll have to unpack it manually. >> >> One possible (better) long-term solution might be to have the dram snapshot >> block be identified with a different xps tag. Then casperfpga can tell it >> apart and do this automatically for you. >> >> Jason >> >> On 01 Aug 2016, at 23:43, Franco Curotto <francocuro...@gmail.com> wrote: >> >>> Dear Casper Community, >>> >>> I'm trying to use the snapshot block with the DRAM as storage medium to >>> save "instantaneous" spectra (in ROACH I). >>> >>> I'm running into troubles when I try to read the snapshot, I used the >>> function "get_snapshot()", but I get an error when the snapshot tries to >>> read the memory as: "?read snapshot_bram >>> 0 8192". >>> >>> So apparently with that function I can only read the bram version of the >>> snapshot: then what is the correct way to read the data from DRAM-snapshot? >>> >>> Sorry if this question is too basic. >>> >>> Thanks, >>> >>> Franco. >>> >>> >
