emmc flashing with u-boot.img & image.fit images onto BBB

Hi Srini,

You can flash the u-boot.img and image.fit files into eMMC after you booted the board through NFS.

In other words, you can access the eMMC once you booted the board via NFS.

Hi Srini,

please refer to the following TI WIKIS which gives the general procedure.

http://processors.wiki.ti.com/index.php/Linux_Core_U-Boot_User's_Guide#Using_SD.2C_eMMC_or_USB_storage

Regards,

Shankari

-------------------------------------------------------------------------------------------------------

Please click the Verify Answer button on this post if it answers your question.
--------------------------------------------------------------------------------------------------------

Hi Srini,

* Flash Beaglebone Black's eMMC (verified with AM335x SDK 07.00.00.00):
http://www.adminempire.com/how-to-install-arch-linux-on-beaglebone-black-bbb/

1. Prepare a SD card either with the create-sdcard.sh script or:
On the host PC with the SD card inserted:
1.01. sudo fdisc /dev/sdd (or /dev/mmcblk0)
1.02. o - this clears the existing partitions
1.03. p - this lists all partition tables on the card (there should be none)
1.04. n - create a new partition
1.05. p - primary partition
1.06. 1 - partition number
1.07. 2048 - default value for the first sector
1.08. +64M - last sector / partition size
1.09. t - change the partition type (select partition 1)
1.10. e - change tha partition type to "W95 FAT16 (LBA)"
1.11. a - set the bootable flag for the selected partition (1)
1.12. n - create a new partition
1.13. p - primary partition
1.14. 2 - partition number
1.15. hit Enter to choose the default (next available) value for the first sector
1.16. hit Enter to choose the default (last) value for the last sector
1.17. p - this lists all partition tables on the card (there should be two)
1.18. w - write all the above changes to disk
1.19. sudo mkfs.vfat -F 16 /dev/mmcblk0p1 (or /dev/sdd1) - format the first partition
1.20. sudo mkfs.ext4 /dev/mmcblk0p2 (or /dev/sdd2) - format the second partition
1.21. copy the {MLO,u-boot.img,uEnv.txt} files to the first partition:
# mkdir boot
# sudo mount /dev/mmcblk0p1 boot
# cp {MLO,u-boot.img,uEnv.txt} boot
# sudo umount boot
1.22. copy the root file system to the second partition:
# mkdir root
# sudo mount /dev/mmcblk0p2 root
# tar -xf tisdk-rootfs-image-am335x-evm.tar.gz -C root
# sudo umount root

2. Run the BBB from the SD card (hold the USR button when powering the board up)

3. ssh into the board:
# ssh root@172.20.0.111

4. The eMMC is /dev/mmcblk1. Format it this way:
4.01. fdisk /dev/mmcblk1
4.02. o - this clears the existing partitions
4.03. p - this lists all partition tables on the card (there should be none)
4.04. n - create a new partition
4.05. p - primary partition
4.06. 1 - partition number
4.07. 2048 - default value for the first sector
4.08. +16M - last sector / partition size
4.09. t - change the partition type (select partition 1)
4.10. e - change tha partition type to "W95 FAT16 (LBA)"
4.11. a - set the bootable flag for the selected partition (1)
4.12. n - create a new partition
4.13. p - primary partition
4.14. 2 - partition number
4.15. hit Enter to choose the default (next available) value for the first sector
4.16. hit Enter to choose the default (last) value for the last sector
4.17. p - this lists all partition tables on the card (there should be two)
4.18. w - write all the above changes to disk
4.19. umount /dev/mmcblk1p1; mkfs.vfat -F 16 /dev/mmcblk1p1 - format the first partition
4.20. umount /dev/mmcblk1p2; mkfs.ext4 /dev/mmcblk1p2 - format the second partition

5. Copy the {MLO,u-boot.img,uEnv.txt} files to the first partition:
# mkdir boot
# mount /dev/mmcblk1p1 boot
# cp {MLO,u-boot.img,uEnv.txt} boot
# umount boot

6. Copy the root file system to the second partition:
# mkdir root
# mount /dev/mmcblk1p2 root
# tar -xf tisdk-rootfs-image-am335x-evm.tar.gz -C root
# umount root

7. Shutdown the BBB, remove the SD card and start it from the eMMC.

BR
Ivan

Hi Titus,

Thanks a lot for your support

