DRA722: U-BOOT

Hi Sasikumar,

Which version is your SDK?
Can you stop at the u-boot, execute printenv and post the output?
Can you also show the contents of uEnv.txt?

Regards,
Yordan

MY SDK version is ti-glsdk_dra7xx-evm_7_04_00_03

contents of uEnv -mmcargs=part uuid mmc 0:2 uuid; setenv bootargs "console=ttyO0,115200n8 elevator=noop root=PARTUUID=${uuid} rw rootwait earlyprintk fixrtc omapdrm.num_crtc=2 consoleblank=0 cma=64M rootfstype=ext4 snd.slots_reserved=1,1"

U-Boot# dfu 0 mmc 1
ERROR: "dfu_alt_info" env variable not defined!
pri dfu_alt_info_emmc
dfu_alt_info_emmc=rawemmc raw 0 3751936;boot part 1 1;rootfs part 1 2;MLO fat 1 1;MLO.raw raw 0x100 0x100;u-boot.img.raw raw 0x200 0x400;spl-os-args.raw raw 0x80 0x80;spl-os-image.raw raw 0x900 0x2000;spl-
os-args fat 1 1;spl-os-image fat 1 1;u-boot.img fat 1 1;uEnv.txt fat 1 1
U-Boot#
dfu_alt_info_emmc=rawemmc raw 0 3751936;boot part 1 1;rootfs part 1 2;MLO fat 1 1;MLO.raw raw 0x100 0x100;u-boot.img.raw raw 0x200 0x400;spl-os-args.raw raw 0x80 0x80;spl-os-image.raw raw 0x900 0x2000;spl-
os-args fat 1 1;spl-os-image fat 1 1;u-boot.img fat 1 1;uEnv.txt fat 1 1
U-Boot#
dfu_alt_info_emmc=rawemmc raw 0 3751936;boot part 1 1;rootfs part 1 2;MLO fat 1 1;MLO.raw raw 0x100 0x100;u-boot.img.raw raw 0x200 0x400;spl-os-args.raw raw 0x80 0x80;spl-os-image.raw raw 0x900 0x2000;spl-
os-args fat 1 1;spl-os-image fat 1 1;u-boot.img fat 1 1;uEnv.txt fat 1 1
U-Boot# dfu 0 mmc 1
ERROR: "dfu_alt_info" env variable not defined!

at drivers/dfu/dfu.c:55/dfu_init_env_entities()
exit not allowed from main input shell.
U-Boot# setenv dfu_alt_info ${dfu_alt_info_emmc}
U-Boot# pri dfu_alt_info_emmc                   
dfu_alt_info_emmc=rawemmc raw 0 3751936;boot part 1 1;rootfs part 1 2;MLO fat 1 1;MLO.raw raw 0x100 0x100;u-boot.img.raw raw 0x200 0x400;spl-os-args.raw raw 0x80 0x80;spl-os-image.raw raw 0x900 0x2000;spl-
os-args fat 1 1;spl-os-image fat 1 1;u-boot.img fat 1 1;uEnv.txt fat 1 1
U-Boot# dfu 0 mmc 1                             
set_config: high speed config #1: usb_dnload













U-Boot# dfu 0 mmc 1
set_config: high speed config #1: usb_dnload
#############################################################################################################################################################################################################
#############################################################################################################################################################################################################
#############################################################################################################################################################################################################
#############################################################################################################################################################################################################
############################################################################################################################################################################Request would exceed designated a
rea!
#Request would exceed designated area!
#Request would exceed designated area!
#Request would exceed designated area!
#Request would exceed designated area!
#Request would exceed designated area!
#Request would exceed designated area!
#Request would exceed designated area!
#Request would exceed designated area!
#Request would exceed designated area!

some times when iload boot.img and then when i check sudo dfu-util -l it is not showing boot and root fs partition and how to flash zimage so please help me out..

this is my u-boot prompt output

