From mboxrd@z Thu Jan  1 00:00:00 1970
From: Glenson Muthedan <glenson@gmx.de>
Date: Wed, 17 Sep 2003 16:17:14 +0200
Subject: [U-Boot-Users] data abort
References: <20030915112918.28A8CC59E4@atlas.denx.de> <fc.004c4e48001ca3053b9aca0046c440fa.1ca324@rea.de> <3F6759D6.3070406@gmx.de> <fc.004c4e48001cb53e3b9aca0046c440fa.1cb55e@rea.de>
Message-ID: <3F686CEA.7020809@gmx.de>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hi Anders,

Ohh, yes! You're right. I had put some printf-lines in board.c between 
devices_init() and console_init_r(). As you explained, removing those 
lines solved that problem. Now U-Boot seems to run quite normal.

Thanks.
Glenson.


Anders Larsen wrote:
> Hi Glenson,
> 
> does it happen immediately at that line, or did you add any debug
> output?
> 
> As soon as GD_FLG_DEVINIT is set, the output functions (puts, printf,
> ...) will search for the output device in a lookup table, which
> unfortunately has not yet been initialized at that point (the lookup
> table is initialized in console_init_r() which is called *after*
> devices_init() has completed).
> 
> Perhaps the line "gd->flags |= GD_FLG_DEVINIT;" should better be
> moved to console_init_r() ?
> 
> Cheers
>  Anders
> 
>