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.

RTA Not Working In CCSv4 (C6000)

Other Parts Discussed in Thread: OMAP-L137

Hi,

I've asked about RTA in CCSv4 before (http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/3205/11203.aspx#11203).

Sometime has passed and I'm now using CCSv4.1.1.00014, BIOS V5.41.03.17 and a XDS100v2. My target is a C6455.

Unfortunately the RTA tools still don't work and it's getting a bit boring because I need to do some timing. I'm considering finding another emulator and going back to CCSv3 because I know RTA will work fine in CCSv3.

Occassionally I see stuff in the Statistics Data window but most of the time it is empty. I can see my STS objects changing in the memory view and I've taken to using LOG_event and looking at trace$buf in the memory view.

Surely RTA and RTDX are fundamental and important selling points of CCS and TI wouldn't allow them to stop working. If RTA stopped working wouldn't there be loads of people complaining? So what am I doing wrong?

Is there anyone out there that can tell that they are using the RTA windows in CCSv4 without any problems?

Is there anyone from TI who's interested and/or worried because I'm on the verge of giving up on CCSv4?

Thanks,

Matt

  • I found an XDS510PP and tried CCSv3 and was surprised to find that the Statistics View and Message Log windows are only update when the processor is halted.

    I've read this page - http://wiki.davincidsp.com/index.php/DSP/BIOS_Real-time_Analysis_%28RTA%29_troubleshooting

    Does the C6455 only support stop-mode debugging? At times in CCSv4 the RTA windows update continuously which implies that realtime-mode should work.

    Are my problems related to the C6455 rather than CCS?

  • Right, so, I'm getting warmer!

    It turns out that the Statistics View and Message Log windows update while the processor is running the first time I load the project. If I halt and reload the same program the windows will only update when the processor is halted.

    I have to perform a power-on reset to get the windows updating in real-time again. A software reset doesn't work.

    Does all this imply that my problem has something to do with the interrupt peripheral?

    I also believe, but can't find the link now, that CCSv4 does halt mode differently (or doesn't do it at all) which perhaps explains why I see nothing most of the time in CCSv4.

  • What I said about resets wasn't quite right.

    I can do a power-on reset  or a warm reset but it appears I can use either but I also have to disconnect the target in CCS.

    In other words, the first time after connecting and resetting the target everything is okay but after that it starts going down hill!

  • Matt,

    The XDS100 emulators do not support RTDX:

    http://tiexpressdsp.com/index.php/XDS100#Q:_Does_DSP.2FBIOS_Real_Time_Analysis_with_RTDX_work.3F

    You will only get stop-mode updates using XDS100 with the 6455.

    Mark

  • Hi Mark,

    Thanks for taking an interest, it helps to talk!

    MarkGrosen said:
    The XDS100 emulators do not support RTDX:

    Hhmmm...

    my experience doesn't quite match this statement!

    The first time after a reset and connect I get real-time updates (using an XDS100v2) but after a reload I get nothing, not even stop mode updates.

    Is this because I need to change some settings somewhere, possibly build without RTDX, so that it doesn't try real-time updates in the first place?

    MarkGrosen said:
    You will only get stop-mode updates using XDS100 with the 6455.

    I would be happy if this was the case. RTA works once and then I have to reset and reconnect to get it to get anything to appear in Statistics Data window (XDS100v2 & CCSv4).

    I'm sorry my previous posts were a bit rambling! I described RTA working in stop mode but that was when I tried a XDS510PP Plus (& CCSv3). I believe RTDX should work with an XDS510PP Plus but that's not what I see.

    In other words I've got 2 test systems, XDS100v2 & CCSv4 and XDS510PP & CCSv3, and neither of them behaviour as I would expect. Note, I also have 2 different target boards, an EVM6455 and our board, and which target I use doesn't make any difference.

    Surely there must be lots of people using C6455s so hopefully I'm doing something stupid!

    Thanks,

    Matt

  • I have similar issues with RTA.  In general I find they are very reliable in CCS v3.3, but in CCS v4 they are unreliable.  Can someone from TI explain why this is?  CPU load graph rarely works (e.g. updates with any data).  The printf logs seems to work as Matt describes - the 1st time they work, but on subsequent reloads of the program, they will not work until a system reset is performed.  So now I found myself building in CCS v4 but debugging in CCS v3.3 because the debug environment is much more reliable and stable in CCS v3.3.  When will TI resolve these RTA issues with CCS v4 so they will perform as well as CCS v3.3?

    Matt, FYI, you can build in CCS v4 and then take and load that .out file  in CCS v3.3 for debugging if that can help your situation.  I do it sometimes but it is a hassle to switch between 2 different IDEs.

     

    Mike

  • Hi Mike,

    It makes me feel a bit better that I'm not the only one having problems! Perhaps I'm not as mad as I thought I was! :-}

    What parts are you developing for? I thought perhaps the problems are just related to C6455s which is why there aren't too many people complaining.

    Matt

  • I'm developing on a C6747 (or OMAP-L137).  I've seen posts from others with similar problems.  I'm just wondering why TI hasn't addressed this issue formally; or maybe they have and we just don't know about it.

    Mike

  • I have a similar problem - developing on the OMAPL-137 EVM with CCS 3.3. The LogTrace window and CPU load graphs only update in real time the first 2 or 3 times I reload and run a program from CCS. I have to restart CCS to get them to work again after that. Otherwise i only get updates when I halt, which is no good for CPU usage when I'm trying to optimize.