Le 04/12/2010 07:51, Dirk Behme a écrit :
On 03.12.2010 22:11, Carlo Caione wrote:
On Thu, 2010-12-02 at 20:40 -0800, Prafulla Wadaskar wrote:
-----Original Message----- From: u-boot-bounces@lists.denx.de [mailto:u-boot-bounces@lists.denx.de] On Behalf Of Carlo Caione Sent: Friday, December 03, 2010 3:11 AM To: U-Boot@lists.denx.de Subject: Re: [U-Boot] [STATUS] v2010.12-rc2 released
Some of the times, the boot hung after printing DRAM: 128 MiB, but never did it hang without printing anything.
The same here. Beagleboard xM rev.A hangs after DRAM: 256 MiB
For fix this, needs to change global variables in timer.c REF: http://lists.denx.de/pipermail/u-boot/2010-December/082834.html
Applied but nothing is changed:
Texas Instruments X-Loader 1.4.4ss (Dec 2 2010 - 21:40:58) Beagle xM Rev A Reading boot sector Loading u-boot.bin from mmc
U-Boot 2010.12-rc2-00029-g49733aa-dirty (Dec 03 2010 - 22:05:44)
OMAP3630/3730-GP ES1.0, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz OMAP3 Beagle board + LPDDR/NAND I2C: ready DRAM: 512 MiB
I'm not totally sure, so sorry if I'm wrong. But:
I understood the link given by Prafulla above only as a reference what has to be done to fix the OMAP hang. I don't think the given patch fixes the issue itself. Most probably we additionally need something like
http://lists.denx.de/pipermail/u-boot/2010-December/082965.html
for OMAP, too?
Also make sure that the r8 register is not trashed by the relocation code in the start.S used for this board. See Andreas' patch for that.
Best regards
Dirk
Amicalement,