• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 97 subscribers
  • Views 408 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.

CCS/AM5728: Project import issue

Dermot Murphy
Intellectual 895 points
Part Number: AM5728


Tool/software: Code Composer Studio

Hi there - In CCSv7 if I import a project and select "Copy projects into workspace" the files are still symlinks to the original files in the PDK package directory structure.

I'm trying to work through the IPC examples on this page: http://processors.wiki.ti.com/index.php/Linux_IPC_on_AM57xx#Adding_IPC_to_an_existing_TI_RTOS_application_on_the_IPU 

I'm unable to copy and paste a project unless the original project is imported into CCS with the files copied into the CCS workspace as opposed to linked back to the PDK "MyExampleProjects" directory.

I was going to try and manually replace the links with copies of the original files but I can't find where these links are made in CCSv7.  They're not regular symlnks since I can't see them in the workspace directory itself.  For example, files such as main_uart_example.c and uart_m4_evmAM572x.cfg are still linked back to the PDK "MyExampleProjects" directory even though I imported the project with "Copy projects into workspace" selected.

If I try to look for any references within the workspace, I'm not seeing anything:

grep -ri main_uart_example.c *

returns nothing.

Any ideas very welcome...am I missing something when importing the project?

Thanks,

Dermot

  • 0
    TI__Guru**** 393215 points
    The RTOS team have been notified. They will respond here.
  • 0 in reply to Biser Gatchev-XID
    TI__Guru* 95265 points
    Hi,

    In CCSv7 if I import a project and select "Copy projects into workspace" the files are still symlinks to the original files in the PDK package directory structure. ==========> This is the correct observation. Only the project files: .project, .cproject, .ccsproject, etc are copied into the workspace, not the real .c, .h, .cfg files. The CCS project created is not designed to copy all the files into the workspace, but it still refers/soft links to individual files in the PDK installation.

    I'm unable to copy and paste a project unless the original project is imported into CCS with the files copied into the CCS workspace as opposed to linked back to the PDK "MyExampleProjects" directory. =====> That is also true, you need to find those files in the PDK installation. They are not centralized that you can just copy and paste.

    I was going to try and manually replace the links with copies of the original files but I can't find where these links are made in CCSv7. They're not regular symlnks since I can't see them in the workspace directory itself. For example, files such as main_uart_example.c and uart_m4_evmAM572x.cfg are still linked back to the PDK "MyExampleProjects" directory even though I imported the project with "Copy projects into workspace" selected. =============> Using the GPIO_LedBlink_evmAM572x_c66xTestProject as an example:

    In the .project file, you can see :

    <linkedResources>
    <link>
    <name>GPIO_evmAM572x_board.c</name>
    <type>1</type>
    <locationURI>PDK_INSTALL_PATH/ti/drv/gpio/test/led_blink/src/am572x/GPIO_evmAM572x_board.c</locationURI>
    </link>
    <link>
    <name>GPIO_log.c</name>
    <type>1</type>
    <locationURI>PDK_INSTALL_PATH/ti/drv/gpio/test/led_blink/src/GPIO_log.c</locationURI>
    </link>
    <link>
    <name>GPIO_soc.c</name>
    <type>1</type>
    <locationURI>PDK_INSTALL_PATH/ti/drv/gpio/soc/am572x/GPIO_soc.c</locationURI>
    </link>
    <link>
    <name>UART_soc.c</name>

    ......

    This is how they are soft linked in the CCS project. If you want to have all the files locally, you can modify here.

    ========
    Another approach, in processor_sdk_rtos_am57xx_5_00_00_15\demos\rtos_template_app, there are CCS projects: there are created by *.projectspec file and ALL source files are copied into the workspace. This serves as an example for customers who want to copy source files into workspace.

    Regards, Eric
  • 0 in reply to lding
    Intellectual 895 points
    Thanks for clarifying that, Eric.

    I think I was, once again, mislead by the documentation at the link below:
    processors.wiki.ti.com/.../Linux_IPC_on_AM57xx
    processors.wiki.ti.com/.../Linux_IPC_on_AM57xx

    The document gives the impression that by copying and pasting a project within CCS, the source files in the copy can be edited without affecting the souce files in the original. However, since the original project is imported from PDF, the copy project source files link to the same PDK location as the original project source files.

    Thanks also for providing the method of modifying the .project file to workaround that issue.

    Regards,
    Dermot