• State TI Thinks Resolved
  • Locked Locked
  • Replies 11 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 1924 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Error while flashing pre built images on TI8168 EVM

Tushar Nautiyal
Prodigy 160 points 
Been trying to flash the pre built images to 8168 EVM. But,
getting the following error(Boot Logs):

m25p80 spi1.0: found m25p05-nonjedec, expected m25p80
m25p80 spi1.0: m25p05-nonjedec (64 Kbytes)
mtd: partition size too small (2)
Creating 4 MTD partitions on "spi_flash":
0x000000000000-0x000000040000 : "U-Boot"
mtd: partition "U-Boot" extends beyond the end of device "spi_flash" --
size truncated to 0x10000
0x000000010000-0x000000012000 : "U-Boot Env"
mtd: partition "U-Boot Env" is out of reach -- disabled
0x000000000000-0x000000280000 : "Kernel"
mtd: partition "Kernel" extends beyond the end of device "spi_flash" --
size truncated to 0x10000
0x000000010000-0x000000010000 : "File System"
mtd: partition "File System" is out of reach -- disabled
omap2-nand driver initializing
UBI: attaching mtd0 to ubi0
UBI error: io_init: bad write buffer size 0 for 1 min. I/O unit
UBI error: ubi_init: cannot attach mtd0


IP-Config: Got DHCP answer from 192.168.1.1, my address is 192.168.1.72
IP-Config: Complete:
     device=eth0, addr=192.168.1.72, mask=255.255.255.0, gw=192.168.1.254,
     host=192.168.1.72, domain=yourdomainname.com, nis-domain=(none),
     bootserver=192.168.1.1, rootserver=192.168.1.1, rootpath=
VFS: Unable to mount root fs via NFS, trying floppy.
List of all partitions:
1f00              64 mtdblock0  (driver?)
1f02              64 mtdblock2  (driver?)
No filesystem could mount root, tried:  ubifs
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(2,0)
Backtrace:
[<c004efac>] (dump_backtrace+0x0/0x110) from [<c03a01dc>]
(dump_stack+0x18/0x1c)
 r6:00008000 r5:ce7f0006 r4:c052ce98 r3:60000013
[<c03a01c4>] (dump_stack+0x0/0x1c) from [<c03a023c>] (panic+0x5c/0x178)
[<c03a01e0>] (panic+0x0/0x178) from [<c0009184>]
(mount_block_root+0x1c4/0x204)
 r3:00000000 r2:00000020 r1:ce42bf58 r0:c0460985
 r7:c04609e9
[<c0008fc0>] (mount_block_root+0x0/0x204) from [<c0009358>]
(mount_root+0xac/0xcc)
[<c00092ac>] (mount_root+0x0/0xcc) from [<c00094e4>]
(prepare_namespace+0x16c/0x1cc)
 r4:c052c2e4
[<c0009378>] (prepare_namespace+0x0/0x1cc) from [<c0008d70>]
(kernel_init+0x114/0x154)
 r5:c002e9ec r4:c002e9ec
[<c0008c5c>] (kernel_init+0x0/0x154) from [<c0077780>] (do_exit+0x0/0x5d0)
 r5:c0008c5c r4:00000000



It seems like the mtd partitions are not getting created.

