From mboxrd@z Thu Jan  1 00:00:00 1970
From: Eckart Goehler <E.Goehler@ifen.com>
Date: Thu, 03 Nov 2005 11:34:18 +0100
Subject: [U-Boot-Users] When starting linux, nothing happens
In-Reply-To: <b89c9ad40511030209i591e02eakaa1388da401ea53c@mail.gmail.com>
References: <b89c9ad40511030209i591e02eakaa1388da401ea53c@mail.gmail.com>
Message-ID: <4369E7AA.20702@ifen.com>
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,

jescythe wrote:
> i don't know if the problem is with my configuration of u-boot or the
> linux image.
> 
> # bootm bfc80000
> ## Booting image at bfc80000 ...
>    Image Name:   linux kernel image
>    Created:      2005-11-03   9:22:24 UTC
>    Image Type:   MIPS Linux Kernel Image (gzip compressed)
>    Data Size:    1234499 Bytes =  1.2 MB
>    Load Address: 80080000
>    Entry Point:  80080000
>    Verifying Checksum ... OK
>    Uncompressing Kernel Image ... OK
> 
> Starting kernel ... <hangs indefinitely>

Well, I'm not familliar with the MIPS system but the load address and
entry point look suspicious. According U-Boot README and my own
experience they should be either 0 (newer linux kernels) or 0xc (older
one). Did you use mkimage on your own?


> Any help will be deeply appreciated.

Any further notes/debugging statements also are appreciated. Please try
to enable boot progress report (CONFIG_SHOW_BOOT_PROGRESS) to make sure
that not u-boot is the culprit.

Also good point to look for (rtfm): use linux image map file
(System.map) for log_buf and try to read from given address -> some 
information what might have gone wrong *before* the kernel was able to 
establish a terminal connection. This requires some debugging facility.

Please tell us something about the environment (embedded, console etc).

> CPU = NEC VR5701 (MIPS)
> memory is 128MB mapped at 0x0000 0000

ok.


sincerely

eckart