I can comment on the clock speeds reporting incorrectly: this is
because your uboot is outdated. You'll also notice that your system
clock (in Linux/BORPH) is not ticking at the correct rate.
WRT 10GbE: You can confirm that your 10GbE cores are configured
correctly by using the
corr.katcp_wrapper.print_10gbe_core_details(mycore) function in the
corr package. I suspect a configuration problem for your cores.
Note that the tgtap call was changed earlier this year to fix a string
overflow bug. This means that you need the latest corr package and
tcpborphserver packages together to correctly configure 10GbE cores.
You can't mix 'n match versions. If you use the old stuff you should
be fine as long as the path to your 10GbE core (ie complete Simulink
block name) was less than 8 characters long. Original announcement and
details here: http://www.mail-archive.com/[email protected]/msg01386.html
Jason
On 08 Jun 2010, at 23:31, Steve Maher wrote:
Hi,
I'm trying to track down why our roach 10GbE is not transmitting.
We have this roach configuration from Nov 2009 (in order to be
compatible with another roach system - exception: our Uboot version
is a bit different). Interestingly, our reported clock numbers at
startup are slightly different (see below). Not sure that means
anything. Our serial # is something like 2020..
OURS:
CPU: AMCC PowerPC 440EPx Rev. A at 528 MHz (PLB=132, OPB=66, EBC=66
MHz)
From CASPER upgrade notice:
CPU: AMCC PowerPC 440EPx Rev. A at 533.333 MHz (PLB=133, OPB=66,
EBC=66 MHz)
After I saw no data transmitting from our custom roach program
(using python client and also Wireshark sniffing Myri NIC on XP), I
tried using the "old" 10GbE tutorial. I'm not sure if it is
_supposed to be able to run with our configuration, but it gets as
far as trying to send and receive data. Unfortunately, no data is
transmitted and the output buffer overflows (see below) - like it's
not being clocked(?)
Any suggestions on what to check next?
Thanks -
Steve
[ 883]: data: 3F4 IP: 10. 0. 0. 30 [Link up]
[ 884]: data: 3F5 IP: 10. 0. 0. 30 [Link up]
[ 885]: data: 3F6 IP: 10. 0. 0. 30 [Link up]
[ 886]: data: 3F7 IP: 10. 0. 0. 30 [Link up]
[ 887]: data: 3F8 IP: 10. 0. 0. 30 [TX almost full]
[Link up]
[ 888]: data: 3F9 IP: 10. 0. 0. 30 [TX almost full]
[Link up]
[ 889]: data: 3FA IP: 10. 0. 0. 30 [TX almost full]
[Link up]
[ 890]: data: 3FB IP: 10. 0. 0. 30 [TX almost full]
[Link up]
[ 891]: data: 3FC IP: 10. 0. 0. 30 [TX almost full]
[Link up]
[ 892]: data: 3FD IP: 10. 0. 0. 30 [TX almost full]
[Link up]
[ 893]: data: 3FE IP: 10. 0. 0. 30 [TX almost full]
[Link up]
[ 894]: data: 3FF IP: 10. 0. 0. 30 [TX almost full]
[Link up]
[ 895]: data: 400 IP: 10. 0. 0. 30 [TX almost full]
[Link up] [eof]
[ 896]: data: 401 IP: 10. 0. 0. 30 [TX almost full]
[Link up]
[ 897]: data: 402 IP: 10. 0. 0. 30 [TX almost full]
[Link up]
[ 898]: data: 403 IP: 10. 0. 0. 30 [TX almost full]
[Link up]
[ 899]: data: 404 IP: 10. 0. 0. 30 [TX almost full]
[Link up]
[ 900]: data: 405 IP: 10. 0. 0. 30 [TX overflow] [TX
almost full] [Link up]
[ 901]: data: 406 IP: 10. 0. 0. 30 [TX overflow] [TX
almost full] [Link up]
[ 902]: data: 407 IP: 10. 0. 0. 30 [TX overflow] [TX
almost full] [Link up]
