[Avila] mtd0 not found on board - intend to load redboot image

[David Acker]

Bhanu Prakash Adhikari wrote:
> 
> Hope it is apt to discuss in this thread itself.
> 
> My board has -
> 
> ls:~# cat /proc/mtd
> dev:    size   erasesize  name
> mtd0: 00080000 00020000 "RedBoot"
> mtd1: 00140000 00020000 "zimage"
> mtd2: 00320000 00020000 "ramdisk"
> mtd3: 00b00000 00020000 "unallocated"
> mtd4: 0001f000 00020000 "FIS directory"
> mtd5: 00001000 00020000 "RedBoot config"
> 
> 
> I find "redboot config" in /dev/mtdblock5.
> 
> 1.	How can I access mtd0 when there is no corresponding mtdblock0
> available? How can I get into mtd0 and manipulate it either to load
> redboot or to tweak it?
mtd0 is the raw access.  You can feel free to use it through mtd utils.

> 
> 2.	Does the patch mentioned at
> http://mailman.uclinux.org/pipermail/uclinux-dev/2006-September/040068.h
> tml is applicable to mtd0 i.e., redboot partition also? Does the patch
> make mtd0 also read-write?
The patch applies to the FIS directory and RedBoot config partitions. 
By default redboot puts them in a single flash block.  The mtd driver 
wants each partition to end on a flash block.  There are various ways to 
fix this.  The above patch may work but I have never tried it.  I 
changed redboot for this.  See the email I sent you on 2/22, subject 
"fail over mechanism strategy"

> 
> 3.	What are the typical steps involved in linux to load/overwrite
> redboot image from linux (as said by David Acker in the following mail)?
See the email I sent you today, subject "loading redboot image without 
using JTAG or flash burners"

-Ack