From: Sylvain Munaut <tnt@246tNt.com>
To: linux-mips@linux-mips.org
Subject: AMD Au1100 problems (USB & Ethernet)
Date: Fri, 05 Aug 2005 21:39:10 +0200 [thread overview]
Message-ID: <42F3C05E.7060002@246tNt.com> (raw)
Hello,
I've been trying to adapt linux ( the HEAD CVS version ) to a
custom board based around a Au1100. To be more precise, the board
use a "cpu module" (CSB650 from Cogent
http://www.cogcomp.com/csb_csb650.htm ) that's placed on a custom PCB.
I've compiled and booted a kernel sucessfully, I see the message on the
serial console. It's in Big Endian mode since the boot loaded on the
card is big endian only and I could manage to get it to switch to little
endian ...
Now, let's go on with the problems :
* About USB. First time I tried, it just hung but I quicly found out
that it was because I didn't route the 48Mhz clock to USB module. After
that, I had to slightly adapt the ohci bus glue to enable the OHCI big
endian mode. After that, when a USB stick is inserted, it gets detected,
I can mount it and read small files. But when I try to read bigger files
( just 1 or 2 MB ), I get stuff like :
[4294743.146000] usb 1-1: reset full speed USB device using au1xxx-ohci
and address 2
[4294743.618000] usb 1-1: reset full speed USB device using au1xxx-ohci
and address 2
[4294743.891000] usb 1-1: reset full speed USB device using au1xxx-ohci
and address 2
[4294744.151000] usb 1-1: reset full speed USB device using au1xxx-ohci
and address 2
[4294744.328000] au1xxx-ohci au1xxx-ohci.0: bad entry 4b
[4294744.346000] au1xxx-ohci au1xxx-ohci.0: bad entry ac450000
[4294744.363000] au1xxx-ohci au1xxx-ohci.0: bad entry 8f820014
[4294744.381000] au1xxx-ohci au1xxx-ohci.0: bad entry 38210001
[4294744.495000] hub 1-0:1.0: port 1 disabled by hub (EMI?),
re-enabling...
[4294744.515000] usb 1-1: USB disconnect, address 2
[4294745.532000] au1xxx-ohci au1xxx-ohci.0: IRQ INTR_SF lossage
[4294745.532000] usb 1-1: sg_complete, unlink --> -19
[4294745.532000] usb 1-1: sg_complete, unlink --> -19
Which means absolutly nothing to me ;( Has anyone got a clue ?
I can't say for sure it's not hardware but the cpu module is used by
others and on the base board, it's just a couple of differential pair
with 90ohm differential impedance, nothing more ...
* About ethernet : It works, I have a network access. However I have
two kind of errors. On the RX side, I get quite a lot of "rx miss"
errors (when au1x00_eth debug is on). About 5% of packets are dropped.
That's not _too_ much of a problem as log as it doesn't increase. But
what can that be due too ?
A more annoying problem is that I get a lot of :
[ 506.397000] NETDEV WATCHDOG: eth0: transmit timed out
[ 506.412000] eth0: au1000_tx_timeout: dev=8048b400
theses are quite comment when I transmitt a lot
and they completly ruin the transmission
(_real_ slow !).
Heres is some stats from ifconfig :
RX packets:50496 errors:76 dropped:76 overruns:0 frame:0
TX packets:49573 errors:47 dropped:0 overruns:0 carrier:74
Any insight / suggestion is appreciated, I'm getting desperate ;)
Sylvain
next reply other threads:[~2005-08-05 19:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-05 19:39 Sylvain Munaut [this message]
2005-08-05 19:47 ` AMD Au1100 problems (USB & Ethernet) Pete Popov
[not found] ` <6.2.0.14.2.20050805155414.044a0f00@mail.cogcomp.com>
2005-08-05 20:10 ` Pete Popov
2005-08-05 21:05 ` Sylvain Munaut
2005-08-05 21:14 ` Pete Popov
2005-08-06 10:42 ` Sylvain Munaut
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=42F3C05E.7060002@246tNt.com \
--to=tnt@246tnt.com \
--cc=linux-mips@linux-mips.org \
/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