As per the previous conversation we had regarding flashing of u-boot.img and image.fit files into eMMC ,

1) As I have my NFS setup already, Could you please let me know with detailed steps how u-boot.img and image.fit files can be flashed into eMMC after we boot the board through NFS, 

2)And could you please let me know whether  this method of flashing emmc with uboot.img & image.fit files is feasible in factory production environment

3)Can we use the procedure provided in the  link(http://processors.wiki.ti.com/index.php/Sitara_Linux_Program_the_eMMC_on_Beaglebone_Black), if we use this procedure, please confirm which is the fastest method of flashing process in factory production environment ie., either ( Ethernet or USB), could you please let em know uboot.img & image.fit can be flashed using this procedure

Many Many Thanks in advance again

Hi Titus,

Could you please provide any solutions w.r.t the above issue

Hi Srini,

You can follow Ivan's suggestion.

After NFS or SD boot, try to use "fdisk" command to format and create the partitions for boot images as well as rootfs.

Could anybody please do the needful how u-boot.img & image.fit can be flashed onto emmc & finally booted with these images as trying with google search I was not able to succeed from many days

Before trying with eMMC, try to boot from MMC with these images "u-boot.img & image.fit"

3)Can we use the procedure provided in the  link(http://processors.wiki.ti.com/index.php/Sitara_Linux_Program_the_eMMC_on_Beaglebone_Black), if we use this procedure, please confirm which is the fastest method of flashing process in factory production environment ie., either ( Ethernet or USB), could you please let em know uboot.img & image.fit can be flashed using this procedure

Once you able to boot from eMMC/MMC then we can create one script (flashing) for this "fdisk" and copying stuff after booted through RAMDISK.

For production,

1) Need to create flashing script which has automated commands with fdisk copy and paste commands etc.,

2) Boot the board from MMC with flashing script.

3) After boot, flashing script would initiate every flashing process automatically by getting user inputs.

Hi Titus,

Many Thanks a lot for your quick responses & appreciate the same
Am following the Ivan steps as shown above , Could you please clarify the following points

1) Inorder to execute the step 4.19. umount /dev/mmcblk1p1; mkfs.vfat -F 16 /dev/mmcblk1p1 - format the first partition,
Am unable to find mkfs.vfat command in Poky (Yocto Project Reference Distro) rootfs which ever am using,
could you please attach this command cross compiled for beaglebone black,

2)Before trying with eMMC, I tried to boot from MMC with these images "u-boot.img & image.fit" this works fine
But Could you please provide me the detailed steps how this images can be copied from SD card to emmc

3)I didn't understand the point "Once you able to boot from eMMC/MMC then we can create one script (flashing) for this "fdisk" and copying stuff after booted through RAMDISK."
Can't I use the same rootfs ie., Poky (Yocto Project Reference Distro) 1.6.2, Is it mandatory to use RAMDISK or what?..

4)I am unable to see the file uEnv.txt in SD card, Is this required(I hope this for bootargs, correct me if my understanding is wrong) for eMMC also,
since am unable to see could you please attach this file ie.,  uEnv.txt  also, so that that can be copied to eMMC

Kindly do the needful as early as possible

Awaiting for your replies

Many Many Thanks in advance again

Hi Titus,

Many Thanks a lot for your quick responses & appreciate the same
Am following the Ivan steps as shown above , Could you please clarify the following points

1) Inorder to execute the step 4.19. umount /dev/mmcblk1p1; mkfs.vfat -F 16 /dev/mmcblk1p1 - format the first partition,
Am unable to find mkfs.vfat command in Poky (Yocto Project Reference Distro) rootfs which ever am using,
could you please attach this command cross compiled for beaglebone black,

[14/11/14 - 14:42:36:208] root@beaglebone:~# mkfs.vfat -F 16 /dev/mmcblk1p1
[14/11/14 - 14:42:36:224] -sh: mkfs.vfat: command not found

2)Before trying with eMMC, I tried to boot from MMC with these images "u-boot.img & image.fit" this works fine
But Could you please provide me the detailed steps how this images can be copied from SD card to emmc

3)I didn't understand the point "Once you able to boot from eMMC/MMC then we can create one script (flashing) for this "fdisk" and copying stuff after booted through RAMDISK."
Can't I use the same rootfs ie., Poky (Yocto Project Reference Distro) 1.6.2, Is it mandatory to use RAMDISK or what?..

4)I am unable to see the file uEnv.txt in SD card, Is this required(I hope this for bootargs, correct me if my understanding is wrong) for eMMC also, 
since am unable to see could you please attach this file ie.,  uEnv.txt  also, so that that can be copied to eMMC

Kindly do the needful as early as possible

Awaiting for your replies

Many Many Thanks in advance again

Hi Srini,

4)I am unable to see the file uEnv.txt in SD card, Is this required(I hope this for bootargs, correct me if my understanding is wrong) for eMMC also, 
since am unable to see could you please attach this file ie.,  uEnv.txt  also, so that that can be copied to eMMC

Yes, you are right. Change the bootcmd and bootargs as per your boot method.

http://processors.wiki.ti.com/index.php/AM335x_U-Boot_User%27s_Guide#Setting_U-Boot_environment_using_uEnv.txt

http://linux-sunxi.org/UEnv.txt

https://sites.google.com/site/how2beagleboard/u-boot/uenv

3)I didn't understand the point "Once you able to boot from eMMC/MMC then we can create one script (flashing) for this "fdisk" and copying stuff after booted through RAMDISK."
Can't I use the same rootfs ie., Poky (Yocto Project Reference Distro) 1.6.2, Is it mandatory to use RAMDISK or what?..

RAMDISK is not mandatory and can be used SD card 's filesystem as your yocto rootfs.

I meant to say, for flashing the rootfs in production, you have to create automated scripts to execute the flashing commands automatically.

1) Inorder to execute the step 4.19. umount /dev/mmcblk1p1; mkfs.vfat -F 16 /dev/mmcblk1p1 - format the first partition,
Am unable to find mkfs.vfat command in Poky (Yocto Project Reference Distro) rootfs which ever am using,
could you please attach this command cross compiled for beaglebone black,

[14/11/14 - 14:42:36:208] root@beaglebone:~# mkfs.vfat -F 16 /dev/mmcblk1p1
[14/11/14 - 14:42:36:224] -sh: mkfs.vfat: command not found

You need to cross compile the "dosfstools" package to get "mkfs.vfat" command in your filesystem (you can use yocto poky also through adding repo).

Hi Titus,

Many Many Thanks for your quick updates

1)But Could you please provide me the detailed steps how this images can be copied from SD card to emmc

2)I have partitioned eMMC as below, I mounted boot folder & copied MLO & uboot.img, mounted root & copied my rootfs contents to root folder & image.fit to /home/root/root/boot/,
through scp from my host to the target , then I had shutdown the BeagleBone Black, removed the SD-Card, then reapplied power source to it.

But I ended up root@am335x-evm:~# CCCCCCCC 

As this didn't work :( 

Could you please do the needful in resolving this issue  or could you please correct me if I had many mistakes or missed anything

3)As am stuck this, could you please reproduce the same thing from your end & give me the detailed procedure so that I try the same over here,

4)Once if this issue is resolved I would takecare of writing my own script for factory flashing environment

root@beaglebone:~# fdisk /dev/mmcblk1

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

Command (m for help): m

Help:

DOS (MBR)
a toggle a bootable flag
b edit nested BSD disklabel
c toggle the dos compatibility flag

Generic
d delete a partition
l list known partition types
n add a new partition
p print the partition table
t change a partition type
v verify the partition table

Misc
m print this menu
u change display/entry units
x extra functionality (experts only)

Save & Exit
w write table to disk and exit
q quit without saving changes

Create a new label
g create a new empty GPT partition table
G create a new empty SGI (IRIX) partition table
o create a new empty DOS partition table
s create a new empty Sun partition table

Command (m for help): o
Created a new DOS disklabel with disk identifier 0x52c17ed6.

Command (m for help): p
Disk /dev/mmcblk1: 3.6 GiB, 3867148288 bytes, 7553024 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x52c17ed6

Command (m for help): n

Partition type:
p primary (0 primary, 0 extended, 4 free)
e extended
Select (default p): p
Partition number (1-4, default 1): 1
First sector (2048-7553023, default 2048):
Last sector, +sectors or +size{K,M,G,T,P} (2048-7553023, default 7553023): +64M

Created a new partition 1 of type 'Linux' and of size 64 MiB.

Command (m for help): t
Selected partition 1
Hex code (type L to list all codes): e
If you have created or modified any DOS 6.x partitions, please see the fdisk documentation for additional information.
Changed type of partition 'Linux' to 'W95 FAT16 (LBA)'.

Command (m for help): a
Selected partition 1
The bootable flag on partition 1 is enabled now.

Command (m for help): p
Disk /dev/mmcblk1: 3.6 GiB, 3867148288 bytes, 7553024 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x52c17ed6

Device Boot Start End Blocks Id System
/dev/mmcblk1p1 * 2048 133119 65536 e W95 FAT16 (LBA)

Command (m for help): n

Partition type:
p primary (1 primary, 0 extended, 3 free)
e extended
Select (default p): p
Partition number (2-4, default 2): 2
First sector (133120-7553023, default 133120):
Last sector, +sectors or +size{K,M,G,T,P} (133120-7553023, default 7553023):

Created a new partition 2 of type 'Linux' and of size 3.6 GiB.

Command (m for help): p
Disk /dev/mmcblk1: 3.6 GiB, 3867148288 bytes, 7553024 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x52c17ed6

Device Boot Start End Blocks Id System
/dev/mmcblk1p1 * 2048 133119 65536 e W95 FAT16 (LBA)
/dev/mmcblk1p2 133120 7553023 3709952 83 Linux

Command (m for help): w

The partition table has been altered.
Calling ioctl() to re-read partition table.
mmcblk1: p1 p2
Syncing disks.

root@beaglebone:~# mkfs.vfat -F 16 /dev/mmcblk1p1
-sh: mkfs.vfat: command not found

root@beaglebone:~# mkfs.ext4 /dev/mmcblk1p2
mke2fs 1.42.9 (28-Dec-2013)
Discarding device blocks: done
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
232000 inodes, 927488 blocks
46374 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=952107008
29 block groups
32768 blocks per group, 32768 fragments per group
8000 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736

Allocating group tables: done
Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done

root@beaglebone:~#

root@am335x-evm:~# fdisk /dev/mmcblk1
Welcome to fdisk (util-linux 2.22.2).

Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

Command (m for help): p

Disk /dev/mmcblk1: 3867 MB, 3867148288 bytes, 7553024 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x52c17ed6

Device Boot Start End Blocks Id System
/dev/mmcblk1p1 * 2048 133119 65536 e W95 FAT16 (LBA)
/dev/mmcblk1p2 133120 7553023 3709952 83 Linux

Command (m for help): ^C
root@am335x-evm:~#

root@am335x-evm:~# ls
boot root
root@am335x-evm:~#

root@am335x-evm:~# cd boot
root@am335x-evm:~/boot# ls
MLO u-boot.img
root@am335x-evm:~# cd root/
root@am335x-evm:~/root# ls
bin dev home media proc run sys usr www
boot etc lib mnt rootfs sbin tmp var
root@am335x-evm:~/root/boot# ls
image.fit uImage-3.14.0-yocto-standard
uImage
root@am335x-evm:~# mount /dev/mmcblk1p1 boot
root@am335x-evm:~# cd boot
root@am335x-evm:~/boot# ls
MLO u-boot.img
root@am335x-evm:~# umount boot
root@am335x-evm:~# mount /dev/mmcblk1p2 root
root@am335x-evm:~# umount root

root@am335x-evm:~# CCCCCCCC

Kindly do the needful as early as possible

Many Thanks in advance again,

Hi Srini,

1)But Could you please provide me the detailed steps how this images can be copied from SD card to emmc

2)I have partitioned eMMC as below, I mounted boot folder & copied MLO & uboot.img, mounted root & copied my rootfs contents to root folder & image.fit to /home/root/root/boot/,
through scp from my host to the target , then I had shutdown the BeagleBone Black, removed the SD-Card, then reapplied power source to it.

Are you able to see the content which you written in eMMC through SD boot ?

Did you ever boot from eMMC without using "image.fit" ?

Hi TiTus,

I am able to see the contents after copying MLO, uboot.img of ti-sdk-am335x-evm-07.00.00.00 after mounting /dev/mmcblk1p1 onto boot & rootfs contents onto root

Till now am trying eMMC without image.fit only, I am using the same SD card images onto eMMC

But now able to get till uboot prompt where it is looking for uEnv.txt , As discussed previously, I tried to modify it in several ways to make the kernel to boot & get the prompt, but I was unable to succeed further

Could you please provide me the contents to be added in uEnv.txt, inorder to boot the kernel as this am stuck with this.

And Could you please let me know in general, how much time it takes for booting eMMC, after programming eMMC through the Ivans method

Kindly do the needful as early as possible, as am stuck only with this uEnv.txt to get the prompt in eMMC

Thanks a lot for all your quick support Titus so far & appreciate the same

Thanks in advance again

Hi Ivan,

Am following your steps, am able to get till uboot prompt with the above steps

Could you please provide uEnv.txt,  I tried modifying it in several ways I couldn't succeed hope this is blocking

from my side,

Could you please provide this uEnv.txt for booting from eMMC

Many Thanks in advance

Hi Titus,

Could you please provide any updates w.r.t the above thread

Thanks in advance,

Hi Srini,

Now, you able to boot eMMC upto u-boot stage right ?

Have you tried the same procedure with "image.fit" with "u-boot.img"  and able to get u-boot shell atleast ?

You can also boot eMMC for kernel & filesystem if you know the exact location of kernel and filesystem partition and we can avoid "uEnv.txt"

I will also ask my colleague to provide the uEnv.txt file.

Hi Titus,

Thanks a lot for your quick response

I mounted eMMC partitions as below

(This is the 1st partition of the eMMC)

# mkdir /mnt/p1 ; mount /dev/mmcblk1p1 /mnt/p1

(This is the 2st partition of the eMMC)
mkdir /mnt/p2 ; mount /dev/mmcblk1p2 /mnt/p2

(This is the 1st partition of the SD card)
# mkdir /mnt/sd1 ; mount /dev/mmcblk0p1 /mnt/sd1
(This is the 2nd partition of the SD card)
# mkdir /mnt/sd2 ; mount /dev/mmcblk0p2 /mnt/sd2

root@am335x-evm:/# cd /mnt/p1
root@am335x-evm:/mnt/p1# ls
MLO u-boot-2013.img u-boot.img uEnv.txt

root@am335x-evm:/# mount /dev/mmcblk1p2 /mnt/p2
root@am335x-evm:/# cd /mnt/p2
root@am335x-evm:/mnt/p2# ls
Settings dev lib opt sbin tmp www
bin etc media proc srv usr
boot home mnt run sys var
root@am335x-evm:/mnt/p2# cd boot/
root@am335x-evm:/mnt/p2/boot# ls
am335x-bone.dtb devicetree-zImage-am335x-evmsk.dtb
am335x-boneblack.dtb image.fit
am335x-evm.dtb uImage
am335x-evmsk.dtb vmlinux-3.12.10-ti2013.12.01
devicetree-zImage-am335x-bone.dtb zImage
devicetree-zImage-am335x-boneblack.dtb zImage-3.12.10-ti2013.12.01
devicetree-zImage-am335x-evm.dtb

I rebooted & stopped in the uboot prompt, I have given the below arguments

setenv bootargs console=ttyO0,115200n8 quiet root=/dev/mmcblk1p2 ro rootfstype=ext4 rootwait
ext2load mmc 1:2 82000000 /boot/image.fit
bootm 82000000

I rebooted & captured the logs below, but am unable to get the shell prompt, am stuck with this Titus,

Could you please let me know how to resolve this issue, as am trying this from many days, pls do the needful as early as possible

