Linux/TDA2: Linux boot problem from Micro SD card

Archit Adwant

Intellectual 710 points

Part Number: TDA2
Other Parts Discussed in Thread: DRA742, PMP, DRA752, DRA72

Tool/software: Linux

Hello,

Have built the vision SDK for linux for the TDA2xx EVM5777BG

Created the SD card.

the two partitions viz boot and root are created and have the contents as mentioned in the user manual.

When i try to boot the board with the micro SD card, i get the following errors on the UART console.

i do not get the login prompt.

Pls. advise.

Thanks and Regards,

-----------------------------------------------------------------------------------------------------------------------------------
U-Boot SPL 2016.05-00010-g9551b3d23ef3 (Nov 26 2018 - 09:04:39)
DRA752-GP ES1.1
no pinctrl for ddr_1_8v
** First descriptor is NOT a primary desc on 1:1 **
*** Warning - bad CRC, using default environment

Trying to boot from MMC1
reading dra7-ipu2-fw.lzop
spl_load_file_fat: error reading file dra7-ipu2-fw.lzop, err - -1
spl: error reading image dra7-ipu2-fw.lzop, err - -1
Error loading remotecore IPU2!,Continuing with boot ...
reading dra7-dsp1-fw.lzop
spl_load_file_fat: error reading file dra7-dsp1-fw.lzop, err - -1
spl: error reading image dra7-dsp1-fw.lzop, err - -1
Error loading remotecore DSP1!,Continuing with boot ...
reading dra7-dsp2-fw.lzop
spl_load_file_fat: error reading file dra7-dsp2-fw.lzop, err - -1
spl: error reading image dra7-dsp2-fw.lzop, err - -1
Error loading remotecore DSP2!,Continuing with boot ...
reading dra7-ipu1-fw.lzop
spl_load_file_fat: error reading file dra7-ipu1-fw.lzop, err - -1
spl: error reading image dra7-ipu1-fw.lzop, err - -1
Error loading remotecore IPU1!,Continuing with boot ...
*** Warning - bad CRC, using default environment

reading u-boot.img
reading u-boot.img
reading u-boot.img
reading u-boot.img

U-Boot 2016.05-00010-g9551b3d23ef3 (Nov 26 2018 - 09:04:39 +0530)

GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
part_get_info_efi: *** ERROR: Invalid GPT ***
GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
part_get_info_efi: *** ERROR: Invalid Backup GPT ***
ERROR: cannot find partition: 'userdata'

Usage:
mmc info - display info of the current MMC device
mmc read addr blk# cnt
mmc write addr blk# cnt
mmc erase blk# cnt
mmc rescan
mmc part - lists available partition on current mmc device
mmc dev [dev] [part] - show or set current mmc device [partition]
mmc list - lists available devices
mmc hwpartition [args...] - does hardware partitioning
arguments (sizes in 512-byte blocks):
[user [enh start cnt] [wrrel {on|off}]] - sets user data area attributes
[gp1|gp2|gp3|gp4 cnt [enh] [wrrel {on|off}]] - general purpose partition
[check|set|complete] - mode, complete set partitioning completed
WARNING: Partitioning is a write-once setting once it is set to complete.
Power cycling is required to initialize partitions after set to complete.
mmc bootbus dev boot_bus_width reset_boot_bus_width boot_mode
- Set the BOOT_BUS_WIDTH field of the specified device
mmc bootpart-resize <dev> <boot part size MB> <RPMB part size MB>
- Change sizes of boot and RPMB partitions of specified device
mmc partconf dev boot_ack boot_partition partition_access
- Change the bits of the PARTITION_CONFIG field of the specified device
mmc rst-function dev value
- Change the RST_n_FUNCTION field of the specified device
WARNING: This is a write-once field and 0 / 1 / 2 are the only valid values.
mmc setdsr <value> - set DSR register value

mmc - MMC sub system

