AM37xx ti-sdk-beagleboard-06.00.00.00 Nand Flashing Issue

Hi Dibin,

What procedure are you using to do this?

Hi Biser,

Thankyou verymuch for your response.

Below are the steps i Followed.

1. mkfs.ubifs -r /home/salher/ti-sdk-beagleboard-06.00.00.00/filesystem/TI -m 2048 -e 131072 -c 4095 -F -o ubifs.img

2. ubinize -o ubi.img -O 2048 -m 2048 -p 128KiB -s 512 ubinize.cfg

3. where ubinize.cfg contains:

$ cat ubinize.cfg
[ubifs]
mode=ubi
image=ubifs.img
vol_id=0
vol_size=450MiB
vol_type=dynamic
vol_name=rootfs
vol_alignment=1
vol_flags=autoresize

On Board.

1. ubiformat -y /dev/mtd4 -s 512 -O 2048

2. ubiformat -y /dev/mtd4 -f ubi.img -s 512 -O 2048

3. ubiattach /dev/ubi_ctrl -m 4 -O 2048

Regards,

Dibin

Hi Dibin,

Try to follow this guide where I have explained all the calculations: http://e2e.ti.com/support/arm/sitara_arm/f/791/p/268305/941327.aspx#941327

Best regards,
Miroslav

Hi Miroslave,

Thankyou verymuch for link. 

I am little confused about sub-page support .

In This link : http://processors.wiki.ti.com/index.php/UBIFS_Support#Creating_UBIFS_file_system

It is specified that sub page is not supported .

And mtdinfo in ez-sdk 06.00.00 shows 

root@beagleboard:~# mtdinfo /dev/mtd4
mtd4
Name: File System
Type: nand
Eraseblock size: 131072 bytes, 128.0 KiB
Amount of eraseblocks: 3968 (520093696 bytes, 496.0 MiB)
Minimum input/output unit size: 2048 bytes
Sub-page size: 512 bytes
OOB size: 64 bytes
Character device major/minor: 90:8
Bad blocks are allowed: true
Device is writable: true

Does it support sub page? ez-sdk 06.00.00 

Regards,

Dibin

Hi Misoslav,

Can you please confirm the subpage support of sdk 06.00.00 nand driver.

Regards,

Dibin

Hi Dibin,

This particular section of the wiki page hasn't been updated for a long time, so mu suggestion is to direct your question to the U-Boot mailing list: http://lists.denx.de/mailman/listinfo/u-boot

Best regards,
Miroslav

Hi Miroslav,

   The filesystem is written from kernel , how is it related to u-boot.

    http://e2e.ti.com/support/arm/sitara_arm/f/791/t/230032.aspx  As per this link

   rather than creating ubi.img image I have extracted the rootfs directly to mtd4 .

  but still getting below error

 List of all partitions:
[    4.320922] 1f00             512 mtdblock0  (driver?)
[    4.326263] 1f01            1920 mtdblock1  (driver?)
[    4.331604] 1f02             128 mtdblock2  (driver?)
[    4.336883] 1f03            4096 mtdblock3  (driver?)
[    4.342193] 1f04          507904 mtdblock4  (driver?)
[    4.347503] No filesystem could mount root, tried:  ubifs
[    4.353179] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

I have again rooted with memory card to check the mtd4 , and I can see all the rootfs in mtd4.

So I belive the nandwrite to mt4 is working fine.

The problem is at start-up there is something going wrong with mounting mtd4 .

Can you give me any input regarding this.

Regards,

Dibin

Hi Miroslav,

I have made further improvements . 

With the change in boot parameter I was able to boot from nand.

Issue is the booting is not consistent  it fails to load the filesystem randomly.

Below are the error messages when booting fails

[ 1.368408] uncorrectable error :
[ 1.385009] uncorrectable error :
[ 1.400634] uncorrectable error :
[ 1.431915] uncorrectable error :
[ 1.446502] uncorrectable error :
[ 1.463134] uncorrectable error :
[ 1.470794] UBI warning: process_eb: valid VID header but corrupted EC header at PEB 490
[ 1.501342] UBI warning: process_eb: valid VID header but corrupted EC header at PEB 599

If you have any input to debug this issue please share.

Regards,

Dibin