public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
* K9F5608U0B-YIB0000: 528 byte in page, or 512?
@ 2003-03-31 22:07 A.L. Klyutchenya
  2003-04-01  3:36 ` Charles Manning
  0 siblings, 1 reply; 6+ messages in thread
From: A.L. Klyutchenya @ 2003-03-31 22:07 UTC (permalink / raw)
  To: linux-mtd

I try to use the microcircuits K9F5608U0B-YIB0000 from Samsung. 
Herewith, size of the page size of this chip is 512 + 16 bytes 
(528). When I write the image of the disk on chip, me it is 
necessary to write all bytes consecutively? Or only 512 on each 
page, but remained 16 not to use?
-- 
????????!      
      ____   __
     /   |  / / ?. ?. ????????
    / /| | / /  (asoneofus)
   / /_| |/ /   mail:   asoneofus at kde.ru
  / ____  _ \   www:    http://www.qt.kde.ru
 / /   | | \ \  icq:    113679387
/_/    |_|  \_\ 

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: K9F5608U0B-YIB0000: 528 byte in page, or 512?
  2003-03-31 22:07 K9F5608U0B-YIB0000: 528 byte in page, or 512? A.L. Klyutchenya
@ 2003-04-01  3:36 ` Charles Manning
  2003-04-01 11:02   ` A.L. Klyutchenya
  0 siblings, 1 reply; 6+ messages in thread
From: Charles Manning @ 2003-04-01  3:36 UTC (permalink / raw)
  To: A.L. Klyutchenya, linux-mtd

This is NAND flash. Do not try to treat it as NOR flash.
Use it with mtd/nand  and use YAFFS or JFFS2 file system.

You must write NAND in whole pages, not on a per-byte basis.

On Tue, 01 Apr 2003 10:07, A.L. Klyutchenya wrote:
> I try to use the microcircuits K9F5608U0B-YIB0000 from Samsung.
> Herewith, size of the page size of this chip is 512 + 16 bytes
> (528). When I write the image of the disk on chip, me it is
> necessary to write all bytes consecutively? Or only 512 on each
> page, but remained 16 not to use?

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: K9F5608U0B-YIB0000: 528 byte in page, or 512?
  2003-04-01  3:36 ` Charles Manning
@ 2003-04-01 11:02   ` A.L. Klyutchenya
  2003-04-02 10:28     ` Thomas Gleixner
  0 siblings, 1 reply; 6+ messages in thread
From: A.L. Klyutchenya @ 2003-04-01 11:02 UTC (permalink / raw)
  To: linux-mtd

Dear sir,
Thank you for quick answer.

1 Апрель 2003 07:36, Charles Manning написал:
> This is NAND flash. Do not try to treat it as NOR flash.
> Use it with mtd/nand  and use YAFFS or JFFS2 file system.

I want to write the first image, for booting system. I create 
this image (with kernel, MTD & Co). I have a possibility his 
write. Herewith: I have an physical access to page: size 
256+256+16, and block on 32 pages. While NO MTD and NO kernel!

> You must write NAND in whole pages, not on a per-byte basis.

I understand that page it is necessary to write, but what bring 
the first image: chain on 512+512.... or 512+16 free + 512+16 
free...

As even so write? :-) (to hrdware-level)

> On Tue, 01 Apr 2003 10:07, A.L. Klyutchenya wrote:
> > I try to use the microcircuits K9F5608U0B-YIB0000 from
> > Samsung. Herewith, size of the page size of this chip is 512
> > + 16 bytes (528). When I write the image of the disk on
> > chip, me it is necessary to write all bytes consecutively?
> > Or only 512 on each page, but remained 16 not to use?

-- 
ВсехБлаг!      
      ____   __
     /   |  / / А. Л. Клютченя
    / /| | / /  (asoneofus)
   / /_| |/ /   mail:   asoneofus@kde.ru
  / ____  _ \   www:    http://www.qt.kde.ru
 / /   | | \ \  icq:    113679387