jasminuser@jasminuser:~/usbboot_bins$ sudo minicom -w
[sudo] password for jasminuser:


Welcome to minicom 2.5

OPTIONS: I18n
Compiled on May 2 2011, 10:05:24.
Port /dev/ttyUSB0

Press CTRL-A Z for help on special keys


U-Boot SPL 2014.07-dirty (Jul 19 2017 - 18:44:09)
DRA752-GP ES2.0
Bypassing DPLL failed 4a008180
Using default environment

set_config: high speed config #1: usb_dnload
######DOWNLOAD ... OK
Ctrl+C to exit ...
@
U-Boot SPL 2014.07-dirty (Jul 19 2017 - 18:44:09)
DRA752-GP ES2.0
Bypassing DPLL failed 4a008180
Using default environment

set_config: high speed config #1: usb_dnload
################################################################################
################################################################################
################################################################################
################################################################################
################################################################################
################################################################################
################################################################################
################################################################################
################################################################################
################################################################################
################################################################################
################################################################################
################################DOWNLOAD ... OK
Ctrl+C to exit ...
SATA link 0 timeout.
AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: 64bit ncq stag pm led clo only pmp pio slum part ccc apst
scanning bus for devices...
Found 0 device(s).
SCSI: Net: <ethaddr> not set. Validating first E-fuse MAC
cpsw
Hit any key to stop autoboot: 0
Card did not respond to voltage select!
Card did not respond to voltage select!
switch to partitions #0, OK
mmc1(part 0) is current device
SD/MMC found on device 1
** Invalid partition 1 **
** Invalid partition 2 **
U-Boot#
U-Boot#
U-Boot#
U-Boot# printenv
arch=arm
baudrate=115200
board=dra7xx
board_name=dra7xx
board_rev=H.0
bootcmd=run findfdt; run mmcboot;setenv mmcdev 1; setenv bootpart 1:2; setenv mm
croot /dev/mmcblk0p2 rw; run mmcboot;
bootdelay=1
bootdir=/boot
bootenv=uEnv.txt
bootfile=zImage
bootm_size=0x10000000
bootpart=1:2
bootscript=echo Running bootscript from mmc${mmcdev} ...; source ${loadaddr}
console=ttyO0,115200n8
cpu=armv7
dfu_alt_info_emmc_spl=rawemmc raw 0 14680064;MLO.raw raw 0x100 0x100;u-boot.img.
raw raw 0x200 0x400;spl-os-args.raw raw 0x80 0x80;spl-os-image.raw raw 0x900 0x2
000;spl-os-args fat 1 1;spl-os-image fat 1 1;u-boot.img fat 1 1;uEnv.txt fat 1 1
dfu_bufsiz=0x10000
eth1addr=a0:f6:fd:9e:6f:5b
ethact=cpsw
ethaddr=a0:f6:fd:9e:6f:5a
fdt_addr_r=0x88000000
fdtaddr=0x88000000
fdtfile=dra7-evm-lcd10.dtb
findfdt=if test $board_name = omap5_uevm; then setenv fdtfile omap5-uevm.dtb; fi
; if test $board_name = dra7xx; then setenv fdtfile dra7-evm-lcd10.dtb; fi;if te
st $board_name = dra72x; then setenv fdtfile dra72-evm-lcd10.dtb; fi;if test $bo
ard_name = beagle_x15; then setenv fdtfile am57xx-beagle-x15.dtb; fi;if test $fd
tfile = undefined; then echo WARNING: Could not determine device tree to use; fi
;
importbootenv=echo Importing environment from mmc${mmcdev} ...; env import -t ${
loadaddr} ${filesize}
kernel_addr_r=0x82000000
loadaddr=0x82000000
loadbootenv=fatload mmc ${mmcdev} ${loadaddr} ${bootenv}
loadbootscript=fatload mmc ${mmcdev} ${loadaddr} boot.scr
loadfdt=load mmc ${bootpart} ${fdtaddr} ${bootdir}/${fdtfile};
loadimage=load mmc ${bootpart} ${loadaddr} ${bootdir}/${bootfile}
mmcargs=setenv bootargs console=${console} ${optargs} vram=${vram} root=${mmcroo
t} rootfstype=${mmcrootfstype}
mmcboot=mmc dev ${mmcdev}; if mmc rescan; then echo SD/MMC found on device ${mmc
dev};if run loadbootenv; then echo Loaded environment from ${bootenv};run import
bootenv;fi;if test -n $uenvcmd; then echo Running uenvcmd ...;run uenvcmd;fi;if
run loadimage; then run loadfdt; echo Booting from mmc${mmcdev} ...; run mmcargs
; bootz ${loadaddr} - ${fdtaddr}; fi;fi;
mmcdev=1
mmcroot=/dev/mmcblk0p2 rw
mmcrootfstype=ext4 rootwait
netargs=setenv bootargs console=${console} ${optargs} root=/dev/nfs nfsroot=${se
rverip}:${rootpath},${nfsopts} rw ip=dhcp
netboot=echo Booting from network ...; set env autoload no; dhcp; tftp ${loadadd
r} ${bootfile}; tftp ${fdtaddr} ${fdtfile}; run netargs; bootz ${loadaddr} - ${f
dtaddr}
partitions=uuid_disk=${uuid_gpt_disk};name=rootfs,start=2MiB,size=-,uuid=${uuid_
gpt_rootfs}
ramdisk_addr_r=0x88080000
rdaddr=0x88080000
scsidevs=0
serial#=2e6408f037a400a2
soc=omap5
stderr=serial
stdin=serial
stdout=serial
usbtty=cdc_acm
vendor=ti
ver=U-Boot 2014.07-dirty (Jul 19 2017 - 18:44:09)
vram=16M

