DM8168 ubi_128_dm816x file system

Balaji,

Balaji Govindarajan said:

I have loaded the file system of ubi_128_DM816X_UD_DVR in udworks board. Whether i can load the same file system or different?

Is this NAND based fllesystem? Do you load this filesystem into NAND flash?

BR
Pavel

Balaji,

Balaji Govindarajan said:

SLN_AVC $mw.b 0x81000000 0xFF 0x300000;tftp 0x81000000 uImage;nand erase 0x00580000 0x440000;nand write 0x81000000 0x00580000 ${filesize}

It seems to me you are flashing the linux kernel (uImage) with these set of commands, not the filesystem, could you comment on that point?

Balaji Govindarajan said:

Attempt to write non page aligned data

See the below e2e threads which has info regarding this error and how to fix:

BR
Pavel

Dear Pavel,

    I have given region for 128k boundary.

      mw.b 0x81000000 0xFF 0x300000;tftp 0x81000000 uImage;nand erase 0x00500000 0x440000;nand write.e 0x81000000 0x00500000 ${filesize}

still i am getting same error message.

NAND write: device 0 offset 0x500000, size 0x26cefc

Attempt to write non page aligned data
2543356 bytes written: ERROR

  Regards

  Balaji

Balaji Govindarajan said:

mw.b 0x81000000 0xFF 0x300000;tftp 0x81000000 uImage;nand erase 0x00500000 0x440000;nand write.e 0x81000000 0x00500000 ${filesize}

It seems to me you are flashing the linux kernel (uImage) with these set of commands, not the filesystem, could you comment on that point???

Balaji,

Balaji Govindarajan said:

i got the following information after enter printenv. Is anything to be done except following these cmds?

I do not see/understand what is the connection between your default boot arguments and flashing linux kernel in NAND? Can you provide more details on that? What makes you think your default boot arguments are the problem to flash your linux kernel in NAND properly?

BR
Pavel

Balaji,

Balaji Govindarajan said:

and custom board used as MT29F8G08ABABAWP(512 MB)

See the below e2e threads which discuss this NAND flash chip usage:

BR
Pavel

Balaji,

Balaji Govindarajan said:

NAND: HW ECC BCH8 Selected
512 MiB

u-boot reports 512MiB NAND size, but you are having 1GB/8Gb NAND.

Balaji Govindarajan said:

bootcmd=bootm 0x81000000

Balaji Govindarajan said:

SLN_AVC $bootm
## Booting kernel from Legacy Image at 81000000 ...

I suspect you are not transferring the uImage from NAND to DDR3/0x81000000 before loading the image from 0x81000000. Refer to the below e2e post for more info:

The bootcmd there is:

TI8168_EVM#setenv bootcmd 'nand read.i 0x81000000 280000 500000; bootm 0x81000000'

After you set and save the bootcmd, you should use TI8168_EVM#boot instead of TI8168_EVM#bootm 0x81000000

BR
Pavel

3716.uImage.rar

Balaji,

When I download and extract uImage.rar, I have as a result empty uImage folder. There is no uImage_DM816X_UD_DVR file inside the uImage folder. Can you try again?

BR
Pavel

4857.uImage.rar

0310.uImage.7zPavel,

         I am not attaching the file.  It is showing error messages if drag and drop uimage on forum. Now, i did archive in 7 zip.

Regards

Balaji

Balaji,

uImage.7z is fine at my side. I am able to flash it to NAND and boot it. See the below flow at try at your side. If fail provide me full console log, do not just state that it is not working.

TI8168_EVM#mw.b 0x81000000 0xFF 0x440000

TI8168_EVM#tftp 0x81000000 uImage

Using DaVinci EMAC device

TFTP from server 172.20.1.195; our IP address is 172.20.2.44

Filename 'uImage'.

Load address: 0x81000000

Loading: #################################################################

#################################################################

#################################################################

#################################################################

#################################################################

#################################################################

#################################################################

##########################################

done

Bytes transferred = 2543356 (26cefc hex)

TI8168_EVM#nand erase 0x00280000 0x00440000

