Re: [U-Boot-Users] problem with S29GL128N flash using cfi driver
Mr Dyer,
I have indeed seen the ChangeLogs for u-boot version 1.1.5, stating that support for these chips have been added, but that would assume that the cfi information could be read in the first place. I seem to be unable to put the flash chip into CFI Query mode in the software, although issuing the exact same commands manually with a BDI effortlessly displays the QRY message in the flash, so I don't think the problem lays with the chip not (fully) supporting the CFI.
I have been changing configuration settings, but to no avail. I even tried defining __LITTLE_ENDIAN ;-)
Nicky Geerts
2007/6/26, Andrew Dyer amdyer@gmail.com:
I am using this same FLASH chip (and the 256N) and cfi driver on an ARM (little endian) CPU with no issues.
-- Hardware, n.: The parts of a computer system that can be kicked.
I have been changing configuration settings, but to no avail. I even tried defining __LITTLE_ENDIAN ;-)
You should look at your HW configuration: we've had issues like that during the startup of our board and I hardcoded it 128N detection in U-boot, even submitted a patch for this (which was correctly rejected by Wolfgang).
After another round of checking the design, we've had no issues whatsoever with this Spansion flash chip (or 256N).
Hi,
The board configuration is based on the PPChameleonEVB board. The flash driver included (/board/dave/PPChameleonEVB/flash.[ch]) works on my board, and I can perform CFI commands manually. Is it nevertheless possible that there is an hardware problem preventing software to execute those CFI commands?
Best Regards
Nicky Geerts
2007/6/27, Marc Leeman marc.leeman@gmail.com:
I have been changing configuration settings, but to no avail. I even tried defining __LITTLE_ENDIAN ;-)
You should look at your HW configuration: we've had issues like that during the startup of our board and I hardcoded it 128N detection in U-boot, even submitted a patch for this (which was correctly rejected by Wolfgang).
After another round of checking the design, we've had no issues whatsoever with this Spansion flash chip (or 256N).
-- greetz, marc That's great it's a whole world designed for your rutting instincts. Aeryn - Look at the Princess - A Kiss is Just a Kiss chiana 2.6.18-4-ixp4xx #1 Tue Mar 27 18:01:56 BST 2007 GNU/Linux
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGgha+UQpj09NWLeERAkeiAJ9zIfoOrW5c8DwN1+fuOThoid6bRQCfb42X PxhCTxtgtDrr2VM21vLwjIQ= =WzK0 -----END PGP SIGNATURE-----
update: the cfi driver in the version 1.1.0 displays:
FLASH: flash detect cfi fwc addr fe000000 cmd ff ff 8bit x 8 bit fwc addr fe000055 cmd 98 98 8bit x 8 bit is= cmd 51(Q) addr fe000010 is= 0 51 fwc addr fe000000 cmd ff ffff 16bit x 8 bit fwc addr fe0000aa cmd 98 9898 16bit x 8 bit is= cmd 51(Q) addr fe000020 is= 0051 5151 fwc addr fe000000 cmd ff 00ff 16bit x 16 bit fwc addr fe0000aa cmd 98 0098 16bit x 16 bit is= cmd 51(Q) addr fe000020 is= 0051 0051 is= cmd 52(R) addr fe000022 is= 0052 0052 is= cmd 59(Y) addr fe000024 is= 0059 0059 ushort addr is at fe000050 info->portwidth = 2 addr[0] = 0x0 addr[1] = 0x2 addr[2] = 0x0 addr[3] = 0x0 retval = 0x2 device interface is 2 found port 2 chip 2 port 16 bits chip 16 bits ushort addr is at fe000026 info->portwidth = 2 addr[0] = 0x0 addr[1] = 0x2 addr[2] = 0x0 addr[3] = 0x0 retval = 0x2 fe000020 : 00 51 00 52 00 59 00 02 00 00 00 40 00 00 00 00 .Q.R.Y.....@.... fe000030 : 00 00 00 00 00 00 00 27 00 36 00 00 00 00 00 07 .......'.6...... fe000040 : 00 07 00 0a 00 00 00 03 00 05 00 04 00 00 00 18 ................ fe000050 : 00 02 00 00 00 05 00 00 00 01 00 7f 00 00 00 00 ................ fe000060 : 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ fe000070 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ fe000080 : 00 50 00 52 00 49 00 31 00 33 00 10 00 02 00 01 .P.R.I.1.3...... fe000090 : 00 00 00 08 00 00 00 00 00 02 00 b5 00 c5 00 05 ................ manufacturer is 2 size_ratio 1 port 16 bits chip 16 bits
so that's a success
however, when changing and saving environment variables, I get:
=> saveenv Saving Environment to Flash... Protect off FFFA0000 ... FFFBFFFF Error: start and/or end address not on sector boundary Error: start and/or end address not on sector boundary Error: start and/or end address not on sector boundary
I'll keep searching :-) i'll take a look at the changes in the cfi flash driver, and at my settings, maybe I screwed up something in the sector sizes
Nicky
2007/6/27, nicky geerts nicky.geerts.news@gmail.com:
Hi,
The board configuration is based on the PPChameleonEVB board. The flash driver included (/board/dave/PPChameleonEVB/flash.[ch]) works on my board, and I can perform CFI commands manually. Is it nevertheless possible that there is an hardware problem preventing software to execute those CFI commands?
Best Regards
Nicky Geerts
2007/6/27, Marc Leeman marc.leeman@gmail.com:
I have been changing configuration settings, but to no avail. I even tried defining __LITTLE_ENDIAN ;-)
You should look at your HW configuration: we've had issues like that during the startup of our board and I hardcoded it 128N detection in U-boot, even submitted a patch for this (which was correctly rejected by Wolfgang).
After another round of checking the design, we've had no issues whatsoever with this Spansion flash chip (or 256N).
-- greetz, marc That's great it's a whole world designed for your rutting instincts. Aeryn - Look at the Princess - A Kiss is Just a Kiss chiana 2.6.18-4-ixp4xx #1 Tue Mar 27 18:01:56 BST 2007 GNU/Linux
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGgha+UQpj09NWLeERAkeiAJ9zIfoOrW5c8DwN1+fuOThoid6bRQCfb42X PxhCTxtgtDrr2VM21vLwjIQ= =WzK0 -----END PGP SIGNATURE-----
participants (2)
-
Marc Leeman -
nicky geerts