Environment size: 2814/131067 bytes
U-Boot#

Hi Sasikumar,

I have forwarded your question to bootloader expert.

Regards,
Yordan

Hi Sasikumar,

Which board are you using? The subject of this thread indicates its DRA722, however the logs indicate that the board is a DRA74x EVM. 

As part of the package there's a set of prebuilt images, does flashing these images work? 

Could you please migrate to the latest release? The latest release can be downloaded from here: 
downloads.ti.com/.../index_FDS.html

Regards
Shravan

Hi Karthik,
I already downloaded latest version and flashing the images ara happening properly only my problem is i changed the configuration files according to texas user boot guide i,e...

#define DFU_ALT_INFO_EMMC \
"dfu_alt_info_emmc=" \
"rawemmc raw 0 3751936;" \
"boot part 1 1;" \
"rootfs part 1 2;" \
"MLO fat 1 1;" \
"ZImage ext4 1 2;" \
"dra7-evm-lcd10.dtb ext4 1 2;" \
"README fat 1 1;" \
"MLO.raw raw 0x100 0x100;" \
"u-boot.img.raw raw 0x200 0x400;" \
"spl-os-args.raw raw 0x80 0x80;" \
"spl-os-image.raw raw 0x900 0x2000;" \
"spl-os-args fat 1 1;" \
"spl-os-image fat 1 1;" \
"u-boot.img fat 1 1;" \
"uEnv.txt fat 1 1\0"

and when i run from host sudop dfu-util -l it is not showing zimage and as per described below


Execute "dfu-util -l" from PC host, the new interfaces added will be listed

