LINUXSDK-OMAPL138: NAND BOOT

Hi, Tzvi,

We can't possibly document how it should be done to all available NAND out in the market. It should be possible, but we haven't done it. You may want to research a bit. The nand driver code may need to change to reflect the differences between different NAND.

Rex

Hi,

Thank you for the reply.

I did change the driver code in u-boot/kernel in order to work with software ECC ( 8 bit ), I can read/write from u-boot for now.

However, I am not sure what kind of support I have in the chip bootrom, what is the correct ecc layout and spare area since it is not documented ( or at least I did not find the documentation)

I read the document SPRAB41F–January 2014–Revised January 2019 (Using the OMAP-L132/L138 Bootloader)

in the section: Details of Supported NAND Devices -There is a list of nand devices none of the is 4K page size with 8 bit ecc, there is a statement that if the device is onfi complaint then the bootrom should work.

I just want to make sure that I don't have a hardware design problem with not compatible nand. 

Please advise,

Thanks

Tzvi

Hi, Tzvi,

Please refer to the NAND ECC layout document. Though it is for the other device, but OMAP-L138 falls into Davinci NAND architecture. The document should apply.

https://processors.wiki.ti.com/index.php/DM365_Nand_ECC_layout

Rex

Hi, 

Thanks for the reply, however I did not understand how to use the information in this document for our NAND device.

The layout specified is compatible with our old NAND device , and the ECC layout for RBL with 2K page is clear.

I don't understand how to define the ecc layout so that the bootrom will understand it for 4k page size NAND with 224 oob data.

There is no information in the omapl138 or dm365 datasheet and reference manual that explains how the bootrom access such a device.

If you think that OMAPL138 can boot from this device please help us understand how to define our spare area.

Can we configure the hardware so that the bootrom will work without ecc ? 

Regards,

Tzvi

Hi, Tzvi,

We don't have info on your particular NAND part. Since we don't have the part you mentioned, We can only guide you with what info we have and hopefully you can reach the solution. We won't be able to tell exact changes needed to support this device because we can't verify it. 

You probably can disable the ecc in the dts file, and see if it works for you.

Rex

Hi rex,

I understand,

However, my question is more general, I don't understand how the RBL treats a 4k page with 224 oob data, since this is the ROM that is burned on the chip.

It is not documented, or I did not find the relevant documentation, so I don't know how to burn my bootloader so that processor can understand the format and be able to copy it to ram and boot.

Please if you have any relevant documentation regarding OMAPL138 RBL it will be very helpful.

Thanks,

Tzvi.

Hi, 

Thank you for the information.

Our device is ONFI 1.0 compliant, 8 bit ECC, page size is 4096(oob 224), subpage 1024( subpage oob 56). 8 bit width, NAND size is 4G

If there is a way to burn the u-boot so that RBL will understand the format please specify how.

In case you think our device is not supported, please recommend a different device that will be supported, so we can boot from it.

Thanks,

Tzvi