Nand access issue in T1040

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Nand access issue in T1040

1,468 Views
suchitasharma
Contributor I

Hi

     I am having a nand device (with the below mentioned details) for T1040 processor.

 nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xd3
 nand: Micron MT29F8G08ABACAWP

I came to know that i was not able to write properly on to the NAND after i faced the the following  ubi attach issue

root@t1040d4rdb:/tmp# ubiattach /dev/ubi_ctrl -m 4
ubi0: attaching mtd4
ubi0 warning: scan_peb: valid VID header but corrupted EC header at PEB 1
ubi0: scanning is finished
ubi0 error: vtbl_check: bad CRC at record 2: 0xe3cfe020, not 0xf11ec36b
Volume table record 2 dump:
reserved_pebs 0
alignment 0
data_pad 0
vol_type 0
upd_marker 0
name_len 0
name NULL
ubi0 error: vtbl_check: bad CRC at record 1: 0x4321950, not 0xf11ec36b
Volume table record 1 dump:
reserved_pebs 0
alignment 0
data_pad 0
vol_type 0
upd_marker 0
name_len 0
name NULL
ubi0 error: process_lvol: both volume tables are corrupted
ubi0 error: ubi_attach_mtd_dev: failed to attach mtd4, error -22
ubiattach: error!: cannot attach mtd4
error 22 (Invalid argument)

then I checked the nandtest utility and it shows as follows

nand test shows the following

root@t1040d4rdb:~# nandtest -p 1 /dev/mtd3
ECC corrections: 0
ECC failures : 0
Bad blocks : 0
BBT blocks : 0
00000000: reading...fsl_ifc_run_command 338
00000000: checking...
compare failed. seed 1396897799
Byte 0x4 is fe should be ee
Byte 0x6 is 7a should be 5a
Byte 0x8 is f9 should be e9
ECC corrections: 0
ECC failures : 0
Bad blocks : 0
BBT blocks : 0
00000000: reading...fsl_ifc_run_command 338
00000000: checking...
compare failed. seed 1396897799
Byte 0x4 is fe should be ee
Byte 0x6 is 7a should be 5a
Byte 0x8 is f9 should be e9
Byte 0x15 is 6c should be 64
Byte 0x16 is cb should be c3
Byte 0x18 is 73 should be 53
Byte 0x23 is f5 should be e5
Byte 0x28 is d9 should be d1
Byte 0x29 is ce should be c6
Byte 0x42 is 36 should be 26
Byte 0x56 is fe should be ee
Byte 0x57 is f8 should be e8
Byte 0x59 is 1f should be 0d
Byte 0x5c is 99 should be 89
Byte 0x61 is 5e should be 56
Byte 0x62 is ff should be f7

Therefore I suspected there was 1 bit ECC error so i tried changing the nand ecc mode nand timings. Even after doing so the issue is still there.

 

My NAND configurations:

 ECC mode  =  8 (chnaged ecc mode from 4 to 8 in the CSOR register) 

 

IFC NAND timings  ( all timings are in decimal)

FTIM0

TCCST - 2 

TWP  - 5

TWCHT - 2

TWH - 3

FTIM1

TADLE - 20

TWBE - 31

TRR - 7

TRP - 5

FTIM2

TRAD - 7

TREH - 3

TWHRE - 18

FTIM3 - 0 

 

Please Suggest a solution.......

 

 

 

0 Kudos
Reply
5 Replies

1,457 Views
yipingwang
NXP TechSupport
NXP TechSupport

Please refer to "https://community.nxp.com/t5/Layerscape-Knowledge-Base/IFC-Controller-Configuration-on-QorIQ-Custom-... to calculate IFC  flash Timing configuration parameters. 

0 Kudos
Reply

1,450 Views
suchitasharma
Contributor I

Hi,

      The above given link is invalid. Pls send correct link.

 

Thanks & Regards,

 

0 Kudos
Reply

1,441 Views
yipingwang
NXP TechSupport
NXP TechSupport
0 Kudos
Reply

1,431 Views
suchitasharma
Contributor I

Hi,

     I calculated the Ifc nand timings with the help of Flash_memory_list_timings excel sheet  which you shared recently but after doing so NAND itself is not getting detected.Please suggest

NAND Description :

 nand: Micron MT29F8G08ABACAWP (3.3V)

0 Kudos
Reply

1,432 Views
suchitasharma
Contributor I

 

Spoiler

Hi,

     I calculated the Ifc nand timings with the help of Flash_memory_list_timings excel sheet  which you shared recently but after doing so NAND itself is not getting detected.Please suggest

NAND Description :

 nand: Micron MT29F8G08ABACAWP (3.3V)

Spoiler
 

 

 

0 Kudos
Reply