From: Dan Brown <dan_brown@ieee.org>
To: Andrew Schultz <alschult@eecs.berkeley.edu>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Problem booting DOCboot and Linux 2.6
Date: Wed, 06 Jul 2005 15:36:16 -0400 [thread overview]
Message-ID: <42CC32B0.4020101@ieee.org> (raw)
In-Reply-To: <42CC2CCA.2050409@eecs.berkeley.edu>
Andrew Schultz wrote:
> I am currently having a problem getting DOCboot to work with a 256MB
> DoC2000 TSOP and a Linux 2.6.11 kernel image.
> 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
I be interested in seeing the results of "cat /proc/mtd" on your system.
Also, it would be interesting to see what happens if you omit step 3).
Obviously, if you do that your kernel will be unable to load your root
filesystem. But at the moment you aren't even getting the kernel loaded.
You might also want to examine the output from "./nanddump -p
/dev/mtd1", to see if the 0xdbb1 tag shows up. Omit the -p flag if you
prefer binary (rather than pretty-printed ascii) output.
BTW I do everything with the 2.6 kernel; that certainly is not the
problem. In fact the MTD developers don't generally test against the
2.4 kernel :)
-Dan
prev parent reply other threads:[~2005-07-06 19:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 19:11 Problem booting DOCboot and Linux 2.6 Andrew Schultz
2005-07-06 19:36 ` Dan Brown [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=42CC32B0.4020101@ieee.org \
--to=dan_brown@ieee.org \
--cc=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