Hi,
I am new to Sitara Linux SDK V7.0. I am following the "Sitara Linux SDK Setup Script" on BeagleBone Black. I removed MLO in resident eMMC. I have FTDI USB-UART to BBB. Also have e-net cable connect BBB directly to Linux host (my Win7 laptop running Ubuntu V12.04 inside VMWare V10.)
The setup.sh runs without problem. But at the end of script, it complains about not having "boot partition." See the dump below. I examined the script. It seems to expect boot partition in /media directory. So I copy entire folder .../targetNFS/boot to /media. Rerun the script, and it went further. But not much. It hangs at console putting "CCCCCC..."
What did I do wrong? Please help.
-------------------------------------------------------------------------------
TISDK setup script
This script will set up your development host for SDK development.
Parts of this script require administrator priviliges (sudo access).
-------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Verifying Linux host distribution
Ubuntu 10.04 LTS or Ubuntu 12.04 LTS is being used, continuing..
--------------------------------------------------------------------------------
Starting with Ubuntu 12.04 serial devices are only accessible by members of the 'dialout' group.
A user must be apart of this group to have the proper permissions to access a serial device.
Are you running this script using sudo? The detected username is 'root'.
Verify and enter your Linux username below
[ root ] jc
User 'jc' is already apart of the 'dialout' group
-------------------------------------------------------------------------------
setup package script
This script will make sure you have the proper host support packages installed
This script requires administrator priviliges (sudo access) if packages are to be installed.
-------------------------------------------------------------------------------
System has required packages!
--------------------------------------------------------------------------------
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/jc/ti-sdk-am335x-evm-07.00.00.00/targetNFS ]
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
This step will extract the target filesystem to /home/jc/ti-sdk-am335x-evm-07.00.00.00/targetNFS
Note! This command requires you to have administrator priviliges (sudo access)
on your host.
Press return to continue
/home/jc/ti-sdk-am335x-evm-07.00.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/jc/ti-sdk-am335x-evm-07.00.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/jc/ti-sdk-am335x-evm-07.00.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/zImage-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 zImage-am335x-evm.bin, existing version will be used
/tftpboot/am335x-boneblack.dtb already exists. The existing installed file can be renamed and saved under the new name.
(o) overwrite (s) skip copy
[o] s
Skipping copy of am335x-boneblack.dtb, existing version will be used
/tftpboot/am335x-bone.dtb already exists. The existing installed file can be renamed and saved under the new name.
(o) overwrite (s) skip copy
[o] s
Skipping copy of am335x-bone.dtb, existing version will be used
/tftpboot/am335x-evm.dtb already exists. The existing installed file can be renamed and saved under the new name.
(o) overwrite (s) skip copy
[o] s
Skipping copy of am335x-evm.dtb, existing version will be used
/tftpboot/am335x-evmsk.dtb already exists. The existing installed file can be renamed and saved under the new name.
(o) overwrite (s) skip copy
[o] s
Skipping copy of am335x-evmsk.dtb, 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 3388
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------"
This step will set up minicom (serial communication application) for
SDK development
For boards that contain a USB-to-Serial converter on the board such as:
* BeagleBone
* AM335x EVM-SK
* OMAP5 uEVM
the port used for minicom will be automatically detected. By default Ubuntu
will not recognize this device. Setup 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/jc/.minirc.dfl to /home/jc/.minirc.dfl.old
Configuration saved to /home/jc/.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.80.131 ]
Select Linux kernel location:
1: TFTP
2: SD card
[ 1 ]
Select root file system location:
1: NFS
2: SD card
[ 1 ]
Available kernel images in /tftproot:
am335x-bone.dtb
am335x-boneblack.dtb
am335x-evm.dtb
am335x-evmsk.dtb
zImage-am335x-evm.bin
Which kernel image do you want to boot from TFTP?
[ zImage-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
The boot partition doesn't appear to be mounted on the host.
If you're using a virtual machine, please ensure it has been imported to Linux
Please ensure the boot partition is mounted and run setup.sh again.
We have detected that you are using a BeagleBone Black. Please ensure that the Micro USB cable is plugged in.
For more information please see:
http://processors.wiki.ti.com/index.php/Sitara_Linux_SDK_Setup_Script#BeagleBone_Black_Users
Press Enter to exit
-------------------------------------------------------------------------------
TISDK setup completed!
Please continue reading the Software Developer's Guide for more information on
how to develop software on the EVM
-------------------------------------------------------------------------------
