• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 662 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

version mismatch between the ROV server and the ROV plugin

Brad Griffis
Guru*** 125430 points

CCS 4.1.2
55x Rev 2.x Functional Simulator
BIOS 5.41.00.06
XDCtools 3.16.00.03 (that's what XDC_CG_ROOT macro points to)

I see the following error dialog when I try to open ROV:

How do I correct the issue?  Is my xdctools version too new for the BIOS version?

  • 0
    TI__Guru*** 125430 points

    Ok, just updated my BIOS to 5.41.04.18 and now it works fine.  So my guess was right that BIOS was too old.

    So the issue definitely seems to be a problem between xdctools and BIOS.  I'm going to move this to the BIOS forum.

  • 0 in reply to Brad Griffis
    TI__Expert 4095 points

    Brad,

    That issue is actually unrelated to your BIOS version. Do you or did you have multiple versions of XDC tools installed?

    ROV is composed of a server and a client, and it's possible for the server to come from one version of XDC and the client to come from another. The server version is selected when you choose your XDC tools version in your project or global preferences. The client is an eclipse plugin and its version is determined by eclipse, which always chooses the most recent version.

    This becomes a problem when you have a newer XDC tools installed, for example, but want to use ROV on an app built with older XDC tools. The client from the new one can be incompatible with the server from the old one, and you'll receive the error that you saw.

    We addressed this in the GA release of XDC 3.20 by making the ROV plugin (the client) compatible with all servers back to first release of  3.16.

    I'm guessing that you resolved your issue by changing your XDC tools selection to be the most recent version.

    Sorry for the confusion! It was a mistake to ever allow the servers and clients to become incompatible, but the problem wasn't recognized until relatively recently. Users who only ever have one XDC tools version installed, or who always use their most recent version don't encounter this issue.

    Thanks,

    Chris