From: Iztok Zupet <iz@vsr.si>
To: Jasmine Strong <jasmine@hex.linuxgrrls.org>
Cc: <linux-mtd@lists.infradead.org>
Subject: Re: RedBoot from DoC not working quite well
Date: Mon, 1 Jul 2002 16:03:35 +0200 [thread overview]
Message-ID: <200207011603.35218.iz@vsr.si> (raw)
In-Reply-To: <Pine.LNX.4.33.0207011440090.1800-100000@hex.linuxgrrls.org>
On Monday 01 July 2002 15:41, Jasmine Strong wrote:
> On Mon, 1 Jul 2002, Iztok Zupet wrote:
> > RedBoot boots fine (int18 or int19). But after formating my DoC with
> >
> > nftl_format utility:
> > >>> nftl_format /dev/mtd0 128000
>
> You can't start a format from that address. It's not an erase block
> boundary. (Most DoC devices have 8k erase blocks. THat means 8192 bytes,
> not 8000.)
>
> Try erasing from 131072, rather than 128000.
>
> Jas.
I tried but it still owerwrites or erases my RedBoot.
Size of my redboot_firmware is exactly 123.2K.
Regards
iz
next prev parent reply other threads:[~2002-07-01 14:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-01 13:35 RedBoot from DoC not working quite well Iztok Zupet
2002-07-01 13:41 ` Jasmine Strong
2002-07-01 14:03 ` Iztok Zupet [this message]
2002-07-02 10:28 ` Iztok Zupet
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=200207011603.35218.iz@vsr.si \
--to=iz@vsr.si \
--cc=jasmine@hex.linuxgrrls.org \
--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