#sudo dfu-util -l
dfu-util 0.5
(C) 2005-2008 by Weston Schmidt, Harald Welte and OpenMoko Inc.
(C) 2010-2011 Tormod Volden (DfuSe support)
This program is Free Software and has ABSOLUTELY NO WARRANTY
dfu-util does currently only support DFU version 1.0
Found DFU: [0403:bd00] devnum=0, cfg=1, intf=0, alt=0, name="rawemmc"
Found DFU: [0403:bd00] devnum=0, cfg=1, intf=0, alt=1, name="boot"
Found DFU: [0403:bd00] devnum=0, cfg=1, intf=0, alt=2, name="rootfs"
Found DFU: [0403:bd00] devnum=0, cfg=1, intf=0, alt=3, name="MLO"
Found DFU: [0403:bd00] devnum=0, cfg=1, intf=0, alt=4, name="zImage"
Found DFU: [0403:bd00] devnum=0, cfg=1, intf=0, alt=5, name="dra7-evm-lcd10.dtb"
Found DFU: [0403:bd00] devnum=0, cfg=1, intf=0, alt=6, name="README"
Found DFU: [0403:bd00] devnum=0, cfg=1, intf=0, alt=7, name="MLO.raw"
Found DFU: [0403:bd00] devnum=0, cfg=1, intf=0, alt=8, name="u-boot.img.raw"
Found DFU: [0403:bd00] devnum=0, cfg=1, intf=0, alt=9, name="spl-os-args.raw"
Found DFU: [0403:bd00] devnum=0, cfg=1, intf=0, alt=10, name="spl-os-image.raw"
Found DFU: [0403:bd00] devnum=0, cfg=1, intf=0, alt=11, name="spl-os-args"
Found DFU: [0403:bd00] devnum=0, cfg=1, intf=0, alt=12, name="spl-os-image"
Found DFU: [0403:bd00] devnum=0, cfg=1, intf=0, alt=13, name="u-boot.img"
Found DFU: [0403:bd00] devnum=0, cfg=1, intf=0, alt=14, name="uEnv.txt"


so let me know solution for my problem..............

and one more is i partitioned the sd card into boot and rootfs and when i load boot image it is not entering into u-boot environment i am getting the error
U-Boot SPL 2014.07 (Mar 24 2016 - 23:56:19)
DRA752-GP ES2.0
spl_mmc_load_image
** Partition 1 not valid on device 1 **
spl_register_fat_device: fat register err - -1
### ERROR ### Please RESET the board ###


and when i make entire partition for boot image it is working fine..so if i did like this i am unable to upgrade the rootfs image

Hi Sasikumar,

Can you confirm that your emmc is partitioned into a boot and rootfs partition and you aren't using the raw partition?

Could you reset your environment to the default u-boot environment by running the below commands on target 

U-Boot # env default -f -a

U-Boot # saveenv

Once you run the above steps you should be able to see zImage in the list of partitions when you run the dfu-util -l' command on your PC. Can you confirm this? 

If the above step succeeds you should be able to transfer the zImage using DFU. To make-sure that the transfer is correct, can you memory dump the zImage from u-boot and compare it with the hexdump of the zImage on the PC? This will ensure that the zImage transfer using DFU is successful.

Regards
Shravan

Dear Karthik,
How to confirm eMMC is partitioned into boot and roofs...

Can you try the below commands from U-boot:

       #Uboot: mmc dev 1 (sets the device as emmc)

       #Uboot: mmc part  (lists the partitions on emmc)

You may find this section on the processor wiki-guide useful which lists how the partitions are mapped to dfu-util

processors.wiki.ti.com/.../Linux_Core_U-Boot_User's_Guide

Ya..I am getting and showing the partitions and those are mapped to dfu-util and after that can u tell me the procedure how to load zImage and in my case it is not showing the partition for zImage and device tree even though i changed the ti_omap5_common.h file i,e..MACRO for eMMC was changed.

What changes did you make to the eMMC macro in ti_omap5_common. file? And what are the reasons for these changes? The default macro itself should have the necessary environment variables set.

Dear karthik,
My output is came like this..
U-Boot# mmc dev 1
switch to partitions #0, OK
mmc1(part 0) is current device
U-Boot# mmc part

Partition Map for MMC device 1 -- Partition Type: DOS

Part Start Sector Num Sectors UUID Type
1 2048 126976 6f300e81-01 0c Boot
2 129024 14997504 6f300e81-02 83

