This is what I had in my gpmi node. The rest of the node is in the file
/* General purpose media interface is used for NAND control */
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_gpmi_nand_axion>;
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.
2017-04-10 8:00 GMT-04:00 Oliver Graute <oliver.gra...@gmail.com>:
> On 07/04/17, Jonathan Poulin wrote:
> > Hello Olivier,
> > I had a similar problem. Look at
> > https://lists.yoctoproject.org/pipermail/meta-freescale/
> > This was cause by a mismatch between the ECC strength used by the write
> > the partition and the one used by the reader. Try the solution that I
> > 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
> Best Regards,
> meta-freescale mailing list
meta-freescale mailing list