Keystone II: can't boot kernel with device tree error

Prathamesh Ghodke

Other Parts Discussed in Thread: 66AK2H12

Hi,

I am getting below error:
TCI6638 EVM #    boot
Using TCI6638_EMAC device
TFTP from server 10.110.1.120; our IP address is 10.110.1.109
Filename '/tftpboot/uImage-k2hk-evm.dtb'.
Load address: 0x87000000
Loading: T #################################################################
   #################################################################
   #################################################################
   #################################################################
   #################################################################
   #################################################################
   ################################
   328.1 KiB/s
done
Bytes transferred = 2155580 (20e43c hex)
Using TCI6638_EMAC device
TFTP from server 10.110.1.120; our IP address is 10.110.1.109
Filename '/tftpboot/skern-k2hk-evm.bin'.
Load address: 0xc5f0000
Loading: #########
   1.4 MiB/s
done
Bytes transferred = 45056 (b000 hex)
Using TCI6638_EMAC device
TFTP from server 10.110.1.120; our IP address is 10.110.1.109
Filename '/tftpboot/uImage-keystone-evm.bin'.
Load address: 0x88000000
Loading: T #################################################################
   #################################################################
   #################################################################
   #################################################################
   #################################################################
   #################################################################
   #################################################################
   #################################################################
   #################################################################
   #################################################################
   #################################################################
   ##############################################################
   509.8 KiB/s
done
Bytes transferred = 3973208 (3ca058 hex)
## installed monitor, freq [133120000], status 133120000
## Booting kernel from Legacy Image at 88000000 ...
   Image Name:   Linux-3.10.10
   Created:      2014-10-02   5:54:16 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3973144 Bytes = 3.8 MiB
   Load Address: 80008000
   Entry Point: 80008000
   Verifying Checksum ... OK
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree
TCI6638 EVM #

Scenario:
Till last weekend we were using it without any issues, from yesterday its giving above error. Sometimes even its not loading EVM prompt. I have tried tweaking most of the key parameters after comparing it with my last working boot parameters configuration, still issue persists.

EVM: 66AK2H12/06 Multicore DSP+ARM KeyStone II System-on-Chip (SoC)
Bootmode: ARM SPI Little Endian mode
Filesystem: Network File System
Linux Images Prebuilt: loading from TFTP
(TFTP Server, NFS Server, Computer System Ubuntu, K2H EVM all are on the same network, connected to the same switch, firewalls are off, even tried connecting with other test Computer).

