This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Question about nand change 256MB to 512MB

Hi,

I'm facing a problem.
I used am335x-evm and I used ti-processor-sdk-linux-am335x-evm-02.00.02.11.
I mounted a 256MByte NAND flash (MT29F2G08AB)
I can boot up the SPL, u-boot then kernel successfully from NAND device.

But when I changed the NAND to 512MByte (JS27HU4G08SDN(512MB))


1. nand boot (SPL, uboot, zImage, ...) => DIP SW 1:off  2:on 3:off 4:off 5:on

ROM boot loader doesn't work anyting...

I am getting continuous "CCCCCCC" characters from UART...


2. SD boot (SPL, uboot) + nand boot(zImage, ...)  => DIP SW 1:on 2:off 3:off 4:off 5:off

U-Boot# CCCCCCCC
U-Boot SPL 2014.07-svn354 (Sep 05 2016 - 23:12:51)
read_eeprom
read_eeprom
read_eeprom
read_eeprom
reading args
spl_load_image_fat_os: error reading image args, err - -1
reading u-boot.img
reading u-boot.img

U-Boot 2014.07-svn354 (Sep 05 2016 - 23:12:51)

I2C:   ready
DRAM:  1 GiB
NAND:  512 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
reading uboot.env

** Unable to read "uboot.env" from mmc0:1 **
Using default environment

read_eeprom
Net:   <ethaddr> not set. Validating first E-fuse MAC
read_eeprom
cpsw, usb_ether
Hit any key to stop autoboot:  0
Booting from nand ...

NAND read: device 0 offset 0x80000, size 0x40000
 262144 bytes read: OK

NAND read: device 0 offset 0x200000, size 0x800000
 8388608 bytes read: OK
Kernel image @ 0x82000000 [ 0x000000 - 0x2df820 ]
## Flattened Device Tree blob at 88000000
   Booting using the fdt blob at 0x88000000
   Loading Device Tree to 8fff3000, end 8ffff265 ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0

...................................................................................................

[    1.245670] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xdc
[    1.252262] nand: Hynix H27U4G8F2EKA-BM  <=(not change kernel)
[    1.256169] nand: 512 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
[    1.263916] nand: using OMAP_ECC_BCH8_CODE_HW ECC scheme
[    1.269382] 14 ofpart partitions found on MTD device 8000000.nand

...................................................................................................

nand operation is no problem...

The key difference between these 2 NANDs are:

             Size              Device ID             Page Size                        ECC bit

2G08: 2Gb(256MB)       0xDA             2112 Bytes                           4-bit
4G08: 4Gb(512MB)       0xDC             4352(2176 + 2176) Bytes    4-bit


I do not see why this 512MByte version of NAND should not be supported by the ROM code.
how to use to 512MByte?
thank you your reply.