MMWCAS-DSP-EVM: repo sync giving connection refused

William Cram

Part Number: MMWCAS-DSP-EVM

According to the Processor SDK Linux Automotive Software Developers Guide - Texas Instruments Wiki I am to run the setup script in the INSTALL_DIR:

I ran the setup.sh script from to get the source code development using repo tool and I got the following error:

Parsing through much of the help I ran across a thread that mentioned where to get manifest.xml, I noticed there was no file called manifest.xml and I chose the one that looked closest what I needed, and was in line with what the thread was talking about (dra7xx-psdkla_evm_06_00_00_03.xml).

Once I downloaded the release-manifest-master.tar.gz and copied dra7xx-psdkla_evm_06_00_00_03.xml (renamed it to manifest.xml) and placed it into the .repo directory I got the following error:

I tried just a repo sync and got the following error:

So I am wondering if I need to use my TI registered username/password for the repo to work, I am wondering if that is the reason I am getting a connection refused?

Also, as an FYI, when I was following the document, I had to download python3 since Ubuntu 14.04 only came with python2, and the install was failing earlier in the setup.

Thank you,

William

over 3 years ago

0 William Cram over 3 years ago

Prodigy 205 points

Also, ran into the problem of having python 2 instead of 3, and this was not documented in the developers guide

0 William Cram over 3 years ago

Prodigy 205 points

I believe I found the solution, I had to go to a later Ubuntu Version (20.04 for me), however this required me to modify the setup.sh and comment out the lines:

$cwd/bin/setup-host-check.sh

check_status

Then I had to configure git to use my user.email I registered with TI:

This allowed me to download the source SDK files

0 Suman Anna over 3 years ago in reply to William Cram

TI__Guru** 111055 points

Hi William,

I am glad you are able to resolve the issue yourself. The Processor-SDK-Linux-Automotive 6_00_00_03 SDK for DRA7xx platforms is released back in 2019 and was validated using Ubuntu 14.04.

The TI SDKs are typically released, verified and supported only for a specific version of Ubuntu. We do not verify installations of every SDK and Ubuntu version combinations in general.

regards

Suman

0 William Cram over 3 years ago in reply to Suman Anna

Prodigy 205 points

What versions of Ubuntu have you verified this installation of SDK / Yocto build and successful build and install of the examples?

0 Suman Anna over 3 years ago in reply to William Cram

TI__Guru** 111055 points

Hi William,

The SDK was officially released on Ubuntu 14.04 (Ubuntu 16.04 also seems to be ok as per documentation, but Ubuntu 14.04 is preferred).

regards

Suman

0 William Cram over 3 years ago in reply to Suman Anna

Prodigy 205 points

Ok, I am on a 14.04 and I am getting the following error and I am unsure how to proceed:

Here is the text output of the entire run:

Fullscreen ti_processor_sdk_linux_automotive_dra7xx-evm_setup_error.txt Download

--------------------------------------------------------------------------------
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 14.04 found successfully, continuing..
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This step will make sure you have the proper host support packages installed
using the following command: sudo apt-get install ssh corkscrew gawk texinfo chrpath git-email g++ libc6:i386 libc6-i386 libstdc++6:i386 libncurses5:i386 libz1:i386 libc6:i386 libc6-dev-i386 device-tree-compiler nfs-kernel-server

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
Note, selecting 'zlib1g:i386' instead of 'libz1:i386'
chrpath is already the newest version.
device-tree-compiler is already the newest version.
g++ is already the newest version.
gawk is already the newest version.
texinfo is already the newest version.
corkscrew is already the newest version.
libncurses5:i386 is already the newest version.
libc6-dev-i386 is already the newest version.
libc6-i386 is already the newest version.
nfs-kernel-server is already the newest version.
ssh is already the newest version.
git-email is already the newest version.
libc6:i386 is already the newest version.
libstdc++6:i386 is already the newest version.
zlib1g:i386 is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
./bin/setup-package-install.sh: line 17: svn: command not found

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)
Ensure that complete path is provided, otherwise NFS path in bootargs might be incomplete
[ /home/osboxes/targetfs ] 
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This step will extract the target filesystem to /home/osboxes/targetfs

Note! This command requires you to have administrator priviliges (sudo access) 
on your host.
Press return to continue
Please wait while extracting NFS filesystem...

Successfully extracted tisdk-rootfs-image-dra7xx-evm.tar.xz to /home/osboxes/targetfs
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This step will update the EXEC_DIR variables in the Rules.make file
This will facilitate the SDK to install (with make install) rebuilt binaries in
    /home/osboxes/targetfs/home/root/dra7xx

The files will be available from /home/root/dra7xx on the target.

This setting can be changed later by editing Rules.make and changing the
EXEC_DIR variable.

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/osboxes/targetfs already NFS exported, skipping..
--------------------------------------------------------------------------------
Restarting NFS and TFTP server

 * Stopping NFS kernel daemon                                                                                                                                          [ OK ] 
 * Unexporting directories for NFS kernel daemon...                                                                                                                    [ OK ] 
 * Exporting directories for NFS kernel daemon...                                                                                                                      [ OK ] 
 * Starting NFS kernel daemon                                                                                                                                          [ OK ] 
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
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 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/ttyUSB0. 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/ttyUSB0 ] 

Copied existing /home/osboxes/.minirc.dfl to /home/osboxes/.minirc.dfl.old

Configuration saved to /home/osboxes/.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.
Select Linux kernel location:
 1: SD card

[ 1 ] 

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

[ 1 ] 

Resulting u-boot variable settings:

setenv baudrate 115200
fatload mmc 0:1 0x825f0000 dra7-evm.dtb
fatload mmc 0:1 0x80300000 uImage
setenv bootargs 'elevator=noop console=ttyO0,115200n8 earlyprintk root=/dev/mmcblk0p2 rw rootwait fixrtc'
setenv fdt_high 0x84000000
bootm 0x80300000 - 0x825f0000
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
To use the SDK, you need to have Linaro cross compiler toolchain installed
Do you want to install it now Y/n  
[ y ]

In which directory do you want to fetch the cross compiler on the host?(if this directory does not exist it will be created)
[ /home/osboxes ] 
--------------------------------------------------------------------------------
--2021-12-01 13:32:37--  https://developer.arm.com/-/media/Files/downloads/gnu-a/8.3-2019.03/binrel/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf.tar.xz
Resolving developer.arm.com (developer.arm.com)... 184.25.139.123
Connecting to developer.arm.com (developer.arm.com)|184.25.139.123|:443... connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: https://armkeil.blob.core.windows.net/developer/Files/downloads/gnu-a/8.3-2019.03/binrel/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf.tar.xz [following]
--2021-12-01 13:32:37--  https://armkeil.blob.core.windows.net/developer/Files/downloads/gnu-a/8.3-2019.03/binrel/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf.tar.xz
Resolving armkeil.blob.core.windows.net (armkeil.blob.core.windows.net)... 52.239.137.100
Connecting to armkeil.blob.core.windows.net (armkeil.blob.core.windows.net)|52.239.137.100|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 256094408 (244M) [application/octet-stream]
Saving to: ‘gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf.tar.xz’

100%[====================================================================================================================================>] 256,094,408  900KB/s   in 12m 42s

2021-12-01 13:45:20 (328 KB/s) - ‘gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf.tar.xz’ saved [256094408/256094408]


Successfully extracted the cross compiler to /home/osboxes
You seem to have 64 bit ubuntu, installing ia32-libs...
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Package ia32-libs is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  lib32z1 lib32ncurses5 lib32bz2-1.0

E: Package 'ia32-libs' has no installation candidate
Updating cross compiler used by Makefile
--------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------
The repo tool will be installed in ./bin folder
----------------------------------------------------------------------------------------------
--2021-12-01 13:45:39--  http://commondatastorage.googleapis.com/git-repo-downloads/repo
Resolving commondatastorage.googleapis.com (commondatastorage.googleapis.com)... 142.250.115.128, 2607:f8b0:4023:1004::80
Connecting to commondatastorage.googleapis.com (commondatastorage.googleapis.com)|142.250.115.128|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 44944 (44K) [application/octet-stream]
Saving to: ‘./bin/repo-temp’

100%[====================================================================================================================================>] 44,944      --.-K/s   in 0.04s   

2021-12-01 13:45:40 (1.16 MB/s) - ‘./bin/repo-temp’ saved [44944/44944]

Successfully extracted the repo tool to ./bin
Proceeding with repo init -u git://git.ti.com/glsdk/release-manifest.git
 
repo: error: Python 2 is no longer supported; Please upgrade to Python 3.5+.
Failed setup, aborting..
Failed setup, aborting..

0 Suman Anna over 3 years ago in reply to William Cram

TI__Guru** 111055 points

Hi William,

I believe the issue is caused by the latest repo tool, the error you are seeing is being thrown by the repo tool. Python 2.7 has been marked EOL sometime in 2020, and the latest repo tool is updated for this.

Can you give the output of repo --version?

I will meanwhile try to check the version used when the SDK was released.

regards

Suman