Hi,
We designed a board based on omap3530 with 1GB micron NAND Flash (MT29F8G08ABABA). We are able to download and boot x-loader and U-boot from LPDDR (256MB) by using code composer studio in linux environment. Then we initialized NAND settings by refering MT29F8G08ABABA datasheet and GPMC configuration OMAP3530 Technical reference manual. By using NAND SW ECC we downloaded U-boot into 1GB nand with the following partitions.
device nand0 <nand>, # parts = 5
#: name size offset mask_flags
0: x-loader 0x00080000 0x00000000 0
1: u-boot 0x00400000 0x00080000 0
2: u-boot-env 0x00080000 0x00480000 0
3: kernel 0x00400000 0x00500000 0
4: fs 0x0f700000 0x00900000 0
active partition: nand0,0 - (x-loader) 0x00080000 @ 0x00000000
Here we downloaded x-loader from JTAG by using CCSV5, and from there U-boot from nand flash. Now we are trying to write and boot x-loader from NAND Flash. Its not worked. So, we tried the same x-laoder in Beagle board (by changing NAND setting to beagle board). It running succefully.
From the OMAP3530 Technical Reference (spruf98t) Manual Pg no 3404 - 3406 and tables 25-32 , 25-33. We came to know that ROM code looking for the known device ID as from the list specified on table 25-32. But, NAND flash which we are using not listed there. So, from table 25-33 we verified the ID, on our NAND Flash.
From BYTE3
In OMAP3530 manual --> bit4 - 1, bit 5 - 0 (128)
NAND Flash data sheet --> bit4 - 0, bit 5 - 1 (128)
we are suspecting this might be a reasion for boot failure.
How can we resolve this issue?
How can we change device ID to boot x-loader from NAND flash?
If any information missed regarding this issue please reply.
Thanks Regards
Eswar
