public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Danny Gale <Daniel.Gale@coloradoengineeringinc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] T4240 SGMII "Tx buffer not ready"
Date: Fri, 08 Aug 2014 15:43:44 -0600	[thread overview]
Message-ID: <53E54490.1000507@coloradoengineeringinc.com> (raw)

Hi everybody,

We're trying to bring up a 100M/1G ethernet interface on a custom T4240 
board over SGMII and running into the following errors:

Immediately after board reset:
=> ping 192.168.1.53
Using FM2 at DTSEC6 device
FM2 at DTSEC6: Tx error
FM2 at DTSEC6: Rx error
ping failed; host 192.168.1.53 is not alive

On any subsequent attempts:
=> ping 192.168.1.53
Using FM2 at DTSEC6 device
FM2 at DTSEC6: Tx buffer not ready. txbd->status = 0x8800
FM2 at DTSEC6: Tx buffer not ready. txbd->status = 0x8800
ping failed; host 192.168.1.53 is not alive

We're running from u-boot 2014.07-rc3. Our custom board ethernet 
bring-up code is closely based on the code for the t4rdb. The SGMII 
interface hardware is coming up out of reset (we're seeing the interface 
toggling at the expected rate) but it looks like u-boot isn't 
communicating with it properly. There's very little information to go on 
in the source code related to this error (drivers/net/fm/eth.c, in 
fm_eth_send). What can cause this problem?

Here are my environment variables related to networking:
eth1addr=00:50:C2:72:01:04
eth2addr=00:50:C2:72:01:06
eth3addr=00:50:C2:72:01:08
eth4addr=00:50:C2:72:01:0a
eth5addr=00:50:C2:72:01:0c
eth6addr=00:50:C2:72:01:0e
ethact=FM2 at DTSEC6
ethaddr=00:50:C2:72:01:02
ethprime=FM2 at DTSEC6
ipaddr=192.168.1.230
netmask=255.255.255.0
gatewayip=192.168.1.11

Thanks for any help you can provide. Let me know if you need more 
information,
Danny Gale
daniel.gale at coloradoengineeringinc.com

                 reply	other threads:[~2014-08-08 21:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53E54490.1000507@coloradoengineeringinc.com \
    --to=daniel.gale@coloradoengineeringinc.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox