• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Subscribers 101 subscribers
  • Views 864 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.

build ti-rtos on win7 hangs. help buil ti-rtos for arm targets

alexander lityagin
Prodigy 200 points
Other Parts Discussed in Thread: SYSBIOS, CCSTUDIO

hallow. i download and install ti-rtos 2.0.1.23 for C6000. since it is not contains arm libraryes, i try to build it with additional targets/ i changes tirtos.mak so:

correct pathes to my CGT compilers C6000 (7.4.11) and arm (5.1.9)

correct XDCTOOLS_INSTALLATION_DIR to my one (3.30.5.60)

append defines:

ti.targets.elf.Arm9           ?= $(DEFAULT_INSTALLATION_DIR)/ccsv6/tools/compiler/arm_5.1.9
ti.targets.elf.Arm9t          ?= $(DEFAULT_INSTALLATION_DIR)/ccsv6/tools/compiler/arm_5.1.9
ti.targets.elf.Arm8F          ?= $(DEFAULT_INSTALLATION_DIR)/ccsv6/tools/compiler/arm_5.1.9
ti.targets.elf.Arm9F          ?= $(DEFAULT_INSTALLATION_DIR)/ccsv6/tools/compiler/arm_5.1.9
ti.targets.elf.Arm15F         ?= $(DEFAULT_INSTALLATION_DIR)/ccsv6/tools/compiler/arm_5.1.9

enhance XDCARGS with:

       ti.targets.elf.Arm8F='$(ti.targets.elf.Arm8F)' \
       ti.targets.elf.Arm9F='$(ti.targets.elf.Arm9F)' \
       ti.targets.elf.Arm15F='$(ti.targets.elf.Arm15F)' \
       ti.targets.elf.Arm9='$(ti.targets.elf.Arm9)' \
       ti.targets.elf.Arm9t='$(ti.targets.elf.Arm9t)'

after all building target 'bios' hangs after such log:

cle674 c:/ti/xdctools_3_30_05_60_core/packages/xdc/runtime/knl/GateProcessSupportNull.c ...
archiving package/lib/lib/ti.targets.rts6000/package/package_ti.targets.rts6000.oe674 package/lib/lib/ti.targets.rts6000
/xdc/runtime/Assert.oe674 package/lib/lib/ti.targets.rts6000/xdc/runtime/Core-mem.oe674 package/lib/lib/ti.targets.rts60
00/xdc/runtime/Core-smem.oe674 package/lib/lib/ti.targets.rts6000/xdc/runtime/Core-label.oe674 package/lib/lib/ti.target
s.rts6000/xdc/runtime/Core-params.oe674 package/lib/lib/ti.targets.rts6000/xdc/runtime/Diags.oe674 package/lib/lib/ti.ta
rgets.rts6000/xdc/runtime/Error.oe674 package/lib/lib/ti.targets.rts6000/xdc/runtime/Gate.oe674 package/lib/lib/ti.targe
ts.rts6000/xdc/runtime/GateNull.oe674 package/lib/lib/ti.targets.rts6000/xdc/runtime/HeapMin.oe674 package/lib/lib/ti.ta
rgets.rts6000/xdc/runtime/HeapStd.oe674 package/lib/lib/ti.targets.rts6000/xdc/runtime/Log.oe674 package/lib/lib/ti.targ
ets.rts6000/xdc/runtime/LoggerBuf.oe674 package/lib/lib/ti.targets.rts6000/xdc/runtime/LoggerCallback.oe674 package/lib/
lib/ti.targets.rts6000/xdc/runtime/LoggerSys.oe674 package/lib/lib/ti.targets.rts6000/xdc/runtime/Memory.oe674 package/l
ib/lib/ti.targets.rts6000/xdc/runtime/Registry.oe674 package/lib/lib/ti.targets.rts6000/xdc/runtime/Rta.oe674 package/li
b/lib/ti.targets.rts6000/xdc/runtime/Startup.oe674 package/lib/lib/ti.targets.rts6000/xdc/runtime/System.oe674 package/l
ib/lib/ti.targets.rts6000/xdc/runtime/SysCallback.oe674 package/lib/lib/ti.targets.rts6000/xdc/runtime/SysMin.oe674 pack
age/lib/lib/ti.targets.rts6000/xdc/runtime/SysStd.oe674 package/lib/lib/ti.targets.rts6000/xdc/runtime/Text.oe674 packag
e/lib/lib/ti.targets.rts6000/xdc/runtime/Timestamp.oe674 package/lib/lib/ti.targets.rts6000/xdc/runtime/TimestampNull.oe
674 package/lib/lib/ti.targets.rts6000/xdc/runtime/TimestampStd.oe674 package/lib/lib/ti.targets.rts6000/xdc/runtime/xdc
_noinit.oe674 package/lib/lib/ti.targets.rts6000/xdc/runtime/knl/Cache.oe674 package/lib/lib/ti.targets.rts6000/xdc/runt
ime/knl/GateThread.oe674 package/lib/lib/ti.targets.rts6000/xdc/runtime/knl/Semaphore.oe674 package/lib/lib/ti.targets.r
ts6000/xdc/runtime/knl/SyncNull.oe674 package/lib/lib/ti.targets.rts6000/xdc/runtime/knl/GateH.oe674 package/lib/lib/ti.
targets.rts6000/xdc/runtime/knl/SemProcess.oe674 package/lib/lib/ti.targets.rts6000/xdc/runtime/knl/Sync.oe674 package/l
ib/lib/ti.targets.rts6000/xdc/runtime/knl/SyncSemThread.oe674 package/lib/lib/ti.targets.rts6000/xdc/runtime/knl/GatePro
cess.oe674 package/lib/lib/ti.targets.rts6000/xdc/runtime/knl/SemThread.oe674 package/lib/lib/ti.targets.rts6000/xdc/run
time/knl/SyncGeneric.oe674 package/lib/lib/ti.targets.rts6000/xdc/runtime/knl/Thread.oe674 package/lib/lib/ti.targets.rt
s6000/xdc/runtime/knl/CacheSupportNull.oe674 package/lib/lib/ti.targets.rts6000/xdc/runtime/knl/GateThreadSupportNull.oe
674 package/lib/lib/ti.targets.rts6000/xdc/runtime/knl/GateProcessSupportNull.oe674 into lib/ti.targets.rts6000.ae674 ..
.
cle674 package/package_ti.targets.rts6000.c ...
cle674 boot.c ...
"boot.c", line 76 (col. 1): remark #1463-D: Link-time optimization is disabled for this file due to the use of inline as
sembly
cle674 autoinit.c ...
"autoinit.c", line 30 (col. 26): remark #1463-D: Link-time optimization is disabled for this file due to the use of weak
 symbols
archiving package/lib/lib/boot/package/package_ti.targets.rts6000.oe674 package/lib/lib/boot/boot.oe674 package/lib/lib/
boot/autoinit.oe674 into lib/boot.ae674 ...
.libraries files complete: Mon Dec 15 13:41:01 RTZ 2014.
======== .dlls [./packages/gnu/targets] ========
======== .dlls [./packages/gnu/targets/arm] ========
======== .dlls [./packages/gnu/targets/arm/rtsv7A] ========
======== .dlls [./packages/ti/sysbios] ========
configuring instrumented.pe66 from package/cfg/instrumented_pe66.cfg ...
generating custom ti.sysbios library makefile ...
Starting build of library sources ...

and there is hanging infinitely....

  • 0
    TI__Mastermind 30830 points
    Does it truly hang infinitely or simply for a very long time?
  • 0 in reply to Alan DeMars
    Prodigy 200 points
    i wait about 5 minutes, system monitor shows that ccstudio.exe and sh.exe is ocupies about 1% of cpu all this time, after ctrl+break it shows:

    Full thread dump Java HotSpot(TM) Client VM (11.3-b02 mixed mode):

    "Thread-0" prio=6 tid=0x004b4800 nid=0x278 runnable [0x0e17f000..0x0e17fb68]
    java.lang.Thread.State: RUNNABLE
    at java.io.FileInputStream.readBytes(Native Method)
    at java.io.FileInputStream.read(Unknown Source)
    at sun.nio.cs.StreamDecoder.readBytes(Unknown Source)
    at sun.nio.cs.StreamDecoder.implRead(Unknown Source)
    at sun.nio.cs.StreamDecoder.read(Unknown Source)
  • 0 in reply to alexander lityagin
    TI__Mastermind 30830 points
    I'll try to reproduce the results.
    Which ARM devices are you trying to build for?
    Is there a reason you don't simply download the corresponding TI-RTOS package for that device (ie TivaC or Sitara)?
  • 0 in reply to Alan DeMars
    TI__Mastermind 30830 points
    I was able to reproduce the problem if I used a non dos cmd.exe shell (ie git bash) to build with.
    If I use a normal dos cmd.exe shell, the build proceeds to completion.
  • 0 in reply to Alan DeMars
    Prodigy 200 points

    this is reproduces for any kind of building arm and c6000 on Win7 standart cmd.exe

  • 0 in reply to alexander lityagin
    TI__Mastermind 30830 points
    Hmm. This worked for me and I'm running Windows 7.
    If you remove the ARM targets does the problem occur?
    How are you invoking the cmd.exe DOS prompt window?
    I am typing 'cmd' in the 'Run' window launched from the Start menu.
  • 0 in reply to Alan DeMars
    Prodigy 200 points

    i try both: from start menu run cmd, or from totalcmd in admistrator user run same.

    maybe helps my environment?

    ACTEL_FOR_ALTIUM_OVERRIDE=
    ALLUSERSPROFILE=C:\ProgramData
    APPDATA=C:\Users\a_lityagin\AppData\Roaming
    COMMANDER_DRIVE=C:
    COMMANDER_EXE=C:\Program Files\Total Commander\TOTALCMD64.EXE
    COMMANDER_INI=C:\Users\a_lityagin\AppData\Roaming\GHISLER\wincmd.ini
    COMMANDER_PATH=C:\Program Files\Total Commander
    CommonProgramFiles=C:\Program Files\Common Files
    CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
    CommonProgramW6432=C:\Program Files\Common Files
    COMPUTERNAME=DEVELOPER
    ComSpec=C:\Windows\system32\cmd.exe
    FP_NO_HOST_CHECK=NO
    HOMEDRIVE=C:
    HOMEPATH=\Users\a_lityagin
    LOCALAPPDATA=C:\Users\a_lityagin\AppData\Local
    LOGONSERVER=\\SERVER03
    NUMBER_OF_PROCESSORS=2
    OS=Windows_NT
    Path=C:\Python\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\TortoiseSVN\bin;C:\Python\Scripts;C:\Program Files\TortoiseGit\bin;C:\Git\cmd;C:\Git\bin;C:\Program Files\TortoiseHg\
    PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
    PROCESSOR_ARCHITECTURE=AMD64
    PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 23 Stepping 10, GenuineIntel
    PROCESSOR_LEVEL=6
    PROCESSOR_REVISION=170a
    ProgramData=C:\ProgramData
    ProgramFiles=C:\Program Files
    ProgramFiles(x86)=C:\Program Files (x86)
    ProgramW6432=C:\Program Files
    PROMPT=$P$G
    PSModulePath=C:\Windows\system32\WindowsPowerShell\v1.0\Modules\
    PUBLIC=C:\Users\Public
    SAL_ACCESSIBILITY_ENABLED=1
    SystemDrive=C:
    SystemRoot=C:\Windows
    TEMP=C:\Users\A_LITY~1\AppData\Local\Temp
    TMP=C:\Users\A_LITY~1\AppData\Local\Temp
    USERDNSDOMAIN=TCT
    USERDOMAIN=TCT
    USERNAME=a_lityagin
    USERPROFILE=C:\Users\a_lityagin
    VBOX_MSI_INSTALL_PATH=C:\Program Files\Oracle\VirtualBox\
    windir=C:\Windows
    XILINX_FOR_ALTIUM_OVERRIDE=

  • 0 in reply to alexander lityagin
    TI__Mastermind 30830 points
    I suspect that one of the directories in your Path has a 'gmake' executable in it that is taking precedent over the gmake provided by the xdctools. Can you try removing the WindowsPowerShell directory from the Path and see if that makes a difference? You might also try removing everything but "C:\Windows\system32;C:\Windows" from the Path.
  • 0 in reply to Alan DeMars
    Prodigy 200 points

    i try to invoke gmake and cmd report that cant foun one - so there is no gmake availiable from PATH

    how PowerShell can affects cmd? this directory not comtain any cmd.exe

    my locale, maybe it helps, is russian. and for some cmd limitations - it is supports only ansi characters, any no-ansi char replaces as ?

  • 0 in reply to Alan DeMars
    Prodigy 200 points
    ok? it now works! look like something from c:\git\bin or subversion\bin hampers.
    but now i stands another problem - wahat started from - how to build sysbios for arm?
    my addition for arm9,arm9 - doesnt build anything.
    i try to add:
    #
    # Enable TI-RTOS to build for GCC.
    # Set IAR_ENABLE to true and modify path to toolchain
    #
    GCC_BUILD ?= true
    GCC_INSTALLATION_DIR ?= $(DEFAULT_INSTALLATION_DIR)/ccsv6/tools/compiler/gcc-arm-none-eabi-4_7-2013q3
    gnu.targets.arm.A8F ?= $(GCC_INSTALLATION_DIR)
    gnu.targets.arm.A9F ?= $(GCC_INSTALLATION_DIR)
    ....
    and
    ifeq ("$(GCC_BUILD)", "true")
    XDCARGS += \
    gnu.targets.arm.A8F='$(gnu.targets.arm.A8F)' \
    gnu.targets.arm.A9F='$(gnu.targets.arm.A9F)'
    endif

    and GNU doesnt build anything for arm9 too.