/_/    |_|  \_\ 

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: K9F5608U0B-YIB0000: 528 byte in page, or 512?
  2003-04-01 11:02   ` A.L. Klyutchenya
@ 2003-04-02 10:28     ` Thomas Gleixner
  2003-04-22  9:06       ` A.L. Klyutchenya
  0 siblings, 1 reply; 6+ messages in thread
From: Thomas Gleixner @ 2003-04-02 10:28 UTC (permalink / raw)
  To: A.L. Klyutchenya, linux-mtd@lists.infradead.org

On Tuesday 01 April 2003 13:02, A.L. Klyutchenya wrote:
> Dear sir,
> Thank you for quick answer.
>
> 1 Апрель 2003 07:36, Charles Manning написал:
> > This is NAND flash. Do not try to treat it as NOR flash.
> > Use it with mtd/nand  and use YAFFS or JFFS2 file system.
>
> I want to write the first image, for booting system. I create
> this image (with kernel, MTD & Co). I have a possibility his
> write. Herewith: I have an physical access to page: size
> 256+256+16, and block on 32 pages. While NO MTD and NO kernel!
>
> > You must write NAND in whole pages, not on a per-byte basis.
>
> I understand that page it is necessary to write, but what bring
> the first image: chain on 512+512.... or 512+16 free + 512+16
> free...
>
> As even so write? :-) (to hrdware-level)
Please read http://linux-mtd.infraded.org/tech/nand.html

-- 
Thomas
________________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: K9F5608U0B-YIB0000: 528 byte in page, or 512?
  2003-04-02 10:28     ` Thomas Gleixner
@ 2003-04-22  9:06       ` A.L. Klyutchenya
  2003-04-23 20:32         ` Charles Manning
  0 siblings, 1 reply; 6+ messages in thread
From: A.L. Klyutchenya @ 2003-04-22  9:06 UTC (permalink / raw)
  To: linux-mtd@lists.infradead.org

2 Апрель 2003 14:28, Thomas Gleixner написал:
> On Tuesday 01 April 2003 13:02, A.L. Klyutchenya wrote:
> > Dear sir,
> > Thank you for quick answer.
> >
> > 1 Апрель 2003 07:36, Charles Manning написал:
> > > This is NAND flash. Do not try to treat it as NOR flash.
> > > Use it with mtd/nand  and use YAFFS or JFFS2 file system.
> >
> > I want to write the first image, for booting system. I
> > create this image (with kernel, MTD & Co). I have a
> > possibility his write. Herewith: I have an physical access
> > to page: size 256+256+16, and block on 32 pages. While NO
> > MTD and NO kernel!
> >
> > > You must write NAND in whole pages, not on a per-byte
> > > basis.
> >
> > I understand that page it is necessary to write, but what
> > bring the first image: chain on 512+512.... or 512+16 free +
> > 512+16 free...
> >
> > As even so write? :-) (to hrdware-level)
>
> Please read http://linux-mtd.infraded.org/tech/nand.html

I read, and don't find answer.

1) make jffs2 image: correct erase block-size for NAND (512+16 
page x 32) is 0x4200 or (512 page x 32) 0x4000?

2) for writing jffs2 image to NAND use only 512byte space on each 
page, or 512+16?

-- 
ВсехБлаг!      
      ____   __
     /   |  / / А. Л. Клютченя
    / /| | / /  (asoneofus)
   / /_| |/ /   mail:   asoneofus@kde.ru
  / ____  _ \   www:    http://www.qt.kde.ru
 / /   | | \ \  icq:    113679387
/_/    |_|  \_\ 

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: K9F5608U0B-YIB0000: 528 byte in page, or 512?
  2003-04-22  9:06       ` A.L. Klyutchenya
@ 2003-04-23 20:32         ` Charles Manning
  0 siblings, 0 replies; 6+ messages in thread
From: Charles Manning @ 2003-04-23 20:32 UTC (permalink / raw)
  To: A.L. Klyutchenya, linux-mtd@lists.infradead.org

[snip]
> > >
> > > I understand that page it is necessary to write, but what
> > > bring the first image: chain on 512+512.... or 512+16 free +
> > > 512+16 free...
> > >
> > > As even so write? :-) (to hrdware-level)
> >
> > Please read http://linux-mtd.infraded.org/tech/nand.html
>
> I read, and don't find answer.
>
> 1) make jffs2 image: correct erase block-size for NAND (512+16
> page x 32) is 0x4200 or (512 page x 32) 0x4000?

The eraseure size is 0x4000. 
>
> 2) for writing jffs2 image to NAND use only 512byte space on each
> page, or 512+16?

The 512-byte part is written by the write function and the 16 bit "spare" or 
"out of band"  area is written with the write_oob function.

-- Charles

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2003-04-23 20:31 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-03-31 22:07 K9F5608U0B-YIB0000: 528 byte in page, or 512? A.L. Klyutchenya
2003-04-01  3:36 ` Charles Manning
2003-04-01 11:02   ` A.L. Klyutchenya
2003-04-02 10:28     ` Thomas Gleixner
2003-04-22  9:06       ` A.L. Klyutchenya
2003-04-23 20:32         ` Charles Manning

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox