On 2013-03-19 15:49, Tom Rini wrote:
On Sat, Mar 16, 2013 at 02:13:54PM +0100, Manfred Huber wrote:
I'm surprised that no one is interested in a functioning Beagleboard. Has no one tested the Beagleboard since 2012-09-19?
I don't see this problem on mine (classic and xM), which is probably part of the why. I'm inclined to accept the patch, but can you try two things please:
- How reproducible is this problem, with the host and beagleboard combination you have? 100%?
- Do you have another beagleboard or another host PC (or USB-Serial dongle) you can try?
Thanks!
Thanks for your answer. I have only one Beagleboard Revision C4 (CONTROL_IDCODE of the OMAP3530 is 0x4B7AE02F). My host is a Ubuntu 12.10 (Quantal Quetzal) and I use the gcc-arm-linux-gnueabihf cross-compiler version 4.7.2-1.
Compiling the actual u-boot leaded to the reported error. All version since commit cb55b3320014b7f6014416c556fe506efbf0a84b led to the hanging. All version before boots correctly.
Adding the define to omap3_beagle.h leads to a correct booting for all versions. Also a reset of the uart at the beginning of the init function leads to a correct booting. So I exclude that the hardware is defective.
If you can tell me your compiler and version I can try to use your cross-compiler.
Best regards, Manfred