Flash left in a write mode

Allen Curtis acurtis at onz.com
Fri Feb 8 09:43:59 EST 2002


Luckily our boot ROM is not the same device as the flash file-system.
Another recommendation for hardware designers. Separate your flash
functions.

Thanks for the feedback.

> -----Original Message-----
> From: linux-mtd-admin at lists.infradead.org
> [mailto:linux-mtd-admin at lists.infradead.org]On Behalf Of Arne Jonsson
> Sent: Thursday, February 07, 2002 11:06 PM
> To: acurtis at onz.com
> Cc: linux-mtd at lists.infradead.org
> Subject: Re: Flash left in a write mode
>
>
> Hi!
>
> Another problem is when you have your interrupt vectors stored
> in the flash you are accessing.
> If you get an interrupt and have unlocked the flash your interrupt
> vectors are not seen by the CPU, and off you go into the deep binary
> space.
> I had to disable interrupts at all times when the flash was "unlocked".
> Maybe this is something that we could have a switch/define for ?
> Putting the boot address and hard interrupt vectors in the same address
> range
> is IMHO _very_ bad chip design.
> Another approach would be to have external hardware for the boot vector,
> switching to the flash and have RAM at the address of the interrupt
> vectors, but the extra HW is an extra cost.
>
> Best regards,
> /Arne Jonsson
>
> --
> Arne Jonsson
> i3 micro technology AB
> Phone:+46-8-506 388 00
> Fax:  +46-8-506 388 75
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/





More information about the linux-mtd mailing list