[U-Boot] Ethernet on PandaBoard

Gary Thomas
2012-07-11T15:41:06Z

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.