EVM configuration parameters:
TCI6638 EVM #
addr_fdt=0x87000000
addr_fs=0x82000000
addr_kern=0x88000000
addr_mon=0x0c5f0000
addr_uboot=0x87000000
args_all=setenv bootargs console=ttyS0,115200n8 rootwait=1
args_net=setenv bootargs ${bootargs} rootfstype=nfs root=/dev/nfs rw nfsroot=${serverip}:${nfs_root},${nfs_options} ip=dhcp
args_ramfs=setenv bootargs ${bootargs} earlyprintk rdinit=/sbin/init rw root=/dev/ram0 initrd=0x802000000,9M
args_ubi=setenv bootargs ${bootargs} rootfstype=ubifs root=ubi0:rootfs rootflags=sync rw ubi.mtd=2,2048
baudrate=115200
boot=net
bootargs=console=ttyS0,115200n8 rootwait=1 rootfstype=nfs root=/dev/nfs rw nfsroot=10.110.1.120:/home/poonam/workdir,v3,tcp,rsize=4096,wsize=4096 ip=dhcp
bootcmd=run init_${boot} get_fdt_${boot} get_mon_${boot} get_kern_${boot} run_mon run_kern
bootdelay=3
bootfile=/tftpboot/uImage-k2hk-evm.dtb
burn_uboot=sf probe; sf erase 0 0x100000; sf write ${addr_uboot} 0 ${filesize}
ethact=TCI6638_EMAC
ethaddr=00:17:ea:f7:a6:dd
fdt_high=0xffffffff
fileaddr=88000000
filesize=3CA058
gatewayip=10.110.1.2
get_fdt_net=tftp 0x87000000 /tftpboot/uImage-k2hk-evm.dtb
get_fdt_ramfs=tftp 0x87000000 /tftpboot/uImage-k2hk-evm.dtb
get_fdt_ubi=ubifsload 0x87000000 uImage-k2hk-evm.dtb
get_fs_ramfs=tftp 0x82000000 /tftpboot/arago-console-image.cpio.gz
get_kern_net=tftp 0x88000000 /tftpboot/uImage-keystone-evm.bin
get_kern_ramfs=tftp 0x88000000 /tftpboot/uImage-keystone-evm.bin
get_kern_ubi=ubifsload 0x88000000 uImage-keystone-evm.bin
get_mon_net=tftp 0x0c5f0000 /tftpboot/skern-k2hk-evm.bin
get_mon_ramfs=tftp 0x0c5f0000 /tftpboot/skern-k2hk-evm.bin
get_mon_ubi=ubifsload 0x0c5f0000 skern-keystone-evm.bin
get_uboot_net=tftp 0x87000000 /tftpboot/u-boot-spi-keystone-evm.gph
get_uboot_ramfs=tftp 0x87000000 /tftpboot/u-boot-spi-keystone-evm.gph
has_mdio=0
init_net=run args_all args_net
init_ramfs=run args_all args_ramfs get_fs_ramfs
init_ubi=run args_all args_ubi; ubi part ubifs; ubifsmount boot
ipaddr=10.110.1.109
mem_lpae=1
mem_reserve=536M
name_fdt=uImage-k2hk-evm.dtb
name_fs=arago-console-image.cpio.gz
name_kern=uImage-keystone-evm.bin
name_mon=skern-keystone-evm.bin
name_uboot=u-boot-spi-keystone-evm.gph
nfs_options=v3,tcp,rsize=4096,wsize=4096
nfs_root=/home/poonam/workdir
nfs_serverip=10.110.1.120
run_kern=bootm ${addr_kern} - ${addr_fdt}
run_mon=mon_install ${addr_mon}
serverip=10.110.1.120
set=mem_lpae 1
stderr=serial
stdin=serial
stdout=serial
tftp_root=/tftpboot
ver=U-Boot 2013.01 (May 31 2013 - 01:01:04)

Environment size: 2555/262140 bytes

I am sharing this issue with reference to similar issue raised earlier and addresses by David and Randy:
e2e.ti.com/.../921207

It was recommanded to update uboot initially and later discussion about BMC upgrade, but in this case we were using this EVM without any issues till last week and suddenly we are getting above error. Kindly share your useful thoughts.

Regards,
Prathamesh Ghodke

over 8 years ago

0 Raja over 8 years ago

TI__Guru* 81335 points

Hi Prathamesh,
Please provide below information.

1. MCSDK Version
2. Do you see this error pre-built binaries of MCSDK 3.x?

Thank you.

0 Prathamesh Ghodke over 8 years ago in reply to Raja

Prodigy 120 points

Hi Raja,

Thanks for replying, please find my response below.

1. MCSDK (Multicore Software Development Kit): mcsdk_3_00_04_18: for DSP build tools
2. Desktop Linux SDK: desktop-linux-sdk_01_00_00_07
3. MCSDK Video: mcsdk_video_2_1_0_8

But before running anything using mpmcl, I am getting mentioned error for 'can't boot kernel'. It was working till last weekend till last power off, suddenly from this week its started giving mentioned error.

- Yes, the binaries we are using are pre-built (uImage-k2hk-evm.dtb, skern-k2hk-evm.bin, uImage-keystone-evm.bin).

Regards,
Prathamesh Ghodke

0 Prathamesh Ghodke over 8 years ago in reply to Prathamesh Ghodke

Prodigy 120 points

Hi,

- We are in between of planned tasks, due to these issues from last couple of days, some dependent tasks got delayed.

As per david Zhou's suggestion we should upgrade uboot, kernel, file system to match to the latest version MCSDK 3_01_03_06
software-dl.ti.com/.../index_FDS.html
But apart from planned deadlines, this work can go in another loop. So can somebody please let us know in detail what are troubleshooting steps we can follow, your expert opinion with covering all possible steps, can further save time to resolve this. If you need anymore information please let us know.

