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 Agent support on Arm targets

Other Parts Discussed in Thread: OMAP-L137, SYSBIOS

Hello,

I've a question related to the rta agent for the ARM on the OMAP-L137.
On the ARM side of the OMAP the following version are used:
- BIOS Version: bios_6_20_01_41
- CCS Version : 4.0.1.01001

When adding the ti.sysbios.rta.Agent to my configuration and build the project,
I got the error, that "RTA Agent not supported on Arm targets.":

Turning on task names...
error: ti.sysbios.rta.Agent: "C:/Program Files/Texas Instruments/bios_6_20_01_41/packages/ti/sysbios/rta/Agent.xs", line 59: ti.sysbios.rta.Agent : RTA Agent not supported on Arm targets.
js: "C:/Program Files/Texas Instruments/xdctools_3_15_02_62/packages/xdc/cfg/Main.xs", line 115: Error: Configuration failed!

In the meantime newer BIOS and CCS version are available.

With which BIOS/CCS versions is RTA for the ARM (as part of the OMAP-L137) supported?

Thanks,
Frank

  • RTDX, which RTA uses to transfer log records while the target is running, is not supported on the Arm.

    However, RTA does support what we call 'stop mode' where RTA will read the records off of the target when the target is halted.

    Stop-mode RTA was not implemented in the version of BIOS and XDC that you are using. You'll want at least XDCtools 3.16.00.18 and BIOS 6.21.00.13.

    I'm having trouble determining what version of CCS you will need, but it's possible that your version (4.0.1) does support it.

  • I got a second opinion and we think you will need CCSv4.1. If you download CCSv4.1, the BIOS and XDC products included with it should include stop mode support.

    Again, Arm is only supported by stop mode. While the target is running, you will not receive records RTA. You'll only see records come up after the target has halted.

    Thanks,

    Chris

  • Hello Chris,

    a few more questions.

    Within CCS (Help --> Software Updates -> Find and Install...) I can find an update to CCS 4.1.2.00027 (when markining the Search for new features to install).
    When marking Search for updates of the currently installed features, the search tool only shows 4.0.x.xxxxx versions.
    So my question: Can I directly upgrade from 4.0.1.01001 CCS version to 4.1.2.00027 without any prerequisites via this update tool?

    Is the new BIOS installed in parallel to the current one?
    Do you know which BIOS comes with 4.1.2.00027 (newest BIOS is 6.21.03.21)?
    As I have my own RTSC platform, the new XDCtools and BIOS are selected through the "RTSC Platform Wizard", correct?

    In the release notes for newer BIOS I found:
    Updated Target Support:  DSP/BIOS 6.21 now adds ELF object file format for all of the supported Arm targets.  COFF support for the Arm targets is being phased out and has been removed for most of the Arm targets.
    What does this mean for me / what do I have to change if COFF is no longer supported?
    E.g. In the Properties of my project under C/C++ Build -> Binary Parser the
    TI Coff Parser checkbox is checked or under  C/C++ Build -> Runtime Model Options the COFF is selected.
    Is this then automatically changed by the update?

    Is it correct, that for getting some load statistics of the ARM, only the Agent and the load module need to be added to the configuration?

    Thanks,
    Frank

  • Hello,

    anybody there who can answer my questions?

    Thanks,

    Frank

  • Hi Frank,

    Sorry for the late response, I've been on paternity leave for the past couple weeks :)

    Unfortunately I'm not very familiar with the CCS update process. I typically grab new versions of CCS directly and just uninstall the old one. You may want to post your questions about updating to the CCS forum to get some help there.

    I think you should find the transition from COFF to ELF pretty seamless. When you select your RTSC target, you just need to select the elf target.

    To get the load statistics, just add the Agent to your configuration. On the Arm, make sure to set:

        Agent.transport = Agent.Transport_STOP_MODE_ONLY;

    Since RTDX is not supported. This will get you execution graph and load details by default. If you don't want the execution graph data, you can set:

        Agent.configureSystemLog = false;

    Thanks,

    Chris

  • Hi Chris,

    congratulations on the birth of your child(s)!

    This thread can be closed.

    Thanks a lot,

    Frank