Hi Jason and all:
I have compiled the X engine of rev. 322g,210MHz finally. Thanks.
The F engine of rev 306 for iBOB you mentioned is for Quad ADC which we
don't have. Do you have F engine model with the popular ADC boards ?
regards
homin jiang
Jason Manley wrote:
I have just checked-in the latest versions. F engine is at revision 306
(stable) for ibobs and X engine is up to rev 322g (debug compile) for
roach.
There are two major outstanding issues before the system is deployable:
1) Loss of packets from F engines. There is a loss of data (about 1 in
4 million packets) in the 10GbE network. I am trying to debug this at
the moment, and the problem appears to be in the 10GbE RX core, but this
is as yet unconfirmed. There should be zero data loss in a correctly
functioning system.
2) Output not thoroughly checked. I do not yet have working receive
code to capture and plot the correlator output packets and so have not
confirmed correct end-to-end instrument operation.
Minor issues which I hope to correct by Feb 2010:
* SPEAD metadata not yet issued. The python code that controls the
system will eventually output SPEAD compliant metadata describing the
data stream, including instructions on how the receiver should interpret
the data. See http://github.com/sratcliffe/PySPEAD for further info.
* Some cleanup is required. I want to mux the output data over the
existing 10GbE link rather than use a separate 10GbE core. Various
blocks can use some optimisation too.
If you want to start playing with the design, please ensure that you're
running the latest tcpborphserver2 on your ROACHes
(http://casper.berkeley.edu/svn/trunk/roach/sw/binaries/tcpborphserver/)
because there were fixes to the tgtap call.
Jason
--
Regards,
Homin Jiang(¦¿§»©ú)
