public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Ethernet on PandaBoard
Date: Wed, 11 Jul 2012 09:41:06 -0600	[thread overview]
Message-ID: <4FFD9E92.7060507@mlbassoc.com> (raw)
In-Reply-To: <8F9A1319-A460-44EF-9914-20CAFCF9FF43@kmckk.co.jp>

On 2012-07-11 09:32, Tetsuyuki Kobayashi wrote:
> Hi Gray,
>
> On 2012/07/12, at 0:13, Gary Thomas wrote:
>
>> On 2012-07-11 07:08, Gary Thomas wrote:
>>> I just tried rev 211e47549b668c7cdd8658c0413a272f0d0495d4 (v2012.07-rc1)
>>> for my PandaBoard.  Sadly, this is failing when I try to use the onboard
>>> ethernet (EHCI USB based) controller:
>>>
>>> U-Boot SPL 2012.07-rc1 (Jul 11 2012 - 06:56:00)
>>> OMAP4430 ES2.2
>>> OMAP SD/MMC: 0
>>> reading u-boot.img
>>> reading u-boot.img
>>>
>>>
>>> U-Boot 2012.07-rc1 (Jul 11 2012 - 06:56:00)
>>>
>>> CPU  : OMAP4430 ES2.2
>>> Board: OMAP4 Panda
>>> I2C:   ready
>>> DRAM:  1 GiB
>>> MMC:   OMAP SD/MMC: 0
>>> Using default environment
>>>
>>> In:    serial
>>> Out:   serial
>>> Err:   serial
>>> Net:   No ethernet found.
>>> Hit any key to stop autoboot:  0
>>> Panda # usb start
>>> (Re)start USB...
>>> USB:   Register 1313 NbrPorts 3
>>> data abort
>>> pc : [<bff9acb0>]          lr : [<bff9ac91>]
>>> sp : bff08e28  ip : 0000000f     fp : 00000000
>>> r10: bff0a370  r9 : 00000002     r8 : bff08f68
>>> r7 : bffbb070  r6 : 00000000     r5 : bffaee04  r4 : 00001313
>>> r3 : bffaee04  r2 : 98000000     r1 : 0000000a  r0 : 00000019
>>> Flags: Nzcv  IRQs off  FIQs off  Mode SVC_32
>>> Resetting CPU ...
>>>
>>> Anyone else see this?  Ideas?
>>>
>>> How do I map these addresses (PC=0xbff9acb0) to the ones in my
>>> u-boot ELF image (so I can figure out what went wrong)?
>>>
>>> Thanks
>>>
>>
>> This turns out to be related to access to the wHubCharacteristics
>> field in a hub descriptor.  This field is u16, but not u16 aligned,
>> hence the data abort.
>>
>> Has something changed recently?  I have a version of U-Boot built
>> for this board based on 2011.06 from the meta-ti tree which does
>> not suffer from these problems.
>>
>
>
> How about this patch?
>
> [PATCH] arm: armv7: add compile option	-mno-unaligned-access if available
> http://lists.denx.de/pipermail/u-boot/2012-July/127260.html
>

Cool!  that fixed it - my network is working now.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

  reply	other threads:[~2012-07-11 15:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-11 13:08 [U-Boot] Ethernet on PandaBoard Gary Thomas
2012-07-11 14:34 ` Tetsuyuki Kobayashi
2012-07-11 15:13 ` Gary Thomas
2012-07-11 15:32   ` Tetsuyuki Kobayashi
2012-07-11 15:41     ` Gary Thomas [this message]
2012-07-12  9:20 ` Tom Rini
2012-07-12  9:30   ` Tom Rini
2012-07-12 13:06     ` Gary Thomas
2012-07-12 13:15       ` Tom Rini
2012-07-12 13:17         ` Gary Thomas
2012-07-12 13:20           ` Tom Rini
2012-07-12 13:27             ` Gary Thomas
2012-07-12 14:26               ` Gary Thomas
2012-07-12 16:16                 ` Tom Rini
2012-07-12 16:44                   ` Gary Thomas

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=4FFD9E92.7060507@mlbassoc.com \
    --to=gary@mlbassoc.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