Hi,
I changed according to DRA7XX user guide they told to add zImage ..

Adding a custom file to DFU configuration

1. Add a custom/new file to the root directory of existing rootfs(ext4) or boot(vfat) partition of sdcard and flash the filesystem raw disk images to eMMC. For example consider the file zImage, dra7-evm-lcd10.dtb is added to root directory of rootfs(ext4) and README file in boot(vfat) partition. Make sure file read/write permission is set.
2. From u-boot source repository, edit the file include/configs/dra7xx_evm.h, add a new entry to DFU_ALT_INFO_EMMC macro.

#define DFU_ALT_INFO_EMMC \
"dfu_alt_info_emmc=" \
"rawemmc raw 0 3751936;" \
"boot part 1 1;" \
"rootfs part 1 2;" \
"MLO fat 1 1;" \
"ZImage ext4 1 2;" \
"dra7-evm-lcd10.dtb ext4 1 2;" \
"README fat 1 1;" \
"MLO.raw raw 0x100 0x100;" \
"u-boot.img.raw raw 0x200 0x400;" \
"spl-os-args.raw raw 0x80 0x80;" \
"spl-os-image.raw raw 0x900 0x2000;" \
"spl-os-args fat 1 1;" \
"spl-os-image fat 1 1;" \
"u-boot.img fat 1 1;" \
"uEnv.txt fat 1 1\0"

3. Compile the u-boot to create MLO, u-boot.img and load MLO/u-boot.img to EVM
4. Execute "dfu-util -l" from PC host, the new interfaces added will be listed

Hi Sasikumar,

Can you set the macro DFU_ALT_INFO_EMMC to the same as that defined for DFU_ALT_INFO_MMC? Once you make the change and rebuild u-boot, run the below command from the modified u-boot.

U-boot# dfu 0 mmc 1

After this run the 'dfu-util -l' command on the PC? You should be able to see the zImage option

and from host side when i am trying to update MLO and u-boot.img i am getting errors in u-boot environment

** Unable to use mmc 1:1 for fatwrite **
dfu: Read error!
DOWNLOAD ... OK
Ctrl+C to exit ...
######
** Unable to use mmc 1:1 for fatwrite **
dfu: Read error!
DOWNLOAD ... OK
Ctrl+C to exit ...

Before entering into u-boot only i modified the files and builded the MLO and u-boot.img but i am unable to see zImage from host

Environment size: 3259/131067 bytes
U-Boot# dfu 0 mmc 1
set_config: high speed config #1: usb_dnload
######writing u-boot.img
389704 bytes written
DOWNLOAD ... OK
Ctrl+C to exit ...
###writing MLO
147764 bytes written
DOWNLOAD ... OK
Ctrl+C to exit ...

Hi,
when i type boot in U-boot prompt i am getting the below msg

U-Boot# boot
Card did not respond to voltage select!
SD/MMC found on device 0
Card did not respond to voltage select!
** Bad device mmc 0 **
Card did not respond to voltage select!
** Bad device mmc 0 **
switch to partitions #0, OK
mmc1(part 0) is current device
SD/MMC found on device 1
** Unrecognized filesystem type **
** File not found /boot/zImage **

Hi Sasikumar,

In DFU_ALT_INFO_EMMC can you remove the entry "ZImage ext4 1 2;". Update the entry "spl-os-image fat 1 1;" with "spl-os-image ext4 1 2;". And from your host PC run

host@: sudo dfu-util -D zImage -a spl-os-image

Any particular reason you're using DFU to transfer images? The same can be achieved using UMS as well. UMS will mount the FAT and ext4 partitions on your system, and you can copy the zImage to the boot folder in the rootfs.

Regards
Shravan

Hi karthik,
And presently i am trying to get zImage and if i get zImage then can i boot the kernel from emmc?

And one more thing is i already tried for ums i am getting error message....
U-Boot# ums 0 mmc 1
Unknown command 'ums' - try 'help'

