ay to
overcome this behaviour?
Following is my test environment.
gcc : 3.4.4 / 4.2.1 arm-linux toolchain
- used for uClinux, distributed by http://www.snapgear.org/
Processor : ARM922T Micrel KS8695P
NOR Flash : STMicro M29W640FT (64Mbit 16bit buswidth)
Regards,
Choe, Hy
In cpu dir, there is arm920t/ks8695.
ks8695p is some modified chip from ks8695.
In board section, OpenGear cm4008 and cm41xx uses ks8695.
2008-11-20 (목), 18:45 +0100, Jean-Christophe PLAGNIOL-VILLARD 쓰시길:
> On 01:27 Fri 21 Nov , Choe, Hyun-ho wrote:
> > Hello, everyone.
> >
Hi.
2008-11-20 (목), 19:02 +0100, Jean-Christophe PLAGNIOL-VILLARD 쓰시길:
> On 02:59 Fri 21 Nov , Choe, Hyun-ho wrote:
> > In cpu dir, there is arm920t/ks8695.
> > ks8695p is some modified chip from ks8695.
> do this modification is U-Boot mainline supported?
> >
I thin
e
should be work because two sequential read from CFI flash changes toggle
bit while erase/write is in action.
But, two read operation gets the same result.
Any other things that I wasn't understand ?
TIA, Any advice will be appreciated.
Best regards,
Choe, Hyun-ho
2008-11-20 (목), 12:34 -
() can be modified to get another
parameter for sector. (flash_read_long() already gets sector)
And, flash_read_long_long() function may needs to be defined.
What do you think about this? Is there any side effect between each
platform?
Regards,
Choe, Hyun-ho
_
2008-11-26 (수), 10:58 +0100, Wolfgang Denk 쓰시길:
> Dear "Choe, Hyun-ho",
>
> In message <[EMAIL PROTECTED]> you wrote:
> > I did several tests for my b'd that has CFI Nor erase/write problem.
> >
> > My main problem is that flash_toggle() functio
2008-11-26 (수), 16:10 +0100, Michael Lawnick 쓰시길:
> Choe, Hyun-ho said the following:
> > My second workaround is strange, too.
> > In ARM code, mapping physical address to logical is actually does
> > nothing, except re-calculating pointer with sector no. and offset.
>
7 matches
Mail list logo
