[casper] spontaneous tcpborphserver3 crash

Hi, We have been running eight ROACH IIs for the past few weeks using tcpborphserver3 and have experienced occasional "crashes" where the ROACH stops responding to KATCP and upon investigation we find that the tcpborphserver3 program is no longer running. uname -a gives Linux vegasr2-3 3.7.0-rc2+

Re: [casper] Problem with dram block using mlib_devel

Turns out there was a problem with the XPS library as some DRAM-related files and variables were accidentally removed from the SKA-SA repo. Should be fixed now, though without the modelsim co-simulation option. Jason On 16 Jan 2013, at 20:39, Kenneth R. Treptow wrote: > Hi Jason, > > I remove

Re: [casper] spontaneous tcpborphserver3 crash

Hi, Glenn, I don't know if this is practical, but you could build tcpborphserver3 with debugging enabled (-g compiler option) and then run tcpborphserver under gdb in a screen session of the roach. When/if it crashes you can go to the gdb session to see exactly where/why it crashed. Dave On

Re: [casper] Problem with dram block using mlib_devel

Thanks Jason it is working for me now. Ken -Original Message- From: Jason Manley [mailto:jman...@ska.ac.za] Sent: Thursday, January 17, 2013 10:45 AM To: Kenneth R. Treptow Cc: casper@lists.berkeley.edu Subject: Re: [casper] Problem with dram block using mlib_devel Turns out there was a

[casper] Problem setting parameters in fft blocks using mlib_devel

I get the following simulink error if I place a new fft block from the library and try to set parameters. Error:Error invoking object method Error due to multiple causes. --> Error in 'new_adc_test/fft': Initialization commands cannot be evaluated. --> Invalid object name: fft_biplex0/4 This hap

Re: [casper] Problem setting parameters in fft blocks using mlib_devel

Hi Kenneth > I get the following simulink error if I place a new fft block from the > library and try to set parameters. > > Error:Error invoking object method > Error due to multiple causes. --> Error in 'new_adc_test/fft': Initialization > commands cannot be evaluated. --> Invalid object name: