• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 53 subscribers
  • Views 1851 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CCSv6 Linux - Error: No build-tools are currently installed for ISA family 'ARM'!

Stephan Goldenberg
Intellectual 420 points

This is what I get when I try to start a new Tiva-C LP project. When I go to 'Help'->'Install New Software', there's a TI Tiva-C device support and GCC Arm Tools Update site listed but nothing to add.

How do I get this working ?

  • 0
    TI__Guru**** 450141 points

    Hi Stephan,

    When installing CCS, did you select the options for Tiva C support and TI ARM compiler?

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 420 points

    Hehe, I don't remember but I do think so. Would they appear in the target list and related sites in the update list if not ?

    oppa@oppa-hex-ssd:~/bin/ccsv6/ccsv6$ ls tools/compiler/
C5500_4.4.1  dmed  gcc-arm-none-eabi-4_7-2012q4  MSP430_4.2.2
oppa@oppa-hex-ssd:~/bin/ccsv6/ccsv6$ ls tools/compiler/gcc-arm-none-eabi-4_7-2012q4/
arm-none-eabi  bin  lib  share
oppa@oppa-hex-ssd:~/bin/ccsv6/ccsv6$

    This is from /home/oppa/bin/ccsv6/ccsv6/install_logs/ccs_setup_6.0.0.00091_install.log

    06/11/2014 16:13:27 - writeDebugFile - Edition selected: ::edition0
06/11/2014 16:13:27 - writeDebugFile - Product Families selected: 
06/11/2014 16:13:27 - writeDebugFile - PF_MSP430
06/11/2014 16:13:27 - writeDebugFile - PF_C28
06/11/2014 16:13:27 - writeDebugFile - PF_STELLARIS
06/11/2014 16:13:27 - writeDebugFile - PF_SITARA
06/11/2014 16:13:27 - writeDebugFile - PF_OMAPL13
06/11/2014 16:13:27 - writeDebugFile - PF_C6000_SINGLE
06/11/2014 16:13:27 - writeDebugFile - PF_C6000_MULTI
06/11/2014 16:13:27 - writeDebugFile - Components to be installed: 
06/11/2014 16:13:27 - writeDebugFile - MSP430_CGT_HELP
06/11/2014 16:13:27 - writeDebugFile - CGT_DEFAULTLIBS_MSP430
06/11/2014 16:13:27 - writeDebugFile - DMED
06/11/2014 16:13:27 - writeDebugFile - GCC_ARM_COMPILER
06/11/2014 16:13:27 - writeDebugFile - EMU_STELLARIS
06/11/2014 16:13:27 - writeDebugFile - TIVA_TM4C
06/11/2014 16:13:27 - writeDebugFile - TIVA_TM4E
06/11/2014 16:13:27 - writeDebugFile - DEV_SUPPORT_OMAP
06/11/2014 16:13:27 - writeDebugFile - DEV_SUPPORT_C55XX
06/11/2014 16:13:27 - writeDebugFile - C5500_CGT_HELP
06/11/2014 16:13:27 - writeDebugFile - CGT_DEFAULTLIBS_C5500
06/11/2014 16:13:27 - writeDebugFile - EMU_MSP430
06/11/2014 16:13:27 - writeDebugFile - JRE
06/11/2014 16:13:27 - writeDebugFile - ECLIPSE
06/11/2014 16:13:27 - writeDebugFile - ECLIPSECORE
06/11/2014 16:13:27 - writeDebugFile - P2TOOLS
06/11/2014 16:13:27 - writeDebugFile - GMF
06/11/2014 16:13:27 - writeDebugFile - IDE_MAIN
06/11/2014 16:13:27 - writeDebugFile - IDE_WORKFLOW
06/11/2014 16:13:27 - writeDebugFile - DVT_COMMON
06/11/2014 16:13:27 - writeDebugFile - DVT_UIA
06/11/2014 16:13:27 - writeDebugFile - DVT_VIA_CCS
06/11/2014 16:13:27 - writeDebugFile - XULRUNNER
06/11/2014 16:13:27 - writeDebugFile - INSTALLER
06/11/2014 16:13:27 - writeDebugFile - IDE_MSP430
06/11/2014 16:13:27 - writeDebugFile - DS
06/11/2014 16:13:27 - writeDebugFile - IDE_C2000
06/11/2014 16:13:27 - writeDebugFile - IDE_ARM
06/11/2014 16:13:27 - writeDebugFile - EMU_TI
06/11/2014 16:13:27 - writeDebugFile - EMU_C2000_FLASH
06/11/2014 16:13:27 - writeDebugFile - EMU_C2000
06/11/2014 16:13:27 - writeDebugFile - GREE_C2000_SUPPORT
06/11/2014 16:13:27 - writeDebugFile - DVT_TRACE
06/11/2014 16:13:27 - writeDebugFile - DEV_SUPPORT_SITARA
06/11/2014 16:13:27 - writeDebugFile - DEV_SUPPORT_SHARED
06/11/2014 16:13:27 - writeDebugFile - ARM_QT
06/11/2014 16:13:27 - writeDebugFile - IDE_C6000
06/11/2014 16:13:27 - writeDebugFile - IDE_C5500
06/11/2014 16:13:27 - writeDebugFile - EMU_TI_XDS100
06/11/2014 16:13:27 - writeDebugFile - EMU_TI_XDS200

  • 0 in reply to Stephan Goldenberg
    TI__Guru**** 450141 points

    One quick way to check is to re-run the installer and point it to the existing installation. It should allow you to add/remove components and show which are currently installed.

  • 0 in reply to Ki
    Intellectual 420 points

    Hehe, it's complaining that the directory is not empty and crashes.

    Invalid external http://software-dl.ti.com/ccs/esd/CCSv6/CCS6.0.0.00091_linux and internal http://go-bradley.am.dhcp.ti.com/CCS6.0.0.00091_linux urls
Invalid external http://software-dl.ti.com/ccs/esd/CCSv6/CCS6.0.0.00091_linux and internal http://go-bradley.am.dhcp.ti.com/CCS6.0.0.00091_linux urls
    while executing
"error "Invalid external $m_exturl and internal $m_inturl urls""
    (object "::manifest0" method "::Manifest::setComponentLocation" body line 16)
    invoked from within
"setComponentLocation $component "
    (object "::manifest0" method "::Manifest::readManifestFiles" body line 12)
    invoked from within
"$_instance readManifestFiles"
    (procedure "::Manifest::instance" body line 6)
    invoked from within
"Manifest::instance"
    (object "::iSAPane0" method "::BaseTreePane::createPane" body line 34)
    invoked from within
"::iSAPane0 createPane"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 [string map $map $command]"
    (procedure "_eval_command" line 22)
    invoked from within
"_eval_command $path $cmd $item"
    (procedure "Wizard::createstep" line 29)
    invoked from within
"Wizard::createstep $path $item"
    (procedure "Wizard::raise" line 20)
    invoked from within
"Wizard::raise $path $item $generateEvent"
    (procedure "Wizard::next" line 24)
    invoked from within
"Wizard::next .wizard 1"
    ("eval" body line 1)
    invoked from within
"eval [linsert $args 0 Wizard::$cmd .wizard]"
    (procedure ".wizard" line 1)
    invoked from within
".wizard next 1"
    invoked from within
".wizard.buttons.b1:cmd invoke"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 [list $path:cmd invoke]"
    (procedure "TTKButton::invoke" line 2)
    invoked from within
"TTKButton::invoke .wizard.buttons.b1"
    ("eval" body line 1)
    invoked from within
"eval [linsert $args 0 TTKButton::$cmd .wizard.buttons.b1]"
    (procedure ".wizard.buttons.b1" line 1)
    invoked from within
".wizard.buttons.b1 invoke "
    invoked from within
".wizard.buttons.b1:cmd instate {pressed !disabled} { .wizard.buttons.b1 state !pressed; .wizard.buttons.b1 invoke }"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 [list $path:cmd instate] $args"
    (procedure "TTKButton::instate" line 2)
    invoked from within
"TTKButton::instate .wizard.buttons.b1 {pressed !disabled} { .wizard.buttons.b1 state !pressed; .wizard.buttons.b1 invoke }"
    ("eval" body line 1)
    invoked from within
"eval [linsert $args 0 TTKButton::$cmd .wizard.buttons.b1]"
    (procedure ".wizard.buttons.b1" line 1)
    invoked from within
".wizard.buttons.b1 instate {pressed !disabled} { .wizard.buttons.b1 state !pressed; .wizard.buttons.b1 invoke } "
    (command bound to event)

  • 0 in reply to Stephan Goldenberg
    TI__Guru**** 450141 points

    Stephan,

    I noticed you are using a beta version of v6. i would recommend uninstalling that and installing the full release version (6.0.0.00190). Make sure you install Tiva support and the ARM compiler when doing so.

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 420 points

    Hi,

    downloaded and installed a fresh copy. It's pulling the 'ware's right now. Installer was complaining about a missing libudev.so.0. libudev is installed, a google search made me fool the installer by symlinking libudev.so.1. Looks good so far.

    Well, there's still the old installation around. I will just delete the folder.

    Thanks and have a nice weekend,

    Stephan