• State TI Thinks Resolved
  • Locked Locked
  • Replies 20 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 1381 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.

CCS: Resource explorer encountered a problem...

Saleh Elmohamed
Intellectual 970 points
Other Parts Discussed in Thread: C2000WARE, MSP430WARE, CONTROLSUITE, POWERSUITE, CC2652RB, UNIFLASH

Tool/software: Code Composer Studio

Dear TI friends,

Currently running CCS version 8.3.1.00004 on a

windows-based desktop at our lab. A colleague &

I have been running into difficulties in trying to open

Resource Explorer. What we get every time we try

to open the explorer is the following message

(appearing just few seconds after trying to do

Loading ... Starting TIREX ...):

"RE encountered a problem. Please close & reopen

RE: If you continue to experience problems then please refer to: 

processors.wiki.ti.com/.../Troubleshooting_CCSv7

Done all of that few times to no avail. Re-started CCS few times

as well but still no solution to getting RE opened ....

Would appreciate any suggestions you might have on this.

Many thanks and very happy summer.

-Saleh

  • 0
    TI__Guru**** 159715 points

    Saleh,

    Could you see if there are any log files here:

     c:\Users\<user>\ti\tirex-localserver-3.7.1\logs

    If there are log files please zip them up and attach them to this thread.  They may be able to help us figure out what is going on.

    Regards,

    John

  • 0 in reply to JohnS
    Intellectual 970 points

    Hi John,

    Thanks for the reply. Looks like we only got tirex-localserver-3.7.0

    and inside that folder I noticed two folders: db and downloads.

    1. The db folder contains:

    _packages.db    devtools.db    overviews.db    packages.db.index
    devices.db    devtools.db.index   overviews.db.index   resources.db
    devices.db.index  logs    packages.db     sitemap

    Ok, the logs sub-folder is empty. sitemap and resources.db sub-folders

    are also empty.

    2. The downloads folder contains:

    devices.dbimages.zip
    devtools.dbimages.zip
    tmp_bundle_motor_control_c2000ware_sdk_software_package__2.00.00.00_makeoffline_2a8575ea752ef9bcb0133b8609e8249e899434c3

    The 3rd item is sub-folder and it is empty as well.

    That is all there is there. Any thoughts on what is happening there?

    I certainly have no idea on that at this point.

    Many thanks,

    Saleh

  • 0 in reply to Saleh Elmohamed
    TI__Guru**** 159715 points

    Saleh,

    3.7.0 is fine.  

    Looks like on Windows the logs folder is actually .logs.  Sorry about that.

    Depending on your windows settings that could be hidden. In windows explorer just add the \.logs manually after tires-localserver-3.7.0

    Regards,

    John

  • 0 in reply to Saleh Elmohamed
    Intellectual 970 points

    John,

    Attached is the gzip of the log file appearing there.

    I missed it the first time so sorry about that.

    -Saleh

  • 0 in reply to Saleh Elmohamed
    TI__Intellectual 970 points

    Hi Saleh,

    I looked at the log file you sent. It appears there was a problem with downloading SimpleLink CC13x2 26x2 SDK v3.20.00.68. Could you send me the exception/crash logs which are in C:\Users\<user>\AppData\Local\Texas Instruments\CCS\CCSx.x.x.xxxxx\0\dmp\tirex_uncaughtException_<timestamp>.log? 

    Thanks!

    Oliver

  • 0 in reply to OliverP
    Intellectual 970 points

    Hi Oliver,

    CCSx.x.x.xxxxx\0\dmp\tirex_uncaughtException_<timestamp>.log

    Sorry to say that it doesn't exist.

    Doing ls -al inside the CCS folder only show \ti folder and nothings there

    either. I don't recall at all that I ran into any problems with resource explorer

    before now, so I'm not sure what is happening there.

    Thanks for any suggestions.

    -Saleh

  • 0 in reply to Saleh Elmohamed
    TI__Guru**** 159715 points

    Saleh,

    Oliver and I were talking and were wondering if you could try the following.   

    Close Resource Explorer

    Open Resource Explorer

    Repeat a few times

    We have seen a couple cases where this has enabled Resource Explorer to load ok.

    Regards,

    John

  • 0 in reply to JohnS
    Intellectual 970 points

    Will give it a try. Hope it would help.

    It is a bit of strange situation and I was

    not expecting it at all.

    I'll let you now very shortly.

    I appreciate it and very sorry to

    take quite a bit of your time on this.

    -Saleh

  • 0 in reply to Saleh Elmohamed
    Intellectual 970 points

    Did the closing and opening over 10 times

    to no avail.... a loading panel appears for TIREX

    and just few seconds later it disappears and get

    panel of the error message and the referral

    to:

    processors.wiki.ti.com/index.php/Troubleshooting_CCSv7#Resource_Explorer

    Why the referral there to CCSv7?  The version we have is 8 (8.3.1.00004).

    Thanks,

    Saleh

  • 0 in reply to Saleh Elmohamed
    Intellectual 970 points

    Hi John and Oliver,

    Sorry to bug you with all this. Any additional

    thoughts/suggestions to perhaps try out to

    maybe fix this?

    Restarted it few times as well as tried all

    the suggestions mentioned there in the link.

    No luck so far but perhaps I might have

    missed something somewhere...

    Fee free to drop me any possible

    suggestion to try out.

    Thanks,

    Saleh

  • 0 in reply to Saleh Elmohamed
    TI__Guru**** 159715 points

    Saleh,

    As a temporary solution you can import any of the example projects that come with the SDK from the Project -> Import CCS projects menu.

    I would look on dev.ti.com/tirex to find the example that you are interested in and then use the Import tool to import the example into CCS.

    Our thought was that an underlying process was running out of memory which was preventing Resource Explorer from parsing through all the data to display content.  Are you developing on both C2000 and SimpleLink cc13xx/26xx?  

    Regards,

    John

  • 0 in reply to JohnS
    Intellectual 970 points

    Hi John,

    Thanks for the information and suggestions. I'm also inclined to

    believe that some process was running out of memory. Any hint

    on the name or where to look for it? I looked around quite a bit

    but didn't notice anything.

    At the stage I'm not developing anything on SimpleLink cc13xx/26xx,

    so is there away to get rid of it or delete ...? That perhaps may

    solve the problem .... maybe.

    It is a bit weird, as i recall something like this never happened

    before and we have been CCS for quite a while now.

    Thanks for your help.

    -Saleh

  • 0 in reply to Saleh Elmohamed
    TI__Guru**** 159715 points

    Saleh,

    The SimpleLink SDK will be located in: C:\ti\simplelink_cc13x2_26x2_sdk_<version#>

    If you delete that it will delete the SDK.  

    Lets also delete the local resource explorer database C:\Users\<username>\tirex-localserver-3.7.0

    That will clear out the database files that we believe are causing the process to run out of memory.  Resource Explorer will recreate that folder and this time it won't download the content for the SimpleLink SDK which should reduce the amount of memory used as that is the largest package we have.

    Regards,

    John

  • 0 in reply to JohnS
    TI__Intellectual 970 points

    Saleh,

    Generally it appears you have a large number of packages in c:\ti  -- 88 in total according to your log. While we tried to optimize memory usage on the desktop it still has some limitations (we have plans to make more improvements in future). You also happen to have the top 3 largest Tirex packages installed: SimpleLink CC13x2 26x2 SDK, C2000, and MSP430Ware. So I recommend that if you don't need a package any more to delete the folder in c:\ti. Tirex will then remove the package from its database the next time you start it. 

    Regards,

    Oliver

  • 0 in reply to OliverP
    Intellectual 970 points

    Thanks John and Oliver for the suggestions. I guess there

    are currently a large list of packages and deleting those you

    mentioned helped solve the problem. I deleted the first and

    third largest package: SimpleLink CC13x2 26x2 SDK and

    MSP430Ware ...

    Here is the list of things available there now:

     bios_6_73_00_12
     c2000
     C2000Ware_1_00_00_00_Software
     C2000Ware_1_00_02_00_Software
     C2000Ware_1_00_03_00_Software
     C2000Ware_1_00_04_00_Software
     C2000Ware_1_00_05_00_Software
     C2000Ware_1_00_06_00
     C2000Ware_1_00_06_00_setup.exe
     C2000Ware_1_00_06_00_Software
     C2000Ware_2_00_00_02_Software
     C2000Ware_DigitalPower_SDK_1_00_00_00
     C2000Ware_DigitalPower_SDK_1_00_01_00
     C2000Ware_DigitalPower_SDK_1_02_00_00
     C2000Ware_MotorControl_SDK_1_00_00_00
     C2000Ware_MotorControl_SDK_2_00_00_00
     ccsv8
    'Code Composer Studio 8.3.1.lnk'
     controlSUITE
     msp
     powerSUITE_2_00_00_00
     powerSUITE_2_01_00_00
     powerSUITE_2_03_00_00
     sail_1_10_00_06
     sail_1_20_00_02
     sail_1_30_00_02
     sail_1_40_00_00
     simplelink_academy_154stackplugin_3_10_02_00
     simplelink_academy_154stackplugin_3_20_01_00
     simplelink_academy_bleplugin_3_10_02_00
     simplelink_academy_cc13x0sdk_2_10_02_10
     simplelink_academy_cc13x0sdk_2_20_03_05
     simplelink_academy_cc13x0sdk_2_30_02_00
     simplelink_academy_cc13x0sdk_2_40_01_00
     simplelink_academy_cc13x0sdk_3_10_01_00
     simplelink_academy_cc13x0sdk_3_20_01_00
     simplelink_academy_cc13x2_26x2sdk_2_40_01_00
     simplelink_academy_cc13x2_26x2sdk_3_10_01_00
     simplelink_academy_cc13x2sdk_2_10_02_10
     simplelink_academy_cc13x2sdk_2_20_03_05
     simplelink_academy_cc13x2sdk_2_30_02_00
     simplelink_academy_cc13x2sdk_chinese_1_15_05_02
     simplelink_academy_cc2640r2sdk_2_20_03_05
     simplelink_academy_cc2640r2sdk_2_30_02_00
     simplelink_academy_cc2640r2sdk_2_40_03_00
     simplelink_academy_cc2640r2sdk_3_10_01_00
     simplelink_academy_cc2640r2sdk_3_20_01_00
     simplelink_academy_cc26x2sdk_2_10_02_10
     simplelink_academy_cc26x2sdk_2_20_03_05
     simplelink_academy_cc26x2sdk_2_30_02_00
     simplelink_academy_cc26x2sdk_chinese_1_15_05_02
     simplelink_academy_cc32xxsdk_2_10_00_16
     simplelink_academy_cc32xxsdk_2_20_01_04
     simplelink_academy_cc32xxsdk_2_30_00_02
     simplelink_academy_cc32xxsdk_2_40_00_17
     simplelink_academy_cc32xxsdk_3_10_01_00
     simplelink_academy_msp432e4sdk_2_20_01_04
     simplelink_academy_msp432e4sdk_2_30_01_01
     simplelink_academy_msp432e4sdk_2_40_00_17
     simplelink_academy_msp432e4sdk_3_10_02_00
     simplelink_academy_msp432e4sdk_3_20_00_00
     simplelink_academy_msp432sdk_2_20_01_04
     simplelink_academy_msp432sdk_2_30_01_01
     simplelink_academy_msp432sdk_2_40_00_17
     simplelink_academy_msp432sdk_3_10_02_00
     simplelink_academy_msp432sdk_3_20_00_00
     simplelink_academy_wifiplugin_2_40_00_17
     simplelink_academy_zigbeeplugin_1_15_04_08
     simplelink_academy_zigbeeplugin_2_20_02_02
     simplelink_cc13x0_sdk_1_60_00_21
     simplelink_cc13x0_sdk_2_10_00_36
     simplelink_cc13x0_sdk_2_20_00_38
     simplelink_cc13x0_sdk_2_30_00_20
     simplelink_cc13x0_sdk_2_40_00_20
     simplelink_cc13x0_sdk_3_10_00_11
     simplelink_cc13x0_sdk_3_20_00_23
     simplelink_cc13x2_sdk_2_20_00_71
     simplelink_cc13x2_sdk_2_30_00_45
     simplelink_cc2640r2_sdk_1_40_00_45
     simplelink_cc2640r2_sdk_1_50_00_58
     simplelink_cc2640r2_sdk_2_20_00_49
     simplelink_cc2640r2_sdk_2_30_00_28
     simplelink_cc2640r2_sdk_2_40_00_32
     simplelink_cc2640r2_sdk_3_10_00_15
     simplelink_cc2640r2_sdk_3_20_00_21
     simplelink_cc2640r2_sdk_ble_example_pack_1_50_00_62
     simplelink_cc2652rb_ble_sdk_3_10_00_15
     simplelink_cc26x2_sdk_1_60_00_43
     simplelink_cc26x2_sdk_2_20_00_36
     simplelink_cc26x2_sdk_2_30_00_34
     simplelink_cc32xx_sdk_1_40_01_00
     simplelink_cc32xx_sdk_1_60_00_04
     simplelink_cc32xx_sdk_2_10_00_04
     simplelink_cc32xx_sdk_2_20_00_10
     simplelink_cc32xx_sdk_2_20_01_00
     simplelink_cc32xx_sdk_2_30_00_05
     simplelink_cc32xx_sdk_2_40_02_00
     simplelink_cc32xx_sdk_3_10_00_04
     simplelink_cc32xx_sdk_3_20_00_06
     simplelink_msp432e4_sdk_1_60_00_10
     simplelink_msp432e4_sdk_2_10_00_17
     simplelink_msp432e4_sdk_2_20_00_20
     simplelink_msp432e4_sdk_2_30_00_14
     simplelink_msp432e4_sdk_2_40_00_11
     simplelink_msp432e4_sdk_3_10_00_11
     simplelink_msp432e4_sdk_3_20_00_10
     simplelink_msp432p4_sdk_1_50_00_12
     simplelink_msp432p4_sdk_1_60_00_12
     simplelink_msp432p4_sdk_2_10_00_14
     simplelink_msp432p4_sdk_2_20_00_12
     simplelink_msp432p4_sdk_2_30_00_14
     simplelink_msp432p4_sdk_2_40_00_10
     simplelink_msp432p4_sdk_3_10_00_08
     simplelink_msp432p4_sdk_3_20_00_06
     simplelink_sdk_ble_plugin_1_40_00_42
     simplelink_sdk_nfc_plugin_2_20_00_08
     simplelink_sdk_ti_15_4_stack_plugin_2_20_00_05
     simplelink_sdk_voice_detection_plugin_1_50_00_15
     simplelink_sdk_wifi_plugin_1_55_00_42
     simplelink_sdk_wifi_plugin_1_60_00_07
     simplelink_sdk_wifi_plugin_2_30_00_10
     simplelink_sdk_wifi_plugin_2_40_00_22
     simplelink_zigbee_sdk_plugin_1_60_00_14
     simplelink_zigbee_sdk_plugin_1_60_01_09
     simplelink_zigbee_sdk_plugin_2_20_00_06
     Sitara_1_02_00_00
     tirex-product-tree
     tirtos_cc13xx_cc26xx_2_21_00_06
     tirtos_msp43x_2_20_00_06
     tirtos_simplelink_2_13_01_09
     tirtos_tivac_2_16_00_08
     TivaWare_C_Series-2.1.3.156
     TivaWare_C_Series-2.1.4.178
     uniflash_4.4.0
     uniflash_4.5.0
     uniflash_4.6.0
     watson_cc32xx_1_00_00_04
     watson_cc32xx_1_00_01_01
     watson_cc32xx_1_10_00_04
     watson_cc32xx_1_20_00_04
     watson_msp432e4_1_00_00_04
     watson_msp432e4_1_00_01_01
     watson_msp432e4_1_10_00_04
     watson_msp432e4_1_20_00_04
     xdctools_3_32_00_06_core
     xdctools_3_32_02_25_core
     xdctools_3_50_05_12_core
     xdctools_3_50_07_20_core
     xdctools_3_50_08_24_core
     xdctools_3_51_01_18_core
     xdctools_3_51_02_21_core
     zips

  • 0 in reply to Saleh Elmohamed
    TI__Guru**** 159715 points

    That is a long list!

    Great to hear that it is working for you now.

    Regards,

    John

  • 0 in reply to JohnS
    Intellectual 970 points

    Thanks again John. I'll try to keep on eye on it

    as I update things... Need to be prudent about adding

    any additional materials unless it is quite necessary.

    Might have to offset that by removing old stuff.

    I appreciate the suggestions. I was a bit worried on

    the size of the materials kept there and particularly

    the multiple versions of the same package. So I guess

    now I know its quite negative side-effects.

    Many thanks,

    Saleh

  • 0 in reply to Saleh Elmohamed
    TI__Guru**** 159715 points

    You could always move the older packages to an archive somewhere.  That way you have them if you ever need them again and can just copy them back.

    John

  • 0 in reply to JohnS
    Intellectual 970 points

    That is a great suggestion. I deleted a number of those

    packages (from 018) that we have not used in a while but quite

    likely would need to use them again. So yes moving them

    out of the /c/ti/ folder afterward to something like /c/ti-archive-packages/

    would be a good idea.

    Thanks for your help. Very much appreciate it.

    -Saleh