[meta-freescale] linux-fslc 4.9.x and gpmi-nand driver support

Jonathan Poulin jopoulin at gmail.com
Mon Apr 10 09:11:16 PDT 2017


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 */
&gpmi {
    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.

good luck

2017-04-10 8:00 GMT-04:00 Oliver Graute <oliver.graute at 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/
> 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 at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-freescale/attachments/20170410/dfbd6cf3/attachment.html>

More information about the meta-freescale mailing list