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 Object view failed to start

Other Parts Discussed in Thread: SYSBIOS, CCSTUDIO

Hi

I have a large program which was ported from Dsp/Bios to sysbios.

When I run the program, even in the start of the main I get the following:

ROV failed to start, ROV failed to initialize for an unknown reason. Issues with the package path are the most common cause.

When I remove most of the code, and run the application, the ROV starts fine. As I add more and more code the time it takes to start is longer and longer. 

At some point it takes so long that the CCS gets stuck and all i can do is close it.

When a lot of the code is in I get the error almost immediately.

So I wasn't able to pinpoint which code causes the problem or if it is just the size of the code.

My configuration is as follows:

CCS - Version: 6.0.1.00040

Compiler version 7.4.8

Varient : Generic C66xx Device

XDC: 3.30.3.47_core

Keystone2 PDK - 3.0.4.18

NDK 2.22.2.16 

SYS/BIOS - 6.40.2.27

Any ideas on how to overcome this?

Shiran

  • Shiran,

    It seems that configuration problems can be ruled out.  To debug this we’ll probably need to get your .out file, and a companion file used by ROV (in the Debug/configPkg/package/cfg subdirectory of the project, with a .rov.xs extension).

    One thing you might try first, is to add an option when invoking CCS to open a separate console window that can show some instrumentation information.  To do this, you can add “-consolelog” option to the shortcut, or when launching CCS directly, for example:

        C:\ti\ccsv6\eclipse>ccstudio -consolelog

    Can you try that and capture what gets thrown to the console?

    If that doesn’t show anything, and if you are able to send me the .out and .rov.xs files, we can do this privately by becoming ‘friends’ on the forum, so you can send them just to me, and not the whole community…

    Regards,
    Scott

  • Hi

    I found a fix for this.

    I noticed that when I open the ROV, I see the JVM low heap memory message.

    My problem was that before I increased the max heap value in eclipse.ini instead of the ccstudio.ini, so the size wasn't increased at all.

    When I increased it to 1024 I got the error "DWARF information is corrupted" when I tried to load my application.

    When I set it to 512, I didn't get the error and it was large enough to load the ROV.

     

    However I still have have a problem.

    It took 15 minutes for the ROV to load.

    Any suggestions on how to decrease the loading time?

    Shiran

  • what type of emulator are you using?   ROV reads memory to populate the views.  But, ROV only reads what it needs on a per module basis as you click through the modules.

    Would it be possible to zip up your .out file and .rov.xs file so that we can look into this further?

    Thanks,
    -Karl-

  • Hi

    I found out that the cause of the long load is the size of my out file which was 150 mb (the .rov.xs was exactly the same as another project with a short load time).

    I decreased the out file size by turning on --compress_dwarf.

    Now the load time of the rov is seconds.

    I don't see any noticeable increase in link time.

    Do I lose something by turning it on?

    Shiran