From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 8482CE00A96; Mon, 10 Apr 2017 05:00:21 -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=-1.5 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, RCVD_IN_SORBS_SPAM autolearn=no version=3.3.1 X-Spam-HAM-Report: * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (oliver.graute[at]gmail.com) * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no * trust * [74.125.82.65 listed in list.dnswl.org] * 0.5 RCVD_IN_SORBS_SPAM RBL: SORBS: sender is a spam source * [74.125.82.65 listed in dnsbl.sorbs.net] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -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 Received: from mail-wm0-f65.google.com (mail-wm0-f65.google.com [74.125.82.65]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id DF6DBE009AA for ; Mon, 10 Apr 2017 05:00:20 -0700 (PDT) Received: by mail-wm0-f65.google.com with SMTP id d79so9256436wmi.2 for ; Mon, 10 Apr 2017 05:00:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=w3tBDY4K63vj1+SeTzNXQ7v3hh2oF8s2l3r1q2nRU38=; b=maSWjjO51mIyr6w5rAbea2jwmCzPbFZ6jCLBjgu8bejQWi5pGxlXbsfFyatkofpIJv i7rFVIyKOV0ejHjjBQ71TNOnxa4pw3roNZUdQURLYZGAr8Po7QKeUCSspxh1g0KeedRT gTIdaRDzKDX2jSmBdtIRCPxx6B+fvR9QTsyNnHxFPwv6IId8HQ3BtNVSogeRycFMNIv8 zM15crX79nCXm+X/XTHxDWnrr5lZizLzNztoA+Xir0uxG92OCFGqqcrxVR/LL+ted7CK 3KacISxux48QoYnEbKJfScwmNbVAqL9hFfwYbT0LaTAZvKPPY3r6THBpMFJH+h/P9C9w slTQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mail-followup-to :references:mime-version:content-disposition:in-reply-to:user-agent; bh=w3tBDY4K63vj1+SeTzNXQ7v3hh2oF8s2l3r1q2nRU38=; b=H0uXWnDW2FveHliBH1cwkGy4sNdkJa8uiqBZbUpQRNAvyIOf27QnUowFLZ/zCCQoCT +tQL5TgsBP5rF2gfPU2kTkxozk8B1vpysYbNsI5v2z6SL5uiFpBdG0RDlcg0W6h92hvS RH49Hub33wdBTXFggAzZrkg/voE9Aklgozkypn/x97AEepWVoRcM0M1FfjlTASUMlmTO kWBb6/Uqx1vC9FDrxzYaT1XKnCnDlfcvhJf8TLFHHur1a6NeWmV3DwSCImOSYzR8trQ3 LkIh7sVwvw+piVplKjAmCUiMMGXzgAVVERHuh7RVgoZOzk2eeOdmtwzX114OGC7uORLF FZHg== X-Gm-Message-State: AN3rC/4xLdnVcrBlW6Ldd3Uz9uOQefqZK9/YH+bvKftouuCRUcCIpmh2 H0g3UM9ACXB0PnzJAbI= X-Received: by 10.28.129.147 with SMTP id c141mr5388220wmd.98.1491825619131; Mon, 10 Apr 2017 05:00:19 -0700 (PDT) Received: from localhost (x4e365259.dyn.telefonica.de. [78.54.82.89]) by smtp.gmail.com with ESMTPSA id z38sm17273424wrc.36.2017.04.10.05.00.18 for (version=TLS1_2 cipher=AES128-SHA bits=128/128); Mon, 10 Apr 2017 05:00:18 -0700 (PDT) Date: Mon, 10 Apr 2017 14:00:17 +0200 From: Oliver Graute To: meta-freescale@yoctoproject.org Message-ID: <20170410120017.GA22105@graute-opti> Mail-Followup-To: meta-freescale@yoctoproject.org References: <20170406082351.GB23716@graute-opti> MIME-Version: 1.0 In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) 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 12:00:21 -0000 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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