From: Felipe Balbi <me@felipebalbi.com>
To: Jerry Johns <Jerry.Johns@nuvation.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: OMAP35xx Boot failure
Date: Sat, 10 Apr 2010 20:59:50 +0300 [thread overview]
Message-ID: <20100410175949.GA2183@gandalf> (raw)
In-Reply-To: <274F7B50569A1B4C9D7BCAB17A9C7BE102216BC8@mailguy3.skynet.nuvation.com>
Hi,
first of all, please read http://elinux.org/Netiquette
On Fri, Apr 09, 2010 at 08:33:20AM -0700, Jerry Johns wrote:
> Hello all, I've got a custom OMAP3503 board with 256Mbytes of
> LPDDR memory (single die, x32-bit) that i've got working with x-loader
> and u- boot. However, when i load the Linux kernel (2.6.32 git), it
> randomly produces the following errors:
>
> 1) Hangs midway through the "Uncompressing Linux ...." stage, and
> this is arbitrary and random on different attempts 2) If it ever does
> go through, it sometimes displays "invalid compressed format (err =
> 2)" or "crc error", "incomplete literal tree" and says "System
> halted" 3) If i disable caching in the kernel (in
> arch/arm/boot/compressed.S, line 233 "bl cache_on"), it at least
> completes the Uncompressing stage fine and proceeds to print ".......
> done, booting the kernel.", at which point it does not boot (most
> likely since i disabled the caching) 4) If i reset the board (not
> power-cycle) after the board hang above, and do a crc32 check on the
> kernel image in DDR memory (this is possible since DDR2 memory
> contents do not get changed after a soft- reset), it matches the CRC32
> that i have calculated manually on the kernel image. This shows that
> the main kernel image (from which it is uncompressed) is still
> intact.
could it be memory timings ??
One thing you might wanna do is enable CONFIG_DEBUG_LL and
CONFIG_EARLY_PRINTK and append "debug earlyprintk" to your CMDLINE this
might give your more information about the problem.
--
balbi
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-04-10 17:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 15:33 OMAP35xx Boot failure Jerry Johns
2010-04-10 17:59 ` Felipe Balbi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100410175949.GA2183@gandalf \
--to=me@felipebalbi.com \
--cc=Jerry.Johns@nuvation.com \
--cc=linux-omap@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox