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.

RTOS/TMDSLCDK6748: Cannot create PDK example test project

Part Number: TMDSLCDK6748
Other Parts Discussed in Thread: OMAPL138, CCSTUDIO, MATHLIB, SYSBIOS

Tool/software: TI-RTOS

Hello,

I'm trying to make an example project but cmd gives this error: "the system cannot find the specified path".


C:\ti\pdk_omapl138_1_0_4\packages>pdkProjectCreate.bat C6748 evmc6748 little gpio all dsp
=========================================================================
Configuration:
SOC : C6748
BOARD : evmc6748
ENDIAN : little
MODULE : gpio
PROJECT_TYPE : all
PROCESSOR : dsp
PDK_SHORT_NAME : C:\ti\PDK_OM~1\packages\
=========================================================================
Checking Configuration...
Complete
=========================================================================
PDK_PARTNO : OMAPL138
PDK_ECLIPSE_ID : com.ti.pdk.omapl138
RTSC_PLATFORM_NAME : ti.platforms.evmOMAPL138
RTSC_TARGET : ti.targets.elf.C674
CCS_DEVICE : "com.ti.ccstudio.deviceModel.C6000.GenericC674xDevice"
*****************************************************************************
Detecting all projects in PDK and importing them in the workspace C:\ti\PDK_OM~1\packages\\MyExampleProjects
Detected Test Project: GPIO_LedBlink_lcdkOMAPL138_c674xTestProject
Het systeem kan het opgegeven pad niet vinden.
Copying macros.ini
Het systeem kan het opgegeven pad niet vinden.
0 file(s) copied.
No projects detected
Project generation complete
*****************************************************************************

How can I solve this?

  • The team is notified. They will post their feedback directly here.

    BR
    Tsvetolin Shulev
  • Roberto del Pozo Gallardo said:

    C:\ti\pdk_omapl138_1_0_4\packages>pdkProjectCreate.bat C6748 evmc6748 little gpio all dsp

    Hi Roberto,

    Change evmc6748 to lcdkomapl138. "evmc6748" isn't a valid board. To see a list of valid board inputs, refer to pdk_<soc>_<version>\packages\ti\board\lib.

    Projects for the lcdkomapl138 will run on the lcdkc6748 as the boards are identical. The OMAPL138 is just a C6748 with an ARM core. 

  • If I try that I still got this:

    C:\ti\pdk_omapl138_1_0_4\packages>pdkProjectCreate.bat C6748 lcdkomapl138 little gpio all dsp
    =========================================================================
    Configuration:
    SOC : C6748
    BOARD : lcdkomapl138
    ENDIAN : little
    MODULE : gpio
    PROJECT_TYPE : all
    PROCESSOR : dsp
    PDK_SHORT_NAME : C:\ti\PDK_OM~1\packages\
    =========================================================================
    Checking Configuration...
    ERROR: Board (lcdkomapl138) is invalid for the specified SOC (C6748)
    Exiting...
    =========================================================================


    Or I get this:


    C:\ti\pdk_omapl138_1_0_4\packages>pdkProjectCreate.bat OMAPL138 lcdkomapl138 little gpio all dsp
    =========================================================================
    Configuration:
    SOC : OMAPL138
    BOARD : lcdkomapl138
    ENDIAN : little
    MODULE : gpio
    PROJECT_TYPE : all
    PROCESSOR : dsp
    PDK_SHORT_NAME : C:\ti\PDK_OM~1\packages\
    =========================================================================
    Checking Configuration...
    Complete
    =========================================================================
    PDK_PARTNO : OMAPL138
    PDK_ECLIPSE_ID : com.ti.pdk.omapl138
    RTSC_PLATFORM_NAME : ti.platforms.evmOMAPL138
    RTSC_TARGET : ti.targets.elf.C674
    CCS_DEVICE : "com.ti.ccstudio.deviceModel.C6000.GenericC674xDevice"
    *****************************************************************************
    Detecting all projects in PDK and importing them in the workspace C:\ti\PDK_OM~1\packages\\MyExampleProjects
    Detected Test Project: GPIO_LedBlink_lcdkOMAPL138_c674xTestProject
    Het systeem kan het opgegeven pad niet vinden.
    Copying macros.ini
    Het systeem kan het opgegeven pad niet vinden.
    0 file(s) copied.
    No projects detected
    Project generation complete
    *****************************************************************************

    C:\ti\pdk_omapl138_1_0_4\packages>

    So what else is wrong?
  • For the first error, it looks like lcdkC6748 should be paired with C6748 SOC and lcdkOMAPL138 with OMAPL138 SOC. The second attempt should have worked though. Did you run pdksetupenv.bat before running pdkProjectCreate?
  • Yes now I did it all again.

    Microsoft Windows [Version 10.0.16299.371]
    (c) 2017 Microsoft Corporation. Alle rechten voorbehouden.

    C:\Users\Roberto>cd C:\ti\pdk_omapl138_1_0_4\packages

    C:\ti\pdk_omapl138_1_0_4\packages>pdksetupenv.bat
    **************************************************************************
    Environment Configuration:
    LIMIT_SOCS : omapl138
    LIMIT_BOARDS : lcdkOMAPL138
    PDK_INSTALL_PATH : /ti/PDK_OM~1/packages
    IMGLIB_INSTALL_PATH : C:/ti/imglib_c674x_3_1_1_0
    DSPLIB_INSTALL_PATH : C:/ti/dsplib_c674x_3_4_0_0
    MATHLIB_INSTALL_PATH : C:/ti/mathlib_c674x_3_1_1_0
    XDC_INSTALL_PATH : C:/ti/xdctools_3_50_03_33_core

    C:\ti\pdk_omapl138_1_0_4\packages>pdkProjectCreate.bat OMAPL138 lcdkomapl138 little gpio all dsp
    =========================================================================
    Configuration:
    SOC : OMAPL138
    BOARD : lcdkomapl138
    ENDIAN : little
    MODULE : gpio
    PROJECT_TYPE : all
    PROCESSOR : dsp
    PDK_SHORT_NAME : C:\ti\PDK_OM~1\packages\
    =========================================================================
    Checking Configuration...
    Complete
    =========================================================================
    PDK_PARTNO : OMAPL138
    PDK_ECLIPSE_ID : com.ti.pdk.omapl138
    RTSC_PLATFORM_NAME : ti.platforms.evmOMAPL138
    RTSC_TARGET : ti.targets.elf.C674
    CCS_DEVICE : "com.ti.ccstudio.deviceModel.C6000.GenericC674xDevice"
    *****************************************************************************
    Detecting all projects in PDK and importing them in the workspace C:\ti\PDK_OM~1\packages\\MyExampleProjects
    Detected Test Project: GPIO_LedBlink_lcdkOMAPL138_c674xTestProject
    Het systeem kan het opgegeven pad niet vinden.
    Copying macros.ini
    Het systeem kan het opgegeven pad niet vinden.
    0 file(s) copied.
    No projects detected
    Project generation complete
    *****************************************************************************

    C:\ti\pdk_omapl138_1_0_4\packages>
  • Please see the post by Rahul in the following thread:

  • I followed all the steps but it will not work.
  • I fixed it. In the pdkProjectCreate.bat file the CCS version was 7 and I am using 8. That was the problem.

    Now I have a new problem. I can not build the project in CCS8.

    What am I doing wrong?

  • I think that might be due to the linker command file in your project folder (C6748.cmd) causing conflicts. CCS/XDCtools automatically generates the linker cmd file during the build process so C6748.cmd shouldn't be needed.

    All you should have to do is import the project by going to File->Import->CCS Projects and it should build without having to make any changes.
  • It will build now but I got this 3 warnings:

    **** Build of configuration Debug for project GPIO_LedBlink_lcdkOMAPL138_c674xTestProject ****

    "C:\\ti\\ccsv8\\utils\\bin\\gmake" -k -j 8 all -O

    Building file: "C:/ti/pdk_omapl138_1_0_4/packages/ti/drv/gpio/test/led_blink/omapl138/c674/bios/gpio_test.cfg"

    Invoking: XDCtools

    "C:/ti/xdctools_3_50_03_33_core/xs" --xdcpath="C:/ti/bios_6_52_00_12/packages;C:/ti/pdk_omapl138_1_0_4/packages;C:/ti/edma3_lld_2_12_05_30C/packages;C:/ti/ipc_3_47_01_00/packages;C:/ti/ndk_2_26_00_08/packages;C:/ti/uia_2_21_02_07/packages;" xdc.tools.configuro -o configPkg -t ti.targets.elf.C674 -p ti.platforms.evmOMAPL138 -r debug -b "C:/ti/pdk_omapl138_1_0_4/packages/ti/build/omapl138/config_omapl138_c674x.bld" -c "C:/ti/ti-cgt-c6000_8.2.2" -DBOARD=lcdkOMAPL138 "C:/ti/pdk_omapl138_1_0_4/packages/ti/drv/gpio/test/led_blink/omapl138/c674/bios/gpio_test.cfg"

    making package.mak (because of package.bld) ...

    generating interfaces for package configPkg (because package/package.xdc.inc is older than package.xdc) ...

    configuring gpio_test.xe674 from package/cfg/gpio_test_pe674.cfg ...

    generating custom ti.sysbios library makefile ...

    Linking with library ti.drv.i2c:./lib/omapl138/c674/release/ti.drv.i2c.ae674

    Linking with library ti.drv.uart:./lib/omapl138/c674/release/ti.drv.uart.ae674

    Linking with library ti.drv.gpio:./lib/omapl138/c674/release/ti.drv.gpio.ae674

    Linking with library ti.board:./lib/lcdkOMAPL138/c674/release/ti.board.ae674

    Linking with library ti.csl:./lib/omapl138/c674/release/ti.csl.ae674

    Linking with library ti.osal:./lib/tirtos/omapl138/c674/release/ti.osal.ae674

    Starting build of library sources ...

    making C:/ti/pdk_omapl138_1_0_4/packages/ti/drv/gpio/test/led_blink/omapl138/c674/bios/src/sysbios/sysbios.ae674 ...

    gmake[1]: Entering directory `C:/ti/pdk_omapl138_1_0_4/packages/ti/drv/gpio/test/led_blink/omapl138/c674/bios/src/sysbios'

    gmake[1]: Nothing to be done for `all'.

    gmake[1]: Leaving directory `C:/ti/pdk_omapl138_1_0_4/packages/ti/drv/gpio/test/led_blink/omapl138/c674/bios/src/sysbios'

    Build of libraries done.

    cle674 package/cfg/gpio_test_pe674.c ...

    Finished building: "C:/ti/pdk_omapl138_1_0_4/packages/ti/drv/gpio/test/led_blink/omapl138/c674/bios/gpio_test.cfg"

    Building file: "C:/ti/pdk_omapl138_1_0_4/packages/ti/drv/gpio/test/led_blink/omapl138/GPIO_board.c"

    Invoking: C6000 Compiler

    "C:/ti/ti-cgt-c6000_8.2.2/bin/cl6x" -mv6740 --include_path="C:/ti/pdk_omapl138_1_0_4/packages/MyExampleProjects/GPIO_LedBlink_lcdkOMAPL138_c674xTestProject" --include_path="C:/ti/pdk_omapl138_1_0_4/packages/ti/drv/gpio" --include_path="C:/ti/pdk_omapl138_1_0_4/packages" --include_path="/packages" --include_path="C:/ti/ti-cgt-c6000_8.2.2/include" --define=SOC_OMAPL138 --define=LCDK_OMAPL138 --define=USE_BIOS --define=lcdkOMAPL138 -g --diag_suppress=1111 --diag_suppress=827 --diag_suppress=824 --diag_suppress=837 --diag_suppress=1037 --diag_suppress=195 --diag_suppress=77 --diag_suppress=232 --diag_warning=225 --diag_warning=994 --diag_warning=262 --diag_wrap=off --display_error_number --preproc_with_compile --preproc_dependency="GPIO_board.d_raw" --cmd_file="configPkg/compiler.opt" "C:/ti/pdk_omapl138_1_0_4/packages/ti/drv/gpio/test/led_blink/omapl138/GPIO_board.c"

    Finished building: "C:/ti/pdk_omapl138_1_0_4/packages/ti/drv/gpio/test/led_blink/omapl138/GPIO_board.c"

    Building file: "C:/ti/pdk_omapl138_1_0_4/packages/ti/drv/gpio/test/led_blink/src/main_led_blink.c"

    Invoking: C6000 Compiler

    "C:/ti/ti-cgt-c6000_8.2.2/bin/cl6x" -mv6740 --include_path="C:/ti/pdk_omapl138_1_0_4/packages/MyExampleProjects/GPIO_LedBlink_lcdkOMAPL138_c674xTestProject" --include_path="C:/ti/pdk_omapl138_1_0_4/packages/ti/drv/gpio" --include_path="C:/ti/pdk_omapl138_1_0_4/packages" --include_path="/packages" --include_path="C:/ti/ti-cgt-c6000_8.2.2/include" --define=SOC_OMAPL138 --define=LCDK_OMAPL138 --define=USE_BIOS --define=lcdkOMAPL138 -g --diag_suppress=1111 --diag_suppress=827 --diag_suppress=824 --diag_suppress=837 --diag_suppress=1037 --diag_suppress=195 --diag_suppress=77 --diag_suppress=232 --diag_warning=225 --diag_warning=994 --diag_warning=262 --diag_wrap=off --display_error_number --preproc_with_compile --preproc_dependency="main_led_blink.d_raw" --cmd_file="configPkg/compiler.opt" "C:/ti/pdk_omapl138_1_0_4/packages/ti/drv/gpio/test/led_blink/src/main_led_blink.c"

    "C:/ti/pdk_omapl138_1_0_4/packages/ti/drv/gpio/test/led_blink/src/main_led_blink.c", line 214: warning #112-D: statement is unreachable

    Finished building: "C:/ti/pdk_omapl138_1_0_4/packages/ti/drv/gpio/test/led_blink/src/main_led_blink.c"

    Building target: "GPIO_LedBlink_lcdkOMAPL138_c674xTestProject.out"

    Invoking: C6000 Linker

    "C:/ti/ti-cgt-c6000_8.2.2/bin/cl6x" -mv6740 --define=SOC_OMAPL138 --define=LCDK_OMAPL138 --define=USE_BIOS --define=lcdkOMAPL138 -g --diag_suppress=1111 --diag_suppress=827 --diag_suppress=824 --diag_suppress=837 --diag_suppress=1037 --diag_suppress=195 --diag_suppress=77 --diag_suppress=232 --diag_warning=225 --diag_warning=994 --diag_warning=262 --diag_wrap=off --display_error_number -z -m"GPIO_LedBlink_lcdkOMAPL138_c674xTestProject.map" -i"C:/ti/ti-cgt-c6000_8.2.2/lib" -i"C:/ti/ti-cgt-c6000_8.2.2/include" --reread_libs --diag_wrap=off --display_error_number --warn_sections --xml_link_info="GPIO_LedBlink_lcdkOMAPL138_c674xTestProject_linkInfo.xml" --rom_model -o "GPIO_LedBlink_lcdkOMAPL138_c674xTestProject.out" "./GPIO_board.obj" "./main_led_blink.obj" -l"configPkg/linker.cmd" -llibc.a

    <Linking>

    Finished building target: "GPIO_LedBlink_lcdkOMAPL138_c674xTestProject.out"

    C:/ti/pdk_omapl138_1_0_4/packages/pdkAppImageCreate.bat C:/ti/pdk_omapl138_1_0_4/packages C:/ti/ti-cgt-c6000_8.2.2 C:/ti/pdk_omapl138_1_0_4/packages/MyExampleProjects/GPIO_LedBlink_lcdkOMAPL138_c674xTestProject/Debug GPIO_LedBlink_lcdkOMAPL138_c674xTestProject OMAPL138 dsp

    Parsing the input object file, C:/ti/pdk_omapl138_1_0_4/packages/MyExampleProjects/GPIO_LedBlink_lcdkOMAPL138_c674xTestProject/Debug/GPIO_LedBlink_lcdkOMAPL138_c674xTestProject.out.

    File conversion complete!

    Number of Input Files 1

    **** Build Finished ****

    How can I fix this?

  • It looks like the project was built successfully. You'll find the .out file that you can load to the DSP under the Binaries folder.
  • I'm trying to flash the DSP but it don't work.

    I don't get the massage BOOTME.

    I set the dipswitches on 00000101.

    I tried this three ways:

    Could you give step by step instruction so I could try it the good way?

  • Hi Roberto,

    This issue is outside of the scope of this thread. If your project create issue has been resolved, can you please mark this thread as answered and create another thread for the flashing/booting issue? This will help the community find answers quicker and will help us route threads to the correct experts.