• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 99 subscribers
  • Views 1455 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.

Problem in booting kernel from beagle bone

Javed Iqbal
Intellectual 285 points

Hey hi all,

I have downloaded the EZSDK from and when I run the ./setup.sh script it gives as below....

http://www.ti.com/tool/linuxezsdk-sitara

 ./setup.sh

--------------------------------------------------------------------------------
TISDK setup script

This script will set up your development host for dvsdk development.
Parts of this script require administrator priviliges (sudo access).
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
Verifying Linux host distribution
Ubuntu 10.04 LTS found successfully, continuing..
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This step will make sure you have the proper host support packages installed
using the following command: sudo apt-get install xinetd tftpd nfs-kernel-server minicom build-essential libncurses5-dev uboot-mkimage autoconf automake

Note! This command requires you to have administrator priviliges (sudo access)
on your host.
Press return to continue

Reading package lists... Done
Building dependency tree       
Reading state information... Done
autoconf is already the newest version.
automake is already the newest version.
build-essential is already the newest version.
libncurses5-dev is already the newest version.
nfs-kernel-server is already the newest version.
uboot-mkimage is already the newest version.
xinetd is already the newest version.
minicom is already the newest version.
tftpd is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Package verification and installation successfully completed
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
In which directory do you want to install the target filesystem?(if this directory does not exist it will be created)
[ /usr/local/ti-sdk-am335x-evm/targetNFS ]
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This step will extract the target filesystem to /usr/local/ti-sdk-am335x-evm/targetNFS

Note! This command requires you to have administrator priviliges (sudo access)
on your host.
Press return to continue
/usr/local/ti-sdk-am335x-evm/targetNFS already exists
(r) rename existing filesystem (o) overwrite existing filesystem (s) skip filesystem extraction
[r]
Path for old filesystem:
[ /usr/local/ti-sdk-am335x-evm/targetNFS.09032012_14.28 ]

Successfully moved old /usr/local/ti-sdk-am335x-evm/targetNFS to /usr/local/ti-sdk-am335x-evm/targetNFS.09032012_14.28

Successfully extracted tisdk-rootfs-am335x-evm.tar.gz to /usr/local/ti-sdk-am335x-evm/targetNFS
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This step will set up the SDK to install binaries in to:
    /usr/local/ti-sdk-am335x-evm/targetNFS/home/root/am335x-evm

The files will be available from /home/root/am335x-evm on the target.

This setting can be changed later by editing Rules.make and changing the
EXEC_DIR or DESTDIR variable (depending on your SDK).

Press return to continue
Rules.make edited successfully..
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This step will export your target filesystem for NFS access.

Note! This command requires you to have administrator priviliges (sudo access)
on your host.
Press return to continue
/usr/local/ti-sdk-am335x-evm/targetNFS already NFS exported, skipping..

 * Stopping NFS kernel daemon                                                                                                 [ OK ]
 * Unexporting directories for NFS kernel daemon...                                                                           [ OK ]
 * Exporting directories for NFS kernel daemon...                                                                             [ OK ]
 * Starting NFS kernel daemon                                                                                                 [ OK ]
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Which directory do you want to be your tftp root directory?(if this directory does not exist it will be created for you)
[ /tftpboot ]
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This step will set up the tftp server in the /tftpboot directory.

Note! This command requires you to have administrator priviliges (sudo access)
on your host.
Press return to continue

/tftpboot already exists, not creating..

/tftpboot/uImage-am335x-evm.bin already exists. The existing installed file can be renamed and saved under the new name.
(r) rename (o) overwrite (s) skip copy
[r] o

Successfully overwritten uImage-am335x-evm.bin in tftp root directory /tftpboot

/etc/xinetd.d/tftp already exists..
/tftpboot already exported for TFTP, skipping..

Restarting tftp server
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service xinetd stop

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the stop(8) utility, e.g. stop xinetd
xinetd stop/waiting
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service xinetd start

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the start(8) utility, e.g. start xinetd
xinetd start/running, process 4431
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This step will set up minicom (serial communication application) for
SDK development


For boards that contain a USB-to-Serial converter on the board (BeagleBone),
the port used for minicom will be automatically detected. By default Ubuntu
will not recognize this device. Setup will add will add a udev rule to
/etc/udev/ so that from now on it will be recognized as soon as the board is
plugged in.

For other boards, the serial will defualt to /dev/ttyS0. Please update based
on your setup.
--------------------------------------------------------------------------------


NOTE: For boards with a built-in USB to Serial adapter please press
      ENTER at the prompt below.  The correct port will be determined
      automatically at a later step.  For all other boards select
      the serial port that the board is connected to
Which serial port do you want to use with minicom?
[ /dev/ttyS0 ]

Copied existing /root/.minirc.dfl to /root/.minirc.dfl.old

Configuration saved to /root/.minirc.dfl. You can change it further from inside
minicom, see the Software Development Guide for more information.
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This step will set up the u-boot variables for booting the EVM.
Becuase the not all AM335x devices have a NAND, the u-boot variables will
be stored in uEnv.txt on the boot partition. U-boot will read this
file on boot.

Autodetected the following ip address of your host, correct it if necessary
[ 10.110.2.146 ]

Select Linux kernel location:
 1: TFTP
 2: SD card

[ 1 ] 1

Select root file system location:
 1: NFS
 2: SD card

[ 1 ] 1

Available kernel images in /tftproot:
    uImage-am335x-evm.bin
    uImage-am335x-evm.bin.09012012_18.31
    uImage-am335x-evm.bin.09032012_12.05

Which kernel image do you want to boot from TFTP?
[ uImage-am335x-evm.bin ]
--------------------------------------------------------------------------------
Would you like to create a minicom script with the above parameters (y/n)?
[ y ]

Successfully wrote /usr/local/ti-sdk-am335x-evm/bin/setupBoard.minicom
Would you like to run the setup script now (y/n)? This requires you to connect
the RS-232 cable between your host and EVM as well as your ethernet cable as
described in the Quick Start Guide. Once answering 'y' on the prompt below
you will have 300 seconds to connect the board and power cycle it
before the setup times out

After successfully executing this script, your EVM will be set up. You will be
able to connect to it by executing 'minicom -w' or if you prefer a windows host
you can set up Tera Term as explained in the Software Developer's Guide.
If you connect minicom or Tera Term and power cycle the board Linux will boot.

[ y ]


Welcome to minicom 2.5

OPTIONS: I18n
Compiled on May  2 2011, 00:39:27.
Port /dev/ttyS0

Press CTRL-A Z for help on special keys                                        
                                                                               
bigger 50                                                                      
                                                                               

and when I terminate the process minicom  by ctrl+a+x) it gives like this....  but finally it does not boot the kernel why ???  and it has not set the uboot parameters or it has not done anything  regarding uEnv.txt setup ???? Is anything there which has been left to set...????  if anybody have any idea about this then please let me know... thanks


CTRL-A Z for help |115200 8N1 | NOR | Minicom 2.5    | VT102 |      Offline                                                        
/usr/local/ti-sdk-am335x-evm
You can manually run minicom in the future with this setup script using: minicom -S ./bin/setupBoard.minicom
--------------------------------------------------------------------------------

TISDK setup completed!
Please continue reading the Software Developer's Guide for more information on
how to develop software on the EVM
root@pc:/usr/local/ti-sdk-am335x-evm# minicom -S ./b
bin/           board-support/
root@pc:/usr/local/ti-sdk-am335x-evm# minicom -S ./b
bin/           board-support/
root@pc:/usr/local/ti-sdk-am335x-evm# minicom -S ./bin/setupBoard.minicom

Welcome to minicom 2.5

OPTIONS: I18n
Compiled on May  2 2011, 00:39:27.
Port /dev/ttyS0

Press CTRL-A Z for help on special keys                                        
                                                                               
bigger 50    

Regards

Muhammad                                                                


                                                                               

  • 0
    TI__Expert 5450 points

    Muhammad,

    It appears that the beaglebone is not connected to your Linux host because it is not being seen by the setup script.  The setup script for beaglebone will try to copy the uEnv.txt file to the mounted boot partition when a beaglebone is detected.  You should boot your beaglebone, see the /media/boot mount point show up, then run the setup.sh script.

    To be clear, you can also perform all the configuration the setup script is doing manually as well by creating your own uEnv.txt file and placing it on the boot partition of the SD card.

    Chase

  • 0 in reply to Chase Maupin
    Intellectual 285 points

    ok i have done manually and finally  rebooted bone then it entered to minicom and give this kind of error as below on minicom ???  is there any problem with file system ??? on boot partition or anything else..??

    Welcome to minicom 2.5

    OPTIONS: I18n
    Compiled on May  2 2011, 00:39:27.
    Port /dev/ttyUSB1

    Press CTRL-A Z for help on special keys

    bigger 50

    [ 1313.029083] EXT4-fs error (device mmcblk0p2): ext4_find_entry:935: inode #9499: comm agetty: reading directory lblock 0
    beaglebone login: root
    [ 1370.806854] EXT4-fs error (device mmcblk0p2): ext4_find_entry:935: inode #2: comm agetty: reading directory lblock 0
    root


    [ 1380.820800] EXT4-fs error (device mmcblk0p2): ext4_find_entry:935: inode #426: comm systemd: reading directory lblock 0
    [ 1380.832458] EXT4-fs error (device mmcblk0p2): ext4_find_entry:935: inode #426: comm systemd: reading directory lblock 0

  • 0 in reply to Javed Iqbal
    Intellectual 285 points

    and when next time I boot console like this....

    This SDK supports both the AM335x EVM and the BeagleBone/EVM-SK.
    A BeagleBone/EVM-SK has been detected as attached to your host system
    Are you wanting to configure u-boot for this device?  An
    answer of 'n' will configure u-boot for the AM335x EVM instead
    (y/n) y
    Copying uEnv.txt to boot partition...


    --------------------------------------------------------------------------------
    uEnv.text has been saved to the boot partition. uEnv.txt contains:
    serverip=10.110.2.146
    rootpath=/home/javed/ti-sdk-am335x-evm-05.05.00.00/targetNFS
    bootfile=uImage-am335x-evm.bin
    ip_method=dhcp
    tftp_nfs_boot=echo Booting from network...; dhcp ${loadaddr} ${bootfile}; run net_args; bootm ${loadaddr}
    uenvcmd=run tftp_nfs_boot

    On the next boot, the BeagleBone will boot with these settings.
    Would you like to restart now (y/n)?
    [ y ]y


    Welcome to minicom 2.5

    OPTIONS: I18n
    Compiled on May  2 2011, 00:39:27.
    Port /dev/ttyUSB1

    Press CTRL-A Z for help on special keys

    bigger 50

  • 0 in reply to Javed Iqbal
    Intellectual 285 points

    it is already in root of bone but no command is working thear.....????

    oot@beaglebone:~# ls
    -sh: ls: command not found
    root@beaglebone:~# opkg update
    [  706.123260] EXT4-fs error (device mmcblk0p2): ext4_find_entry:935: inode #10049: comm sh: reading directory lblock 0
    [  706.134399] EXT4-fs error (device mmcblk0p2): ext4_find_entry:935: inode #29111: comm sh: reading directory lblock 0
    [  706.145477] EXT4-fs error (device mmcblk0p2): ext4_find_entry:935: inode #29227: comm sh: reading directory lblock 0
    -sh: opkg: command not found
    root@beaglebone:~# l          
    [  713.233215] EXT4-fs error (device mmcblk0p2): ext4_find_entry:935: inode #10049: comm sh: reading directory lblock 0
    [  713.244354] EXT4-fs error (device mmcblk0p2): ext4_find_entry:935: inode #29111: comm sh: reading directory lblock 0
    [  713.255432] EXT4-fs error (device mmcblk0p2): ext4_find_entry:935: inode #29227: comm sh: reading directory lblock 0
    -sh: l: command not found
    root@beaglebone:~# ls
    -sh: ls: command not found
    root@beaglebone:~# adduser
    [  784.853240] EXT4-fs error (device mmcblk0p2): ext4_find_entry:935: inode #10049: comm sh: reading directory lblock 0
    [  784.864379] EXT4-fs error (device mmcblk0p2): ext4_find_entry:935: inode #29111: comm sh: reading directory lblock 0
    [  784.875549] EXT4-fs error (device mmcblk0p2): ext4_find_entry:935: inode #29227: comm sh: reading directory lblock 0
    -sh: adduser: command not found
    root@beaglebone:~#
    ????????????????

  • 0 in reply to Javed Iqbal
    Intellectual 285 points

    this is the U-boot:>>>>>>>>..

    U-Boot SPL 2011.09-00000-gf63b270-dirty (Apr 24 2012 - 09:51:01)
    Texas Instruments Revision detection unimplemented
    OMAP SD/MMC: 0
    reading u-boot.img
    reading u-boot.img


    U-Boot 2011.09-00000-gf63b270-dirty (Apr 24 2012 - 09:51:01)

    I2C:   ready
    DRAM:  256 MiB
    No daughter card present
    NAND:  HW ECC Hamming Code selected
    No NAND device found!!!
    0 MiB
    MMC:   OMAP SD/MMC: 0
    *** Warning - readenv() failed, using default environment

    Net:   cpsw
    Hit any key to stop autoboot:  0
    SD/MMC found on device 0
    reading uEnv.txt

    261 bytes read
    Loaded environment from uEnv.txt
    Importing environment from mmc ...
    Running uenvcmd ...
    Booting from network...
    link up on port 0, speed 100, full duplex
    BOOTP broadcast 1
    BOOTP broadcast 2
    BOOTP broadcast 3
    BOOTP broadcast 4
    BOOTP broadcast 5

    Abort
    Wrong Image Format for bootm command
    ERROR: can't get kernel image!
    Loading file "/boot/uImage-am335x-evm.bin" from mmc device 0:2 xxa2
    ** File not found /boot/uImage-am335x-evm.bin
    Booting from nand ...

    no devices available
    Wrong Image Format for bootm command
    ERROR: can't get kernel image!

    and these are the printenv...............................................>>>>>>>>>>>

    U-Boot# printenv
    autoload=yes
    baudrate=115200
    bootargs=console=ttyO0,115200n8 root=/dev/mtdblock7 rw noinitrd rootfstype=jffs2 ip=dhcp
    bootargs_defaults=setenv bootargs console=${console} ${optargs}
    bootcmd=if mmc rescan; then echo SD/MMC found on device ${mmc_dev};if run loadbootenv; then echo Loaded environment from ${bootenv};r
    un importbootenv;fi;if test -n $uenvcmd; then echo Running uenvcmd ...;run uenvcmd;fi;if run mmc_load_uimage_ext4; then run mmc_args;
    bootm 0x80007fc0;fi;fi;run nand_boot;
    bootdelay=1
    bootenv=uEnv.txt
    bootfile=uImage-am335x-evm.bin
    console=ttyO0,115200n8
    ethact=cpsw
    ethaddr=00:18:31:8e:18:1f
    filesize=105
    importbootenv=echo Importing environment from mmc ...; env import -t $loadaddr $filesize
    ip_method=dhcp
    loadaddr=0x82000000
    loadbootenv=fatload mmc ${mmc_dev} ${loadaddr} ${bootenv}
    mmc_args=run bootargs_defaults;setenv bootargs ${bootargs} root=${mmc_root} rootfstype=${mmc_root_fs_type} ip=${ip_method}
    mmc_boot=run mmc_args; run mmc_load_uimage_ext4; bootm 0x80007fc0
    mmc_dev=0
    mmc_load_uimage=fatload mmc ${mmc_dev}:1 0x80007fc0 ${bootfile}
    mmc_load_uimage_ext2=ext2load mmc ${mmc_dev}:2 0x80007fc0 /boot/${bootfile}
    mmc_load_uimage_ext4=ext4load mmc ${mmc_dev}:2 0x80007fc0 /boot/${bootfile}
    mmc_root=/dev/mmcblk0p2 ro
    mmc_root_fs_type=ext4 rootwait
    nand_args=run bootargs_defaults;setenv bootargs ${bootargs} root=${nand_root} noinitrd rootfstype=${nand_root_fs_type} ip=${ip_method
    }
    nand_boot=echo Booting from nand ...; run nand_args; nand read.i ${loadaddr} ${nand_src_addr} ${nand_img_siz}; bootm ${loadaddr}
    nand_img_siz=0x500000
    nand_root=/dev/mtdblock7 rw
    nand_root_fs_type=jffs2
    nand_src_addr=0x280000
    net_args=run bootargs_defaults;setenv bootargs ${bootargs} root=/dev/nfs nfsroot=${serverip}:${rootpath},${nfsopts} rw ip=dhcp
    net_boot=echo Booting from network ...; setenv autoload no; dcache off; dhcp; tftp ${loadaddr} ${bootfile}; run net_args; bootm ${loa
    daddr}
    nfsopts=nolock
    nor_args=run bootargs_defaults;setenv bootargs ${bootargs} root={nor_root} rootfstype=${nor_root_fs_type} ip=${ip_method}
    nor_boot=echo Booting from NOR ...; run nor_args; cp.b ${0x08080000} ${loadaddr} ${nor_img_siz}; bootm ${loadaddr}
    nor_img_siz=0x280000
    nor_root=/dev/mtdblock3 rw
    nor_root_fs_type=jffs2
    nor_src_addr=0x08080000
    rootpath=/home/javed/ti-sdk-am335x-evm-05.05.00.00/targetNFS
    script_addr=0x81900000
    serverip=10.110.2.146
    spi_args=run bootargs_defaults;setenv bootargs ${bootargs} root=${spi_root} rootfstype=${spi_root_fs_type} ip=${ip_method}
    spi_boot=echo Booting from spi ...; run spi_args; sf probe ${spi_bus_no}:0; sf read ${loadaddr} ${spi_src_addr} ${spi_img_siz}; bootm
     ${loadaddr}
    spi_bus_no=0
    spi_img_siz=0x280000
    spi_root=/dev/mtdblock4 rw
    spi_root_fs_type=jffs2
    spi_src_addr=0x62000
    static_ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off
    stderr=serial
    stdin=serial
    stdout=serial
    tftp_nfs_boot=echo Booting from network...; dhcp ${loadaddr} ${bootfile}; run net_args; bootm ${loadaddr}
    uenvcmd=run tftp_nfs_boot

    Environment size: 3087/8188 bytes

    still it is not booting the kernel......??????????????

  • 0 in reply to Javed Iqbal
    Prodigy 220 points

    Hi Javed,

    I have the same problem and I would like knowing how you have solved.
    because in my case in /media there is not the file /boot.

    -Regards