Also please note that booting via nfs works.
  • 0
    TI__Guru**** 170625 points

    Hi Tushar,

    Which EZSDK version you are using? Which pre-built images you are flashing? You flash SPI or NAND?

    Regards,
    Pavel

  • 0 in reply to Pavel Botev
    Prodigy 160 points
    Hi Pavel,

    Actually we are using DVRRDK_04.01.00.02. The pre-built images are from: pre_built_binary/ti816x_evm.

    And, we are using TI8168 EVM and not the DVR.

    We are trying to flash NAND.

    Thanks
    Tushar
  • 0 in reply to Tushar Nautiyal
    TI__Guru**** 170625 points
    Tushar,

    Can you provide me the exact name of the pre-built image you are using? For example, in EZSDK this is u-boot.noxip.bin

    You are booting from NFS, but from where you flash the NAND (NFS, SD card, CCS)? Can you provide me the steps you are using to flash the NAND?

    Regards,
    Pavel
  • 0 in reply to Pavel Botev
    Prodigy 160 points

    Hi Pavel,

    The name of the images are:


    1) uboot_NAND_DM816X_TI_EVM

    2) uImage_DM816X_TI_EVM

    3) ubi_128_DM816X_TI_EVM.img


    Actually booting from NFS works.


    In this case we want to flash the images to NAND and boot from there.


    Steps followed are:

    For flashing uBoot to NAND on TI816X EVM
    UBOOT# mw.b 0x81000000 0xFF 0x260000;tftp 0x81000000
    uboot_NAND_DM816X_TI_EVM;nandecc hw 2;nand erase 0x0 0x260000;nand write.i
    0x81000000 0x0 0x260000
     
    reset
     
    UBOOT # mw.b 0x81000000 0xFF 0x300000;tftp 0x81000000
    uImage_DM816X_TI_EVM;nand erase 0x00580000 0x440000;nand write.i 0x81000000
    0x00580000 0x300000
     
    UBOOT# nand scrub 0x009C0000 0xC820000
     
    UBOOT# mw.b 0x81000000 0xFF 0x4C00000;tftp 0x81000000
    ubi_128_DM816X_TI_EVM.img;nand erase 0x009C0000 0xC820000;nand write
    0x81000000 0x009C0000 0x4C00000
     
    UBOOT# dhcp
    UBOOT# setenv logoreadaddr '0x81000000'
    UBOOT# saveenv
     
    UBOOT# setenv bootcmd 'nand read ${logoreadaddr} 0x280000 0x300000; logo on
    ${logoreadaddr} 0xA0000000 0xBEA00000 40 60; nand read 0x81000000 0x00580000
    0x300000; bootm 0x81000000'
     
    UBOOT# setenv bootargs 'console=ttyO2,115200n8 noinitrd ip=dhcp mem=256M
    rootwait=1 rw ubi.mtd=8,2048 rootfstype=ubifs root=ubi0:rootfs init=/init
    vram=20M notifyk.vpssm3_sva=0xBEE00000 stdin=serial ddr_mem=1024M'
     
    UBOOT# saveenv
    UBOOT# boot


    Thanks

    Tushar

  • 0 in reply to Tushar Nautiyal
    TI__Guru**** 170625 points
    Hi Tushar,

    Please refer to the below e2e threads which discuss the same issue.

    e2e.ti.com/.../231497
    e2e.ti.com/.../258708
    e2e.ti.com/.../268190

    And I will also recommend you to start with writing/flashing u-boot first. Flash u-boot, change switch settings for NAND, reboot and verify that u-boot is fine. Then proceed with bootargs, kernel and rootfs.

    Regards,
    Pavel
  • 0 in reply to Pavel Botev
    Prodigy 160 points
    Hi Pavel,

    We went through other posts and interestingly

    using:

    1) TI8168 EVM SDK u-boot
    2) TI8168 EVM RDK uImage and ubi fs

    we are able to boot up

    This points to the RDK u-boot image being corrupted.

    Can you please provide some pointers how to make RDK u-boot work.

    Thanks
    Tushar
  • 0 in reply to Tushar Nautiyal
    TI__Guru**** 170625 points
    Tushar,

    Can you try to build your own u-boot from the RDK u-boot code base (not using the pre-built), will you be able to boot then?

    BR
    Pavel
  • 0 in reply to Pavel Botev
    Prodigy 160 points

    Hi Pavel,

    Tried that, still does not work. My guess is there is something in the u-boot source code that might be causing this. Any pointers on where to look?

    Thanks

    Tushar

  • 0 in reply to Tushar Nautiyal
    TI__Guru**** 170625 points
    Tushar,

    "1) TI8168 EVM SDK u-boot" - you mean the pre-built u-boot here right?
    ti-ezsdk_dm816x-evm_5_05_02_00/board-support/prebuilt-images/u-boot.noxip.bin

    Can you provide me full console log when you build the RDK u-boot? You can copy the text from the console, place it in txt file and attach the txt file here.

    Can you also try the below things:

    * Use the below RDK u-boot code base to build the u-boot and try with it
    arago-project.org/.../

    *Use the EZSDK u-boot code base to build the u-boot and try with it

    Regards,
    Pavel
  • 0 in reply to Pavel Botev
    Prodigy 160 points
    Hi Pavel,

    Downloaded latest u-boot code from arago project git.

    After compiling and flashing to NAND, boot process gets stuck at

    Starting Kernel ...

    again TI8168 EVM SDK u-boot works

    Thanks
    Tushar Nautiyal
  • 0 in reply to Tushar Nautiyal
    TI__Guru**** 170625 points
    Tushar,

    Can you provide me full console log when you build the RDK u-boot? You can copy the text from the console, place it in txt file and attach the txt file here.

    Can you also provide me the boot arguments you are using in the successful/EZSDK case and in the failing/RDK case?

    BR
    Pavel