I am getting below error message when i tried ums.
U-Boot# ums 0 mmc 1
Unknown command 'ums' - try 'help'

Hi,
I tried as per your suggestion it is working fine i,e..zImage is copied succesfully but it is not showing on host side and when i type boot in u-boot prompt i am getting the below error message....


U-Boot# boot
switch to partitions #0, OK
mmc1(part 0) is current device
SD/MMC found on device 1
reading uEnv.txt
195 bytes read in 1 ms (190.4 KiB/s)
Loaded environment from uEnv.txt
Importing environment from mmc1 ...
** File not found /boot/zImage **
switch to partitions #0, OK
mmc1(part 0) is current device
SD/MMC found on device 1
reading uEnv.txt
195 bytes read in 2 ms (94.7 KiB/s)
Loaded environment from uEnv.txt
Importing environment from mmc1 ...
** File not found /boot/zImage **
U-Boot#


U-Boot# boot
switch to partitions #0, OK
mmc1(part 0) is current device
SD/MMC found on device 1
reading uEnv.txt
195 bytes read in 1 ms (190.4 KiB/s)
Loaded environment from uEnv.txt
Importing environment from mmc1 ...
** File not found /boot/zImage **
switch to partitions #0, OK
mmc1(part 0) is current device
SD/MMC found on device 1
reading uEnv.txt
195 bytes read in 2 ms (94.7 KiB/s)
Loaded environment from uEnv.txt
Importing environment from mmc1 ...
** File not found /boot/zImage **
U-Boot#

even though i changed file i am getting fro u-boot prompt

U-Boot# printenv dfu_alt_info_emmc
dfu_alt_info_emmc=rawemmc raw 0 3751936;boot part 1 1;rootfs part 1 2;MLO fat 1 1;MLO.raw raw 0x100 0x100;u-boot.img.raw raw 0x200 0x400;spl-os-args.raw raw 0x80 0x80;spl-os-image.raw raw 0x900 0x2000;spl-os-args fat 1 1;spl-os-image fat 1 1;u-boot.img fat 1 1;uEnv.txt fat 1 1 i,e....spl-os-image is not changinf to ext4 2

Hi Sasikumar,

If you want to copy the zImage to emmc (rootfs partition), you can can use ums. As indicated run the below command on u-boot, 

U-boot# ums 0 mmc 1

You should notice the emmc partition show up on your PC, copy the zImage to the boot folder of the rootfs partition and Linux should start booting.

Regards

Shravan

Hello karthik,
I am unable to boot kernel i,e.. zImage from eMMC can u please help me out?


U-Boot# boot
switch to partitions #0, OK
mmc1(part 0) is current device
SD/MMC found on device 1
reading uEnv.txt
221 bytes read in 2 ms (107.4 KiB/s)
Loaded environment from uEnv.txt
Importing environment from mmc1 ...
** File not found /boot/zImage **
switch to partitions #0, OK
mmc1(part 0) is current device
SD/MMC found on device 1
reading uEnv.txt
221 bytes read in 2 ms (107.4 KiB/s)
Loaded environment from uEnv.txt
Importing environment from mmc1 ...
** File not found /boot/zImage **
U-Boot#

HI shravan,
I tried but it is showing

U-Boot# ums 0 mmc 1
Unknown command 'ums' - try 'help'

Hi Sasikumar,

Can you please migrate to a later version of u-boot? From the logs I realize that the version of U-boot you're using is 2014-07. We have UMS support enabled in latest release. You can mount your emmc partitions on the PC and transfer the necessary files. You can find the latest release here:

processors.wiki.ti.com/.../Category:Processor_SDK_Linux_Automotive

 

You're zImage is getting copied to the rootfs partition, however it isn't being copied into the boot folder in the rootfs partition, which is causing the issue. 

Regards

Shravan

