root@host-VirtualBox:/home/host/ti-sdk# ./setup.sh ------------------------------------------------------------------------------- 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 12.04 LTS, Ubuntu 14.04, or Ubuntu 14.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 ] User 'root' 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/host/ti-sdk/targetNFS ] /export/rootfs -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- This step will extract the target filesystem to /export/rootfs Note! This command requires you to have administrator priviliges (sudo access) on your host. Press return to continue /export/rootfs already exists (r) rename existing filesystem (o) overwrite existing filesystem (s) skip filesystem extraction [r] o Old /export/rootfs removed Successfully extracted tisdk-rootfs-image-am335x-evm.tar.xz to /export/rootfs -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- This step will set up the SDK to install binaries in to: /export/rootfs/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 /export/rootfs 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] o Successfully overwritten zImage-am335x-evm.bin in tftp root directory /tftpboot /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] Successfully overwritten am335x-boneblack.dtb in tftp root directory /tftpboot /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] Successfully overwritten am335x-bone.dtb in tftp root directory /tftpboot /tftpboot/am335x-bonegreen.dtb already exists. The existing installed file can be renamed and saved under the new name. (o) overwrite (s) skip copy [o] Successfully overwritten am335x-bonegreen.dtb in tftp root directory /tftpboot /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] Successfully overwritten am335x-evm.dtb in tftp root directory /tftpboot /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] Successfully overwritten am335x-evmsk.dtb in tftp root directory /tftpboot /tftpboot/am335x-icev2.dtb already exists. The existing installed file can be renamed and saved under the new name. (o) overwrite (s) skip copy [o] Successfully overwritten am335x-icev2.dtb in tftp root directory /tftpboot /tftpboot/am335x-icev2-pru-excl-uio.dtb already exists. The existing installed file can be renamed and saved under the new name. (o) overwrite (s) skip copy [o] Successfully overwritten am335x-icev2-pru-excl-uio.dtb 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 7992 -------------------------------------------------------------------------------- --------------------------------------------------------------------------------" 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 * Beaglebone Black * AM335x EVM-SK * AM57xx EVM * K2H, K2L, and K2E EVMs 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: If your using any of the above boards simply hit enter and 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. Autodetected the following ip address of your host, correct it if necessary [ 10.0.211.29 192.168.2.1 192.168.7.1 ] 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: MLO README.md am335x-bone.dtb am335x-boneblack.dtb am335x-bonegreen.dtb am335x-evm.dtb am335x-evmsk.dtb am335x-icev2-pru-excl-uio.dtb am335x-icev2.dtb u-boot-spl.bin u-boot.img zImage zImage-am335x-evm.bin Which kernel image do you want to boot from TFTP? [ zImage-am335x-evm.bin ] -------------------------------------------------------------------------------- Would you like to create a minicom script with the above parameters (y/n)? [ y ] Successfully wrote /home/host/ti-sdk/bin/setupBoard.minicom No BeagleBone (Black) or StarterKit detected. Assuming general purpose evm is being used. Is this correct? (y/n) n Please connect the Beaglebone (Black) or StarterKit to the PC If your using the StarterKit board make sure it is turned on Press any key to try checking again. No BeagleBone (Black) or StarterKit detected. Assuming general purpose evm is being used. Is this correct? (y/n) n Please connect the Beaglebone (Black) or StarterKit to the PC If your using the StarterKit board make sure it is turned on Press any key to try checking again. No BeagleBone (Black) or StarterKit detected. Assuming general purpose evm is being used. Is this correct? (y/n) y Would you like to run the setup script now (y/n)? For the general purpose evm you must now connect the RS-232 cable to your evm now. For the Beaglebone (Black) or StarterKit this step should of already have been done. Also connect the ethernet cable as described in the Quick Start Guide. **Important** Once answering 'y' on the prompt below you will have 300 seconds to turn on the board or if it was already on reboot the board before the setup times out After successfully executing this script, your board 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 ] n 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@host-VirtualBox:/home/host/ti-sdk#