Thanks & Regards,
Prathamesh Ghodke

0 Raja over 8 years ago in reply to Prathamesh Ghodke

TI__Guru* 81335 points

Hi,
Did the latest release binaries solved the issue? Because we are not seeing any issues with it.

I suspect there may be file system corrupt. Could please make another nfs setup and export and check?

Thank you.

0 Prathamesh Ghodke over 8 years ago in reply to Raja

Prodigy 120 points

Hi Raja,

- Thanks for your suggestions, as far as I understood, I need to use "uImage-k2hk-evm.dtb", "skern-k2hk-evm.bin", "uImage-keystone-evm.bin" from MCSDK 3_01_03_06, right ?

- As per your suggestion we have re-installed nfs setup and we will share results tomorrow.

Apart from this If any other suggestions?

Regards,

Prathamesh Ghodke

0 Raja over 8 years ago in reply to Prathamesh Ghodke

TI__Guru* 81335 points

- Thanks for your suggestions, as far as I understood, I need to use "uImage-k2hk-evm.dtb", "skern-k2hk-evm.bin", "uImage-keystone-evm.bin" from MCSDK 3_01_03_06, right ?

Yes. Also the root file system from latest release (tisdk-rootfs.tar.gz)

Thank you.

0 Mantripragada Nikhil62 over 8 years ago in reply to Raja

Prodigy 10 points

Hi Raja,

Thanks for your suggestion, I am working on this with Prathamesh.

We have tried "uImage-k2hk-evm.dtb", "skern-k2hk-evm.bin", "uImage-keystone-evm.bin" along with tisdk-rootfs.tar.gz from latest MCSDK 3_01_03_06, still the same error->

## Booting kernel from Legacy Image at 88000000 ...

Image Name: Linux-3.10.10

Created: 2014-10-02 5:54:16 UTC

Image Type: ARM Linux Kernel Image (uncompressed)

Data Size: 3973144 Bytes = 3.8 MiB

Load Address: 80008000

Entry Point: 80008000

Verifying Checksum ... OK

ERROR: Did not find a cmdline Flattened Device Tree

Could not find a valid device tree

Kindly if anybody has any suggestions or anymore information required about this issue, please let us know.

Regards,

Nikhil

0 Titusrathinaraj Stalin over 8 years ago in reply to Mantripragada Nikhil62

TI__Guru** 116100 points

Hi Nikhil,
Could you attach the complete log.
Please make sure that you are using the latest u-boot ( 3_01_03_06) also.

0 Titusrathinaraj Stalin over 8 years ago in reply to Mantripragada Nikhil62

TI__Guru** 116100 points

Hi Nikhil,

Thanks for your reply. Please find below error log for your reference.

TCI6638 EVM # boot

Using TCI6638_EMAC device

TFTP from server 10.110.1.120; our IP address is 10.110.1.109

Filename '/tftpboot/uImage-k2hk-evm.dtb'.

Load address: 0x87000000

Loading: T #################################################################

#################################################################

#################################################################

#################################################################

#################################################################

#################################################################

################################

328.1 KiB/s

done

Bytes transferred = 2155580 (20e43c hex)

Using TCI6638_EMAC device

TFTP from server 10.110.1.120; our IP address is 10.110.1.109

Filename '/tftpboot/skern-k2hk-evm.bin'.

Load address: 0xc5f0000

Loading: #########

1.4 MiB/s

done

Bytes transferred = 45056 (b000 hex)

Using TCI6638_EMAC device

TFTP from server 10.110.1.120; our IP address is 10.110.1.109

Filename '/tftpboot/uImage-keystone-evm.bin'.

Load address: 0x88000000

Loading: T #################################################################

#################################################################

#################################################################

#################################################################

#################################################################

#################################################################

#################################################################

#################################################################

#################################################################

#################################################################

#################################################################

##############################################################

509.8 KiB/s

done

Bytes transferred = 3973208 (3ca058 hex)

## installed monitor, freq [133120000], status 133120000

## Booting kernel from Legacy Image at 88000000 ...

