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.

RTOS/TI-RTOS: Cannot get available products window to show anything

Part Number: TI-RTOS

Tool/software: TI-RTOS

CCS Version  Version: 7.1.0.00016  just updated.

This used to work, now not at all

Launch CCSV7 with clean option after update.
Create new Workspace
Project -> New CCS Project
Target MSP430FR5994
Name Test01
Goto
TI_RTOS Examples
Driver Examples
Empty Examples
Empty Project

Next Select TI-RTOS for MSP43X 2.20.0.06
Target:ti.targets.msp430.elf.MSP430X
Platform:ti.platforms.msp430:MSP430FR5994
Build Profile: Release
All the defaults
XDCTools default is 3.32.0.06_core but select 3.5.1.12_core as it is newer.
Finish
Build project
Get errors
Description Resource Path Location Type
error #148: declaration is incompatible with "xdc_Ptr ti_sysbios_BIOS_RtsGateProxy_Proxy__delegate__S(void)" (declared at line 244 of "C:/ti/tirtos_msp43x_2_20_00_06/products/bios_6_46_00_23/packages/ti/sysbios/package/BIOS_RtsGateProxy.h") .xdchelp /Test01 line 7482 C/C++ Problem

Select 3.323.0.06_core
Clean and build
No errors this time
Now select empty.cfg to view
No Available Products Window
Select view - Available products window.
Window opens but tells me there is no RTSC configuration b Filke op0en. But have one open empty.cfg
Apparently it doesn't recognize it
Create new RTSC Configuration File from new file menu  file: Same story
Now what?

  • There is a known issue with XDCtools 3.32 and CCS 7.1. You cannot graphically edit the .cfg file. The build should work (which is what you are seeing). The options are
    1. Use 3.32 and edit the .cfg as a text file.
    2. Use 3.50 to edit and then switch to 3.32 to build.

    Todd
  • Any idea when the underlying problem will be corrected?
  • It turns out that 3.32.00 is okay to use for xGConf and building with CC7.1. Do not use 3.32.01 though. So I should have said
    0. Use 3.32.00 and all is well (you can get it here: http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc/index.html
    1. Use 3.32.01 and edit the .cfg as a text file.
    2. Use 3.50 to edit and then switch to 3.32.01 to build.

    The next TI-RTOS for MSP430 will use XDCtools 3.50. The exact time-frame for the next TI-RTOS release is up in the air. We'll be removing the MSP432 out of TI-RTOS for MSP430 since the MSP432 is supported in the SimpleLink SDK (which has TI-RTOS).

    [edit...fixed link]

  • Todd,

    Thanks.  Don't have 3.32.00 and the link is broken

    http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc/index.html)

    Produces the following error message:

    An error occurred while processing your request.

    Reference #132.c734fea5.1493221232.1ca37083

    I do have

    3.50.1.;12_core

    3.2.1.22_core

    3.2.0.06_core

    Compiling gpiointerrupt with the 3.5 version  yields:

    Description Resource Path Location Type
    error #148: declaration is incompatible with "xdc_Ptr ti_sysbios_BIOS_RtsGateProxy_Proxy__delegate__S(void)" (declared at line 244 of "C:/ti/tirtos_msp43x_2_20_00_06/products/bios_6_46_00_23/packages/ti/sysbios/package/BIOS_RtsGateProxy.h") .xdchelp /gpiointerrupt_MSP_EXP430FR5994_TI line 7293 C/C++ Problem

    Compiling with 3.2.0.06 yields:

    Clean compile but still need to hand edit the cfg file.

    If you can send me a better link to 3.32.0.0 I will give it a try.

    My CCS is fully updated. A check for updates yields no updates found.

    Starting to feel a pinch. I have finished the upstream part of the project and need to get this part going again.

    Thanks again for your help.

    Frank

  • Todd,
    Sorry for all the bother. The link works to a point. I am getting to the correct page but 3.32.00 is not there.

    XDCTools 3.32
    3.32.01.22 - FOR USE WITH CCS 6.1 (or later) ONLY. See release notes for bugs fixed in this release.
    3.32.00.06 - FOR USE WITH CCS 6.1 (or later) ONLY. See release notes for bugs fixed in this release.

    I have tried the 3.32.00.06 version and it doesn't produce the products panel for the cfg file.
    Plan B? Should I use the jre version even the no jre is recommended for CCS which uses Eclipse

    XDCtools Product Downloads
    Title Description Size
    3.32.00.06 Core (Windows) 3.32.00.06 Core for Windows 57816K
    3.32.00.06 Core (Linux) 3.32.00.06 Core for Linux 64344K
    3.32.00.06 Core (MacOS) 3.32.00.06 Core for MacOS 10.9 64176K
    XDCtools Core without a JRE. Recommended for use within the Eclipse IDE.
    3.32.00.06 Core - JRE (Windows) 3.32.00.06 Core without a JRE for Windows 20976K
    3.32.00.06 Core - JRE (Linux) 3.32.00.06 Core without a JRE for Linux 18584K
    3.32.00.06 Core - JRE (MacOS) 3.32.00.06 Core without a JRE for MacOS 10.9 18784K
    ?
    Thanks
    Frank
  • I was omitting the build number (last digit). It is 3.32.00.06 that you want.

    What does your screen look like?

    If it does not have the "Available Products", please open View->Other...->RTSC->Available Projects.

    If it does not have the "Outline", please open View->Outline

  • Todd,

    Alreadfy tried that.  Started anew to make sure everything from the correct place.

    Retrived the TMP006 I2C project using resource explorer. Took it from the TI-RTOS for MSP430-v2.20.00.06 tree from Development tools msp-exp430fr5994 driver examples I2C examples I2C TMP006

    Loaded it, used clean and build, opened up the Available products window, loaded the i2ctmp006.cfg file and got the following text in the window "shows modules on the package path of an RTSC project This view is currently empty because there is no RTSC Configuration file open.  i2ctmp006.cfg IS open so should show the tree.

    Checked the PATHS under properties Resource linked resources, all ok, Correct XDCTools 3.32.0.06_core, TI-RTOS for MSP43x 2.20.0.06 OK Compiler Ti v16.9.2 LTS

    Other paths appear to be correct.

    Ideas?

    Frank

  • Can you attach a screen-shot of your project? For example

    Also the complete rebuild log. Please attach instead of copy/pasting.

  • Todd ,

    Found the log file.  Tried to get the screen shot to you gave up after 20 mins of load time, will try again. Will do screenshot in a seperate reply so you should at least get this

    Thanks

    Frank

    4454.gpiointerrupt_MSP_EXP430FR5994_TI.build.log

  • Frank,
    I am not sure if you still have this problem, but in case you do I would like to ask you for a screenshot that shows Available Products View and the XGconf view at the same time. Right-click on the CFG script and then choose Open With->XGCONF. Can you post a screenshot of the XGconf view, while Available Product View displays the message that there are no open CFG files?
  • It is still a problem but getting curiouser and curiouser.  I have attached a compressed file with two screen shots.  The first illustrates the original problem, which still exists.  In the first one I double cliked the cfg file and got the error., also note that there is no [TIRTOS] after the file name.

    The second screenshot is after opening the cfg file with XGCONF.  Now all is well, it even added the [TIRTOS] indicator.  If I close both instances of the cfg file and then reopen with a double click, in the same sessio.  Available products is ok.

    If I exit CCS and reenter and do the same thing it remebers that it is actuallly a config file.  If I pick a different project the same problem with a double click. open it with XGCONF and it is good to go as a cfg file

    It appears thatthe first time you open a TIRTOS project and double click it doesn't recognize the file for what it is, Once it get s opewned directly by XGCONF it remembers.

    Hope this helps.

    Frank

    7077.AvailableProducts.zip

     
     
  • Frank,
    screens shots display an expected behavior. A CFG script can be opened in two different ways: in a text editor as a regular text file or in the XDGconf view. When it's opened as a text file, there is no extra processing that detects which products are used in the project and you get that message in the Available Products view.

    CCS comes with a default action when you double-click on a CFG script. For CCS 7.1, the default action is to open a CFG script in a text editor, but you can change the default, which is what you did.