• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Subscribers 98 subscribers
  • Views 2688 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.

Linux/PROCESSOR-SDK-AM335X: eMMC device not found

Vamsi Siddhani
Expert 1420 points
Part Number: PROCESSOR-SDK-AM335X


Tool/software: Linux

We wanted to boot our custom board based on AM335x-EVM-SK, using eMMC. As of now our board is booting from SD Card.

SDK we are using is ti-processor-sdk-linux-am335x-evm-05.00.00.15.

To boot it from eMMC we did

1. copied MLO,        u-boot.img,            tisdk-rootfs-image-am335x-evm.tar.xz to SD Card rootfs/boot/files.

2. booted board with sd card.

3. did fdisk /dev/mmcblk1

4. made partitions and

Copied the {MLO,u-boot.img} files to the first partition:


2.1. mkdir boot
2.2. mount /dev/mmcblk1p1 boot
2.3. cp /boot/files/{MLO,u-boot.img} boot
2.4. sync
2.5. umount boot

 

Extracted the root file system to the second partition:


3.1. mkdir root
3.2. mount /dev/mmcblk1p2 root
3.3. tar -xf /boot/files/tisdk-rootfs-image-am335x-evm.tar.gz -C root
3.4. sync
3.5. umount root

5. Powered off the board.

6. Removed SD Card.

7. Powered ON the board.

8. Nothing happened. Blank screen.

9. Inserted SD Card.

10. Booting completed. logged in into root and tried the following things

