From: Marcel Ziswiler <marcel@ziswiler.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [REGRESSION] Ethernet broken on Colibri T20/T30
Date: Sun, 17 Jan 2016 01:51:50 +0100 [thread overview]
Message-ID: <1452991910.3246.25.camel@ziswiler.com> (raw)
Hi Simon
As mentioned before I noticed Ethernet (on-module USB ASIX chip) to be
broken on master while it still worked fine in v2016.01. I kind of
remember having once noticed something along those lines when testing
some of your early dm stuff but could not find our discussion about it
anymore plus I don't think it did actually lead anywhere.
FWIW it currently crashes as follows (showing Colibri T20 but the same
happens on Colibri T30):
U-Boot SPL 2016.01-00205-gb8c5b47 (Jan 17 2016 - 01:31:48)
Trying to boot from RAM
U-Boot 2016.01-00205-gb8c5b47 (Jan 17 2016 - 01:31:48 +0100)
TEGRA20
Model: Toradex Colibri T20
Board: Toradex Colibri T20
DRAM:??512 MiB
NAND:??1024 MiB
MMC:???Tegra SD/MMC: 0
*** Warning - bad CRC, using default environment
In:????serial
Out:???lcd
Err:???lcd
USB recovery mode
Net:???No ethernet found.
Hit any key to stop autoboot:??2 \b\b\b 0?
Colibri T20 # usb start
starting USB...
USB0:???USB EHCI 1.00
USB1:???USB EHCI 1.00
USB2:???USB EHCI 1.00
scanning bus 1 for devices... 1 USB Device(s) found
scanning bus 2 for devices...?
Warning: asix_eth using MAC address from ROM
2 USB Device(s) found
scanning bus 0 for devices... 2 USB Device(s) found
Colibri T20 # dhcp
BOOTP broadcast 1
EHCI timed out on TD - token=0x88008d80
Rx: failed to receive: -5
BOOTP broadcast 2
EHCI timed out on TD - token=0x8008d80
Rx: failed to receive: -5
BOOTP broadcast 3
EHCI timed out on TD - token=0x88008d80
Rx: failed to receive: -5
BOOTP broadcast 4
EHCI timed out on TD - token=0x8008d80
Rx: failed to receive: -5
BOOTP broadcast 5
EHCI timed out on TD - token=0x88008d80
Rx: failed to receive: -5
BOOTP broadcast 6
EHCI timed out on TD - token=0x8008d80
Rx: failed to receive: -5
Retry time exceeded; starting again
data abort
pc : [<1fb4d194>] ???lr : [<1fbb9784>]
reloc pc : [<0012d194>] ???lr : [<00199784>]
sp : 1d61c5e0??ip : 6aa665ea ?fp : 1d62bca0
r10: 00000000??r9 : 1d61fee0 ?r8 : 1d62bca0
r7 : 00000000??r6 : 1d6312e0 ?r5 : 1f6da8e0??r4 : 00000000
r3 : 1c585760??r2 : 03155180 ?r1 : 00000000??r0 : caa661ca
Flags: NzCv??IRQs off??FIQs off??Mode SVC_32
Resetting CPU ...
resetting ...
Do you have any clue what could be going on?
Cheers
Marcel
next reply other threads:[~2016-01-17 0:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-17 0:51 Marcel Ziswiler [this message]
2016-01-18 17:42 ` [U-Boot] [REGRESSION] Ethernet broken on Colibri T20/T30 Stephen Warren
2016-01-19 2:13 ` Simon Glass
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=1452991910.3246.25.camel@ziswiler.com \
--to=marcel@ziswiler.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