Hi ,
-finally, we managed to run 'tgtap' manually we added 'x' with chmod 'a+x',
and we launched again the tut2 python script and it works now.
- But sometimes when lauching tut2 with the boffile specified in the python
script, we have an error after the bistream loading step(message: "no cable
connected on 'port0'. "), we use your trick as you said few weeks ago. where
we need to clear and to load manually the '.bof' through ipython, before
launching tut2.py(as we put in comment the bof file ) in order to have a
sucessfull design working without saying that there is no cable connected on
'port0'. it occurs sometimes and that is the workaround that we found. we
will have to look in depth(or investigate) another day...
thanks,
(the case can be closed)
==================== the screen report =====================
Connecting to server roach... ok
------------------------
ok
---------------------------
Port 0 linkup: True
Port 3 linkup: True
---------------------------
Configuring receiver core... done
Configuring transmitter core... done
---------------------------
Setting-up packet source... done
Setting-up destination addresses... done
Resetting cores and counters... done
===============================
10GbE Transmitter core details:
===============================
Note that for some IP address values, only the lower 8 bits are valid!
------------------------
GBE0 Configuration...
My MAC: 02 02 0A 00 00 14
Gateway: 0 0 0 20
This IP: 10 0 0 20
Gateware Port: 60000
Fabric interface is currently: Enabled
XAUI Status: 0000007E
lane sync 0: 1
lane sync 1: 1
lane sync 2: 1
lane sync 3: 1
Channel bond: 1
XAUI PHY config:
RX_eq_mix: 4
RX_eq_pol: 0
TX_pre-emph: 0
TX_diff_ctrl: 0
ARP Table:
>
>
> On Tue, Sep 28, 2010 at 3:19 PM, Jason Manley <jasonman...@gmail.com>wrote:
>
>> ok, so your problem is that tgtap isn't starting. dmesg might provide some
>> clue. Also check ifconfig that there's no existing nic device with that same
>> name. You can also try'n run tgtap manually from the command line during
>> debugging and see what errors it gives.
>>
>> If all else fails, try rebooting your ROACH board so that you start from a
>> known state. This really shouldn't be necessary though.
>>
>> Jason
>>
>>
>