[19/11/14 - 11:16:44:837] U-Boot SPL 2013.10-g78d8ebd (Mar 30 2014 - 20:46:34)
[19/11/14 - 11:16:45:383] reading args
[19/11/14 - 11:16:45:383] spl: error reading image args, err - -1
[19/11/14 - 11:16:45:383] reading u-boot.img
[19/11/14 - 11:16:45:383] reading u-boot.img
[19/11/14 - 11:16:45:430]
[19/11/14 - 11:16:45:430]
[19/11/14 - 11:16:45:430] U-Boot 2014.07 (Nov 10 2014 - 19:07:12)
[19/11/14 - 11:16:45:430]
[19/11/14 - 11:16:45:493] I2C: ready
[19/11/14 - 11:16:45:493] DRAM: 512 MiB
[19/11/14 - 11:16:45:851] MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
[19/11/14 - 11:16:45:914] Using default environment
[19/11/14 - 11:16:45:914]
[19/11/14 - 11:16:46:007] Net: <ethaddr> not set. Validating first E-fuse MAC
[19/11/14 - 11:16:46:054] Phy not found
[19/11/14 - 11:16:46:054] cpsw, usb_ether
[19/11/14 - 11:16:47:070] Hit any key to stop autoboot: 0
[19/11/14 - 11:16:47:086] Card did not respond to voltage select!
[19/11/14 - 11:16:47:101] Card did not respond to voltage select!
[19/11/14 - 11:16:47:148] switch to partitions #0, OK
[19/11/14 - 11:16:47:148] mmc1(part 0) is current device
[19/11/14 - 11:16:47:211] SD/MMC found on device 1
[19/11/14 - 11:16:47:211] reading uEnv.txt
[19/11/14 - 11:16:47:226] ** Unable to read file uEnv.txt **
[19/11/14 - 11:16:47:242] ** File not found /boot/zImage **
[19/11/14 - 11:16:47:242] ## Error: "nandboot" not defined
[19/11/14 - 11:16:47:772] U-Boot#
[19/11/14 - 11:16:48:006] U-Boot#
U-Boot# setenv bootargs console=ttyO0,115200n8 quiet r [19/11/14 - 11:17:40:654] oot=/dev/mmcblk1p2 ro rootfstype=ext4 rootwait
[19/11/14 - 11:17:45:681] U-Boot# ext2load mmc 1:2 82000000 /boot/image.fit
[19/11/14 - 11:17:46:055] 5795330 bytes read in 368 ms (15 MiB/s)
[19/11/14 - 11:17:53:685] U-Boot# bootm 82000000
[19/11/14 - 11:17:53:701] ## Loading kernel from FIT Image at 82000000 ...
[19/11/14 - 11:17:53:701] Using 'conf@1' configuration
[19/11/14 - 11:17:53:701] Verifying Hash Integrity ... OK
[19/11/14 - 11:17:53:701] Trying 'kernel@1' kernel subimage
[19/11/14 - 11:17:53:716] Description: unavailable
[19/11/14 - 11:17:53:716] Created: 2014-11-10 13:33:37 UTC
[19/11/14 - 11:17:53:716] Type: Kernel Image
[19/11/14 - 11:17:53:716] Compression: lzo compressed
[19/11/14 - 11:17:53:716] Data Start: 0x820000a8
[19/11/14 - 11:17:53:732] Data Size: 5758684 Bytes = 5.5 MiB
[19/11/14 - 11:17:53:732] Architecture: ARM
[19/11/14 - 11:17:53:732] OS: Linux
[19/11/14 - 11:17:53:732] Load Address: 0x80008000
[19/11/14 - 11:17:53:732] Entry Point: 0x80008000
[19/11/14 - 11:17:53:732] Hash algo: sha1
Hash value: c062786df7ea2eb179cf4acbc68782cdb68 [19/11/14 - 11:17:53:748] 9a670
[19/11/14 - 11:17:53:857] Verifying Hash Integrity ... sha1+ OK
[19/11/14 - 11:17:53:857] ## Loading fdt from FIT Image at 82000000 ...
[19/11/14 - 11:17:53:872] Using 'conf@1' configuration
[19/11/14 - 11:17:53:872] Trying 'fdt@1' fdt subimage
[19/11/14 - 11:17:53:872] Description: beaglebone-black
[19/11/14 - 11:17:53:872] Created: 2014-11-10 13:33:37 UTC
[19/11/14 - 11:17:53:872] Type: Flat Device Tree
[19/11/14 - 11:17:53:888] Compression: uncompressed
[19/11/14 - 11:17:53:888] Data Start: 0x8257e06c
[19/11/14 - 11:17:53:888] Data Size: 34352 Bytes = 33.5 KiB
[19/11/14 - 11:17:53:888] Architecture: ARM
[19/11/14 - 11:17:53:888] Hash algo: sha1
Hash value: 4b14973cf0fe4a40dc420ed55d2441c6f51 [19/11/14 - 11:17:53:904] f586b
[19/11/14 - 11:17:53:904] Verifying Hash Integrity ... sha1+ OK
[19/11/14 - 11:17:53:904] Booting using the fdt blob at 0x8257e06c
[19/11/14 - 11:17:54:044] Uncompressing Kernel Image ... OK
Loading Device Tree to 8fff4000, end 8ffff62f ... O [19/11/14 - 11:17:54:059] K
[19/11/14 - 11:17:54:059]
[19/11/14 - 11:17:54:075] Starting kernel ...
[19/11/14 - 11:17:54:075]
[ 0.131341] platform mpu.1: FIXME: clock-name 'fck' [19/11/14 - 11:17:54:449] DOES NOT exist in dt!
[ 0.132172] platform 49000000.edma: FIXME: clock-na [19/11/14 - 11:17:54:465] me 'fck' DOES NOT exist in dt!
[ 0.139185] platform 56000000.sgx: FIXME: clock-nam [19/11/14 - 11:17:54:465] e 'fck' DOES NOT exist in dt!
[19/11/14 - 11:17:54:481] [ 0.140692] DSS not supported on this SoC
[ 0.360750] mtdoops: mtd device (mtddev=name/number [19/11/14 - 11:17:54:496] ) must be supplied
[ 0.471539] cpu cpu0: cpu0 regulator not ready, ret [19/11/14 - 11:17:54:605] ry
[ 0.487690] dummy 0-0034: Error -121 writing to cec [19/11/14 - 11:17:54:621] :0xff
[ 0.493357] tda998x 0-0070: Error -121 reading from [19/11/14 - 11:17:54:637] 0xa
[ 0.498931] tda998x 0-0070: Error -121 writing to 0 [19/11/14 - 11:17:54:637] xa
[ 0.557514] tda998x 0-0070: Error -121 reading from [19/11/14 - 11:17:54:699] 0xa
[ 0.563058] tda998x 0-0070: Error -121 writing to 0 [19/11/14 - 11:17:54:699] xa
[ 0.627478] tda998x 0-0070: Error -121 reading from [19/11/14 - 11:17:54:761] 0x1
[ 0.633010] tda998x 0-0070: Error -121 writing to 0 [19/11/14 - 11:17:54:761] x1
[ 0.638368] tda998x 0-0070: Error -121 reading from [19/11/14 - 11:17:54:777] 0x1
[ 0.643898] tda998x 0-0070: Error -121 writing to 0 [19/11/14 - 11:17:54:777] x1
[ 0.649255] tda998x 0-0070: Error -121 writing to R [19/11/14 - 11:17:54:793] EG_CURPAGE
[ 0.655331] tda998x 0-0070: Error -121 writing to 0 [19/11/14 - 11:17:54:793] x200
[ 0.660871] tda998x 0-0070: Error -121 writing to 0 [19/11/14 - 11:17:54:793] x201
[ 0.666400] tda998x 0-0070: Error -121 writing to 0 [19/11/14 - 11:17:54:808] x202
[ 0.671939] tda998x 0-0070: Error -121 writing to 0 [19/11/14 - 11:17:54:808] x203
[ 0.677478] tda998x 0-0070: Error -121 writing to 0 [19/11/14 - 11:17:54:808] x204
[ 0.683008] tda998x 0-0070: Error -121 writing to 0 [19/11/14 - 11:17:54:824] x205
[ 0.688548] tda998x 0-0070: Error -121 writing to 0 [19/11/14 - 11:17:54:824] x20e
[ 0.694077] tda998x 0-0070: Error -121 writing to 0 [19/11/14 - 11:17:54:824] x211
[ 0.699617] tda998x 0-0070: Error -121 writing to 0 [19/11/14 - 11:17:54:839] x207
[ 0.705147] tda998x 0-0070: Error -121 writing to 0 [19/11/14 - 11:17:54:839] x208
[ 0.710685] tda998x 0-0070: Error -121 writing to 0 [19/11/14 - 11:17:54:839] x209
[ 0.716214] tda998x 0-0070: Error -121 writing to 0 [19/11/14 - 11:17:54:855] x20a
[ 0.721754] tda998x 0-0070: Error -121 writing to 0 [19/11/14 - 11:17:54:855] x206
[ 0.727283] tda998x 0-0070: Error -121 writing to R [19/11/14 - 11:17:54:871] EG_CURPAGE
[ 0.733369] tda998x 0-0070: Error -121 reading from [19/11/14 - 11:17:54:871] 0x0
[ 0.738909] tda998x 0-0070: Error -121 reading from [19/11/14 - 11:17:54:871] 0x2
[19/11/14 - 11:18:54:460] [ 60.327798] PM: request_firmware failed

Many Thanks in advance agian

Hi Srini,

Sounds good.

I'm glad that you were able to solve the problem.

Also I'm appreciating your effort on this.

Thanks for your update and for your solutions and it could help other community members too.