• State TI Thinks Resolved
  • Locked Locked
  • Replies 13 replies
  • Answers 3 answers
  • Subscribers 54 subscribers
  • Views 4776 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.

CCS/CCSTUDIO: Can't find the platform package

Michael C
Prodigy 170 points
Part Number: CCSTUDIO
Other Parts Discussed in Thread: TMDSLCDK6748

Tool/software: Code Composer Studio

Hello,

As shown in the screen shot below, I imported the "Hello_World" project. But there is no platform in the drop-down list. I just put "C674" there. Then I got the error "Can't find the platform package" . Please advise. BTW, I am running CCS v8 in Windows 10 with "ti-processor-sdk-rtos-omapl138-lcdk-04.02.00.09-Windows-x86-Install.exe" installed.

Thanks,

Michael

  • 0
    TI__Guru**** 173310 points

    Michael,

    If you click on the arrow in the 'Platform' field it should show a list of platform options to select from. From there, you can pick the one that is the closest match to the device you are working with.

  • 0 in reply to AartiG
    Prodigy 170 points

    Hi AartiG,

    Thanks for your response. Unfortunately, when I clicked on that arrow, nothing was listed. Please advise.

    Thanks,

    Michael

  • 0 in reply to Michael C
    TI__Guru**** 173310 points
    That is very odd. It looks like SYS/BIOS has been detected properly and the package paths passed to the build command look correct as well.

    Could you double-check that SYS/BIOS 6.52.0.12 is listed correctly under "Installed Products" in menu Window->Preferences->Code Composer Studio->Products? Then try restarting CCS and perhaps even restarting your PC to see if that helps.

    If that does not help, I wonder if the SYS/BIOS installation is somehow incomplete or corrupt, in which case I would suggest trying to uninstall and reinstall SYS/BIOS. Sorry about the inconvenience.
  • 0 in reply to AartiG
    Prodigy 170 points

    Hi Aatig,

    I checked "Installed Products". SYS/BIOS 6.52.0.12 is installed. I have tried to unintall / install, restart CCS and restart computer. But the platform is still not showing in the list. The other thing I noticed is that items in Products->RTSC were not checked (see the picture below). But even I checked them all and restart CCS, I still could not see the platforms. Please advise.

    Thanks,

    Michael

  • 0 in reply to Michael C
    TI__Guru**** 173310 points
    Michael,

    Thank you for giving those suggestions a try and I'm sorry to hear that they did not help .
    I will forward this thread to the BIOS experts to see if they have additional ideas.
  • 0 in reply to AartiG
    TI__Guru* 96960 points
    Hi Michael,

    First of all, for that version of SYS/BIOS, you need to use an XDCtools 3.50.00.10 or later (per the SYS/BIOS release notes). I see you are using 3.32.02.25 from the first picture.

    Second, you can import a SYS/BIOS example from Resource Explorer Classic and see what platform is there.

    Todd
  • 0 in reply to ToddMullanix
    Prodigy 170 points

    Hi Todd,

    I tried XDCtools 3.50.5.12 and import the Hello example as shown in the pictures below. But, there is no platforms available for me to select.

    Thanks,

    Michael

  • 0 in reply to Michael C
    TI__Mastermind 37985 points
    Michael,
    there are two things to try. First, try just typing in ti.platforms.evmOMAPL138 and rebuild. I would like to see if that platfowm will be found.
    Another thing that would help us debug is if you can post the file .metadata/.log from your workspace.
  • 0 in reply to Sasha Slijepcevic
    Prodigy 170 points

    Hi Sasha,

    After typing in ti.platforms.evmOMAPL138, I can build the imported project. But there is still no any other platform listed. Then I run the debugger, I got the error message "file load failed" as shown in the picture below. The .log file and building information showing in the console window are included for your reference. Due to the file name the Log File.txt

    Build Info.txt 
    **** Build of configuration Debug for project hello_TMS320C6746_C67XX ****

"C:\\ti\\ccsv8\\utils\\bin\\gmake" -k -j 4 all -O 
 
