• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 1504 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.

Custom Platform won't appear in RTSC Configuration window

Brandy Jabkiewicz
Mastermind 6325 points

Hi. 

I have always had a custom platform and it was working fine.  I recently upgraded to ccs 5.5 from 5.1.  When I imported my projects, the custom platform was fine.

Yesterday, I went to change my custom platform - now I cannot see it to select it in the RTSC configuration window.  When I build, configuro gives me an error saying it cannot find my platform.

If I go to Tools->RTSC Tools->View/Edit Platform, I can see it and edit it. 

If I go to the file location on disk, it is stored appropriately.

I check that that same repo is in the repo list on the RTSC Configuration tab - it is.

I check that I am using the same XDCTools that was listed in my custom platform package.mak file - it is.

Now I am out of ideas but am totally stuck with my projects!  I cannot build.

I am using XDCTools 3.25.3.72 with a C6678, bios 6.33.4.39.

Please help soon!

Thanks,
Brandy

  • 0
    TI__Mastermind 37985 points

    Brandy,
    can you post the content of the console window when you try to build the project with your platform? What's the path to your platform repository, and what's the fully qualified name of your platform package (as specified in package.xdc in your platform package)?

  • 0 in reply to Sasha Slijepcevic
    Mastermind 6325 points

    Hi Sasha,

     

    I think I figured it out, although I don't understand why the change.

     

    It looks like when I list the link to the repository in the RTSC config tab, I have to include the directory name now instead of just listing it to packages.

    In this case I had:

    ${TI_LIBRARIES}\xdctools_3_25_03_72\packages

    and I needed to change it to

    ${TI_LIBRARIES}\xdctools_3_25_03_72\packages\Logos

    Inside the Logos folder is where I keep my custom platforms.  Prior versions of CCS seemed to look inside the lower level dir, but this did not.

     

    But just to be complete, here are the answers to your questions:

    Console Window:

    **** Clean-only build of configuration Debug for project PXM_ACPSUSim ****

    "C:\\ti\\ccsv5\\utils\\bin\\gmake" -k clean

    DEL /F "configPkg\linker.cmd" "configPkg\compiler.opt" "PXM_ACPSUSim.out"

    The system cannot find the file specified.

    gmake: [clean] Error 1 (ignored)

    DEL /F "dspLumberjack.pp" "electrocardiography.pp" "rxDetections.pp" "sendCfg.pp" "txDetections.pp"

    Could Not Find C:\Users\devadmin\workspace_v5_5\PXM_ACPSUSim\trunk\build\Debug\dspLumberjack.pp

    RMDIR /S/Q "configPkg\"

    The system cannot find the file specified.

    gmake: [clean] Error 2 (ignored)

    DEL /F "cppi_device.pp" "device_srio.pp" "initCommon.pp" "networkCommon.pp" "pxmAcpsuSim.pp" "qmss_device.pp" "srioCommon.pp" "ti_osal.pp" "ti_resourcemgr.pp" "timeStamp.pp" "timers.pp"

    Could Not Find C:\Users\devadmin\workspace_v5_5\PXM_ACPSUSim\trunk\build\Debug\cppi_device.pp

    DEL /F "cppi_device.obj" "device_srio.obj" "dspLumberjack.obj" "electrocardiography.obj" "initCommon.obj" "networkCommon.obj" "pxmAcpsuSim.obj" "qmss_device.obj" "rxDetections.obj" "sendCfg.obj" "srioCommon.obj" "ti_osal.obj" "ti_resourcemgr.obj" "timeStamp.obj" "timers.obj" "txDetections.obj"

    Could Not Find C:\Users\devadmin\workspace_v5_5\PXM_ACPSUSim\trunk\build\Debug\cppi_device.obj

    'Finished clean'

    ' '

    **** Build Finished ****

    **** Build of configuration Debug for project PXM_ACPSUSim ****

    "C:\\ti\\ccsv5\\utils\\bin\\gmake" -k all

    'Building file: C:/Users/devadmin/workspace_v5_5/PXM_ACPSUSim/trunk/src/pxmAcpsuSim.cfg'

    'Invoking: XDCtools'

    "C:/Users/devadmin/workspace_v5_5/TI_Libraries/xdctools_3_22_04_46/xs" --xdcpath="C:/Users/devadmin/workspace_v5_5/TI_Libraries/xdctools_3_22_04_46/packages;C:/Users/devadmin/workspace_v5_5/TI_Libraries/pdk_C6678_1_0_0_21/packages;C:/Users/devadmin/workspace_v5_5/TI_Libraries/ndk_2_21_00_32/packages;C:/Users/devadmin/workspace_v5_5/TI_Libraries/bios_6_33_04_39/packages;C:/Users/devadmin/workspace_v5_5/TI_Libraries/ipc_1_24_00_16/packages;C:/ti/ccsv5/ccs_base;" xdc.tools.configuro -o configPkg -t ti.targets.elf.C66 -p Logos.PXM -r debug -c "C:/ti/ccsv5/tools/compiler/c6000_7.4.4" "C:/Users/devadmin/workspace_v5_5/PXM_ACPSUSim/trunk/src/pxmAcpsuSim.cfg"

    js: "C:/Users/devadmin/workspace_v5_5/TI_Libraries/xdctools_3_22_04_46/packages/xdc/tools/Cmdr.xs", line 51: Error: xdc.tools.configuro: InternalError: Logos.PXM: can't resolve name xdc.platform.IPlatform.peripherals

    gmake: *** [configPkg/linker.cmd] Error 1

    gmake: Target `all' not remade because of errors.

    **** Build Finished ****

     

    Path to platform repository:

    C:\Users\devadmin\workspace_v5_5\TI_Libraries\xdctools_3_25_03_72\packages\Logos\PXMv2

     

    Contents of package.xdc

    package PXMv2 {     module Platform;

    }

     

    Thanks!

    Brandy

     

  • 0 in reply to Brandy Jabkiewicz
    TI__Mastermind 37985 points

    Brandy,
    package.xdc states that the name of your platform is 'PXMv2', and that's the name you should always use for the option -p on the configuro command line. The name of the repository is then the name of the directory one level above PXMv2, which is in your case C:\Users\devadmin\workspace_v5_5\TI_Libraries\xdctools_3_25_03_72\packages\Logos. That is the directory that should show up in your package path. I am not sure if the previous versions of XDCtools searched exhaustively the subdirectories, but that's a functionality that you should not rely on.

    I also noticed that your output shows that you were using XDCtools 3.22 to build. The error that refers to the interface IPeripherals hints that you built the platform with newer tools, most likely 3.25, and then try to use it with XDCtools 3.22. That's not always a wrong thing to do, but because of some changes in IPlatform in 3.25, platforms built with 3.25 can't be used with older tools.

    We don't recommend keeping your custom platforms within an XDCtools installation. You may sometimes need to uninstall and reinstall XDCtools, and you don't want your platforms to be accidentally written over.

    If your build is working now, you probably don't want to make changes that I am recommending, but if you have any further problems you may want to adjust your options and paths in the way I propose here.

  • 0 in reply to Sasha Slijepcevic
    Mastermind 6325 points

    Sorry, I switched everything over to 3.25 but I was also trying to discover what went wrong on two computers.  I had already corrected it on one computer and took the error from the second computer that was still pointing at the old version of XDC tools.  

    The problem seemed to be 1.  that CCSv5.5 was using XDCTools 3.25 and my project was using XDCTools 3.22.  When I synced that up, I found problem number 2, that I relied on the exhaustive directory search and that seemed to stop working with the upgrade.

    Thanks for your help speedy help! I think I'll call this closed for now :)

    Brandy