Image Name: Linux-3.10.10

Created: 2014-10-02 5:54:16 UTC

Image Type: ARM Linux Kernel Image (uncompressed)

Data Size: 3973144 Bytes = 3.8 MiB

Load Address: 80008000

Entry Point: 80008000

Verifying Checksum ... OK

ERROR: Did not find a cmdline Flattened Device Tree

Could not find a valid device tree

As per your suggestion we will try with 3_1_3_6 "u-boot-nand-k2hk-evm.gph" , can you please guide us how to do this.

By looking into logs, I suspect that still you are using the older u-boot, if you use newer u-boot you would get "K2HK EVM#" u-boot shell.

Could you please re-flash the newer MCSDK 3.1.3.6 's u-boot with all pre-built binaries.

0 Titusrathinaraj Stalin over 8 years ago in reply to Titusrathinaraj Stalin

TI__Guru** 116100 points

Hi Prathamesh ,

Prathamesh Says said:

I received your response from private chat.

1. You are correct, still we are using older U-boot, we need to try with 3_1_3_6 "u-boot-nand-k2hk-evm.gph" , can you please direct us any guidelines how to flash u-boot?

2. We are not getting reply button while updating for this query, that's why we are sending you private message, can you please guide us, where to raise this issue?

Click the "All Responses" button on your initial reply on this post to get "Reply" button.

Please refer to the following TI wiki page to load the u-boot into RAM for updating new u-boot binary.

processors.wiki.ti.com/.../MCSDK_UG_Chapter_Exploring

After loading the u-boot into MSMCRAM , use the following commands to flash the u-boot binary permanently into flash SPI and NAND.

NAND flash:

tftpboot 0x88000000 u-boot-nand.gph

nand ecclayout set 1

nand erase.part bootloader

nand write 0x88000000 bootloader 0x60000

nand ecclayout set 0

SPI flash:

tftpboot 0x88000000 u-boot-spi.gph

sf probe

sf erase 0 0x100000

sf write 0x88000000 0 0x100000

0 Prathamesh Ghodke over 8 years ago in reply to Titusrathinaraj Stalin

Prodigy 120 points

Thanks Stalin for sharing it, we are trying it, will update you about our progress.

Regards,
Prathamesh

0 Nikhil Mantripragada over 8 years ago in reply to Titusrathinaraj Stalin

Prodigy 100 points

Hi Stalin,

- We are not getting U-boot prompt on K2H EVM to reflash the latest U-boot Image "u-boot-k2hk-evm.bin" of mcsdk_3_1_3_6, if we will get it we need to "run get_uboot_net" and "run burn_uboot" commands on U-boot prompt.

- So can we flash it using CCS? Please direct us how to flash pre-built U-boot Image "u-boot-k2hk-evm.bin" which we have of mcsdk_3_1_3_6, on EVM through CCS.

Thanks and Regards,
Nikhil

0 Titusrathinaraj Stalin over 8 years ago in reply to Nikhil Mantripragada

TI__Guru** 116100 points

Hi,
You can't flash this "u-boot-k2hk-evm.bin" binary into SPI or NAND flash.
We have separate "gph" images, u-boot-spi.gph and u-noot-nand.gph images for SPI and NAND flash images that needs to be compiled.

git clone git://git.ti.com/keystone-linux/u-boot.git u-boot-keystone

cd u-boot-keystone
make k2hk_evm_config ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf-
make u-boot-spi.gph ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf-
make u-boot-nand.gph ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf-

You can load this "u-boot-k2hk-evm.bin" image into MSMCRAM through CCS (loadjs)
Please refer to the below TI wiki.

processors.wiki.ti.com/.../MCSDK_UG_Chapter_Exploring

0 Rex Chang over 8 years ago in reply to Titusrathinaraj Stalin

TI__Guru 50170 points

Hi, Nikhil,

The summary steps for flashing u-boot using CCS:

Set EVM to no boot mode
Launch CCS and connect to ARM core 0
“Load memory” the u-boot.bin to address 0x0c001000
“Load memory” the skern.bin to address 0x0c5f0000
Set PC to 0x0c001000
Click “Resume” to run the uboot and break the boot to be in u-boot prompt
Assuming tftp server has been set up and tftp_root points to the correct directory, perform “run get_uboot_net”, and “run burn_uboot” (be sure the name_uboot is set to u-boot-xxx.gph file)
Once the burn_uboot is completed, disconnect CCS, power off EVM and set the EVM to SPI boot mode
U-boot should come up after EVM powers up

Rex

0 Nikhil Mantripragada over 8 years ago in reply to Titusrathinaraj Stalin

Prodigy 100 points

Hi Stalin,

We flashed the Latest U-boot on K2H EVM using CCS as per the below steps.

The summary steps for flashing u-boot using CCS:

1. Set EVM to no boot mode
2. Launch CCS and connect to ARM core 0
3. “Load memory” the u-boot.bin to address 0x0c001000
4. “Load memory” the skern.bin to address 0x0c5f0000
5. Set PC to 0x0c001000
6. Click “Resume” to run the uboot and break the boot to be in u-boot prompt
7. Assuming tftp server has been set up and tftp_root points to the correct directory, perform “run get_uboot_net”, and “run
burn_uboot” (be sure the name_uboot is set to u-boot-xxx.gph file)
8. Once the burn_uboot is completed, disconnect CCS, power off EVM and set the EVM to SPI boot mode
U-boot should come up after EVM powers up .

I was getting error in the boot process.

addr_fdt=0x87000000
addr_fs=0x82000000
addr_kern=0x88000000
addr_mon=0x0c5f0000
addr_secdb_key=0xc000000
addr_uboot=0x87000000
args_all=setenv bootargs console=ttyS0,115200n8 rootwait=1
args_net=setenv bootargs ${bootargs} rootfstype=nfs root=/dev/nfs rw nfsroot=${serverip}:${nfs_root},${nfs_options} ip=dhcp
args_ramfs=setenv bootargs ${bootargs} rdinit=/sbin/init rw root=/dev/ram0 initrd=0x802000000,9M
args_ubi=setenv bootargs ${bootargs} rootfstype=ubifs root=ubi0:rootfs rootflags=sync rw ubi.mtd=2,2048
baudrate=115200
boot=net
bootargs=console=ttyS0,115200n8 rootwait=1 rootfstype=nfs root=/dev/nfs rw nfsroot=172.17.1.10:/home/poonam/workdir,v3,tcp,rsize=4096,wsize=4096 ip=dhcp
bootcmd=run init_${boot} get_fdt_${boot} get_mon_${boot} get_kern_${boot} run_mon run_kern
bootdelay=3
bootfile=/tftpboot/uImage-k2hk-evm.dtb
burn_uboot=sf probe; sf erase 0 0x100000; sf write ${addr_uboot} 0 ${filesize}
ethact=K2HK_EMAC
ethaddr=00:17:ea:f7:5c:1d
fdt_high=0xffffffff
fileaddr=88000000
filesize=3A45B8
gatewayip=172.17.1.1
get_fdt_net=tftp 0x87000000 /tftpboot/uImage-k2hk-evm.dtb
get_fdt_ramfs=dhcp 0x87000000 /tftpboot/uImage-k2hk-evm.dtb
get_fdt_ubi=ubifsload 0x87000000 uImage-k2hk-evm.dtb
get_fs_ramfs=dhcp 0x82000000 /tftpboot/arago-console-image.cpio.gz
get_kern_net=tftp 0x88000000 /tftpboot/uImage-keystone-evm.bin
get_kern_ramfs=dhcp 0x88000000 /tftpboot/uImage-keystone-evm.bin
get_kern_ubi=ubifsload 0x88000000 uImage-keystone-evm.bin
get_mon_net=tftp 0x0c5f0000 /tftpboot/skern-k2hk-evm.bin
get_mon_ramfs=dhcp 0x0c5f0000 /tftpboot/skern-keystone-evm.bin
get_mon_ubi=ubifsload 0x0c5f0000 skern-keystone-evm.bin
get_ubi_net=dhcp ${addr_ubi} ${tftp_root}/${name_ubi}
get_uboot_net=tftp 0x87000000 /tftpboot/u-boot-spi-k2hk-evm.gph
get_uboot_ramfs=dhcp 0x87000000 /tftpboot/u-boot-spi-keystone-evm.gph
has_mdio=0
init_net=run args_all args_net
init_ramfs=run args_all args_ramfs get_fs_ramfs
init_ubi=run args_all args_ubi
ipaddr=172.17.1.103
mem_lpae=1
mem_reserve=512M
name_fdt=uImage-k2hk-evm.dtb
name_fs=arago-console-image-k2hk-evm.cpio.gz
name_kern=uImage-keystone-evm.bin
name_mon=skern-k2hk-evm.bin
name_ubi=k2hk-evm-ubifs.ubi
name_uboot=u-boot-spi-k2hk-evm.gph
nfs_options=v3,tcp,rsize=4096,wsize=4096
nfs_root=/home/poonam/workdir
nfs_serverip=172.17.1.10
no-post=0
run_kern=bootm ${addr_kern} ${addr_uinitrd} ${addr_fdt}
run_mon=mon_install ${addr_mon}
serverip=172.17.1.10
stderr=serial
stdin=serial
stdout=serial
tftp_root=/tftpboot
ver=U-Boot 2013.01 (Mar 18 2015 - 00:17:01)