Booting from eMMC ...
Wrong Image Format for bootm command
ERROR: can't get kernel image!
=>

over 6 years ago

0 Dwarakesh Radhakrishnan over 6 years ago

Guru 13660 points

Hi,

zImage needs to be present in in root partition /boot folder. Can you confirm if it is available.

0 Dwarakesh Radhakrishnan over 6 years ago in reply to Dwarakesh Radhakrishnan

Guru 13660 points

Hi,

I think you need to follow the steps here, looks like there is error in partition creation too: software-dl.ti.com/.../Overview_Getting_Started_Guide.html

0 Yordan Kamenov over 6 years ago

TI__Mastermind 42515 points

Hi Archit,

can you stop at the u-boot prompt and run following commands:

env default -f -a
saveenv

and try again?

Regards,
Yordan

0 Archit Adwant over 6 years ago in reply to Dwarakesh Radhakrishnan

Intellectual 710 points

ZImage in present in the boot folder of the root file system.

Also, i am using the SDK and documentation from the following link.

http://www.ti.com/tool/PROCESSOR-SDK-TDAX

THis seems different from the link suggested.

Kindly advice.

Regards,

Archit Adwant

0 Dwarakesh Radhakrishnan over 6 years ago in reply to Archit Adwant

Guru 13660 points

Hi Archit,

Yes, I missed to note it to be vision sdk. The link you are following is correct. Please make sure mmc device is correct. You can follow the step suggested by Yordan to jump to the default env and see.

0 Archit Adwant over 6 years ago in reply to Dwarakesh Radhakrishnan

Intellectual 710 points

Hi,

Tried the env default -f -a

and the saveenv commands ( lines 206 and 210) in the attached log.

Still the problem persists.

I am using a smaller micro SD card currently. Only 2 GB, but the image is smaller, so seems to be sufficient.

The targetfs tar is approx 800 MB.

Kindly advise.

Thanks and Regards,

U-Boot SPL 2016.05-00010-g9551b3d23ef3 (Nov 26 2018 - 09:04:39)
DRA752-GP ES1.1
no pinctrl for ddr_1_8v
** First descriptor is NOT a primary desc on 1:1 **
*** Warning - bad CRC, using default environment

reading u-boot.img
reading u-boot.img
reading u-boot.img
reading u-boot.img

U-Boot 2016.05-00010-g9551b3d23ef3 (Nov 26 2018 - 09:04:39 +0530)

mmc - MMC sub system

Booting from eMMC ...
Wrong Image Format for bootm command
ERROR: can't get kernel image!
=>
U-Boot SPL 2016.05-00010-g9551b3d23ef3 (Nov 26 2018 - 09:04:39)
DRA752-GP ES1.1
no pinctrl for ddr_1_8v
** First descriptor is NOT a primary desc on 1:1 **
*** Warning - bad CRC, using default environment

reading u-boot.img
reading u-boot.img
reading u-boot.img
reading u-boot.img

U-Boot 2016.05-00010-g9551b3d23ef3 (Nov 26 2018 - 09:04:39 +0530)

