From rong1129@gmail.com Mon Jun 01 07:07:56 2009 Received: from mail-pz0-f106.google.com ([209.85.222.106]) by stoneboat.aleph1.co.uk with esmtp (Exim 4.69) (envelope-from ) id 1MB0gb-0006XG-Re for yaffs@lists.aleph1.co.uk; Mon, 01 Jun 2009 07:07:56 +0100 Received: by pzk4 with SMTP id 4so5597390pzk.8 for ; Sun, 31 May 2009 23:07:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=MiA9r/iM20lf6CxLrWOORkSma4uEDITxH2MrZ1jqDLM=; b=X2K/fg2sE+N7M8m5u6uzH+2mcDmdiBEWvA/KDFXuBAN0F24ZEx4Lu3mPcaE/CeVTrl pziDAJdAdOb2bXGFYbfyaxua6oC18fR5A4CC1KYvIsmNRsMyL4a9v5cQCxpsyWRBGFB6 lqB2vM1Ix7rbUQCD1rfxA3Fm9/hO67l6O7Ip0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=DR3L+5mfuMi448DdMspvr+jxvJ17HPlG+7JeMDnEG8z0Mp74iGXHuKODKBM8CEG4rm uQtaWL2qN2EUdZjGEWA612kt/P7fgeXErANdUSqqCLJ5K7UeZajYIp0IbqFEtlxFSRQT nA89UO+h71gbj5tyZ5eUfCrVvkLQfoaxsfSvk= MIME-Version: 1.0 Received: by 10.141.26.18 with SMTP id d18mr5969603rvj.48.1243836018066; Sun, 31 May 2009 23:00:18 -0700 (PDT) In-Reply-To: References: Date: Mon, 1 Jun 2009 16:00:18 +1000 Message-ID: From: Rong Shen To: =?ISO-8859-1?Q?Michaela_M=FCcke?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-SA-Exim-Connect-IP: 209.85.222.106 X-SA-Exim-Mail-From: rong1129@gmail.com X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on stoneboat.aleph1.co.uk X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=no version=3.2.5 X-SA-Exim-Version: 4.2.1 (built Wed, 25 Jun 2008 17:14:11 +0000) X-SA-Exim-Scanned: Yes (on stoneboat.aleph1.co.uk) Cc: yaffs@lists.aleph1.co.uk Subject: Re: [Yaffs] BadBlock in YAFFS2 X-BeenThere: yaffs@lists.aleph1.co.uk X-Mailman-Version: 2.1.11 Precedence: list List-Id: Discussion of YAFFS NAND flash filesystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Jun 2009 06:07:57 -0000 On Sun, May 31, 2009 at 7:47 PM, Michaela M=FCcke wrote: > Hi all, > iam Michaela and iam a young Student from Germany (Ulm). > Iam writing my Diploma work about YAFFS2 to integrate in the > real time operation system INTEGRITY-178B from Greenhills. > I have four NAND chips K9K4G08U0M=A0from Samsung, which are > complete one Device. > I think i understand this main working about yaffs2 but iam a little > bit confuse about how to mark bad blocks. Is it a real mark on the There are bad block marks on individual chips. Since you have a device which integrates four NAND chips, there could be extra information on the device, so check the device data sheet. > chip=A0like yaffs1 or=A0is it only a intern thing from yaffs2 ?=A0I have = this It's related to the NAND flash, not an invention of Yaffs*. > PackedTags2=A0with fields SequenceNumber, ObjectID, ChunkID and > byteCount but where is this field for state?? > So what i have to do exactly in=A0this function=A0 markNANDBlockBad? > Real Byte set on the device or only change this variable state of this > block? It should call a MTD layer function, which in turn sets the bad block mark on the NAND flash (or maybe BBT - check the code yourself!). > A other question is, i read YAFFS2 need this Block 0 for intern works. really? I guess this internalStartBlock and StartBlock thing really confuses you and me, maybe someone else here can explain this:) > So what exactly=A0yaffs safe in this block? > Thanks very much !! > > > BR > Michaela > _______________________________________________ > yaffs mailing list > yaffs@lists.aleph1.co.uk > http://lists.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs > > Rong