Yes, you've got the right definition. And Laura's correct in that some ROACHes shipped with old versions. I've appended the original email to the mailing list below for your reference.
All the software is available on SKA-SA's github account, so you can get it even when CASPER's server is down. Check https://github.com/ska-sa/roach1_support_software/tree/master/tgtap Jason From: Jason Manley <jasonman...@gmail.com> Date: 03 April 2010 03:34:54 SAST To: "casper@lists.berkeley.edu CASPER" <casper@lists.berkeley.edu> Subject: Important ROACH software update There is a new KATCP server for ROACH available at http://casper.berkeley.edu/svn/trunk/roach/sw/binaries/tcpborphserver/tcpborphserver2-2010-04-02-tgtap to support the use of 10GbE cores with longer names. This bug would have reared its ugly head if you tried to start multiple instances of tgtap on designs with long 10GbE core names. In this case, the names would have been truncated, leading to possible overwriting of the first instance by the second instance and thus an apparent inability to start more than one tgtap instance. The new KATCP tap-start command is as follows: ?tap-start <tap-device> <register-name> <ip-address> [port [mac]] This new <tap-device> string is the name of the tap device interface you wish to create (which shows up on the roach board when you do ifconfig). It must be 8 characters or shorter, and is typically tap0, tap1, tap2 etc. or gbe0, gbe1, gbe2, gbe3 etc. As a result, corr-0.4.2's katcp_wrapper's tap_start function has also changed and is not backwards compatible as it now requires that additional parameter. ==== NOTE ==== tcpborphserver2-2010-04-02-tgtap and corr-0.4.2 are co-dependant (you need to update both at the same time) ============== Note to new ROACH users (production batch 3): your SD-card filesystem is shipping with http://casper.berkeley.edu/svn/trunk/roach/sw/binaries/tcpborphserver/tcpborphserver2-2010-03-23-pid and will need to be manually updated. Jason On 30 May 2012, at 03:35, Laura Vertatschitsch wrote: > Hey Joseph, > > You may have done this, but there was a need at some point to move to a more > recent version of the tgtap driver and the tcpborphserver. I cant find the > link since the casper website is down, but that may fix your issue if it > hasn't been tried yet. > > --Laura > > On Tue, May 29, 2012 at 6:24 PM, Trinh, Joseph T (335J) > <joseph.t.tr...@jpl.nasa.gov> wrote: > Hi CASPER, > > > > We are having trouble running tap-start. We are running corr-0.6.9. > > > > It has been awhile since I have run tap-start and the arguments have changed > (tap_dev was added). Based on the source code, the arguments appear to be: > > def tap_start(self, tap_dev, device, mac, ip, port) > > > > Can you confirm that this is the correct usage of tap-start? Can tap_dev be > any arbitrary string? > > > > tqtrinh@ska:~/dev/dsn_spec$ ./tengb_test.py > > Connecting to server roach on port... ok > > > > ------------------------ > > Programming FPGA with tengbe.bof... ok > > > > ------------------------ > > Setting the port 0 linkup : True > > ------------------------ > > Configuring receiver core... > > Traceback (most recent call last): > > File "./tengb_test.py", line 41, in <module> > > fpga.tap_start('tap0',gbe0,mac_base+src_ip,src_ip,port) > > File "/usr/local/lib/python2.6/dist-packages/corr/katcp_wrapper.py", line > 182, in tap_start > > reply, informs = self._request("tap-start", tap_dev, device, ip_str, > port_str, mac_str) > > File "/usr/local/lib/python2.6/dist-packages/corr/katcp_wrapper.py", line > 67, in _request > > % (request.name, request, reply)) > > RuntimeError: Request tap-start failed. > > Request: ?tap-start tap0 tengb0 10.0.0.10 46224 02:02:0A:00:00:0A > > Reply: !tap-start fail. > > > > > >