at arch/arm/cpu/armv7/omap-common/utils.c:199/mmc_get_part_size()
Warning: fastboot.userdata_size: unable to calc
SCSI: 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).
Net:
Warning: ethernet@48484000 using MAC address from ROM
eth0: ethernet@48484000
Hit any key to stop autoboot: 0
=> env default -f -a
## Resetting to default environment
=> saveend
Unknown command 'saveend' - try 'help'
=> saveenv
Saving Environment to MMC...
Writing to redundant MMC(1)... done
=>
U-Boot SPL 2016.05-00010-g9551b3d23ef3 (Nov 26 2018 - 09:04:39)
DRA752-GP ES1.1
no pinctrl for ddr_1_8v
** First descriptor is NOT a primary desc on 1:1 **
Trying to boot from MMC1
reading dra7-ipu2-fw.lzop
spl_load_file_fat: error reading file dra7-ipu2-fw.lzop, err - -1
spl: error reading image dra7-ipu2-fw.lzop, err - -1
Error loading remotecore IPU2!,Continuing with boot ...
reading dra7-dsp1-fw.lzop
spl_load_file_fat: error reading file dra7-dsp1-fw.lzop, err - -1
spl: error reading image dra7-dsp1-fw.lzop, err - -1
Error loading remotecore DSP1!,Continuing with boot ...
reading dra7-dsp2-fw.lzop
spl_load_file_fat: error reading file dra7-dsp2-fw.lzop, err - -1
spl: error reading image dra7-dsp2-fw.lzop, err - -1
Error loading remotecore DSP2!,Continuing with boot ...
reading dra7-ipu1-fw.lzop
spl_load_file_fat: error reading file dra7-ipu1-fw.lzop, err - -1
spl: error reading image dra7-ipu1-fw.lzop, err - -1
Error loading remotecore IPU1!,Continuing with boot ...
reading u-boot.img
reading u-boot.img
reading u-boot.img
reading u-boot.img

U-Boot 2016.05-00010-g9551b3d23ef3 (Nov 26 2018 - 09:04:39 +0530)

CPU : DRA752-GP ES1.1
Model: TI DRA742
Board: DRA74x EVM REV G.0
DRAM: 1.5 GiB
MMC: mmc@4809c000: fail to find hs-rev11 mode FDT_ERR_NOTFOUND
mmc@4809c000: fail to find sdr25-rev11 mode FDT_ERR_NOTFOUND
mmc@4809c000: fail to find sdr12-rev11 mode FDT_ERR_NOTFOUND
mmc@480b4000: fail to find hs-rev11 mode FDT_ERR_NOTFOUND
OMAP SD/MMC: 0, OMAP SD/MMC: 1
** First descriptor is NOT a primary desc on 1:1 **
GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
part_get_info_efi: *** ERROR: Invalid GPT ***
GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
part_get_info_efi: *** ERROR: Invalid Backup GPT ***
ERROR: cannot find partition: 'userdata'

mmc - MMC sub system

Booting from eMMC ...
Wrong Image Format for bootm command
ERROR: can't get kernel image!
=>

0 Dwarakesh Radhakrishnan over 6 years ago in reply to Archit Adwant

Guru 13660 points

Hi Archit,

Looks like there is similar issue here: e2e.ti.com/.../709450

Please follow the suggestion in the link

0 Archit Adwant over 6 years ago in reply to Dwarakesh Radhakrishnan

Intellectual 710 points

Hi,

I am still facing the problem.

I check i the micro SD card size was a problem. Used a 32GB card. but still problem persists.

Also, the target fs is only approx 800 MB. So that should not be an issue.

Browsed the code a bit. It seems that u-boot is not able to find the kernel image at all.

Looks like some wrong arguments are passed to be bootm command.

Do i need to set the board type to something specific, so that it gets the right bootm command line arguments?

The micro SD card has 2 partitions.

First is the boot ( which is FAT). it has the MLO, u-boot.img, and the uenv.txt.

The other partition is the root partition. It is ext4. It has the targetfs extracted. It has the uImage, zImage and the dtb files in the /boot folder.

Do i need to copy the iImage file in the boot filer?

I am stuck on this. So requesting urgent support please.

Thanks and Regards,

Achit

0 Yordan Kamenov over 6 years ago in reply to Archit Adwant

TI__Mastermind 42515 points

Hi Achit,

can you stop at u-boot prompt and run "printenv" command and show the output?

Regards,
Yordan

0 Archit Adwant over 6 years ago in reply to Yordan Kamenov

Intellectual 710 points

Hi,
The following is the output of printenv command at the u-boot prompt.

