public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: davis_g@comcast.net
To: "George G. Davis" <davis_g@comcast.net>
Cc: linux-mtd@lists.infradead.org
Cc: linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: integrator-flash Chip reports voltage low on erase
Date: Mon, 5 Jan 2004 09:45:23 -0500	[thread overview]
Message-ID: <20040105144523.GB3940@mvista.com> (raw)
In-Reply-To: <20031222190906.GB20778@mvista.com>

Ping, any comments/feedback on this?

Happy New Year!

--
Regards,
George

On Mon, Dec 22, 2003 at 02:09:06PM -0500, George G. Davis wrote:
> Greetings,
> 
> First, I'm intentionlly cross posting this because portions of the relevent
> code are contained in both MTD CVS HEAD and linux-2.6.0-rmk1 patch.
> 
> I submitted a fix for this problem against linux-2.6.0-test10-rmk1 here:
> 
> http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=1728/1
> 
> However RMK has requested further discussion for this issue. So here goes...
> 
> The ARM Integrator/AP (see drivers/mtd/maps/integrator-flash.c) has a single
> contiguous logical bank of flash memory comprised of 4 physical banks x 2 x
> 256kib x 16-bit Intel DT28F320 devices. At least this is the case for my ARM
> Integrator/AP rev D. For my particular hardware rev of the ARM Integrator/AP,
> I get "Chip reports voltage low on erase" errors while running linux-2.6.0-rmk1
> + MTD CVS HEAD as of 19Dec03 +/-. The same problem also exists in past revs of
> linux 2.4, 2.6 and MTD CVS. So this is not a regression in recent kernels or
> MTD.
> 
> Here are the flash details from kernel init messages:
> 
> armflash0: Found 2 x16 devices at 0x0 in 32-bit mode
> armflash0: Found 2 x16 devices at 0x800000 in 32-bit mode
> armflash0: Found 2 x16 devices at 0x1000000 in 32-bit mode
> armflash0: Found 2 x16 devices at 0x1800000 in 32-bit mode
>  Intel/Sharp Extended Query Table at 0x0031
> cfi_cmdset_0001: Erase suspend on write enabled
> Using buffer write method
> 4 cmdlinepart partitions found on MTD device armflash0
> Creating 4 MTD partitions on "armflash0":
> 0x00000000-0x00400000 : "kernel"
> 0x00400000-0x01000000 : "rootfs"
> 0x01000000-0x01fc0000 : "userfs"
> 0x01fc0000-0x02000000 : "sib"
> 
> FWIW, I added MTD cmdlinepart support as follows (because I am not currently
> using RedBoot firmware on this target and I abhor the ARM afs support 8 ):
> 
> Index: drivers/mtd/maps/integrator-flash.c
> ===================================================================
> RCS file: /home/cvs/mtd/drivers/mtd/maps/integrator-flash.c,v
> retrieving revision 1.14
> diff -u -r1.14 integrator-flash.c
> --- drivers/mtd/maps/integrator-flash.c	11 Oct 2003 10:00:31 -0000	1.14
> +++ drivers/mtd/maps/integrator-flash.c	22 Dec 2003 17:55:05 -0000
> @@ -65,7 +65,7 @@
>  		info->plat->set_vpp(on);
>  }
>  
> -static const char *probes[] = { "RedBoot", "afs", NULL };
> +static const char *probes[] = { "cmdlinepart", "RedBoot", "afs", NULL };
>  
>  static int armflash_probe(struct device *_dev)
>  {
> 
> 
> Here's the linux cmdline and flash partition details for this test case:
> 
> cat /proc/cmdline
> console=ttyAM0,38400n8 noinitrd root=/dev/nfs ip=bootp mtdparts=armflash0:0x00400000@0x00000000(kernel),0x00c00000@0x00400000(rootfs),0x00fc0000@0x01000000(userfs),0x00040000@0x01fc0000(sib)
> 
> cat /proc/mtd
> dev:	size   erasesize  name
> mtd0: 00400000 00020000 "kernel"
> mtd1: 00c00000 00020000 "rootfs"
> mtd2: 00fc0000 00020000 "userfs"
> mtd3: 00040000 00020000 "sib"
> 
> 
> And here's the test case with results:
> 
> mkdir -p /initrd
> mkdir -p /mnt/mtdblock1
> eraseall /dev/mtd1
> mount -oloop /boot/initrd.ext2fs /initrd/
> mount -tjffs2 /dev/mtdblock1 /mnt/mtdblock1
> cd /initrd/
> find . -mount -depth--print0 | cpio -padmu0 /mnt/mtdblock1 lock1
> Chip reports voltage low on erase: status 0xa800a8
> Erase at 0x003e0000 failed immediately: errno -5
> Chip reports voltage low on erase: status 0xa800a8
> Erase at 0x003c0000 failed immediately: errno -5
> Chip reports voltage low on erase: status 0xa800a8
> Erase at 0x003a0000 failed immediately: errno -5
> .
> .
> .
> ad nauseam!
> 
> 
> A fix for this problem can be found at the URL noted above. Note that
> the fix is against the linux-2.6.0-rmk1 patch sice the affected code is
> not contained in MTD CVS. Also note that this problem exists in linux-2.4
> as well.
> 
> 
> Comments/feedback appreciated.
> 
> TIA!
> 
> -- 
> Regards,
> George
> 
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/

      reply	other threads:[~2004-01-05 14:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-22 19:09 integrator-flash Chip reports voltage low on erase George G. Davis
2004-01-05 14:45 ` davis_g [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=20040105144523.GB3940@mvista.com \
    --to=davis_g@comcast.net \
    --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