From: Andrew Schultz <alschult@eecs.berkeley.edu>
To: linux-mtd@lists.infradead.org
Subject: Problem booting DOCboot and Linux 2.6
Date: Wed, 06 Jul 2005 12:11:06 -0700 [thread overview]
Message-ID: <42CC2CCA.2050409@eecs.berkeley.edu> (raw)
Hello,
I am currently having a problem getting DOCboot to work with a 256MB
DoC2000 TSOP and a Linux 2.6.11 kernel image. After following all the
steps in the readme, I reboot the system and get the following:
Loading kernel... CANNOT FIND IMAGE ON DEVICE
Looking at the doc_bootstub.S code, it looks like this results from not
finding the "0xdbb1" signature in any of the pages denoting that the
page holds part of the kernel image. I'm not exactly sure why this is
happening, as my doc_spl image that I wrote to the chip is the correct
size (about 1.2MB, or approximately the size of the bzImage + size of
doc_bootstub object file). Other people have recently posted success
using a very similar chip, the only difference being they used a 2.4
kernel. If anyone knows why this might be happening, or if anyone has
had success using a 2.6 kernel (although I don't think that should
matter), any help would be appreciated.
Andrew
Just for completeness, here are the steps I performed to get to this point:
1) Setup the chip with dformat:
dformat /winl:0000 /winh:d8000 /bdkl0:2M (the /winl, /winh stuff is
needed to work for some reason)
2) Reboot into linux off hard drive and put doc_spl image on chip:
./flash_eraseall /dev/mtd1
./nandwrite -o /dev/mtd1 doc_spl
3) Fdisk/format the /dev/inftla device to create the filesystem
4) Reboot and get the "CANNOT FIND IMAGE ON DEVICE" message
next reply other threads:[~2005-07-06 19:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 19:11 Andrew Schultz [this message]
2005-07-06 19:36 ` Problem booting DOCboot and Linux 2.6 Dan Brown
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=42CC2CCA.2050409@eecs.berkeley.edu \
--to=alschult@eecs.berkeley.edu \
--cc=linux-mtd@lists.infradead.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