[casper] Suggested convention for writing registers

Hello all, I've given some thought to the topic of writing (and reading) registers on the ROACH using the python corr module. Often in a design a single register may be sliced into many bits to control various things. The way I've normally seen such a register written in python looks something

Re: [casper] Suggested convention for writing registers

Hi Paul, Thanks for the link. I looked through the code a bit and it doesn't seem as though the corr library at all. Have I been using the wrong tool for the job? Would you be able to point me to which file I should start with to get a handle on how the casperfpga package works? Regards, James

Re: [casper] Suggested convention for writing registers

Morning James We do this in already in the casperfpga package: https://github.com/ska-sa/casperfpga It turns out construct is pretty slow, so we just do the conversions and shifts manually. I think currently the fpg files that are automatically parsed by casperfpga are only generated for ROACH2,

Re: [casper] Suggested convention for writing registers

On Fri, Mar 20, 2015 at 7:08 AM, James Smith jsm...@ska.ac.za wrote: Hello all, I've given some thought to the topic of writing (and reading) registers on the ROACH using the python corr module. Often in a design a single register may be sliced into many bits to control various things. The

Re: [casper] Suggested convention for writing registers

Hello Marc, Thanks for the comments - I've just sat down with Paul and he's mentioned similar things to what you have. The only challenge with that is tcpborphserver3 doesn't run on ROACH yet, only ROACH2 as I understand. I'm going to have a bit of a go at using the casperfpga library anyway and