I recompiled the design with hilariously short block names, and a total
block name of "x_r_gbe3" works just fine. I thought the addition of the tap
name parameter to tap_start was supposed to stop all of that silliness?

On Thu, Mar 31, 2011 at 1:52 AM, Jon Losh <[email protected]> wrote:

> More 10gbe woes, but hopefully more easily solved. I have two models, an
> F-engine and and X-engine, that want to talk via 10gbe. I have been able to
> successfully send data from roach to roach over 10gbe, so I know that I can
> configure cores to send and receive on separate roaches. However, when I try
> to configure the receiving cores, tap_start fails.
>
> I read in the mail archive about tap_start not liking very long gbe core
> names, but I thought that was fixed. Here's the output my Python script
> gives:
>
>
>
> -----------------------------------------------------------------------------------
> Configuring F-engine 10gbe core 0
> done
> Configuring F-engine 10gbe core 1
> done
> Configuring F-engine 10gbe core 2
> done
> Configuring F-engine 10gbe core 3
> done
> Configuring X-engine 10gbe core 0
> ERROR: An unexpected error occurred while tokenizing input
> The following traceback may be corrupted or invalid
> The error message is: ('EOF in multi-line statement', (167, 0))
>
> ---------------------------------------------------------------------------
> RuntimeError                              Traceback (most recent call last)
>
> /home/jlosh/fftt/models/post_wfk_standalones/wfk_correlator.py in
> <module>()
>     638 print 'done'
>     639 print 'Configuring X-engine 10gbe core 0' ### change gbe0 to
> whatever the design names it
> --> 640 xeng0_fpga.tap_start('xtap0', 'X-Engine_tengbe_receiver_gbe3',
> mac_base + xeng0_10gbe_ip, xeng0_10gbe_ip, fabric_port)
>     641 print 'done'
>     642 print 'Configuring X-engine 10gbe core 1'
>
> /usr/lib/python2.6/site-packages/corr-0.6.5-py2.6.egg/corr/katcp_wrapper.pyc
> in tap_start(self, tap_dev, device, mac, ip, port)
>     176
>     177         self._logger.info("Starting tgtap driver instance for %s:
> %s %s %s %s %s"%("tap-start", tap_dev, device, ip_str, port_str, mac_str))
> --> 178         reply, informs = self._request("tap-start", tap_dev,
> device, ip_str, port_str, mac_str)
>     179         if reply.arguments[0]=='ok': return
>     180         else: raise RuntimeError("Failure starting tap device %s
> with mac %s, %s:%s"%(device,mac_str,ip_str,port_str))
>
> /usr/lib/python2.6/site-packages/corr-0.6.5-py2.6.egg/corr/katcp_wrapper.pyc
> in _request(self, name, *args)
>      66
>      67             raise RuntimeError("Request %s failed.\n  Request:
> %s\n  Reply: %s."
> ---> 68                     % (request.name, request, reply))
>      69         return reply, informs
>      70
>
> RuntimeError: Request tap-start failed.
>   Request: ?tap-start xtap0 X-Engine_tengbe_receiver_gbe3 10.0.0.30 60000
> 02:02:0A:00:00:1E
>   Reply: !tap-start fail.
> WARNING: Failure executing file: <wfk_correlator.py>
>
> -----------------------------------------------------------------------------------
>
> If there's any other settings that are useful to know, please tell me.
>

Reply via email to