NAND erase: device 0 offset 0x280000, size 0x440000

Erasing at 0x6a0000 -- 100% complete.

OK

TI8168_EVM#nand write 0x81000000 0x00280000 0x270000

NAND write: device 0 offset 0x280000, size 0x270000

2555904 bytes written: OK

TI8168_EVM#setenv bootargs 'console=ttyO2,115200n8 noinitrd ip=off mem=256M rw ubi.mtd=7,2048 rootfstype=ubifs root=ubi0:rootfs init=/init'

TI8168_EVM#nand read.i 0x81000000 0x280000 0x270000

NAND read: device 0 offset 0x280000, size 0x270000

2555904 bytes read: OK

TI8168_EVM#bootm 0x81000000

## Booting kernel from Legacy Image at 81000000 ...

  Image Name:   Linux-2.6.37

  Image Type:   ARM Linux Kernel Image (uncompressed)

  Data Size:    2543292 Bytes = 2.4 MiB

  Load Address: 80008000

  Entry Point:  80008000

  Verifying Checksum ... OK

  Loading Kernel Image ... OK

OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Linux version 2.6.37 (root@avc-sln-desktop) (gcc version 4.5.3 20110311 (prerelease) (GCC) ) #2 Thu Aug 6 15:51:15 IST 2015

Dear Pavel,

         I have followed the same as you have mentioned in previous post. I am not getting anything After this statement "Uncompressing Linux... done, booting the kernel" .  Can you mail me any other issues will cause this problem because we are using single bank DDR3(512MB)?

U-Boot 2010.06 (Aug 06 2015 - 12:53:05)

TI8168-GP rev 2.1

ARM clk: 987MHz

DDR clk: 796MHz

I2C:   ready

DRAM:  512 MiB

NAND:  HW ECC BCH8 Selected

512 MiB

Net:   Detected MACID:90:59:af:58:d1:66

Ethernet PHY: GENERIC @ 0x00

DaVinci EMAC

Hit any key to stop autoboot:  0

SLN_AVC $

SLN_AVC $mw.b 0x81000000 0xFF 0x440000

SLN_AVC $tftp 0x81000000 uImage_DM816X_UD_DVR;

Using DaVinci EMAC device

TFTP from server 192.168.1.15; our IP address is 192.168.1.180

Filename 'uImage_DM816X_UD_DVR'.

Load address: 0x81000000

Loading: T #################################################################

        #################################################################

        #################################################################

        #################################################################

        #################################################################

        #################################################################

        #################################################################

        ##########################################

done

Bytes transferred = 2543356 (26cefc hex)

SLN_AVC $nand erase 0x00280000 0x00440000

NAND erase: device 0 offset 0x280000, size 0x440000

Erasing at 0x6a0000 -- 100% complete.

OK

SLN_AVC $nand write 0x81000000 0x00280000 0x270000

NAND write: device 0 offset 0x280000, size 0x270000

2555904 bytes written: OK

SLN_AVC $setenv bootargs 'console=ttyO2,115200n8 noinitrd ip=off mem=256M rw ubi.mtd=7,2048 rootfstype=ubifs root=ubi0:rootfs init=/init'

SLN_AVC $nand read.i 0x81000000 0x280000 0x270000

NAND read: device 0 offset 0x280000, size 0x270000

2555904 bytes read: OK

SLN_AVC $bootm 0x81000000

## Booting kernel from Legacy Image at 81000000 ...

  Image Name:   Linux-2.6.37

  Image Type:   ARM Linux Kernel Image (uncompressed)

  Data Size:    2543292 Bytes = 2.4 MiB

  Load Address: 80008000

  Entry Point:  80008000

  Verifying Checksum ... OK

  Loading Kernel Image ... OK

OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Regards

Balaji

Balaji,

Balaji Govindarajan said:

Can you mail me any other issues will cause this problem because we are using single bank DDR3(512MB)?

See if you are aligned with the below e2e thread:

Balaji Govindarajan said:

Uncompressing Linux... done, booting the kernel

See if the below pointers will help: