• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 54 subscribers
  • Views 2251 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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 fails to build ti_rtos_config (wlan_station project) - bad install?

Craig Heilman
Intellectual 310 points

Other Parts Discussed in Thread: CC3200, CC3200SDK, SYSBIOS

I posted a similar question over in the CC3200 forum but didn't receive any useful responses.

PC: Lenovo E530, Windows 7 Pro, 4 GB RAM, 500 GB HD.

Installed software:

  • CCSv6 using the offline installer (CCS6.0.1.00040_win32.zip)
  • CC3200 SDK 1.0.0 (CC3200SDK-1.0.0-windows-installer.exe)
  • ServicePack (CC31xx_CC32xx_ServicePack-1.0.0.1-windows-installer.exe)
  • TI-RTOS for SimpleLink 2.1.0.3 via CCSv6 App Center
  • XDCtool 3.30.04.52

Problem: while working through the CC3200 Getting Started Guide the build of ti_rtos_config fails with errors such as this:

gmake[1]: Entering directory `C:/ti/CC3200SDK_1.0.0/cc3200-sdk/ti_rtos/ti_rtos_config/src/sysbios'

asmem4 C:/ti/tirtos_simplelink_2_01_00_03/products/bios_6_40_03_39/packages/ti/sysbios/family/arm/m3/Clobber_asm.sv7M ...

abnormal program termination

C:/Users/Craig/AppData/Local/Temp/make17992-1.sh: fork failed: no error [1]

I searched the forums and elsewhere online but found no clues to the cause of the build failures.

As part of my investigation, I looked through the C:\ti\ccsv6\install_logs and found a few items of concern (non-zero exit codes).

ti_cc3200_setup_1.0.0.3_install.log

Executing c:/ti/ccsv6\utils\bin\DPInst64.exe /sw /sa /path "c:/ti/ccsv6\ccs_base\emulation\drivers\cc3200\ftdi"

Script exit code: 512

DPInst64.exe retrun error code 512 = 0x00000200 which translates to "2 driver packages copied to DIFx driver store (i.e. driver repository) but were not installed" => may be seeing this return code because the ftdi drivers were already installed before this script was executed?

ti_emupack_5.1.507.2_install.log

[15:54:37] Running XDS100 Driver Installer
Executing c:/ti/ccsv6/ccs_base/emulation/windows/xds100_drivers/ftdi/DPInst64.exe /lm /q
Script exit code: 512

[15:54:38] Running XDS560 Driver Installer
Executing c:/ti/ccsv6/ccs_base/emulation/windows/xds560_drivers/DPInst64.exe /SW /SE
Script exit code: 256

[15:54:39] Running XDS2xx Driver Installer
Executing c:/ti/ccsv6/ccs_base/emulation/windows/xds2xx_drivers/DPInst64.exe /LM /SW
Script exit code: 256

ti_tiva_stellaris_2.0.3.12770_install.log



[15:54:45] installing 64bits icdi on windows
installing 64bits icdi driver
Executing dpinst64.exe /lm /sw
Script exit code: 768

[15:54:46] installing 64bits ftdi on windows
installing ftdi(64bits) driver
Executing dpinst64.exe /lm /sw
Script exit code: 512

As noted above, I'm assuming the error codes I'm seeing are just side effects of the fact that I had previously connected the CC3200 LaunchPad board and installed the drivers for it? Can anyone confirm that?

Of course, if you have any suggestions to address the bigger problem of getting ti_rtos_config to build, I'm open hearing them!

Thanks,

Craig

  • 0
    Intellectual 310 points

    I think I found the solution to the build problem. Based on some postings over in the CCS forum about possible problems with the Windows PATH system environment variable, I checked and discovered numerous modifications to the path, mostly for various tools and utilities. The first two entries were: C:\UnxUtils\bin;C:\UnxUtils\usr\local\wbin; UnxUtils is a set of GNU utilities for Windows, including make! I thought those could be interfering with the build so I removed those two entries. Unbelievably, ti_rtos_config then built without any errors as did the rest of the wlan_station project files.

    I'm posting this followup in case anyone else runs into an error like this!

  • 0 in reply to Craig Heilman
    Prodigy 10 points

    Thanks. I had the same problem building in wlan_station. I had another ARM compiler installed under C:/yagarto 

    As a quick fix I renamed the yagarto directory to was_yagarto and wlan_station built.

  • 0 in reply to Craig Heilman
    Prodigy 10 points

    This solved my problem. Thanks so much!

    Best, Slobodan