From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stefan Roese <sr@denx.de>
Date: Fri, 30 Jun 2006 11:59:14 +0200
Subject: [U-Boot-Users] 1.1.4 and 2.6 kernel
In-Reply-To: <29f916510606292304y8f05a73kdf102b525ac5f010@mail.gmail.com>
References: <29f916510606270143g5d143086oaa336b93f2225495@mail.gmail.com>
	<29f916510606292116h7efe0bccg2fa46272e15daf12@mail.gmail.com>
	<29f916510606292304y8f05a73kdf102b525ac5f010@mail.gmail.com>
Message-ID: <200606301159.15136.sr@denx.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 Alfred,

On Friday 30 June 2006 08:04, alfred hitch wrote:
> I am sending dumps of my logs and what I did..
> Anyone can give any pointers, I will really appreciate it.
>
> Boot up log:
> -----------------------
>
> U-Boot 1.1.1.2 (Nov 17 2004 - 12:54:00)

Pretty old. A major update of the IXP4xx port was done a few weeks ago. Please 
try to port your board support to the current version.

> sB_CONFIG: 32MB_2CHIP
> ----------------------------
> U-Boot code: 00F80000 -> 00F90E64  BSS: -> 00F92374
> RAM Configuration:
> Bank #0: 00000000 16 MB
> Flash: 32 MB
> *** Warning - bad CRC, using default environment
>
> In:    serial
> Out:   serial
> Err:   serial
> Hit any key to stop autoboot:  0
> => setenv bootargs 'console=ttySAC01,115200 root=/dev/mtdblock4 rw,

Try "ttyS0" or "ttyS1" as console parameter.

<snip>

> I created uImage using this command:
>
> ->> u-boot-mkimage -A arm -O linux -T kernel -C none -a 0x01600000 -e
> 0x01600000 -n "Linux" -d ./zImage uImage

Why didn't you just type "make uImage"? This result in a proper uImage to boot 
from U-Boot.

BTW: We are using current U-Boot and current Linux 2.6 kernel on different 
IXP4xx boards without any problems (e.g. ixdpg425, pdnb3).

Best regards,
Stefan