Hi all,
I have just used BeagleBone (Rev A6) and TI Linux EZSDK (5.05.00.00). I have tried to boot my board form ethernet several times but not successful.
My host machine is Ubuntu 10.04 (with VMWare 8.0 on Win7 32 bit). I connected my system as the figure in http://processors.wiki.ti.com/index.php/Sitara_Linux_Software_Developer%E2%80%99s_Guide
I used setup.sh script in TI EZSDK root path as instructed in http://processors.wiki.ti.com/index.php/Sitara_Linux_SDK_Setup_Script
(and Preparing to Develop using the setup.sh Script in http://processors.wiki.ti.com/index.php/Sitara_Linux_Training:_Hands_on_with_the_SDK)
I think the script executed without error. My terminal screeen looked like:
--------------------------------------------------------------------------------
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 53 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)
[ /home/tinnd/ti-sdk-am335x-evm-05.05.00.00/targetNFS ]
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
This step will extract the target filesystem to /home/tinnd/ti-sdk-am335x-evm-05.05.00.00/targetNFS
Note! This command requires you to have administrator priviliges (sudo access)
on your host.
Press return to continue
/home/tinnd/ti-sdk-am335x-evm-05.05.00.00/targetNFS already exists
(r) rename existing filesystem (o) overwrite existing filesystem (s) skip filesystem extraction
[r] s
Skipping filesystem extraction
WARNING! Keeping the previous filesystem may cause compatibility problems if you are upgrading the SDK
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
This step will set up the SDK to install binaries in to:
/home/tinnd/ti-sdk-am335x-evm-05.05.00.00/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
/home/tinnd/ti-sdk-am335x-evm-05.05.00.00/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] s
Skipping copy of uImage-am335x-evm.bin, existing version will be used
/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 24948
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
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 /home/tinnd/.minirc.dfl to /home/tinnd/.minirc.dfl.old
Configuration saved to /home/tinnd/.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
[ 192.168.1.126 ]
Select Linux kernel location:
1: TFTP
2: SD card
[ 1 ] 1
Select root file system location:
1: NFS
2: SD card
[ 1 ] 1
Then, there are 2 cases:
1. If the board did not connect before, I got following messages:
Available kernel images in /tftproot:
uImage-am335x-evm.bin
uImage-am335x-evm.bin.08132012_11.09
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 ] y
Successfully wrote /home/tinnd/ti-sdk-am335x-evm-05.05.00.00/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 ]
I connected the board right after as instructed but I only got a screen of minicom. Nothing more!
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
2. If the board was connected before, the messages are:
Available kernel images in /tftproot:
uImage-am335x-evm.bin
uImage-am335x-evm.bin.08132012_11.09
Which kernel image do you want to boot from TFTP?
[ uImage-am335x-evm.bin ]
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=192.168.1.126
rootpath=/home/tinnd/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 ]
Stopping Dropbear SSH server: stopped /usr/sbin/dropbear (pid 123
7)lcome to minicom 2.5
dropbear.
Stopping telnet daemon.
Stopping Hardware abstraction layer hald
Stopping system message bus: stopped process in pidfile '/var/run/dbus/pid' (pid
1136)
dbus. CTRL-A Z for help on special keys
Stopping network benchmark server: netserverstopped /usr/sbin/netserver (pid 124
9)gger 50
.
Stopping thttpdError opening /dev/fb0: No such file or directory
. _ |___ ___ ___ ___ | _ |___ ___ |_|___ ___| |_
ALSA: Storing mixer settings...| _| . | | | -_| _| _|
/usr/sbin/alsactl: save_state:1519: No soundcards found...
Deconfiguring network interfaces... done.__|
Stopping Lighttpd Web Server: stopped /usr/sbin/lighttpd (pid 1277)
lighttpd.ject http://arago-project.org am335x-evm ttyO0
Stopping syslogd/klogd: stopped syslogd (pid 1254)
stopped klogd (pid 1256) ttyO0
done
Stopping Matrix GUI applicationstart-stop-daemon: warning: killing process 0: No
such process
.
[ 111.428497] musb-hdrc musb-hdrc.0: remove, state 1
[ 111.433532] usb usb2: USB disconnect, device number 1
[ 111.439453] musb-hdrc musb-hdrc.0: USB bus 2 deregistered
***************************************************************
***************************************************************
NOTICE: This file system contains the followin GPLv3 packages:
binutils-symlinks
binutils
gdbserver
If you do not wish to distribute GPLv3 components please remove
the above packages prior to distribution. This can be done using
the opkg remove command. i.e.:
opkg remove <package>
Where <package> is the name printed in the list above
NOTE: If the package is a dependency of another package you
will be notified of the dependent packages. You should
use the --force-removal-of-dependent-packages option to
also remove the dependent packages as well
***************************************************************
***************************************************************
Sending all processes the TERM signal...
Sending all processes the KILL signal...
Unmounting remote filesystems...
Deactivating swap...
Unmounting local filesystems...
Rebooting... [ 127.539672] musb-hdrc musb-hdrc.1: remove, state 1
[ 127.544769] usb usb1: USB disconnect, device number 1
[ 127.550659] musb-hdrc musb-hdrc.1: USB bus 1 deregistered
[ 127.556701] Restarting system.
/home/tinnd/ti-sdk-am335x-evm-05.05.00.00
--------------------------------------------------------------------------------
The board rebooted but could not load the kernel :
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
0
SD/MMC found on device 0
reading uEnv.txt
262 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
*** Unhandled DHCP Option in OFFER/ACK: 46
*** Unhandled DHCP Option in OFFER/ACK: 46
DHCP client bound to address 192.168.1.128
Using cpsw device
TFTP from server 192.168.1.254; our IP address is 192.168.1.128
Filename 'uImage-am335x-evm.bin'.
Load address: 0x82000000
Loading: T T T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
link up on port 0, speed 100, full duplex
BOOTP broadcast 1
*** Unhandled DHCP Option in OFFER/ACK: 46
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5
BOOTP broadcast 6
BOOTP broadcast 7
BOOTP broadcast 8
BOOTP broadcast 9
BOOTP broadcast 10
Retry count exceeded; starting again
link up on port 0, speed 100, full duplex
BOOTP broadcast 1
*** Unhandled DHCP Option in OFFER/ACK: 46
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5
It ran BOOTP broadcasst again and again and again
I tried many times but the result unchanged.
I turned my firewall off . And I had my VMWare network configured as NAT, Host Only, Bridge but I am still unsuccessful.
When the board boot it got the right IP. I could ping the board but could not load the kernel.
Can anybody help me, please!