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.

66AK2H14: Execute setup.sh error: shift: can't shift that many

Part Number: 66AK2H14

I want to upgrade the SDK version of 66AK2H, but the following error occurred while executing setup.sh. What is the reason for this? The SDK version is 06.03.00.106.

root@athena-VirtualBox:/home/ym/python-build/TiBuild/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)
[ /root/project/TiBuild/SDK/targetNFS ] 
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This step will extract the target filesystem to /root/project/TiBuild/SDK/targetNFS

Note! This command requires you to have administrator priviliges (sudo access) 
on your host.
Press return to continue
/root/project/TiBuild/SDK/targetNFS already exists
(r) rename existing filesystem (o) overwrite existing filesystem (s) skip filesystem extraction
[r] o
Old /root/project/TiBuild/SDK/targetNFS removed

Multiple filesystems found.
        1:tisdk-server-rootfs-image-k2hk-evm.tar.xz
        2:tisdk-docker-rootfs-image-k2hk-evm.tar.xz

Enter Number of rootfs Tarball: [1] 


Successfully extracted tisdk-server-rootfs-image-k2hk-evm.tar.xz to /root/project/TiBuild/SDK/targetNFS
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This step will set up the SDK to install binaries in to:
    /root/project/TiBuild/SDK/targetNFS/home/root/k2hk-evm

The files will be available from /home/root/k2hk-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
/root/project/TiBuild/SDK/targetNFS already NFS exported, skipping..

[ ok ] Stopping nfs-kernel-server (via systemctl): nfs-kernel-server.service.
[ ok ] Starting nfs-kernel-server (via systemctl): nfs-kernel-server.service.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
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/*Image-k2hk-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 *Image-k2hk-evm.bin in tftp root directory /tftpboot

/tftpboot/keystone-k2hk-evm.dtb already exists. The existing installed file can be renamed and saved under the new name.
(o) overwrite (s) skip copy 
[o] o

Successfully overwritten keystone-k2hk-evm.dtb in tftp root directory /tftpboot

/tftpboot/keystone-k2hk-evm-k2hk-evm.dtb already exists. The existing installed file can be renamed and saved under the new name.
(o) overwrite (s) skip copy 
[o] o

Successfully overwritten keystone-k2hk-evm-k2hk-evm.dtb in tftp root directory /tftpboot
ls: cannot access '*.dtbo': No such file or directory

/tftpboot/u-boot-spi-k2hk-evm.gph already exists. The existing installed file can be renamed and saved under the new name.
(o) overwrite (s) skip copy 
[o] o

Successfully overwritten u-boot-spi-k2hk-evm.gph in tftp root directory /tftpboot

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

Successfully overwritten skern-k2hk.bin in tftp root directory /tftpboot

/tftpboot/k2-fw-initrd.cpio.gz already exists. The existing installed file can be renamed and saved under the new name.
(o) overwrite (s) skip copy 
[o] o

Successfully overwritten k2-fw-initrd.cpio.gz in tftp root directory /tftpboot

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

Restarting tftp server
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------"
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 ] /dev/ttyUSB0

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.2.15/192.168.1.25/172.17.0.1)
[ 10.0.2.15 ] 192.168.1.25

ls: cannot access './bin/../filesystem/tisdk-server-rootfs-image-k2hk-evm.ubi': No such file or directory
basename: missing operand
Try 'basename --help' for more information.

Successfully copied arago-base-tisdk-image-k2hk-evm.ubi to tftp root directory /tftpboot

/tftpboot/arago-tiny-image-k2hk-evm.ubi already exists. The existing installed file can be renamed and saved under the new name.
(o) overwrite (s) skip copy 
[ o ] 


Successfully overwritten arago-tiny-image-k2hk-evm.ubi in tftp root directory /tftpboot

Successfully copied tisdk-docker-rootfs-image-k2hk-evm.ubi to tftp root directory /tftpboot
--------------------------------------------------------------------------------
Would you like to update U-boot on the board? (y/n)
[ y ] 

Would you like to update the UBI filesystem on the board? (y/n)
[ y ] 

Available ubi images in /tftpboot:
    arago-base-tisdk-image-k2hk-evm.ubi
    arago-tiny-image-k2hk-evm.ubi
    tisdk-docker-rootfs-image-k2hk-evm.ubi

./bin/setup-uboot-env.sh: 74: shift: can't shift that many
Failed setup, aborting..