• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 99 subscribers
  • Views 491 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

OMAP L137 Kernel booting issue

Jitendra Jagasia
Intellectual 840 points

Hi,

     Can provide me suggestion regarding the error i am facing while booting the Linux Kernel

     I have compiled the Linux kernel according to the steps given in the start up guide of OMAP l137

     But while bootup it gives me the following error " Wrong Image format for bootm command  ERROR: can't get kernel image! "

  & Uboot environment is set according to given command

  setenv nfshost 192.168.1.55

  setenv rootpath /home/filesys

   setenv serverip 192.168.1.55

   setenv bootfile uImage

   setenv bootcmd 'set ipaddr 192.168.1.4;tftp 0xc0700000 uImage;bootm'

  setenv bootargs console=ttyS0,115200n8 noinitrd rw ip=192.168.1.4:192.168.1.1:192.168.1.1:255.255.255.0::eth0: root=/dev/nfs nfsroot=${nfshost}:${rootpath},nolock mem=32M

 Can any provide the explanation why the above error is occurring.  

Regards

Jitendra


  • 0
    TI__Expert 5170 points

    Hi,

    I am not sure whether tftp of uImage was successful. Try running the commands in "bootcmd" environment variable one by one and see whether you are able to download the uImage using tftp.

    Regards, Sudhakar

  • 0 in reply to Sudhakar Rajashekhara
    TI__Expert 7225 points

    Hi Jitendra,

     

    Please send us the dump of the boot up...and the entire boot arguments by using "printenv".

     

    Best Regards

    Feroz

  • 0 in reply to K Md Feroz Irfan
    Intellectual 840 points

    Hi Feroz,

    dump of boot up are as follows:

     U-Boot > printenv

    bootdelay=3

    baudrate=115200

    ethaddr=00:0e:99:02:f9:a4

    rootpath=/home/acevin/workdir noinitrd rw ip=dhcp root=/dev/nfs nfsroot=192.168.1.55:/home/acevin/workdir/filesys,nolock mem=M

    ipaddrs=192.168.1.4

    nfshost=192.168.1.55

    gatewayip=0.0.0.0

    dnsip=0.0.0.0

    bootargs=console=ttySA0,115200 noinitrd rw ip=192.168.1.4:192.168.1.1:192.168.1.1:255.255.255.0::eth0: root=/dev/nfs nfsroot=e

    bootcmd=set ipaddr 192.168.1.4;tftp 0xc0700000 uImage;bootm 0xc0700000

    stdin=serial

    stdout=serial

    stderr=serial

    ver=U-Boot 2009.11 (May 03 2010 - 15:39:24)

    filesize=3FB380

    fileaddr=C0700000

    netmask=255.255.255.0

    ipaddr=192.8.1.55

     

     

    TFTP from server 192.168.1.55; our IP address is 192.168.1.4

    Filename 'uImage'.

    Load address: 0xc0700000

    Loading: ###########################################################

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

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

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

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

    done

    Bytes transferred = 4174720 (3fb380 hex)

    ERROR: can't get kernel image!

  • 0 in reply to Jitendra Jagasia
    TI__Expert 6735 points

    Jitendra:

    Below is a very common way to set the bootargs.  Does this work for you?

     

    setenv bootfile uImage

    setenv serverip 192.168.1.4

    setenv bootargs mem=32M

    console=ttyS2,115200n8 noinitrd rw root=/dev/nfs nfsroot=192.168.1.55:/home/acevin/workdir/filesys,nolock,rsize=1024,wsize=1024 ip=dhcp       

    Regards,

    Michael T

  • 0 in reply to Michael T
    TI__Expert 5170 points

    Hi Jitendra,

    On which platform you are building Linux Kernel, is it Windows or Linux? Also, where are you running the tftp server? if you have built the kernel on Linux system and then transferring uImage to Windows system or vice versa, make sure that you are transferring uImage using "binary" mode.

    Regards, Sudhakar