Hi Steven, Yes, your understanding is quite correct. By means of nand layout, I guess you are referring figure: 11-4 and 11-5 of sprufb3.pdf. I have gone through PDF and NAND programmer code. Code is writing data and syndromes as explained.
As per code, irrespective of NAND is of 512, 2048 or 4196 page size, data is stored: 1. 512 bytes of data 2. 6 bytes - 0xFF 3. 10 bytes - syndrome This matches with what sprufb3.pdf says. I guess RBL should be able to read properly. As you suggested, I'll dump data being written and read using NAND programmer and using u-boot. (PS: as NAND is auto incrementing address, I am not able to print the address but able to read the data and data being written in sequence.) Btw, do you suspect there could be timing issue? As I have ported NAND programmer code, I really don't doubt the functionality. Code is developed and working successfully with TI's CCS compiler but as I am now integrating with the U-Boot I am using GCC complier. I have found lot of for loops being used to provide some delay between operations. Also, there is a function "waitloop" in NAND programmer code which is also used in code for same purpose. Regards, Jitendra -----Original Message----- From: Gorwood, Steve [mailto:sgorw...@ti.com] Sent: Monday, January 26, 2009 9:30 PM To: Jain, Jitendra [PROTOOL/RTC/IN]; jon.po...@racelogic.co.uk Cc: davinci-linux-open-source@linux.davincidsp.com Subject: RE: dm355:ecc query OK. To summarize my understanding: a) If you program NAND with NAND programmer hacked to identify 4K device, but only write to 1st 2K of each page, then boot proceeds without problems. b) If you program NAND with u-boot hacked to use NAND programmer driver code, then boot fails ECC read. Is this correct? I suspect that the u-boot is writing the ECC data into a different address than the RBL is reading it from. The NAND layout is documented in the ARM reference guide. I would program the NAND using the NAND programmer, then read back the data using the read routine used by the NAND programmer (paying attention to the address and contents used in the spare byte area). I would then program the NAND using u-boot, then read it back using the NAND programmer read routine and compare the address and contents of the spare byte area. I suspect that you will find that the contents are different. Regards, Steven Gorwood -----Original Message----- From: jitendraj...@emerson.com [mailto:jitendraj...@emerson.com] Sent: Saturday, January 24, 2009 5:04 AM To: Gorwood, Steve; jon.po...@racelogic.co.uk Cc: davinci-linux-open-source@linux.davincidsp.com Subject: RE: dm355:ecc query Hi, Let me rephrase the query: Background: 1. We are using a custom board using DM355 and NAND - MT29F16G08DAA having 4096 page size 2. SD card is carrying binaries for: a. UBL_SD - RBL will fetch from SD Card and load UBOOT_SD in SD BOOT Mode b. UBOOT _SD - UBL_SD will load in SD BOOT Mode, will support burning UBL_NAND and UBOOT_NAND in NAND c. UBL_NAND - in NAND Mode, will load from NAND by RBL d. UBOOT_NAND - in NAND Mode, will load from NAND by UBL_NAND 3. We are burning UBL_NAND, UBOOT_NAND in NAND from UBOOT_SD's command prompt Case-1 (Using JTAG programmer and NAND_programmer.pjt): NAND_Programmer.pjt is hacked to support NAND with 4K page size. Due to modification, NAND_programmer.pjt detects NAND with page size of 4K but treats it same way as if NAND is having Page size equal to 2K. Result: we are able to burn UBL_NAND and UBOOT_NAND. In NAND boot mode, UBL_NAND and UBOOT_NAND works as expected. Case-2 (Using SD boot and UBL_SD/UBOOT_SD): UBOOT_SD is having support of writing UBL_NAND and UBOOT_NAND from SD to NAND. We have ported NAND driver part of NAND_programmer.pjt to burn UBL_NAND and UBOOT_NAND. Result: we are unable to burn UBL_NAND and UBOOT_NAND. Using ported NAND driver of NAND_programmer.pjt, we are failing at very first step of checking bad block. ECC_STATE of NAND FSR register is found 1 for entire NAND which means errors cannot be corrected. However, blocks are not bad. Hope above clarifies the issue. Any help/suggestion is appreciated. Regards, Jitendra ________________________________________ From: Gorwood, Steve [mailto:sgorw...@ti.com] Sent: Friday, January 23, 2009 9:04 PM To: Jon Povey; Jain, Jitendra [PROTOOL/RTC/IN] Cc: davinci-linux-open-source@linux.davincidsp.com Subject: RE: dm355:ecc query The existing DM355 does not support NAND devices with 4K page sizes. As an unrecognized device, the identification should default to assuming a 2K page size with 64 pages/block. I would assume that the UBL was not read correctly due to the page layout. I am surprised, though, that this did not result in a fall back to an SD boot Regards, Steven Gorwood ________________________________________ From: davinci-linux-open-source-boun...@linux.davincidsp.com [mailto:davinci-linux-open-source-boun...@linux.davincidsp.com] On Behalf Of Jon Povey Sent: Friday, January 23, 2009 4:19 AM To: jitendraj...@emerson.com Cc: davinci-linux-open-source@linux.davincidsp.com Subject: RE: dm355:ecc query This may be an issue with the RBL not detecting your NAND chip, if I remember correctly DM355 does not support 4KB page devices at the moment, although it is not very clear and may support some devices, or I have a vague memory that for some 4KB devices it reads them as if they were 2KB page devices, so you can put "hand-crafted" data in the early blocks enough to get UBL loading. I also seem to remember some talk of a new revision of DM355 that could support more recent NAND devices. Maybe someone from TI could comment. I have not been looking into this recently and my memory is flaky. -- Jon Povey, Design Engineer jon.po...@racelogic.co.uk | +44(0)1280 825983 ________________________________________ From: jitendraj...@emerson.com [mailto:jitendraj...@emerson.com] Sent: 23 January 2009 09:12 To: Jon Povey; davinci-linux-open-source@linux.davincidsp.com; davi...@pacbell.net Subject: RE: dm355:ecc query Hi Jon, Actually we are facing a strange problem. I am using MT29F16G08DAA nand chip with page size: 4096 I have written UBL descriptor in block 1, page 0 and UBL in block 2, page 0. When I change boot mode to NAND, I do not see any message on console and as board is not falling back to SD mode, I suspect RBL found valid magic number. But I don't understand why it can't load UBL. On my head I suspect two possibilities a) ECC errors while copying UBL from NAND b) RBL is unable to find UBL (maybe information given in UBL descriptor is taken incorrectly by RBL) I do not have JTAG with me. Regards, Jitendra Racelogic is a limited company registered in England. Registered number 2743719 . Registered Office Unit 10, Swan Business Centre, Osier Way, Buckingham, Bucks, MK18 1TB . The information contained in this electronic mail transmission is intended by Racelogic Ltd for the use of the named individual or entity to which it is directed and may contain information that is confidential or privileged. If you have received this electronic mail transmission in error, please delete it from your system without copying or forwarding it, and notify the sender of the error by reply email so that the sender's address records can be corrected. The views expressed by the sender of this communication do not necessarily represent those of Racelogic Ltd. Please note that Racelogic reserves the right to monitor e-mail communications passing through its network _______________________________________________ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