Environment size: 2627/262140 bytes
K2HK EVM # boot
Using K2HK_EMAC device
TFTP from server 172.17.1.10; our IP address is 172.17.1.103
Filename '/tftpboot/uImage-k2hk-evm.dtb'.
Load address: 0x87000000
Loading: ##########
1.1 MiB/s
done
Bytes transferred = 48300 (bcac hex)
Using K2HK_EMAC device
TFTP from server 172.17.1.10; our IP address is 172.17.1.103
Filename '/tftpboot/skern-k2hk-evm.bin'.
Load address: 0xc5f0000
Loading: #########
1.2 MiB/s
done
Bytes transferred = 45056 (b000 hex)
Using K2HK_EMAC device
TFTP from server 172.17.1.10; our IP address is 172.17.1.103
Filename '/tftpboot/uImage-keystone-evm.bin'.
Load address: 0x88000000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
###############################
1.2 MiB/s
done
Bytes transferred = 3818936 (3a45b8 hex)
## installed monitor, freq [200000000], status 0
## Booting kernel from Legacy Image at 88000000 ...
Image Name: Linux-3.10.10
Created: 2014-04-24 5:26:45 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3818872 Bytes = 3.6 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Wrong Ramdisk Image Format
Ramdisk image is corrupt or invalid

- Please consider the printed environmental variables. I want to boot the EVM through NFS.

- Placed the latest uboot, kernel and boot monitor control Images of mcsdk-3_1_3_6 inside tftpboot and ensured that all the paths are properly set.

- But I am getting error Ramdisk Image error. Please give your suggestions to resolve the error.

Thanks and Regards,
Nikhil

0 Titusrathinaraj Stalin over 8 years ago in reply to Nikhil Mantripragada

TI__Guru** 116100 points

Hi,
You have to modify the bootargs if board needs to be boot from NFS.

Use the following commands.

Note:
I presume that you have setup the "tftpboot" directory and NFS filesystem directory was properly configured.

Please ask us If any doubts from that configuration.

In my case, I have folder "ks2_fs" in "/usr/local" of PC with all the rootfs files and folders which is configured for NFS root filesytstem and exported.

exportfs -rav
exportfs

If you are not familiar with those things, please let us know, we give you links and will guide you.

processors.wiki.ti.com/.../MCSDK_UG_Chapter_Exploring

1)
Ex:
setenv serverip 10.100.1.94
setenv ipaddr 10.100.1.4

setenv tftp_root mcsdk_03_01_03_06

setenv bootcmd 'tftpboot 0x87000000 ${tftp_root}/k2hk-evm.dtb;tftpboot 0x88000000 ${tftp_root}/uImage;tftpboot 0x0c5f0000 ${tftp_root}/skern-keystone-evm.bin;mon_install 0x0c5f0000;bootm 0x88000000 - 0x87000000'