root@am335x-evm:~# sudo fsck /dev/mmcblk1
fsck from util-linux 2.30
[ 1091.873576] mmcblk1: error -84 transferring data, sector 7520128, nr 8, cmd response 0x900, card status 0xb00
[ 1091.884082] mmcblk1: retrying using single block read
[ 1091.889646] mmcblk1: error -84 transferring data, sector 7520128, nr 8, cmd response 0x900, card status 0x0
[ 1091.904432] print_req_error: 70 callbacks suppressed
[ 1091.904441] print_req_error: I/O error, dev mmcblk1, sector 7520128
[ 1091.948641] mmcblk1: error -84 transferring data, sector 7520129, nr 7, cmd response 0x900, card status 0x0
[ 1091.958579] print_req_error: I/O error, dev mmcblk1, sector 7520129
[ 1091.994949] mmcblk1: error -84 transferring data, sector 7520130, nr 6, cmd response 0x900, card status 0x0
[ 1092.005475] print_req_error: I/O error, dev mmcblk1, sector 7520130
[ 1092.041094] mmcblk1: error -84 transferring data, sector 7520131, nr 5, cmd response 0x900, card status 0x0
[ 1092.051072] print_req_error: I/O error, dev mmcblk1, sector 7520131
[ 1092.086132] mmcblk1: error -84 transferring data, sector 7520132, nr 4, cmd response 0x900, card status 0x0
[ 1092.098348] print_req_error: I/O error, dev mmcblk1, sector 7520132
[ 1092.134321] mmcblk1: error -84 transferring data, sector 7520133, nr 3, cmd response 0x900, card status 0x0
[ 1092.144840] print_req_error: I/O error, dev mmcblk1, sector 7520133
[ 1092.179884] mmcblk1: error -84 transferring data, sector 7520134, nr 2, cmd response 0x900, card status 0x0
[ 1092.189850] print_req_error: I/O error, dev mmcblk1, sector 7520134
[ 1092.226244] mmcblk1: error -84 transferring data, sector 7520135, nr 1, cmd response 0x900, card status 0x0
[ 1092.236915] print_req_error: I/O error, dev mmcblk1, sector 7520135
[ 1092.272723] mmcblk1: error -84 transferring data, sector 7520128, nr 8, cmd response 0x900, card status 0xb00
[ 1092.283438] mmcblk1: retrying using single block read
[ 1092.288807] mmcblk1: error -84 transferring data, sector 7520128, nr 8, cmd response 0x900, card status 0x0
[ 1092.303986] print_req_error: I/O error, dev mmcblk1, sector 7520128
[ 1092.335442] mmcblk1: error -84 transferring data, sector 7520129, nr 7, cmd response 0x900, card status 0x0
[ 1092.349455] print_req_error: I/O error, dev mmcblk1, sector 7520129
[ 1092.385168] mmcblk1: error -84 transferring data, sector 7520130, nr 6, cmd response 0x900, card status 0x0
[ 1092.423002] mmcblk1: error -84 transferring data, sector 7520131, nr 5, cmd response 0x900, card status 0x0
[ 1092.461200] mmcblk1: error -84 transferring data, sector 7520132, nr 4, cmd response 0x900, card status 0x0
[ 1092.498377] mmcblk1: error -84 transferring data, sector 7520133, nr 3, cmd response 0x900, card status 0x0
[ 1092.535804] mmcblk1: error -84 transferring data, sector 7520134, nr 2, cmd response 0x900, card status 0x0
[ 1092.573437] mmcblk1: error -84 transferring data, sector 7520135, nr 1, cmd response 0x900, card status 0x0
[ 1092.583392] Buffer I/O error on dev mmcblk1, logical block 940016, async page read
e2fsck 1.43.5 (04-Aug-2017)
[ 1092.633123] mmcblk1: error -84 transferring data, sector 0, nr 32, cmd response 0x900, card status 0xb00
[ 1092.643371] mmcblk1: retrying using single block read
[ 1092.678352] mmcblk1: error -84 transferring data, sector 0, nr 32, cmd response 0x900, card status 0x0
[ 1092.715326] mmcblk1: error -84 transferring data, sector 1, nr 31, cmd response 0x900, card status 0x0
[ 1092.752521] mmcblk1: error -84 transferring data, sector 2, nr 30, cmd response 0x900, card status 0x0
[ 1092.789774] mmcblk1: error -84 transferring data, sector 3, nr 29, cmd response 0x900, card status 0x0
[ 1092.826727] mmcblk1: error -84 transferring data, sector 4, nr 28, cmd response 0x900, card status 0x0
[ 1092.866065] mmcblk1: error -84 transferring data, sector 5, nr 27, cmd response 0x900, card status 0x0
[ 1092.903180] mmcblk1: error -84 transferring data, sector 6, nr 26, cmd response 0x900, card status 0x0
[ 1092.940378] mmcblk1: error -84 transferring data, sector 7, nr 25, cmd response 0x900, card status 0x0
[ 1092.977542] mmcblk1: error -84 transferring data, sector 8, nr 24, cmd response 0x900, card status 0x0
[ 1093.014479] mmcblk1: error -84 transferring data, sector 9, nr 23, cmd response 0x900, card status 0x0
[ 1093.051599] mmcblk1: error -84 transferring data, sector 10, nr 22, cmd response 0x900, card status 0x0
[ 1093.089008] mmcblk1: error -84 transferring data, sector 11, nr 21, cmd response 0x900, card status 0x0
[ 1093.126161] mmcblk1: error -84 transferring data, sector 12, nr 20, cmd response 0x900, card status 0x0
[ 1093.163562] mmcblk1: error -84 transferring data, sector 13, nr 19, cmd response 0x900, card status 0x0
[ 1093.201109] mmcblk1: error -84 transferring data, sector 14, nr 18, cmd response 0x900, card status 0x0
[ 1093.238306] mmcblk1: error -84 transferring data, sector 15, nr 17, cmd response 0x900, card status 0x0
[ 1093.276589] mmcblk1: error -84 transferring data, sector 16, nr 16, cmd response 0x900, card status 0x0
[ 1093.314133] mmcblk1: error -84 transferring data, sector 17, nr 15, cmd response 0x900, card status 0x0
[ 1093.351070] mmcblk1: error -84 transferring data, sector 18, nr 14, cmd response 0x900, card status 0x0
[ 1093.388343] mmcblk1: error -84 transferring data, sector 19, nr 13, cmd response 0x900, card status 0x0
[ 1093.425796] mmcblk1: error -84 transferring data, sector 20, nr 12, cmd response 0x900, card status 0x0
[ 1093.463084] mmcblk1: error -84 transferring data, sector 21, nr 11, cmd response 0x900, card status 0x0
[ 1093.500178] mmcblk1: error -84 transferring data, sector 22, nr 10, cmd response 0x900, card status 0x0
[ 1093.537482] mmcblk1: error -84 transferring data, sector 23, nr 9, cmd response 0x900, card status 0x0
[ 1093.574332] mmcblk1: error -84 transferring data, sector 24, nr 8, cmd response 0x900, card status 0x0
[ 1093.611869] mmcblk1: error -84 transferring data, sector 25, nr 7, cmd response 0x900, card status 0x0
[ 1093.649831] mmcblk1: error -84 transferring data, sector 26, nr 6, cmd response 0x900, card status 0x0
[ 1093.686744] mmcblk1: error -84 transferring data, sector 27, nr 5, cmd response 0x900, card status 0x0
[ 1093.723996] mmcblk1: error -84 transferring data, sector 28, nr 4, cmd response 0x900, card status 0x0
[ 1093.761225] mmcblk1: error -84 transferring data, sector 29, nr 3, cmd response 0x900, card status 0x0
[ 1093.798042] mmcblk1: error -84 transferring data, sector 30, nr 2, cmd response 0x900, card status 0x0
[ 1093.834725] mmcblk1: error -84 transferring data, sector 31, nr 1, cmd response 0x900, card status 0x0
[ 1093.872882] mmcblk1: error -84 transferring data, sector 0, nr 8, cmd response 0x900, card status 0xb00
[ 1093.882494] mmcblk1: retrying using single block read
[ 1093.917203] mmcblk1: error -84 transferring data, sector 0, nr 8, cmd response 0x900, card status 0x0
[ 1093.954130] mmcblk1: error -84 transferring data, sector 1, nr 7, cmd response 0x900, card status 0x0
[ 1093.991546] mmcblk1: error -84 transferring data, sector 2, nr 6, cmd response 0x900, card status 0x0
[ 1094.028488] mmcblk1: error -84 transferring data, sector 3, nr 5, cmd response 0x900, card status 0x0
[ 1094.065671] mmcblk1: error -84 transferring data, sector 4, nr 4, cmd response 0x900, card status 0x0
[ 1094.103133] mmcblk1: error -84 transferring data, sector 5, nr 3, cmd response 0x900, card status 0x0
[ 1094.140091] mmcblk1: error -84 transferring data, sector 6, nr 2, cmd response 0x900, card status 0x0
[ 1094.177090] mmcblk1: error -84 transferring data, sector 7, nr 1, cmd response 0x900, card status 0x0
[ 1094.186539] Buffer I/O error on dev mmcblk1, logical block 0, async page read
[ 1094.224054] mmcblk1: error -84 transferring data, sector 0, nr 8, cmd response 0x900, card status 0xb00
[ 1094.234245] mmcblk1: retrying using single block read
[ 1094.268552] mmcblk1: error -84 transferring data, sector 0, nr 8, cmd response 0x900, card status 0x0
[ 1094.305306] mmcblk1: error -84 transferring data, sector 1, nr 7, cmd response 0x900, card status 0x0
[ 1094.343157] mmcblk1: error -84 transferring data, sector 2, nr 6, cmd response 0x900, card status 0x0
[ 1094.379945] mmcblk1: error -84 transferring data, sector 3, nr 5, cmd response 0x900, card status 0x0
[ 1094.416714] mmcblk1: error -84 transferring data, sector 4, nr 4, cmd response 0x900, card status 0x0
[ 1094.454035] mmcblk1: error -84 transferring data, sector 5, nr 3, cmd response 0x900, card status 0x0
[ 1094.491104] mmcblk1: error -84 transferring data, sector 6, nr 2, cmd response 0x900, card status 0x0
[ 1094.528172] mmcblk1: error -84 transferring data, sector 7, nr 1, cmd response 0x900, card status 0x0
[ 1094.537615] Buffer I/O error on dev mmcblk1, logical block 0, async page read
fsck.ext2: Input/output error while trying to open /dev/mmcblk1

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contai[ 1094.582334] mmcblk1: error -84 transferring data, sector 0, nr 8, cmd response 0x900, card status 0xb00
ns an ext2/ext3/ext4
filesystem (and not swap or ufs or somethi[ 1094.598154] mmcblk1: retrying using single block read
ng else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <d[ 1094.638070] mmcblk1: error -84 transferring data, sector 0, nr 8, cmd response 0x900, card status 0x0
evice>
or
e2fsck -b 32768 <device>

[ 1094.654082] mmcblk1: error -84 transferring data, sector 1, nr 7, cmd response 0x900, card status 0x0
root@am335x-evm:~# [ 1094.695508] mmcblk1: error -84 transferring data, sector 2, nr 6, cmd response 0x900, card status 0x0
[ 1094.707302] mmcblk1: error -84 transferring data, sector 3, nr 5, cmd response 0x900, card status 0x0
[ 1094.745837] mmcblk1: error -84 transferring data, sector 4, nr 4, cmd response 0x900, card status 0x0
[ 1094.783480] mmcblk1: error -84 transferring data, sector 5, nr 3, cmd response 0x900, card status 0x0
[ 1094.820354] mmcblk1: error -84 transferring data, sector 6, nr 2, cmd response 0x900, card status 0x0
[ 1094.863181] mmcblk1: error -84 transferring data, sector 7, nr 1, cmd response 0x900, card status 0x0
[ 1094.884533] Buffer I/O error on dev mmcblk1, logical block 0, async page read
[ 1094.925107] mmcblk1: error -84 transferring data, sector 0, nr 8, cmd response 0x900, card status 0xb00
[ 1094.945637] mmcblk1: retrying using single block read
[ 1094.976193] mmcblk1: error -84 transferring data, sector 0, nr 8, cmd response 0x900, card status 0x0
[ 1095.019811] mmcblk1: error -84 transferring data, sector 1, nr 7, cmd response 0x900, card status 0x0
[ 1095.067138] mmcblk1: error -84 transferring data, sector 2, nr 6, cmd response 0x900, card status 0x0
[ 1095.110179] mmcblk1: error -84 transferring data, sector 3, nr 5, cmd response 0x900, card status 0x0
[ 1095.150898] mmcblk1: error -84 transferring data, sector 4, nr 4, cmd response 0x900, card status 0x0
[ 1095.188177] mmcblk1: error -84 transferring data, sector 5, nr 3, cmd response 0x900, card status 0x0
[ 1095.225045] mmcblk1: error -84 transferring data, sector 6, nr 2, cmd response 0x900, card status 0x0
[ 1095.234972] mmcblk1: error -84 transferring data, sector 7, nr 1, cmd response 0x900, card status 0x0
[ 1095.248997] Buffer I/O error on dev mmcblk1, logical block 0, async page read
[ 1095.258670] mmcblk1: unable to read partition table
[ 1095.315141] mmcblk1: error -84 transferring data, sector 7520128, nr 8, cmd response 0x900, card status 0xb00
[ 1095.325282] mmcblk1: retrying using single block read
[ 1095.330624] mmcblk1: error -84 transferring data, sector 7520128, nr 8, cmd response 0x900, card status 0x0
[ 1095.373189] mmcblk1: error -84 transferring data, sector 7520129, nr 7, cmd response 0x900, card status 0x0
[ 1095.434696] mmcblk1: error -84 transferring data, sector 7520130, nr 6, cmd response 0x900, card status 0x0
[ 1095.477495] mmcblk1: error -84 transferring data, sector 7520131, nr 5, cmd response 0x900, card status 0x0
[ 1095.515495] mmcblk1: error -84 transferring data, sector 7520132, nr 4, cmd response 0x900, card status 0x0
[ 1095.553232] mmcblk1: error -84 transferring data, sector 7520133, nr 3, cmd response 0x900, card status 0x0
[ 1095.590809] mmcblk1: error -84 transferring data, sector 7520134, nr 2, cmd response 0x900, card status 0x0
[ 1095.628413] mmcblk1: error -84 transferring data, sector 7520135, nr 1, cmd response 0x900, card status 0x0
[ 1095.638885] mmcblk1: error -84 transferring data, sector 7520128, nr 8, cmd response 0x900, card status 0xb00
[ 1095.653670] mmcblk1: retrying using single block read
[ 1095.686011] mmcblk1: error -84 transferring data, sector 7520128, nr 8, cmd response 0x900, card status 0x0
[ 1095.724003] mmcblk1: error -84 transferring data, sector 7520129, nr 7, cmd response 0x900, card status 0x0
[ 1095.761436] mmcblk1: error -84 transferring data, sector 7520130, nr 6, cmd response 0x900, card status 0x0
[ 1095.797348] mmcblk1: error -84 transferring data, sector 7520131, nr 5, cmd response 0x900, card status 0x0
[ 1095.836687] mmcblk1: error -84 transferring data, sector 7520132, nr 4, cmd response 0x900, card status 0x0
[ 1095.846871] mmcblk1: error -84 transferring data, sector 7520133, nr 3, cmd response 0x900, card status 0x0
[ 1095.887760] mmcblk1: error -84 transferring data, sector 7520134, nr 2, cmd response 0x900, card status 0x0
[ 1095.926475] mmcblk1: error -84 transferring data, sector 7520135, nr 1, cmd response 0x900, card status 0x0
[ 1095.936430] Buffer I/O error on dev mmcblk1, logical block 940016, async page read

root@am335x-evm:~#

root@am335x-evm:~# sfdisk -d /dev/mmcblk1
sfdisk: cannot open /dev/mmcblk1: No such file or directory
root@am335x-evm:~#

root@am335x-evm:~# fdisk /dev/block/mmcblk1

Welcome to fdisk (util-linux 2.30).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

fdisk: cannot open /dev/block/mmcblk1: No such file or directory
root@am335x-evm:~#

Can anyone of you help me with this?

  • 0
    TI__Guru**** 170625 points
    Hi Vamsi,

    I would suggest you first to focus on u-boot (MLO, u-boot) flashing and booting. One you are fine with it, then you can proceed with kernel and rootfs flashing and booting.

    software-dl.ti.com/.../Foundational_Components_U-Boot.html

    e2e.ti.com/.../706666
    e2e.ti.com/.../757123
    e2e.ti.com/.../754195

    You can also test your custom board eMMC hardware with the RTOS eMMC test cases, emmc_TEST and emmcStress_TEST:

    software-dl.ti.com/.../index_board.html

    Regards,
    Pavel
  • 0 in reply to Pavel Botev
    Expert 1420 points

    I am using the same files of u-boot (MLO, u-boot), which are working with SD Card only. They are fine. No issue with that.

    Now, how to get rid of this below error. It says fdisk: cannot open /dev/mmcblk1p1: No such file or directory always.

    root@am335x-evm:~# sudo fsck.ext4 /dev/mmcblk1
    e2fsck 1.43.5 (04-Aug-2017)
    fsck.ext4: No such file or directory while trying to open /dev/mmcblk1
    Possibly non-existent device?
    root@am335x-evm:~# debugfs /dev/mmcblk1p1
    debugfs 1.43.5 (04-Aug-2017)
    Checksum errors in superblock! Retrying...
    /dev/mmcblk1p1: No such file or directory while opening filesystem
    debugfs: q
    root@am335x-evm:~# sudo e2fsck -fyv /dev/mmcblk1
    e2fsck 1.43.5 (04-Aug-2017)
    e2fsck: No such file or directory while trying to open /dev/mmcblk1
    Possibly non-existent device?
    root@am335x-evm:~# mount /dev/mmcblk1
    mount: /dev/mmcblk1: can't find in /etc/fstab.
    root@am335x-evm:~# fdisk /dev/mmcblk0

    Welcome to fdisk (util-linux 2.30).
    Changes will remain in memory only, until you decide to write them.
    Be careful before using the write command.


    Command (m for help): q

    root@am335x-evm:~# mount /dev/mmcblk1
    mount: /dev/mmcblk1: can't find in /etc/fstab.
    root@am335x-evm:~# fdisk /dev/mmcblk1

    Welcome to fdisk (util-linux 2.30).
    Changes will remain in memory only, until you decide to write them.
    Be careful before using the write command.

    fdisk: cannot open /dev/mmcblk1: No such file or directory
    root@am335x-evm:~# fdisk /dev/mmcblk1

    Welcome to fdisk (util-linux 2.30).
    Changes will remain in memory only, until you decide to write them.
    Be careful before using the write command.

    fdisk: cannot open /dev/mmcblk1: No such file or directory
    root@am335x-evm:~# fdisk /dev/
    Display all 680 possibilities? (y or n)
    root@am335x-evm:~# fdisk /dev/mmcblk1p1

    Welcome to fdisk (util-linux 2.30).
    Changes will remain in memory only, until you decide to write them.
    Be careful before using the write command.

    fdisk: cannot open /dev/mmcblk1p1: No such file or directory
    root@am335x-evm:~# fdisk /dev/mmcblk1p2

    Welcome to fdisk (util-linux 2.30).
    Changes will remain in memory only, until you decide to write them.
    Be careful before using the write command.

    fdisk: cannot open /dev/mmcblk1p2: No such file or directory

  • 0 in reply to Vamsi Siddhani
    Expert 1420 points

    As you said You can also test your custom board eMMC hardware with the RTOS eMMC test cases, emmc_TEST and emmcStress_TEST:

    we are using AM335x EVM SK. are these tests supported by our SDK? No X is marked against these tests in the link you have sent.

    http://software-dl.ti.com/processor-sdk-rtos/esd/docs/latest/rtos/index_board.html#diagnostic-applications

  • 0 in reply to Vamsi Siddhani
    Expert 1420 points
    After all this, now RST_n of eMMC is now low. so our eMMC is in reset. We are suspecting that something wrong we did while copying MLO, u-boot & ti-sdk into partitions.

    Someone please suggest me how to get rid of this reset issue i.e. how to revert back the changes or erase the partitions.
  • 0 in reply to Pavel Botev
    Expert 1420 points
    After all this, now RST_n of eMMC is now low. so our eMMC is in reset. We are suspecting that something wrong we did while copying MLO, u-boot & ti-sdk into partitions.

    Someone please suggest me how to get rid of this reset issue i.e. how to revert back the changes or erase the partitions.
  • 0 in reply to Pavel Botev
    Expert 1420 points
    I tried erasing eMMC using JTAG. For that, ollowing is the console output.

    [CortxA8] Welcome to CCS Nand Flash Utility
    Assuming board is configured for NAND flash support


    Choose your operation
    Enter 1 ---> To Flash an Image
    Enter 2 ---> To ERASE the whole NAND
    Enter 3 ---> To EXIT
    2
    Starting AM335X NAND writer

    ----------------------
    NAND FLASH DETAILS
    ----------------------
    Device ID : 0xff
    Manufacture ID : 0xff
    Page Size : 8192 Bytes
    Spare Size : 256 Bytes
    Pages_Per_Block : 64
    Number_of_Blocks : -1941440558
    Device_width : 2 Byte
    DeviceSize : 3049 MB


    Performing Global Nand Erase
    FAIL!! to erase block number 0x0
    FAIL!! to erase block number 0x1
    FAIL!! to erase block number 0x2
    FAIL!! to erase block number 0x3
    FAIL!! to erase block number 0x4
    FAIL!! to erase block number 0x5
    FAIL!! to erase block number 0x6
    FAIL!! to erase block number 0x7
    FAIL!! to erase block number 0x8
    FAIL!! to erase block number 0x9
    FAIL!! to erase block number 0xa
    FAIL!! to erase block number 0xb
    FAIL!! to erase block number 0xc
    FAIL!! to erase block number 0xd
    FAIL!! to erase block number 0xe
    FAIL!! to erase block number 0xf
    FAIL!! to erase block number 0x10
    FAIL!! to erase block number 0x11
    FAIL!! to erase block number 0x12
    FAIL!! to erase block number 0x13
    FAIL!! to erase block number 0x14
    FAIL!! to erase block number 0x15
    FAIL!! to erase block number 0x16
    FAIL!! to erase block number 0x17
    FAIL!! to erase block number 0x18
    FAIL!! to erase block number 0x19
    FAIL!! to erase block number 0x1a
    FAIL!! to erase block number 0x1b
    FAIL!! to erase block number 0x1c
    FAIL!! to erase block number 0x1d
    FAIL!! to erase block number 0x1e
    FAIL!! to erase block number 0x1f
    FAIL!! to erase block number 0x20
    FAIL!! to erase block number 0x21
    FAIL!! to erase block number 0x22
    FAIL!! to erase block number 0x23
    FAIL!! to erase block number 0x24
    FAIL!! to erase block number 0x25
    FAIL!! to erase block number 0x26
    FAIL!! to erase block number 0x27
    FAIL!! to erase block number 0x28
    FAIL!! to erase block number 0x29
    FAIL!! to erase block number 0x2a
    FAIL!! to erase block number 0x2b
    FAIL!! to erase block number 0x2c
    FAIL!! to erase block number 0x2d
    FAIL!! to erase block number 0x2e
    FAIL!! to erase block number 0x2f
    FAIL!! to erase block number 0x30
    FAIL!! to erase block number 0x31
    FAIL!! to erase block number 0x32
    FAIL!! to erase block number 0x33
    FAIL!! to erase block number 0x34
    FAIL!! to erase block number 0x35
    FAIL!! to erase block number 0x36
    FAIL!! to erase block number 0x37
    FAIL!! to erase block number 0x38
    FAIL!! to erase block number 0x39
    FAIL!! to erase block number 0x3a
    FAIL!! to erase block number 0x3b
    FAIL!! to erase block number 0x3c
    FAIL!! to erase block number 0x3d
    FAIL!! to erase block number 0x3e
    FAIL!! to erase block number 0x3f
    FAIL!! to erase block number 0x40
    FAIL!! to erase block number 0x41
    FAIL!! to erase block number 0x42
    FAIL!! to erase block number 0x43
    FAIL!! to erase block number 0x44
    FAIL!! to erase block number 0x45
    FAIL!! to erase block number 0x46
    FAIL!! to erase block number 0x47
    FAIL!! to erase block number 0x48
    FAIL!! to erase block number 0x49
    FAIL!! to erase block number 0x4a
    FAIL!! to erase block number 0x4b
    FAIL!! to erase block number 0x4c
    FAIL!! to erase block number 0x4d
    FAIL!! to erase block number 0x4e
    FAIL!! to erase block number 0x4f
    FAIL!! to erase block number 0x50
    FAIL!! to erase block number 0x51
    FAIL!! to erase block number 0x52
    FAIL!! to erase block number 0x53
    FAIL!! to erase block number 0x54
    FAIL!! to erase block number 0x55
    FAIL!! to erase block number 0x56
    FAIL!! to erase block number 0x57
    FAIL!! to erase block number 0x58
    FAIL!! to erase block number 0x59
    FAIL!! to erase block number 0x5a
    FAIL!! to erase block number 0x5b
    FAIL!! to erase block number 0x5c
    FAIL!! to erase block number 0x5d
    FAIL!! to erase block number 0x5e
    FAIL!! to erase block number 0x5f
    FAIL!! to erase block number 0x60
    FAIL!! to erase block number 0x61
    FAIL!! to erase block number 0x62
    FAIL!! to erase block number 0x63
    FAIL!! to erase block number 0x64
    FAIL!! to erase block number 0x65
    FAIL!! to erase block number 0x66
    FAIL!! to erase block number 0x67
    FAIL!! to erase block number 0x68
    FAIL!! to erase block number 0x69
    FAIL!! to erase block number 0x6a
    FAIL!! to erase block number 0x6b
    FAIL!! to erase block number 0x6c
    FAIL!! to erase block number 0x6d
    FAIL!! to erase block number 0x6e
    FAIL!! to erase block number 0x6f
    FAIL!! to erase block number 0x70
    FAIL!! to erase block number 0x71
    FAIL!! to erase block number 0x72
    FAIL!! to erase block number 0x73
    FAIL!! to erase block number 0x74
    FAIL!! to erase block number 0x75
    FAIL!! to erase block number 0x76
    FAIL!! to erase block number 0x77
    FAIL!! to erase block number 0x78
    FAIL!! to erase block number 0x79
    FAIL!! to erase block number 0x7a
    FAIL!! to erase block number 0x7b
    FAIL!! to erase block number 0x7c
    FAIL!! to erase block number 0x7d
    FAIL!! to erase block number 0x7e
    FAIL!! to erase block number 0x7f
    FAIL!! to erase block number 0x80
    FAIL!! to erase block number 0x81
    FAIL!! to erase block number 0x82
    FAIL!! to erase block number 0x83
    FAIL!! to erase block number 0x84
    FAIL!! to erase block number 0x85
    FAIL!! to erase block number 0x86
    FAIL!! to erase block number 0x87
    FAIL!! to erase block number 0x88
    FAIL!! to erase block number 0x89
    FAIL!! to erase block number 0x8a
    FAIL!! to erase block number 0x8b
    FAIL!! to erase block number 0x8c
    FAIL!! to erase block number 0x8d
    FAIL!! to erase block number 0x8e
    FAIL!! to erase block number 0x8f
    FAIL!! to erase block number 0x90
    FAIL!! to erase block number 0x91
    FAIL!! to erase block number 0x92
    FAIL!! to erase block number 0x93
    FAIL!! to erase block number 0x94
    FAIL!! to erase block number 0x95
    FAIL!! to erase block number 0x96
    FAIL!! to erase block number 0x97
    FAIL!! to erase block number 0x98
    FAIL!! to erase block number 0x99
    FAIL!! to erase block number 0x9a
    FAIL!! to erase block number 0x9b
    FAIL!! to erase block number 0x9c
    FAIL!! to erase block number 0x9d
    FAIL!! to erase block number 0x9e
    FAIL!! to erase block number 0x9f
    FAIL!! to erase block number 0xa0
    FAIL!! to erase block number 0xa1
    FAIL!! to erase block number 0xa2
    FAIL!! to erase block number 0xa3
    FAIL!! to erase block number 0xa4
    FAIL!! to erase block number 0xa5
    FAIL!! to erase block number 0xa6
    FAIL!! to erase block number 0xa7
    FAIL!! to erase block number 0xa8
    FAIL!! to erase block number 0xa9
    FAIL!! to erase block number 0xaa
    FAIL!! to erase block number 0xab
    FAIL!! to erase block number 0xac
    FAIL!! to erase block number 0xad
    FAIL!! to erase block number 0xae
    FAIL!! to erase block number 0xaf
    FAIL!! to erase block number 0xb0
    FAIL!! to erase block number 0xb1
    FAIL!! to erase block number 0xb2
    FAIL!! to erase block number 0xb3
    FAIL!! to erase block number 0xb4
    FAIL!! to erase block number 0xb5
    FAIL!! to erase block number 0xb6
    FAIL!! to erase block number 0xb7
    FAIL!! to erase block number 0xb8
    FAIL!! to erase block number 0xb9
    FAIL!! to erase block number 0xba
    FAIL!! to erase block number 0xbb
    FAIL!! to erase block number 0xbc
    FAIL!! to erase block number 0xbd
    FAIL!! to erase block number 0xbe
    FAIL!! to erase block number 0xbf
    FAIL!! to erase block number 0xc0
    FAIL!! to erase block number 0xc1
    FAIL!! to erase block number 0xc2
    FAIL!! to erase block number 0xc3
    FAIL!! to erase block number 0xc4
    FAIL!! to erase block number 0xc5
    FAIL!! to erase block number 0xc6
    FAIL!! to erase block number 0xc7
    FAIL!! to erase block number 0xc8
    FAIL!! to erase block number 0xc9
    FAIL!! to erase block number 0xca
    FAIL!! to erase block number 0xcb
    FAIL!! to erase block number 0xcc
    FAIL!! to erase block number 0xcd
    FAIL!! to erase block number 0xce
    FAIL!! to erase block number 0xcf
    FAIL!! to erase block number 0xd0
    FAIL!! to erase block number 0xd1
    FAIL!! to erase block number 0xd2
    FAIL!! to erase block number 0xd3
    FAIL!! to erase block number 0xd4
    FAIL!! to erase block number 0xd5
    FAIL!! to erase block number 0xd6
    FAIL!! to erase block number 0xd7
    .
    .
    .
    .
    .
    .

    What may be the issue?

    Please help me in this regard.
  • 0 in reply to Vamsi Siddhani
    TI__Guru**** 170625 points
    This tool (CCS Nand Flash Utility) seems to be able to flash/erase NAND flash only, not eMMC flash. If you have NAND flash on your custom board, you can try and verify it will work successful for NAND flash.

    Regards,
    Pavel
  • 0 in reply to Pavel Botev
    Expert 1420 points
    I've referred to the following link for eMMC booting.
    processors.wiki.ti.com/.../Linux_Core_U-Boot_User's_Guide

    When i try those steps, it is giving error as shown below.
    => mmc dev 0
    switch to partitions #0, OK
    mmc0 is current device
    => mmc rescan
    => mmc dev 1
    switch to partitions #0, OK
    mmc1(part 0) is current device
    => fatload mmc 0 ${loadaddr} MLO
    reading MLO
    105940 bytes read in 13 ms (7.8 MiB/s)
    => mmc write ${loadaddr} 0x100 0x100

    MMC write: dev # 1, block # 256, count 256 ... 256 blocks written: OK
    => mmc write ${loadaddr} 0x200 0x100

    MMC write: dev # 1, block # 512, count 256 ... 256 blocks written: OK
    => fatload mmc 0 ${loadaddr} u-boot.img
    reading u-boot.img
    644828 bytes read in 56 ms (11 MiB/s)
    => mmc write ${loadaddr} 0x300 0x400

    MMC write: dev # 1, block # 768, count 1024 ... 1024 blocks written: OK
    => fatload mmc 0 ${loadaddr} rootfs.ext4
    ** Unable to read file rootfs.ext4 **


    Why it is unable to read file rootfs.ext4? How to resolve it?


    Best Regards
    Vamsi
  • 0 in reply to Vamsi Siddhani
    Expert 1420 points
    when i used mmc list command following is the output

    => mmc list
    OMAP SD/MMC: 0 (SD)
    OMAP SD/MMC: 1
    =>
    OMAP SD/MMC: 0 (SD)
    OMAP SD/MMC: 1
    =>

    why for OMAP SD/MMC: 1 it is not showing (eMMC)???????
  • 0 in reply to Vamsi Siddhani
    TI__Guru**** 170625 points

    Vamsi,

    Vamsi Siddhani said:
    I've referred to the following link for eMMC booting.
    processors.wiki.ti.com/.../Linux_Core_U-Boot_User's_Guide

    This wiki is old. For PSDK v5.00, you should use below u-boot user guide:

    Regards,
    Pavel