From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id AFD9EE0059A; Mon, 10 Apr 2017 09:11:24 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 X-Spam-HAM-Report: * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (jopoulin[at]gmail.com) * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 HTML_MESSAGE BODY: HTML included in message * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no * trust * [74.125.82.67 listed in list.dnswl.org] Received: from mail-wm0-f67.google.com (mail-wm0-f67.google.com [74.125.82.67]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 33A91E003E1 for ; Mon, 10 Apr 2017 09:11:18 -0700 (PDT) Received: by mail-wm0-f67.google.com with SMTP id d79so10479891wmi.2 for ; Mon, 10 Apr 2017 09:11:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=pMTHorSdwUjj7Umt8dtAvcZBlNHrJ0elpDl6dJgVAPI=; b=rKnD6i9KFHyGd8Zq7wFTMaOWQIGfVPHcjbceQJfWcp2Qk8+ir27qRbEHzC54aN2ckh u4UOBryelr++tB1ZO9X7kvv7csANMgUDOR13arkzfRE2QH4dle4YIeGL1NL76Nxr+Hj0 AAXRn//c+JIVi1UYdTwDK/3+op5L+9kIMTohJpKY+msYyUd5PenhEEB5ZLeUyIrr84LA 70X9bshfDP6FajuX7k+DrJ/s5vlrPJjcvYlMhFZKR+cKPWowa9fhkOW26S86jWZZ/hNF nvE8DJn/z4dVuipcZQyGvuxXIA60z6FtexQFbz//0v9KZTZdNtx52AqBBVCMOMATbuIV 90Gw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=pMTHorSdwUjj7Umt8dtAvcZBlNHrJ0elpDl6dJgVAPI=; b=toMETwGErjxL7njIV5myC3XYHjOb696M+Tc4anKdrWn5gSOLjN0p8QWi8JZ7JH5qXo qqawz/C6sXqn9t00SvfFYXm8YBQZ2bCoaiWdzbP4BfBODsLk6u37Z/+ltArYQp7L50U6 7kEH8tju1WB3uiSL2zm7ZUqsjQku5jkwskfwFwx4tRO/cTZtNFBgyffiM0mqNmUlYYSs /Hvf+g4Y8l3S1TYjhzX0IiY+A4YnYDyCYR/6Tpvk1Kz1TLqtldxORR6LnAgv/tiC6vFc Puo/w4t+BOeauIrO+c8xEgQRr3WN2Xb6P44WRVd9Q2/9BsBys53UT1yH6fg0H5siVj87 NCgA== X-Gm-Message-State: AN3rC/6gskVbPYV7onF8uaTTDnEmREPYbu4pSIbHm+/LtHBBQfYgCiY5 jp4o4DSiyNBtAghjTMxnJjS4Ty0uByqW X-Received: by 10.28.198.65 with SMTP id w62mr6753060wmf.80.1491840677135; Mon, 10 Apr 2017 09:11:17 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.140.209 with HTTP; Mon, 10 Apr 2017 09:11:16 -0700 (PDT) In-Reply-To: <20170410120017.GA22105@graute-opti> References: <20170406082351.GB23716@graute-opti> <20170410120017.GA22105@graute-opti> From: Jonathan Poulin Date: Mon, 10 Apr 2017 12:11:16 -0400 Message-ID: To: meta-freescale@yoctoproject.org Subject: Re: linux-fslc 4.9.x and gpmi-nand driver support X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2017 16:11:24 -0000 Content-Type: multipart/alternative; boundary=94eb2c1942b29f523c054cd239ac --94eb2c1942b29f523c054cd239ac Content-Type: text/plain; charset=UTF-8 Hello, This is what I had in my gpmi node. The rest of the node is in the file imx6q.dtsi. /* General purpose media interface is used for NAND control */ &gpmi { pinctrl-names = "default"; pinctrl-0 = <&pinctrl_gpmi_nand_axion>; fsl,legacy-bch-geometry; status = "okay"; }; I don't know if this is manage correctly in the 4.9.18-fslc. I'm sorry. In my side I had problem between the kernel and the u-boot. My Mfgtool kernel and my target kernel are essentially the same (linux-imx_4.1.15 and linux-fslc-imx_4.1-1.0) and I apply the patch to both. good luck Jonathan 2017-04-10 8:00 GMT-04:00 Oliver Graute : > On 07/04/17, Jonathan Poulin wrote: > > Hello Olivier, > > > > I had a similar problem. Look at > > https://lists.yoctoproject.org/pipermail/meta-freescale/ > 2017-April/020344.html > > > > This was cause by a mismatch between the ECC strength used by the write > of > > the partition and the one used by the reader. Try the solution that I > link > > in the answer of my post. > > thx for this hint. Unfortunately the patch didn't work for me. What does > your gpmi device node look like? > > I write my NAND with mfgtool which runs 4.1.15_1.0.0 kernel during the > flash operation itself. > > But on first boot it starts 4.9.18-fslc and on reading I got these ECC > errors. So it's quite possible that the ECC strength is different > between both kernel versions. > > Furthermore the gpmi-nand driver has major changes between both kernel > versions. > > Best Regards, > > Oliver > -- > _______________________________________________ > meta-freescale mailing list > meta-freescale@yoctoproject.org > https://lists.yoctoproject.org/listinfo/meta-freescale > --94eb2c1942b29f523c054cd239ac Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello,

This is what I had in my gpmi node. The rest of the node is in the file imx6q.dtsi.

/* General purpose media interface is used for NAND control */
&= amp;gpmi {
=C2=A0=C2=A0=C2=A0 pinctrl-names =3D "default";
= =C2=A0=C2=A0=C2=A0 pinctrl-0 =3D <&pinctrl_gpmi_nand_axion>;
= =C2=A0=C2=A0=C2=A0 fsl,legacy-bch-geometry;
=C2=A0=C2=A0=C2=A0 status = =3D "okay";
};

I don't know if this is m= anage correctly in the 4.9.18-fslc. I'm sorry. In my side I had problem= between the kernel and the u-boot. My Mfgtool kernel and my target kernel = are essentially=C2=A0 the same (linux-imx_4.1.15 and linux-fslc-imx_4.1-1.0= ) and I apply the patch to both.


good luck
<= div>Jonathan


<= div class=3D"gmail_quote">2017-04-10 8:00 GMT-04:00 Oliver Graute <o= liver.graute@gmail.com>:
On 07/04/17, Jonathan Poulin wrote:
> Hello Olivier,
>
> I had a similar problem. Look at
> https://lists.yoc= toproject.org/pipermail/meta-freescale/2017-April/020344.html=
>
> This was cause by a mismatch between the ECC strength used by the writ= e of
> the partition and the one used by the reader. Try the solution that I = link
> in the answer of my post.

thx for this hint. Unfortunately the patch didn't work for me. W= hat does
your gpmi device node look like?

I write my NAND with mfgtool which runs 4.1.15_1.0.0 kernel during the
flash operation itself.

But on first boot it starts 4.9.18-fslc and on reading I got these ECC
errors. So it's quite possible that the ECC strength is different
between both kernel versions.

Furthermore the gpmi-nand driver has major changes between both kernel
versions.

Best Regards,

Oliver
--
_______________________________________________
meta-freescale mailing list
meta-freescale@yoctoproj= ect.org
https://lists.yoctoproject.org/listinfo/m= eta-freescale

--94eb2c1942b29f523c054cd239ac--