<div dir="ltr"><div><div><div><div>Hello, <br><br></div>I answer to me for archive and help others.<br><br></div>My problem is effectively related to ECC strength used. I try the configuration and the patch proposed by the following thread and it solve my problem.<br><br><a href="https://community.nxp.com/thread/443085">https://community.nxp.com/thread/443085</a><br><br></div>thanks<br></div>Jonathan<br><div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">2017-03-31 16:45 GMT-04:00 Jonathan Poulin <span dir="ltr"><<a href="mailto:jopoulin@gmail.com" target="_blank">jopoulin@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div><div><div><div><div>Hello,<br><br></div>I built an image for a imx6-dual custom board using yocto krogoth with meta-fsl-arm. I used u-boot-fslc_2016.07 and linux-fslc-imx_4.1-1.0.x.<br><br></div>I successfully burnt u-boot and the kernel to nand with mfgtool. But when I tried to boot it; u-boot got an error in accessing the kernel partition.<br><br>----<br></div>NAND read: device 0 offset 0x500000, size 0x1e00000<br>NAND read from offset 500000 failed -74<br></div>Â 0 bytes read: ERROR<br>-----<br><br></div>If I write the kernel from u-boot then I can boot the kernel correctly.<br><br></div>I also tried to erase and write the kernel from the kernel with flash_ereae and nand_write. Then I couldn't reboot and got the same error.<br><br></div>I suspect an incompatibility in the ECC encoding protocol used by kernel and u-boot.<br><br></div><div>The NAND chip used is MT29F8G08ABABAWP.<br></div><div><br><br></div>Do anyone have a solution or a clue about this ?<br><br></div>thanks<span class="HOEnZb"><font color="#888888"><br></font></span></div><span class="HOEnZb"><font color="#888888">Jonathan<br><div><div><div><div>Â <br></div></div></div></div></font></span></div>
</blockquote></div><br></div>