topic Problem with nand flash programming in i.MX Processors

Problem with nand flash programming

alessandrobenfe — Mon, 22 Apr 2024 17:18:12 GMT

Hi, i work with two SOM one with imx6solo and other one with imx6quad, both SOM have with same nand flash.

With a MicroSD card update the SOM; with imx6quad I always have success, but with imx6solo sometimes don't have success.

For update the rootfs I use a script with this instructions:
ubiformat -y /dev/mtd3
ubiattach /dev/ubi_ctrl -m 3
ubimkvol /dev/ubi0 -N rootfs -s445000000
mkdir /rootfs
mount -t ubifs ubi0:rootfs /rootfs
tar xvf /rootfs.tar.bz2 -C /rootfs
sync

When I boot from nand flash I have some errors of this type:

UBIFS error (ubi0:0 pid 277): ubifs_read_node: bad node type (255 but expected 1)
UBIFS error (ubi0:0 pid 277): ubifs_read_node: bad node at LEB 394:119808, LEB mapping status 0
Not a node, first 24 bytes:
00000000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ........................

I don't understand what the problem could be due to and what settings to check.

Note: I use a yocto pyro distribution

Can you help me?

Thanks,

Alessandro

Re: Problem with nand flash programming

Bio_TICFSL — Tue, 23 Apr 2024 14:42:05 GMT

Hello,

Check your SOM vendor because apparently t does not use the same nand on both MX6 processors.

Regards

Re: Problem with nand flash programming

alessandrobenfe — Fri, 03 May 2024 09:03:59 GMT

Hi,

from the tests carried out the error seems to occur due to the use of two different distributions of yocto to create the OS of the microSD and the one contained in the flash.

For the quad core version the same version of yocto was used for both the microSD and the flash.

I believe there is some incompatibility between the versions of the flash management drivers between the two kernel versions used in the yocto distributions.

At the moment, by using the same version of yocto to build the OS for everyone we solved the problem.

Re: Problem with nand flash programming

kef2 — Fri, 03 May 2024 10:19:55 GMT

FF FF.. looks like erased flash page. It could be for example due to misconfigured U-Boot environment area in NAND flash, so that when U-Boot stores environment variables, NAND page(s) at bottom of your UBI partition gets erased.