HI,
For latest SDK installation it is asking ubuntu 14.04 but currently i am having 12.04 shall i need to upgrade to 14.04 LTS to use the ums in u-boot prompt

Hi Sasikumar,

Yes we would recommend upgrading to 14.04 to ensure all the components of the SDK can be built.

Regards
Shravan

Are you sure it will work in ubuntu 14.04 because once i upgraded i cannot come back to ubuntu 12.04 untill and unless i reinstall the OS &Why zImage is unable to flash in eMMC & in previous versions of SDK?

There is support to flash images to emmc on the older SDK, however this is on raw partitions. The release you're using is old with limited support, and would recommend you move to the latest release, where there are more features supported. Please migrate to 14.04 with the latest release as some components of the SDK don't work on 12.04 (eg. yocto builds) 

processors.wiki.ti.com/.../DRA7xx_GLSDK_Software_Developers_Guide

I dnt want to updgrade to 14.04 if i upgrade i need to change the entire kernel configuration for my current GLSDK project so please help me how to transfer the kernel images by using earlier version of GLSDK and u-boot environment

Hi Sasikumar,

Are you using the TI evm? You can create a bootable SD-card and use this to flash the emmc. 

1. Create bootable SD-card: 

downloads.ti.com/.../DRA7xx_GLSDK_Software_Developers_Guide.html

2. Create bootable emmc: 

http://downloads.ti.com/infotainment/esd/jacinto6/glsdk/7_04_00_03/exports/DRA7xx_GLSDK_Software_Developers_Guide.html#Using_eMMC_Boot

Regards

Shravan

Hi shravan, The above method is working fine for me and it is entering into U-boot mode but when i run boot command in u-boot prompt kernel is not booting as like as booting from sd card and for fresh factory boards without sd card i have to flash the binary images thats y i am prefering by hsing DFU we can flash the images and finally it has to boot the kernel from eMMC which is not happening in my case..

Hi Sasikumar,

So you're saying that even when you create the SD-card as per instructions mentioned in the Software-Developers-Guide (SDG), you're not able to get to kernel to initialize? Please don't halt at u-boot, and let the u-boot automatically jump to kernel. Are you still not able to see kernel coming up? Please confirm your switch-settings to ensure the board is booting in SD-boot mode.

Switch-settings for SD-boot:

SW2 [7:0]: 0011 0000
SW3 [7:0] : 1000 0001
SW5[9:0]: 00 0001 0100
SW8[1:0]: 11

Regards
Shravan

Hi Shravan, From sd card i can able to boot the kernel but from eMMc by using DFU utility procedure i am unable to get so in the entire procedure i just want to avoid usage of sd card....

Hi Sasikumar,

Since you're able to boot it using the SD-card please follow the steps mentioned here in this link (specifically step 'Partitioning and formatting eMMC').

downloads.ti.com/.../DRA7xx_GLSDK_Software_Developers_Guide.html

The commands have to be run on the target. This will format the EMMC and flash the images needed in the boot and rootfs partition of the EMMC. Once this is complete change the pin-settings (as described in the above link), to boot from EMMC. This way you will be able to boot from EMMC.

Regards
Shravan

Hi shravan, This is working fine for us we actually trying to boot the kernel without involvement of sd card thats why we are using the DFU procedure for flashing the images in this case we are facing the issue to boot the kernel from eMMC

Hi Sasikumar,

Can you alter the file 'include/configs/ti_omap5_common.h' as follows:

Change the contents of the macro CONFIG_EXTRA_ENV_SETTINGS

change
"loadimage=load mmc ${bootpart} ${loadaddr} ${bootdir}/${bootfile}\0"
to
"loadimage=load mmc ${bootpart} ${loadaddr} /${bootfile}\0"


and change

"loadfdt=load mmc ${bootpart} ${fdtaddr} ${bootdir}/${fdtfile};\0"

to

"loadfdt=load mmc ${bootpart} ${fdtaddr} /${fdtfile};\0"


Regards
Shravan