setenv bootargs 'earlyprintk debug console=ttyS0,115200n8 ip=dhcp rootwait=1 root=/dev/nfs nfsroot=10.100.1.94:/usr/local/ks2_fs,v3,tcp rw'

saveenv

2)
Ex:

env default -a
saveenv
setenv boot net
setenv serverip 10.100.1.94
setenv ipaddr 10.100.1.4
setenv tftp_root mcsdk_03_01_03_06
saveenv
boot

0 Nikhil Mantripragada over 8 years ago in reply to Titusrathinaraj Stalin

Prodigy 100 points

Hi Stalin,

- Followed the steps suggested by you to flash the Latest U-boot and was able to remove earlier error "POST I2C eeprom read ... FAILED" . But as it continues it gives "Wrong Ramdisk Image Format Ramdisk image is corrupt or invalid" error.

- As suggested by Stalin checked bootargs variable is set for NFS or not. So ensured bootargs are proper(setenv bootargs 'earlyprintk debug console=ttyS0,115200n8 ip=dhcp rootwait=1 root=/dev/nfs nfsroot=10.100.1.94:/usr/local/ks2_fs,v3,tcp rw').

- After Rebooting the EVM again it hangs while connecting to terminal itself(It dosen't show the U-boot prompt).

- Kindly share your expert opinion, on how to solve this issue.

Thanks and Regards,
Nikhil

0 Titusrathinaraj Stalin over 8 years ago in reply to Nikhil Mantripragada

TI__Guru** 116100 points

Hi Nikhil,
Able to flash the latest u-boot and boot from NAND or SPI flash ?

0 Nikhil Mantripragada over 8 years ago in reply to Titusrathinaraj Stalin

Prodigy 100 points

Hi Stalin,

Please find the attached environment variables log :

TCI6638 EVM # printenv
addr_fdt=0x87000000
addr_fs=0x82000000
addr_kern=0x88000000
addr_mon=0x0c5f0000
addr_uboot=0x87000000
args_all=setenv bootargs console=ttyS0,115200n8 rootwait=1
args_net=setenv bootargs earlyprintk debug console=ttyS0,115200n8 ip=dhcp rootwait=1 root=/dev/nfs nfsroot=10.110.2.113:/home/poonam/workdir,v3,tcp rw
args_ramfs=setenv bootargs ${bootargs} earlyprintk rdinit=/sbin/init rw root=/dev/ram0 initrd=0x802000000,9M
args_ubi=setenv bootargs ${bootargs} rootfstype=ubifs root=ubi0:rootfs rootflags=sync rw ubi.mtd=2,2048
baudrate=115200
boot=net
bootcmd=run init_${boot} get_fdt_${boot} get_mon_${boot} get_kern_${boot} run_mon run_kern
bootdelay=3
bootfile=/tftpboot/uImage-k2hk-evm.dtb
burn_uboot=sf probe; sf erase 0 0x100000; sf write ${addr_uboot} 0 ${filesize}
ethact=TCI6638_EMAC
ethaddr=00:17:ea:f7:a6:dd
fdt_high=0xffffffff
gatewayip=10.110.1.2
get_fdt_net=tftp 0x87000000 /tftpboot/uImage-k2hk-evm.dtb
get_fdt_ramfs=dhcp 0x87000000 /tftpboot/uImage-k2hk-evm.dtb
get_fdt_ubi=ubifsload 0x87000000 uImage-k2hk-evm.dtb
get_fs_ramfs=dhcp 0x82000000 /tftpboot/arago-console-image.cpio.gz
get_kern_net=tftp 0x88000000 /tftpboot/uImage-keystone-evm.bin
get_kern_ramfs=dhcp 0x88000000 /tftpboot/uImage-keystone-evm.bin
get_kern_ubi=ubifsload 0x88000000 uImage-keystone-evm.bin
get_mon_net=tftp 0x0c5f0000 /tftpboot/skern-k2hk-evm.bin
get_mon_ramfs=dhcp 0x0c5f0000 /tftpboot/skern-keystone-evm.bin
get_mon_ubi=ubifsload 0x0c5f0000 skern-keystone-evm.bin
get_uboot_net=tftp 0x87000000 /tftpboot/u-boot-spi-keystone-evm.gph
get_uboot_ramfs=dhcp 0x87000000 /tftpboot/u-boot-spi-keystone-evm.gph
has_mdio=0
init_net=run args_all args_net
init_ramfs=run args_all args_ramfs get_fs_ramfs
init_ubi=run args_all args_ubi; ubi part ubifs; ubifsmount boot
ipaddr=10.110.2.126
mem_lpae=1
mem_reserve=512M
name_fdt=uImage-k2hk-evm.dtb
name_fs=arago-console-image.cpio.gz
name_kern=uImage-keystone-evm.bin
name_mon=skern-keystone-evm.bin
name_uboot=u-boot-spi-keystone-evm.gph
nfs_options=v3,tcp,rsize=4096,wsize=4096
nfs_root=/home/poonam/workdir
nfs_serverip=10.110.2.113
run_kern=bootm ${addr_kern} - ${addr_fdt}
run_mon=mon_install ${addr_mon}
serverip=10.110.2.113
stderr=serial
stdin=serial
stdout=serial
tftp_root=/tftpboot
ver=U-Boot 2013.01 (May 31 2013 - 01:01:04)

Environment size: 2348/262140 bytes

The EVM dosen't show U-boot prompt after powering ON and hangs at :

root@nikhil-OptiPlex-3010:/dev# picocom -b 115200 ttyUSB0
picocom v1.4

port is : ttyUSB0
flowcontrol : none
baudrate is : 115200
parity is : none
databits are : 8
escape is : C-a
noinit is : no
noreset is : no
nolock is : no
send_cmd is : ascii_xfr -s -v -l10
receive_cmd is : rz -vv

Kindly share your expert opinion, on how to solve this issue.

Thanks and Regards,
Nikhil

0 Raja over 8 years ago in reply to Nikhil Mantripragada

TI__Guru* 81335 points

Hi Nikhil,
I am confused. Without stopping at u-boot prompt how could you get the enviroment variable shown above?

The EVM dosen't show U-boot prompt after powering ON and hangs at :

Log is missing.

0 Nikhil Mantripragada over 8 years ago in reply to Raja

Prodigy 100 points

Hi Raja,

The U-boot Environmental Variable Log was captured when we flashed the U-boot and run for the first time. Later as per Stalin's suggestion we have modified bootargs for NFS, after onwards rebooting the K2H, it hangs at Terminal Prompt.

Please find the attached Log below, where the K2H Hangs while Booting:

root@nikhil-OptiPlex-3010:/dev# picocom -b 115200 ttyUSB0
picocom v1.4

port is : ttyUSB0
flowcontrol : none
baudrate is : 115200
parity is : none
databits are : 8
escape is : C-a
noinit is : no
noreset is : no
nolock is : no
send_cmd is : ascii_xfr -s -v -l10
receive_cmd is : rz -vv

After this there is no activity on terminal.

So kindly suggest your helpful opinions.

Thanks and Regards,
Nikhil

0 Titusrathinaraj Stalin over 8 years ago in reply to Nikhil Mantripragada

TI__Guru** 116100 points

Hi Nikhil,
Able to load and run the new latest u-boot through CCS (loadlin script) ?

processors.wiki.ti.com/.../MCSDK_UG_Chapter_Exploring

0 Nikhil Mantripragada over 8 years ago in reply to Titusrathinaraj Stalin

Prodigy 100 points

Hi Stalin,

We were able to load and run the latest u-boot through CCS. But after rebooting the EVM it hangs .

Thanks and Regards,
Nikhil

0 Titusrathinaraj Stalin over 8 years ago in reply to Nikhil Mantripragada

TI__Guru** 116100 points

Hi,

We were able to load and run the latest u-boot through CCS. But after rebooting the EVM it hangs .

Hang means, u-boot hang or kernel hang or not able to get u-boot shell ?
After load and run the latest u-boot via CCS, did you flash new u-boot on NAND or SPI ?

Because, if you reboot without flashing then you would get the older u-boot.

Processors

Processors forum

Keystone II: can't boot kernel with device tree error