[U-Boot-Users] 2Gbits NAND flash

Hello,
I am using the latest u-boot (1.1.4) code and it doesn't have 2Gbits (256 MBytes) NAND flash support.
I appreciate if some one can point me in the right direction to use the 2Gbits NAND flash from U-boot. (Chip: Micron MT29F2Gxxxxx) I want to boot the linux kernel from the NAND flash.
Thanks, Hebbar.

Hello,
I am using the latest u-boot (1.1.4) code and it doesn't have 2Gbits (256 MBytes) NAND flash support.
I appreciate if some one can point me in the right direction to use the 2Gbits NAND flash from U-boot. (Chip: Micron MT29F2Gxxxxx)
Maybe you should check with Micron if this is a viable memory chip. MT29F2G16AABWP is dead according to my sources and there are no second sources available.
I want to boot the linux kernel from the NAND flash.
Thanks, Hebbar.
Best Regards Ulf Samuelsson

Ulf Samuelsson stated on 10/6/2006 1:05 AM:
right direction to use the 2Gbits NAND flash from U-boot. (Chip: Micron MT29F2Gxxxxx)
try this also http://www.samsung.com/Products/Semiconductor/NANDFlash/SLC_LargeBlock/1Gbit...
I want to boot the linux kernel from the NAND flash.
u may need x-loader... Regards, Nishanth Menon

Hi Hebbar,
On Friday 06 October 2006 06:36, Srinivasa Hebbar wrote:
I am using the latest u-boot (1.1.4) code and it doesn't have 2Gbits (256 MBytes) NAND flash support.
This statement is not correct:
U-Boot 1.1.4-g64cd52ef-dirty (Oct 1 2006 - 12:05:20)
CPU: AMCC PowerPC 440GX Rev. F at 533.328 MHz (PLB=133, OPB=66, EBC=33 MHz) I2C boot EEPROM enabled Bootstrap Option F - Boot ROM Location I2C (Addr 0x54) Internal PCI arbiter enabled 32 kB I-Cache 32 kB D-Cache Board: ALPR I2C: ready DRAM: 256 MB FLASH: 2 MB NAND: 2048 MiB
<snip>
=> nand info
Device 0: NAND 1GiB 3,3V 8-bit, sector size 128 KiB Device 2: NAND 1GiB 3,3V 8-bit, sector size 128 KiB
I appreciate if some one can point me in the right direction to use the 2Gbits NAND flash from U-boot. (Chip: Micron MT29F2Gxxxxx) I want to boot the linux kernel from the NAND flash.
Please make sure that you use the "new" U-Boot NAND driver (driver/nand/*) and _not_ the "old" legacy driver. This could be your problem.
Best regards, Stefan
participants (4)
-
Nishanth Menon
-
Srinivasa Hebbar
-
Stefan Roese
-
Ulf Samuelsson