• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 52 subscribers
  • Views 8746 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.

Must specify a URI scheme

Patrick McCloskey
Intellectual 965 points
Other Parts Discussed in Thread: TMS320VC5502

I want to migrate a pair of "legacy" DSP applications from CCSv2.21 to CCSv5.2.
Both applications currently use DSP/BIOS 4.90.270 on TMS320VC5502 DSPs.

Unfortunately, I have not discovered a straightforward way to accomplish the migration.

The only path I see involves converting the old projects to CCSv3.3 projects, then importing the "legacy CCSv3.3 projects" into CCSv5.2

At this point, the applications "almost" work in the CCSv3.3 environment.
Refer to my previous post for some details of this effort:

"Should I update from CCSv3.3 toolchain?"
http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/199018.aspx


I gave up trying to troubleshoot the issues in CCSv3.3.
I will see how far I get with CCSv5.2

After wrestling with a "COMMON_ROOT" path variable in my new .project file, I now get the following error message when I try to open a source code file (main.c, for example) in CCSv5.2:


Could not open the editor: Must specify a URI scheme:etram/dsp/main/src/main.c

(I will attach the error message details to this post.)

I would be grateful for some advice that will help me get past this error.

Best regards,
Patrick McCloskey

  • 0
    Intellectual 965 points

    6811.URI_scheme_error.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    Could not open the editor: Must specify a URI scheme:etram/dsp/main/src/main.c
    Details:
    org.eclipse.core.runtime.CoreException: Must specify a URI scheme:etram/dsp/main/src/main.c
    at org.eclipse.core.internal.filesystem.Policy.error(Policy.java:55)
    at org.eclipse.core.internal.filesystem.Policy.error(Policy.java:50)
    at org.eclipse.core.internal.filesystem.InternalFileSystemCore.getStore(InternalFileSystemCore.java:106)
    at org.eclipse.core.filesystem.EFS.getStore(EFS.java:470)
    at org.eclipse.core.internal.filebuffers.ResourceFileBuffer.create(ResourceFileBuffer.java:241)
    at org.eclipse.core.internal.filebuffers.TextFileBufferManager.connect(TextFileBufferManager.java:112)
    at org.eclipse.ui.editors.text.TextFileDocumentProvider.createFileInfo(TextFileDocumentProvider.java:559)
    at org.eclipse.cdt.internal.ui.editor.CDocumentProvider.createFileInfo(CDocumentProvider.java:857)
    at org.eclipse.ui.editors.text.TextFileDocumentProvider.connect(TextFileDocumentProvider.java:478)
    at org.eclipse.cdt.internal.ui.editor.CDocumentProvider.connect(CDocumentProvider.java:779)
    at org.eclipse.ui.texteditor.AbstractTextEditor.doSetInput(AbstractTextEditor.java:4213)
    at org.eclipse.ui.texteditor.StatusTextEditor.doSetInput(StatusTextEditor.java:237)
    at org.eclipse.ui.texteditor.AbstractDecoratedTextEditor.doSetInput(AbstractDecoratedTextEditor.java:1451)
    at org.eclipse.ui.editors.text.TextEditor.doSetInput(TextEditor.java:169)
    at org.eclipse.cdt.internal.ui.editor.CEditor.internalDoSetInput(CEditor.java:1495)
    at org.eclipse.cdt.internal.ui.editor.CEditor.doSetInput(CEditor.java:1458)
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0
    TI__Guru**** 173310 points

    Patrick McCloskey said:

    The only path I see involves converting the old projects to CCSv3.3 projects, then importing the "legacy CCSv3.3 projects" into CCSv5.2

    That is one method to try. The other is to simply create a new project in CCS 5.2. Sometimes that works better than trying to migrate older projects to CCSv5 depending on the complexity of the project itself. The key thing to note is that BIOS 4.9x should first be converted to BIOS 5.3x. Then all the source files/BIOS config files can be added to a newly created CCSv5 project.

    I'm not sure about the URI scheme error you are seeing. You could try cleaning your workspace or using a new workspace (or some of the "General IDE" troubleshooting tips in this page), but if those do not help, I would try creating a new project in CCSv5 instead of migrating the CCs 3.3 project.

  • 0 in reply to AartiG
    Intellectual 965 points

    My new post related to this discussion thread:

    "CCS2 project migrated to CCS5 is too big to fit in VC5502 memory"
    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/200713/713703.aspx#713703