Try sending a reset command before using it. Micron NAND FLASH comes up
in low power state, and you won't be able to access the FLASH in that
state. This was the solution used by one of our engineers to resolve
Micron NAND FLASH issues a few weeks ago.
Regards,
Steve
On Wed, 2009-02-11 at 16:36 +0800, zuowenping wrote:
> 1:first i use the nand flash type is MT29F8G08MAAWC,if i cann't modify
> the address,the Manufacture and device id is always 0,and the
> hardware engineer told me to modify it,then the id can be identify
> ok.when i change nand flash type to HY27UG088 ,the same result it is!
> 2:the micron flash page size is 2048+64,and the HY27UG088 is also
> size.
> 3:we can do uart boot and i have test it ok,but i have xds560
> emluator,it can translate data easy!
> 4:if i use the MT29F8G08M,i have to add {0xD3, 128, 2048
> +64,23, 5}, /* Micron MT29F8G08AAA */ //add by duke 2009.2.9
> item in the const NAND_DEVICE_INFO gNandDevInfo[]
> 5:I am surprising too,but the hardware engineer ask me to do it.
>
>
> 2009-02-11
>
> ______________________________________________________________________
> zuowenping
>
> ______________________________________________________________________
> 发件人： jitendraj...@emerson.com
> 发送时间： 2009-02-11 16:12:50
> 收件人： zuowenp...@dali-tech.com;
> davinci-linux-open-source@linux.davincidsp.com
> 抄送：
> 主题： RE: nand_programmer check all nand flash blocks error
>
> Hi Duke Zuo,
>
> We are also struggling with similar issue since few weeks. We have
> done some investigation that might help you.
>
>
>
> 1. What NAND chip you are using?
>
> 2. What is the page size? As per TI, RBL does not support NAND having
> 4096 page size
>
> 3. Are you able to do UART boot?
>
> 4. Have you modified anything in “NAND_Programmer.pjt” source code? If
> yes, what are those?
>
> 5. It is surprising to see your changes related to ALE/CMD address, we
> are not required to do so.
>
>
>
> Regards,
>
> Jitendra
>
>
>
>
>
> ________________________________________
>
> From: davinci-linux-open-source-boun...@linux.davincidsp.com
> [mailto:davinci-linux-open-source-boun...@linux.davincidsp.com] On
> Behalf Of zuowenping
>
> Sent: Wednesday, February 11, 2009 12:55 PM
>
> To: davinci-linux-open-source
>
> Subject: nand_programmer check all nand flash blocks error
>
>
>
> dear all:
>
> I use a new nand flash for dm355 in my new borad,first i used
> Micron 1G nand flash, the address have been modify:
>
> #define NAND_ALE_ADDR ((volatile Uint8*)0x02000004) //from
> 0x02000008
>
> #define NAND_CMD_ADDR ((volatile Uint8*)0x02000008) //from
> 0x02000010
>
> if i use the old address, the Manufacture id and device id is
> always 0 when read it.and the hardware told me to modify the address!
> but when I run the programmer by jtag,the result is:
>
> Started Nand programming
>
> Manufacture ID 2c
>
> device ID d3
>
> find the NAND device in the table!
>
> NANDInit() Successful
>
> Enter the UBL File Name
>
> D:\dvsdk_1_30_00_40\dvsdk_1_30_00_40\PSP_01_20_00_014\bin\dm355
> \ublDM355-nand.bin
>
> Block number 0 is a BAD BLOCKBlock 0 is a bad block
>
> Block number 1 is a BAD BLOCKBlock 1 is a bad block
>
> Block number 2 is a BAD BLOCKBlock 2 is a bad block
>
> Block number 3 is a BAD BLOCKBlock 3 is a bad block
>
> Block number 4 is a BAD BLOCKBlock 4 is a bad block
>
> Block number 5 is a BAD BLOCKBlock 5 is a bad block
>
> Block number 6 is a BAD BLOCKBlock 6 is a bad block
>
> Block number 7 is a BAD BLOCKBlock 7 is a bad block
>
> Block number 8 is a BAD BLOCKBlock 8 is a bad block
>
> Block number 9 is a BAD BLOCKBlock 9 is a bad block
>
> Block number 10 is a BAD BLOCKBlock 10 is a bad block
>
> Block number 11 is a BAD BLOCKBlock 11 is a bad block
>
> Block number 12 is a BAD BLOCKBlock 12 is a bad block
>
> Block number 13 is a BAD BLOCKBlock 13 is a bad block
>
> Block number 14 is a BAD BLOCKBlock 14 is a bad block
>
> Block number 15 is a BAD BLOCKBlock 15 is a bad block
>
> Block number 16 is a BAD BLOCKBlock 16 is a bad block
>
> Block number 17 is a BAD BLOCKBlock 17 is a bad block
>
> Block number 18 is a BAD BLOCKBlock 18 is a bad block
>
> Block number 19 is a BAD BLOCKBlock 19 is a bad block
>
> Block number 20 is a BAD BLOCKBlock 20 is a bad block
>
> .................................................................
>
> It seemd all block is bad!!
>
> When i skip the block checking(just return E_PASS
> in NANDCheckBadBlock() function ),it can run ok,the ubl and uboot
> seems burning ok,but when i reboot the board,it cann't boot!!
>
> I have contact to the supporter by ti,they told me the RBL(rom
> boot loader) can't support 128 pages of a block,so i changed a nand
> flash type HY27UG088G whick 64 pages of a block,it
> seem the same result!
>
> any one can help me?thanks a lot!!
>
> 2009-02-11
>
> ________________________________________
>
> duke zuo
>
> da-li tech in hangzhou of china
>
>
> _______________________________________________
> Davinci-linux-open-source mailing list
> Davinci-linux-open-source@linux.davincidsp.com
> http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
_______________________________________________
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