Building file: "../hello.cfg"
Invoking: XDCtools
"C:/ti/xdctools_3_50_05_12_core/xs" --xdcpath="C:/ti/bios_6_52_00_12/packages;" xdc.tools.configuro -o configPkg -t ti.targets.elf.C674 -p ti.platforms.evmOMAPL138 -r release -c "C:/ti/ti-cgt-c6000_8.2.2" --compileOptions "-g --optimize_with_debug" "../hello.cfg"
making package.mak (because of package.bld) ...
generating interfaces for package configPkg (because package/package.xdc.inc is older than package.xdc) ...
configuring hello.xe674 from package/cfg/hello_pe674.cfg ...
generating custom ti.sysbios library makefile ... 
Starting build of library sources ...
making D:/EMSCAN/TIworkspaceV8/hello_TMS320C6746_C67XX/src/sysbios/sysbios.ae674 ...
gmake[1]: Entering directory `D:/EMSCAN/TIworkspaceV8/hello_TMS320C6746_C67XX/src/sysbios'
cle674 C:/ti/bios_6_52_00_12/packages/ti/sysbios/BIOS.c ...
remark #24038-D: --optimize_with_debug is deprecated and will be removed in a
   subsequent release. The behavior is enabled by default.
asme674 C:/ti/bios_6_52_00_12/packages/ti/sysbios/family/c64p/Exception_asm.s64P ...
remark #24038-D: --optimize_with_debug is deprecated and will be removed in a
   subsequent release. The behavior is enabled by default.
asme674 C:/ti/bios_6_52_00_12/packages/ti/sysbios/family/c64p/Hwi_asm.s62 ...
remark #24038-D: --optimize_with_debug is deprecated and will be removed in a
   subsequent release. The behavior is enabled by default.
asme674 C:/ti/bios_6_52_00_12/packages/ti/sysbios/family/c64p/Hwi_asm_switch.s62 ...
remark #24038-D: --optimize_with_debug is deprecated and will be removed in a
   subsequent release. The behavior is enabled by default.
asme674 C:/ti/bios_6_52_00_12/packages/ti/sysbios/family/c64p/Hwi_disp_always.s64P ...
remark #24038-D: --optimize_with_debug is deprecated and will be removed in a
   subsequent release. The behavior is enabled by default.
asme674 C:/ti/bios_6_52_00_12/packages/ti/sysbios/rts/ti/tls_get_tp.asm ...
remark #24038-D: --optimize_with_debug is deprecated and will be removed in a
   subsequent release. The behavior is enabled by default.
asme674 C:/ti/bios_6_52_00_12/packages/ti/sysbios/family/c62/TaskSupport_asm.s62 ...
remark #24038-D: --optimize_with_debug is deprecated and will be removed in a
   subsequent release. The behavior is enabled by default.
asme674 C:/ti/bios_6_52_00_12/packages/ti/sysbios/timers/timer64/Timer_asm.s64P ...
remark #24038-D: --optimize_with_debug is deprecated and will be removed in a
   subsequent release. The behavior is enabled by default.
are674 BIOS.obj c64p_Exception_asm.obj c64p_Hwi_asm.obj c64p_Hwi_asm_switch.obj c64p_Hwi_disp_always.obj ti_tls_get_tp.obj c62_TaskSupport_asm.obj timer64_Timer_asm.obj ...
gmake[1]: Leaving directory `D:/EMSCAN/TIworkspaceV8/hello_TMS320C6746_C67XX/src/sysbios'
Build of libraries done.
cle674 package/cfg/hello_pe674.c ...
Finished building: "../hello.cfg"
 
        1 file(s) copied.
making ../src/sysbios/sysbios.ae674 ...
gmake[1]: Nothing to be done for 'all'.
Building file: "../hello.c"
Invoking: C6000 Compiler
"C:/ti/ti-cgt-c6000_8.2.2/bin/cl6x" -mv6740 --include_path="D:/EMSCAN/TIworkspaceV8/hello_TMS320C6746_C67XX" --include_path="C:/ti/ti-cgt-c6000_8.2.2/include" --define=c6746 -g --diag_warning=225 --diag_wrap=off --display_error_number --preproc_with_compile --preproc_dependency="hello.d_raw" --cmd_file="configPkg/compiler.opt" "../hello.c"
Finished building: "../hello.c"
 
making ../src/sysbios/sysbios.ae674 ...
gmake[2]: Nothing to be done for 'all'.
Building target: "hello_TMS320C6746_C67XX.out"
Invoking: C6000 Linker
"C:/ti/ti-cgt-c6000_8.2.2/bin/cl6x" -mv6740 --define=c6746 -g --diag_warning=225 --diag_wrap=off --display_error_number -z -m"hello_TMS320C6746_C67XX.map" --heap_size=0x800 --stack_size=0x800 -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="hello_TMS320C6746_C67XX_linkInfo.xml" --rom_model -o "hello_TMS320C6746_C67XX.out" "./hello.obj" -l"configPkg/linker.cmd" -llibc.a 
<Linking>
Finished building target: "hello_TMS320C6746_C67XX.out"
 

**** Build Finished ****
    extension reason, I have changed ".log" to "the Log file.txt".

    Thanks,

    Michael

  • 0 in reply to Michael C
    TI__Mastermind 37985 points
    I can't tell you about the data verification error, I can only guess that the platform I have proposed does not correspond to the actual board that you have.
    But, I was able to replicate your original problem. I was working in CCS7 and everything looked fine, but then I switched to CCS8.0 and now I can't get any platforms to show up for C6746. Something changed between CCS7 and CCS8 that I can't figure out and it could take some time. The best workaround for you would be to type in the platform that correspond to your board. What board do you have?
  • 0 in reply to Sasha Slijepcevic
    Prodigy 170 points
    Hi Sasha,

    The board is designed by myself using C6746 based on the TMDSLCDK6748 EVB. The DDR2 and flash are different. I will map the memory space to proper range. Would you suggest me to downgrade to CCS7 or even CCS6? Can I use the latest Processor SDK RTOS (ti-processor-sdk-rtos-omapl138-lcdk-04.02.00.09) with CCS7 or CCS6? Can I make a customized platform for my own board? Any suggest would be appreciated.

    Thanks,
    Michael
  • 0 in reply to Michael C
    TI__Mastermind 37985 points
    You can try first to create a custom platform in CCS8.0.0 using the Platform Wizard, Project->RTSC Tools->Platform->New. I think you'll have to do that no matter which version of CCS you use because even if you were able to select a platform from a drop-down list, that platform wouldn't fit your memory map, so you would have to use the Platform Wizard anyway.
  • 0 in reply to Sasha Slijepcevic
    Prodigy 170 points
    Thanks a lot Sasha.