ska-sa / casperfpga Goto Github PK

Hi Folks,
We've found that to get casperfpga working with our roach2 based system we need to add the additional patch of:

if hasattr(katcp.CallbackClient, 'MAX_WRITE_BUFFER_SIZE'):
    setattr(katcp.CallbackClient, 'MAX_WRITE_BUFFER_SIZE',
            katcp.CallbackClient.MAX_WRITE_BUFFER_SIZE * 10)

in katcp_fpga.py (v0.4.2) or probably in transport_katcp.py for v3.1 (untested). We aren't keen on this because it means forking and diving into internals.

Is there an undocumented way of perhaps calling casperfpga.katcp_fpga.KatcpFpga with a MAX_MESSAGE_LEN argument or some such so we can both avoid the write buffer overflow and mucking around with or forking the repo?

https://github.com/ska-sa/casperfpga/blob/master/src/transport_skarab.py#L2536
https://github.com/ska-sa/casperfpga/blob/master/src/transport_skarab.py#L2522

Few things I need to change before installing the casperfpga package.

In requirements.txt I changed version katcp 0.6.2 to katcp 0.6.3
in the setup.py following corrections needed.
2A)data_files = ['src/tengbe_mmap.txt', 'src/tengbe_mmap_legacy.txt']
2B)include_package_data=True, We need to include this line inside setup
2C)package_data={ "": ["*.txt"],'casperfpga': data_files},

I noticed that the shared_bram.read() on casperfpga function struggles to read > 32 bit values. I was able to readback all the values using the standard fpga.read('shared_bram', 0x2000) function for the 64 bit. I think this should be looked into at some point.