Hi Yuri,
Thanks for your reply.
Basically, the customer believes that the ECC feature does not need to be set to 'disable' in i.MX25 side.
They believes the conflict will not occur because the algorithm of ECC on BENAND differs from i.MX25.
And they believe the point is that i.MX25 must support the ‘collective programming’ which is needed for BENAND.
The customer’s understanding is as below.
Are those correct?
I think that there are differences from your opinion.
Could you give your comment on that?
(1)
i.MX25 NFC can support the programming method which is needed for the BENAND.
The BENAND must be programmed en bloc of 512+16Byte at a time, as mentioned in the attached file in the original posting.
(2)
The algorithms of handling ECC differ between the BENAND and i.MX25 NFC.
For the BENAND, ECC is calculated for every 512+16Byte and the ECC is written in the special area in the BENAND.
For i.MX25 NFC, ECC is calculated for every 512byte main area and the ECC is written into 16Byte spare area.
Then, the ECC algorithms of the BENAND and i.MX25 will run separately.
The conflict will not occur between the algorithms of BENAND and i.MX25 NFC.
(3)
They believes that the BENAND can be used for i.MX25 boot.
One can use the following setting for the BENAND.
BMOD[1:0]=00
SLC_NAND/128Byte_spare_for_4kByte/page_size=2kByte
(4)
The customer believes that BENAND can be used for boot device of i.MX25.
BTW, they are using Linux OS, and uboot, kernel and rootfs are written in the NAND.
BR,
Miyamoto