------------------------------------
=> printenv
arch=arm
args_fit=setenv bootargs console=${console}
args_mmc=run finduuid;setenv bootargs console=${console} ${optargs} root=PARTUUID=${uuid} rw r
ootfstype=${mmcrootfstype}
baudrate=115200
board=dra7xx
board_name=dra7xx
board_rev=G.0
boot_fdt=try
boot_fit=0
boot_os=0
bootargs=androidboot.serialno=${serial#}
bootcmd=if test ${dofastboot} -eq 1; then echo Boot fastboot requested, resetting dofastboot .
..;setenv dofastboot 0; saveenv;echo Booting into fastboot ...; fastboot 0; fi;if test ${boot_
fit} -eq 1; then run update_to_fit;fi;run findfdt; run envboot; run mmcboot;run emmc_android_b
oot;
bootdelay=2
bootdir=/boot
bootenvfile=uEnv.txt
bootfile=zImage
bootm_size=0x10000000
bootpart=0:2
bootscript=echo Running bootscript from mmc${mmcdev} ...; source ${loadaddr}
console=ttyO0,115200n8
cpu=armv7
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 0x300 0x1000;u-env.raw raw 0x1300 0x200;spl-os-args.raw raw 0x1
500 0x200;spl-os-image.raw raw 0x1700 0x6900;spl-os-args fat 1 1;spl-os-image fat 1 1;u-boot.i
mg fat 1 1;uEnv.txt fat 1 1
dfu_alt_info_mmc=boot part 0 1;rootfs part 0 2;MLO fat 0 1;MLO.raw raw 0x100 0x100;u-boot.img.
raw raw 0x300 0x1000;u-env.raw raw 0x1300 0x200;spl-os-args.raw raw 0x1500 0x200;spl-os-image.
raw raw 0x1700 0x6900;spl-os-args fat 0 1;spl-os-image fat 0 1;u-boot.img fat 0 1;uEnv.txt fat
0 1
dfu_alt_info_qspi=MLO raw 0x0 0x040000;u-boot.img raw 0x040000 0x0100000;u-boot-spl-os raw 0x1
40000 0x080000;u-boot-env raw 0x1C0000 0x010000;u-boot-env.backup raw 0x1D0000 0x010000;kernel
raw 0x1E0000 0x800000
dfu_alt_info_ram=kernel ram 0x80200000 0x4000000;fdt ram 0x80f80000 0x80000;ramdisk ram 0x8100
0000 0x4000000
dfu_bufsiz=0x10000
dofastboot=0
emmc_android_boot=setenv eval_bootargs setenv bootargs $bootargs; run eval_bootargs; setenv mm
cdev 1; setenv fdt_part 3; setenv boot_part 9; if test $reboot_image = recovery; then setenv b
oot_part 8; setenv reboot_image boot; saveenv; fi;setenv machid fe6; mmc dev $mmcdev; mmc resc
an; part start mmc ${mmcdev} ${fdt_part} fdt_start; part size mmc ${mmcdev} ${fdt_part} fdt_si
ze; part start mmc ${mmcdev} ${boot_part} boot_start; part size mmc ${mmcdev} ${boot_part} boo
t_size; mmc read ${fdtaddr} ${fdt_start} ${fdt_size}; mmc read ${loadaddr} ${boot_start} ${boo
t_size}; echo Booting from eMMC ...; bootm $loadaddr $loadaddr $fdtaddr;
envboot=mmc dev ${mmcdev}; if mmc rescan; then echo SD/MMC found on device ${mmcdev};if run lo
adbootscript; then run bootscript;else if run loadbootenv; then echo Loaded env from ${bootenv
file};run importbootenv;fi;if test -n $uenvcmd; then echo Running uenvcmd ...;run uenvcmd;fi;f
i;fi;
ethaddr=d4:f5:13:b3:8e:36
fastboot.board_rev=G.0
fastboot.cpu=DRA752
fastboot.secure=GP
fastboot.userdata_size=unknown
fdt_addr_r=0x88000000
fdtaddr=0x88000000
fdtcontroladdr=def0b438
fdtfile=undefined
findfdt=if test $board_name = omap5_uevm; then setenv fdtfile omap5-uevm.dtb; fi; if test $boa
rd_name = dra7xx; then setenv fdtfile dra7-evm.dtb; fi;if test $board_name = dra72x-revc; then
setenv fdtfile dra72-evm-revc.dtb; fi;if test $board_name = dra72x; then setenv fdtfile dra72
-evm.dtb; fi;if test $board_name = dra71x; then setenv fdtfile dra71-evm.dtb; fi;if test $boar
d_name = dra76x; then setenv fdtfile dra76-evm.dtb; fi;if test $board_name = beagle_x15; then
setenv fdtfile am57xx-beagle-x15.dtb; fi;if test $board_name = beagle_x15_revb1; then setenv f
dtfile am57xx-beagle-x15-revb1.dtb; fi;if test $board_name = am57xx_evm; then setenv fdtfile a
m57xx-evm.dtb; fi;if test $board_name = am57xx_evm_reva3; then setenv fdtfile am57xx-evm-reva3
.dtb; fi;if test $board_name = am572x_idk && test $idk_lcd = no; then setenv fdtfile am572x-id
k.dtb; fi;if test $board_name = am572x_idk && test $idk_lcd = osd101t2045; then setenv fdtfile
am572x-idk-lcd-osd.dtb; fi;if test $board_name = am572x_idk && test $idk_lcd = osd101t2587; t
hen setenv fdtfile am572x-idk-lcd-osd101t2587.dtb; fi;if test $board_name = am571x_idk && test
$idk_lcd = no; then setenv fdtfile am571x-idk.dtb; fi;if test $board_name = am571x_idk && tes
t $idk_lcd = osd101t2045; then setenv fdtfile am571x-idk-lcd-osd.dtb; fi;if test $board_name =
am571x_idk && test $idk_lcd = osd101t2587; then setenv fdtfile am571x-idk-lcd-osd101t2587.dtb
; fi;if test $board_findfdt != undefined; then run board_findfdt; fi;if test $fdtfile = undefi
ned; then echo WARNING: Could not determine device tree to use; fi;
finduuid=part uuid mmc ${bootpart} uuid
fit_bootfile=fitImage.itb
fit_loadaddr=0x88000000
importbootenv=echo Importing environment from mmc${mmcdev} ...; env import -t ${loadaddr} ${fi
lesize}
kernel_addr_r=0x82000000
loadaddr=0x82000000
loadbootenv=fatload mmc ${mmcdev} ${loadaddr} ${bootenvfile}
loadbootscript=fatload mmc ${mmcdev} ${loadaddr} boot.scr
loadfdt=load ${devtype} ${bootpart} ${fdtaddr} ${bootdir}/${fdtfile}
loadfit=run args_fit; bootm ${loadaddr}#${fdtfile};
loadimage=load mmc ${bootpart} ${loadaddr} ${bootdir}/${bootfile}
mmcboot=if mmc dev ${mmcdev}; then setenv devtype mmc; if mmc rescan; then echo SD/MMC found o
n device ${mmcdev};if run loadimage; then run loadfdt; echo Booting from mmc${mmcdev} ...; run
args_mmc; bootz ${loadaddr} - ${fdtaddr}; fi; fi; fi;
mmcdev=0
mmcloados=run args_mmc; if test ${boot_fdt} = yes || test ${boot_fdt} = try; then if run loadf
dt; then bootz ${loadaddr} - ${fdtaddr}; else if test ${boot_fdt} = try; then bootz; else echo
WARN: Cannot load the DT; fi; fi; else bootz; fi;
mmcrootfstype=ext4 rootwait
netargs=setenv bootargs console=${console} ${optargs} root=/dev/nfs nfsroot=${serverip}:${root
path},${nfsopts} rw ip=dhcp
netboot=echo Booting from network ...; setenv autoload no; dhcp; run netloadimage; run netload
fdt; run netargs; bootz ${loadaddr} - ${fdtaddr}
netloadfdt=tftp ${fdtaddr} ${fdtfile}
netloadimage=tftp ${loadaddr} ${bootfile}
nfsopts=nolock
partitions=uuid_disk=${uuid_gpt_disk};name=rootfs,start=2MiB,size=-,uuid=${uuid_gpt_rootfs}
partitions_android=uuid_disk=${uuid_gpt_disk};name=xloader,start=128K,size=256K,uuid=${uuid_gp
t_xloader};name=bootloader,size=2304K,uuid=${uuid_gpt_bootloader};name=environment,size=256K,u
uid=${uuid_gpt_environment};name=misc,size=128K,uuid=${uuid_gpt_misc};name=reserved,size=384K,
uuid=${uuid_gpt_reserved};name=efs,size=16M,uuid=${uuid_gpt_efs};name=crypto,size=16K,uuid=${u
uid_gpt_crypto};name=recovery,size=30M,uuid=${uuid_gpt_recovery};name=boot,size=10M,uuid=${uui
d_gpt_boot};name=system,size=768M,uuid=${uuid_gpt_system};name=vendor,size=256M,uuid=${uuid_gp
t_vendor};name=cache,size=256M,uuid=${uuid_gpt_cache};name=ipu1,size=8M,uuid=${uuid_gpt_ipu1};
name=ipu2,size=8M,uuid=${uuid_gpt_ipu2};name=dsp1,size=8M,uuid=${uuid_gpt_dsp1};name=dsp2,size
=8M,uuid=${uuid_gpt_dsp2};name=userdata,size=-,uuid=${uuid_gpt_userdata}
pxefile_addr_r=0x80100000
ramdisk_addr_r=0x88080000
rdaddr=0x88080000
reboot_image=boot
rootpath=/export/rootfs
scriptaddr=0x80000000
scsidevs=0
serial#=0600601170e00121
soc=omap5
static_ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off
stderr=serial@4806a000
stdin=serial@4806a000
stdout=serial@4806a000
update_to_fit=setenv loadaddr ${fit_loadaddr}; setenv bootfile ${fit_bootfile}
usbtty=cdc_acm
vendor=ti
ver=U-Boot 2016.05-00010-g9551b3d23ef3 (Nov 26 2018 - 09:04:39 +0530)
vram=16M

Environment size: 7459/131067 bytes
=> <INTERRUPT>
=>
------------------------------------

0 Archit Adwant over 6 years ago in reply to Archit Adwant

Intellectual 710 points

hi,

Also find the output of a few mmc commands below.

=> mmc dev
** First descriptor is NOT a primary desc on 1:1 **
switch to partitions #0, OK
mmc1(part 0) is current device

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

=> mmc dev
** First descriptor is NOT a primary desc on 1:1 **
switch to partitions #0, OK
mmc1(part 0) is current device
=> mmc part

## Unknown partition table type 0

=> mmc part
## Unknown partition table type 0

=> mmc info
Device: OMAP SD/MMC
Manufacturer ID: fe
OEM: 14e
Name: MMC08
Tran Speed: 52000000
Rd Block Len: 512
MMC version 4.5
High Capacity: Yes
Capacity: 7.3 GiB
Bus Width: 8-bit DDR
Erase Group Size: 512 KiB
HC WP Group Size: 8 MiB
User Capacity: 7.3 GiB WRREL
Boot Capacity: 8 MiB ENH
RPMB Capacity: 128 KiB ENH

=> mmc rescan
** First descriptor is NOT a primary desc on 1:1 **

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

** First descriptor is NOT a primary desc on 1:1 **
switch to partitions #0, OK
mmc1(part 0) is current device
=> <INTERRUPT>
=>

0 Yordan Kamenov over 6 years ago in reply to Archit Adwant

TI__Mastermind 42515 points

Hi Archit,

can you make sure your sysboot pins are set correctly for sd boot as described in chapter "4.2 Preparing SD card & Boot" in VisionSDK_Linux_UserGuide.pdf.
Also ensure your kernel and u-boot are at the right branch shown in the same document and the build and sd card creation went without errors.
Make sure fdtfile in your uenv.txt is set to "fdtfile=dra7-evm-infoadas.dtb".

Regards,
Yordan

0 Archit Adwant over 6 years ago in reply to Yordan Kamenov

Intellectual 710 points

Hi Yordan,

I checked the sysboot pins. These are as described in the document.
i think, since u-boot is taking control, it is booting from SD card. Also tried removing the SD and then booting. It fails.

The build was successful. The kernel image and binaries were created.
There are copied to the mentioned location in the targetfs ( the /boot folder and the opt/firmware)
Also, the u-boot, MLO and the uenv.txt are copied to the /boot partition.
the targetfs is copied and extracted to the /root partiion on the micro SD card.

The uenv.txt has the fdtfile as mentioned above.

The only probable suspected cause might be that i am using ubuntu on top of virtual box.
i think due to this reason the mksdboot script fails sometimes. It fails with the message "unable to mount /dev/sdb1.." this is unpredictable. it also works sometimes.
do not know any apparent reason for this.
it also succeeds some times.
So, i think there might be problem when the script is trying to partition or format the SD card. May be interference from underlying windows? Any idea about this. Can this be a possible cause of trouble.
As such the card does get mounted and in accessible from linux.

Alternately, can the card be prepared manually, instead of using the script. Is there any way to confirm the card is created perfectly.

also, evaluating possibly using nfs to boot the system.

Requesting your advice.
Thanks and Regards,

Archit Adwant

0 Shravan Karthik over 6 years ago in reply to Archit Adwant

TI__Genius 14650 points

Hi Archit,

Since your file-system is present in SD, in the file uenv.txt can you set 'root=/dev/mmcblk1p2' instead of root=PARTUUID=${uuid} and give it a try?

Regards
Shravan

0 Archit Adwant over 6 years ago in reply to Shravan Karthik

Intellectual 710 points

Hi Shravan,

Tried it out.
Problem persists.
the uenv.txt file on the boot partition in the SD card is like this.
-----------------------------------------------------------------------------
fdtfile=dra7-evm-infoadas.dtb
args_mmc=part uuid mmc 0:2 uuid; setenv bootargs "console=ttyO0,115200n8 vram=16M root=/dev/mmcblk1p2 rw rootwait ip=none mem=1024M cma=64M"

-----------------------------------------------------------------------------------
the mmc list and mmc dev and mmc part commands output is same as listed above.
can i try and nfs in this scenario?
Not sure why the partition is not visible.

Kindly advise

Thanks and Regards,

Archit Adwant

0 Archit Adwant over 6 years ago in reply to Archit Adwant

Intellectual 710 points

this is now the /boot folder in the root partition on the SD card looks like

0 Archit Adwant over 6 years ago in reply to Archit Adwant

Intellectual 710 points

I checked the micro SD card by connecting it to the PC, via a reader.
Both the partitions are mounted on ubuntu linux.
The root partition is also visible ( as in the snap shot above) with its contents. I am using ubuntu 18.04.
So, if the partition is recognized on desktop, then is it realy a SD card preparation issue?
Or is it a compatibility issue. May be u-boot is older version or so...?

0 Shravan Karthik over 6 years ago in reply to Archit Adwant

TI__Genius 14650 points

Hi Archit,

Can you set the root as root=/dev/mmcblk0p2 instead (maybe the MMC is being enumerated as mmcblk0 instead of mmcblk1 -- rare but possible).
If the issue still persits can you reflash the card (preferably using a new card), and after reflashing, the first time you boot, halt at u-boot and run
=> env default -fa
=> saveenv

and reboot.

You can revert changes to the uenv.txt file too.

I assume you're working off a release, with no changes to u-boot/kernel.

Regards
Shravan

0 Archit Adwant over 6 years ago in reply to Shravan Karthik

Intellectual 710 points

Hi,

I tried mmcblk0p2. It did not work.

trying out the env default option after a rebuild.
I am using the release as it is . No changes to u-boot.
Some more observations.
I tried the fatls, ext2ls, and ext4ls commands.
the following are the output.s
the same sd card gets mounted properly on ubuntu desktop and shows the partition as ext4.
So, file system if mismatch or similar, due to which u-boot cannot recognize the ext4 file system?
Will update after the rebuild, and the default option.

THanks and Regards,
Archit Adwant

=> ext4ls mmc 1
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
=> ext2ls mmc 1
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
=> fatls mmc 0
system volume information/
127316 mlo
820356 u-boot.img
171 uenv.txt

3 file(s), 1 dir(s)

0 Archit Adwant over 6 years ago in reply to Archit Adwant

Intellectual 710 points

HI,

Is it possible to provide me with a prebuilt binary image of u-boot, uenv.txt and MLO, which i can try and put on the boot partition and see it it loads the rootfs and the kernel?

It it fails, then i know it is partition problem.

Thanks and Regards,

Archit Adwant

0 Shravan Karthik over 6 years ago in reply to Archit Adwant

TI__Genius 14650 points

Hi Archit,

Attached the pre-built boot partition which successfully boots to Linux (its a tar.gz file). Please let us know if this works (you may want to run env default -fa and saveenv on the first boot).

Regards

Shravan

boot.tar.gz.txt

0 Archit Adwant over 6 years ago in reply to Shravan Karthik

Intellectual 710 points

Thanks Shravan,

I tried the files.
Copied all three files (MLO, u-boot image, uenv.txt) to the boot partition on the micro SD card, and tried to boot the board.
I got exactly the same result.
--------------------------------------
Booting from eMMC ...
Wrong Image Format for bootm command
ERROR: can't get kernel image!
--------------------------------------
So, since this is a working image, it seems the ext4 partition created on ubuntu 18 is not being recognized by u-boot.
i will try to format the card using a ubuntu 16 machine and check.
Can NFS work in this scenario?
Also, can any body suggest any minor modifications to uboot can make it read the ext4 partition created on the ubuntu 18 machine.
Kindly let me know.

Thanks and Regards,
Archit Adwant

0 Archit Adwant over 6 years ago in reply to Archit Adwant

Intellectual 710 points

Hi Shravan,

I just checked in the VisionSDK_linux_UserGuide.pdf.
It is mentioned that the host machine needs ubuntu 14.04.
Can you confirm the working version on which the above image has been created, and works?
Has it been tested with ubuntu 16.04 on the host?
kindly confirm.

Thanks and Regards,

Archit Adwant

0 Shravan Karthik over 6 years ago in reply to Archit Adwant

TI__Genius 14650 points

Hi Archit,

Vision-SDK has been tested with Ubuntu-16.04 as the host, there are no issues.
Please check the switch settings for (SYSBOOT and USERCONFIG and SW5 settings).
NFS won't really help as the initialization fails at loading kernel image (NFS is useful when the kernel image is present in the SD card, and the rest of the file-system is accessible over the network).

Regards
Shravan

0 Archit Adwant over 6 years ago in reply to Shravan Karthik

Intellectual 710 points

Hi Shravan, All

Finally i got the EVM to boot into linux.
See log below.
Basically, i used another ubuntu 16.04 machine to format the card, and them simply copied the files built onto the partitions.
It worked.

So, it is either a issue with formatting with Ubuntu 18, or else with the virtual box, while formatting from the Ubuntu 18 hosted inside it.

Will update you once if figure out the exact cause.
Thanks for all the support.

Regards,

Archit Adwant

Processors

Processors forum

Linux/TDA2: Linux boot problem from Micro SD card