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

[Bhanu Prakash Adhikari]

Hope it is apt to discuss in this thread itself.

My board has -=0D

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"

ls:~# ls -l /dev/mtd*
brw-r--r--  1 root root 31, 1 Jun  5  2006 /dev/mtdblock1
brw-r--r--  1 root root 31, 2 Jun  5  2006 /dev/mtdblock2
brw-r--r--  1 root root 31, 3 Jun  5  2006 /dev/mtdblock3
brw-r--r--  1 root root 31, 4 Jun  5  2006 /dev/mtdblock4
brw-r--r--  1 root root 31, 5 Jun  5  2006 /dev/mtdblock5
ls:~#

Board Details -=0D

	Avila=0D
	IXDP425
	Linux 2.6.18=0D

I find "redboot config" in /dev/mtdblock5.=0D

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?

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?

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)?

Thanks and rgds,
Bhanu Prakash A

-----Original Message-----
From: David Acker [mailto:dacker at roinet.com]=0D
Sent: Friday, February 23, 2007 8:58 PM
To: Avila
Subject: Re: [Avila] find whether my board uses redboot_RAM.ecm or
redboot_ROM.ecm

Bhanu Prakash Adhikari wrote:
>=0D
> Thanks David.
>=0D
> I'm a newbie to Redboot as developer but have been using it for long.
>=0D
> We are at the right intersection; I'm actually attempting to load the
> custom build redboot to Avila board as a part of my exercise to build
> application on the top of redboot.
>=0D
> I was under the impression these steps will do to load redboot -
>=0D
> (http://ecos.sourceware.org/docs-latest/redboot/ipaq.html )
>=0D
> RedBoot> lo -r -b 0x100000 redboot_ROM.bin
> RedBoot> fi loc -f 0x50000000 -l 0x40000
> RedBoot> fis init
> RedBoot> fi unl -f 0x50040000 -l 0x40000
> RedBoot> fi cr RedBoot -b 0x100000
> RedBoot> fi loc -f 0x50040000 -l 0x40000
> RedBoot> reset
>=0D
> Correct me if I'm wrong.

I believe the avila boards have a redboot in rom mode which will not=0D
over write itself.  You will need to boot to linux (or something else)=0D
and then overwrite redboot.  We changed redboot to make the config=0D
partitions come up the way linux wants.  You could also jtag it but jtag

takes a very long time, even for just redboot.
-Ack

---------------------------------------------------------------------
To unsubscribe, e-mail: avila-unsubscribe at lists.unixstudios.net
For additional commands, e-mail: avila-help at lists.unixstudios.net

The information contained in, or attached to, this e-mail, contains=
 confidential information and is intended solely for the use of the=
 individual or entity to whom they are addressed and is subject to legal=
 privilege. If you have received this e-mail in error you should notify the=
 sender immediately by reply e-mail, delete the message from your system=
 and notify your system manager. Please do not copy it for any purpose, or=
 disclose its contents to any other person. The views or opinions presented=
 in this e-mail are solely those of the author and do not necessarily=
 represent those of the company. The recipient should check this e-mail and=
 any attachments for the presence of viruses. The company accepts no=
 liability for any damage caused, directly or indirectly, by any virus=
 transmitted in this email.

www.aztecsoft.com