Hi Prakash, On Wednesday 14 April 2010 07:03:59 prakash bedge wrote: > Does the latest code supports S29GL512P chip, since I am not seeing any > instance of this chip in 2010.03 uboot code.
Yes. We have told you multiple times, that this chip is supported. You can't find it in the source though, since no code was needed to specifically support this chip. But its working! > >>So you have chipwidth *and* portwidth of 16! This is the most common use > > case. > But when flash is getting detected it shows the chipwidth is 8 and > portwidth is 16. If you see the logs in earlier mail it is like > *found port 2 chip 1 port 16 bits chip 8 bits. *Is it correct or wrong? > > >> Again, please use the mainline CFI driver and give it another try. > > I can not use the current code as we have to use the present code for some > reason. I believe the uboot code 2009.08, I am using, must also support the > S29GL512P chip. Yes. 2009.08 already supported this chip. But you seem to be using a special patch for this driver, which might afflict this. > I replaced the cfi_flash.c with the new cfi_flash.c file from latest uboot > version 2010.03 and done relevant changes. Which changes? No changes to this driver are needed to support this chip!!! > But still I didn't get the > postive result. Is there anything else that I have to check, or by using > only cfi_flash.c and cfi_flash.h from 2010.03 uboot code CFI flash driver > will work? > > I can not use the latest code but I want the CFI support for S29GL512P. > Can you please tell that, what I need to do to make the CFI driver works > for the S29GL512P chip? See above. > >> What kind of "utility"? Don't you use the BDI3000 for FLASH programming? > > We have customized utility to flash the binary. Still not clear to me, what this "utility" is. > Using BDI3000 I tried to > erase the flash but it didn't work. So the BDI FLASH commands ("erase", "prog" etc) don't work? > I followed the CFI erase command > seuence but it fails to erase the flash. > BDI3000>md 0xfe7c0000 > fe7c0000 : 27051956 552d426f 6f742032 3030392e '..VU-Boot 2009. > fe7c0010 : 30382028 41707220 31342032 30313020 08 (Apr 14 2010 > fe7c0020 : 2d203130 3a30313a 32392900 00000000 - 10:01:29)..... > fe7c0030 : 00000000 00000000 00000000 00000000 ................ > fe7c0040 : 00000000 00000000 00000000 00000000 ................ > fe7c0050 : 00000000 00000000 00000000 00000000 ................ > fe7c0060 : 00000000 00000000 00000000 00000000 ................ > fe7c0070 : 00000000 00000000 00000000 00000000 ................ > fe7c0080 : 00000000 00000000 00000000 00000000 ................ > fe7c0090 : 00000000 00000000 00000000 00000000 ................ > fe7c00a0 : 00000000 00000000 00000000 00000000 ................ > fe7c00b0 : 00000000 00000000 00000000 00000000 ................ > fe7c00c0 : 00000000 00000000 00000000 00000000 ................ > fe7c00d0 : 00000000 00000000 00000000 00000000 ................ > fe7c00e0 : 00000000 00000000 00000000 00000000 ................ > fe7c00f0 : 00000000 00000000 00000000 00000000 ................ > *BDI3000>mmb 0xfc000000 0xf0 > BDI3000>mmb 0xfc000aaa 0xaa > BDI3000>mmb 0xfc000555 0x55 > BDI3000>mmb 0xfc000aaa 0x80 > BDI3000>mmb 0xfc000aaa 0xaa > BDI3000>mmb 0xfc000555 0x55 > BDI3000>mmb 0xfe7c0000 0x30 > *BDI3000>mmb 0xfc000000 0xf0 > BDI3000>md 0xfe7c0000 -- *sector data is not erased You are using byte access. You should be using word (16bit) access instead! And the word unlock addresses. Cheers, Stefan -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: off...@denx.de _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot