LAUNCHXL-CC1312R1: Can't find the platform package 'ti.platforms.simplelink'.

Hi Brian,

I see that you are still using Code Composer Version 10. Could you please update to version 12.1?

I am asking because this is what the SDK release notes are suggesting:

https://software-dl.ti.com/simplelink/esd/simplelink_cc13xx_cc26xx_sdk/6.30.01.03/exports/release_notes_simplelink_cc13xx_cc26xx_sdk_6_30_01_03.html

Those tools are being updated between CCS releases.

Regards,

Arthur

Thank you, Arthur, for your reply.  I see now that CCS 12.1.0 is a prerequisite for this SDK so I downloaded and installed it but I'm getting the same error:  "xdc.tools.configuro: Error: Can't find the platform package 'ti.platforms.simplelink'."  (Full output below.)  I've verified that all the paths do indeed exist and that the environment variables expand properly, but to no avail.  Next I will try removing all traces of CCS and the SDK and XDCtools from my system and performing clean installations.  My reasoning is that after repeated import attempts, something is pointing to an incorrect path somewhere.  Otherwise, I'm at a loss.

Thanks again for your suggestion.

**** Build of configuration Debug for project tirtos_builds_CC1312R1_LAUNCHXL_release_ccs ****

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

Building file: "../release.cfg"
Invoking: XDCtools
"C:/ti/ccs1210/xdctools_3_62_01_16_core/xs" --xdcpath="C:/ti/simplelink_cc13xx_cc26xx_sdk_6_30_00_84/.;C:/ti/ccs1210/xdctools_3_62_01_16_core/packages;C:/ti/simplelink_cc13xx_cc26xx_sdk_6_30_00_84/source;C:/ti/simplelink_cc13xx_cc26xx_sdk_6_30_00_84/kernel/tirtos/packages;C:/ti/simplelink_cc13xx_cc26xx_sdk_6_30_00_84/kernel/tirtos7/packages;C:/ti/simplelink_cc13xx_cc26xx_sdk_6_30_00_84;" xdc.tools.configuro -o configPkg -t ti.targets.arm.elf.M4F -p ti.platforms.simplelink:CC1312R1F3 -r release -c "C:/ti/ccs1210/ccs/tools/compiler/ti-cgt-arm_20.2.7.LTS" --compileOptions " -DDeviceFamily_CC13X2 " "../release.cfg"
subdir_rules.mk:12: recipe for target 'build-1109207425-inproc' failed
js: "C:/ti/ccs1210/xdctools_3_62_01_16_core/packages/xdc/tools/Cmdr.xs", line 52: Error: xdc.tools.configuro: Error: Can't find the platform package 'ti.platforms.simplelink'. TI platforms are no longer shipped as part of XDCtools (C:\ti\ccs1210\xdctools_3_62_01_16_core). Please ensure you are either using a pre-3.30 version of XDCtools or you have added a product that includes your platform support along the path 'C:/ti/simplelink_cc13xx_cc26xx_sdk_6_30_00_84;C:/ti/ccs1210/xdctools_3_62_01_16_core/packages;C:/ti/simplelink_cc13xx_cc26xx_sdk_6_30_00_84/source;C:/ti/simplelink_cc13xx_cc26xx_sdk_6_30_00_84/kernel/tirtos/packages;C:/ti/simplelink_cc13xx_cc26xx_sdk_6_30_00_84/kernel/tirtos7/packages;C:\ti\ccs1210\xdctools_3_62_01_16_core/packages'. Check that this path names a directory containing the necessary platform support and that the platform name is properly spelled.
gmake[1]: *** [build-1109207425-inproc] Error 1
Building file: "../release.cfg"
Invoking: XDCtools
"C:/ti/ccs1210/xdctools_3_62_01_16_core/xs" --xdcpath="C:/ti/simplelink_cc13xx_cc26xx_sdk_6_30_00_84/.;C:/ti/ccs1210/xdctools_3_62_01_16_core/packages;C:/ti/simplelink_cc13xx_cc26xx_sdk_6_30_00_84/source;C:/ti/simplelink_cc13xx_cc26xx_sdk_6_30_00_84/kernel/tirtos/packages;C:/ti/simplelink_cc13xx_cc26xx_sdk_6_30_00_84/kernel/tirtos7/packages;C:/ti/simplelink_cc13xx_cc26xx_sdk_6_30_00_84;" xdc.tools.configuro -o configPkg -t ti.targets.arm.elf.M4F -p ti.platforms.simplelink:CC1312R1F3 -r release -c "C:/ti/ccs1210/ccs/tools/compiler/ti-cgt-arm_20.2.7.LTS" --compileOptions " -DDeviceFamily_CC13X2 " "../release.cfg"
subdir_rules.mk:12: recipe for target 'build-1109207425-inproc' failed
js: "C:/ti/ccs1210/xdctools_3_62_01_16_core/packages/xdc/tools/Cmdr.xs", line 52: Error: xdc.tools.configuro: Error: Can't find the platform package 'ti.platforms.simplelink'. TI platforms are no longer shipped as part of XDCtools (C:\ti\ccs1210\xdctools_3_62_01_16_core). Please ensure you are either using a pre-3.30 version of XDCtools or you have added a product that includes your platform support along the path 'C:/ti/simplelink_cc13xx_cc26xx_sdk_6_30_00_84;C:/ti/ccs1210/xdctools_3_62_01_16_core/packages;C:/ti/simplelink_cc13xx_cc26xx_sdk_6_30_00_84/source;C:/ti/simplelink_cc13xx_cc26xx_sdk_6_30_00_84/kernel/tirtos/packages;C:/ti/simplelink_cc13xx_cc26xx_sdk_6_30_00_84/kernel/tirtos7/packages;C:\ti\ccs1210\xdctools_3_62_01_16_core/packages'. Check that this path names a directory containing the necessary platform support and that the platform name is properly spelled.
gmake[2]: *** [build-1109207425-inproc] Error 1
gmake[1]: *** No rule to make target 'build-1109207425', needed by 'configPkg/linker.cmd'.
gmake[1]: Target 'configPkg/linker.cmd' not remade because of errors.
gmake: *** [all] Error 2
makefile:127: recipe for target 'all' failed

**** Build Finished ****

Hi Brian,

Did you try clean re-installing CCS and the SDK? Did it solve your issue?

Regards,

Arthur

Thanks for your follow-up, Arthur.  Yes, I removed all TI references from my drive and performed a clean re-installation of CCS and the SDK and then rediscovered ("refresh") the SimpleLink SDK product in CCS Preferences and installed it via the dialog provided there.  Unfortunately, I encountered the same errors upon build:

js: "C:/ti/xdctools_3_62_01_15_core/packages/xdc/tools/Cmdr.xs", line 52: 
Error: xdc.tools.configuro: Error: 
Can't find the platform package 'ti.platforms.simplelink'.  
TI platforms are no longer shipped as part of XDCtools (C:\ti\xdctools_3_62_01_15_core).  
Please ensure you are either using a pre-3.30 version of XDCtools 
or you have added a product that includes your platform support along the path 
'C:/ti/simplelink_cc13xx_cc26xx_sdk_6_30_00_84;
C:/ti/xdctools_3_62_01_15_core/packages;
C:/ti/simplelink_cc13xx_cc26xx_sdk_6_30_00_84/source;
C:/ti/simplelink_cc13xx_cc26xx_sdk_6_30_00_84/kernel/tirtos/packages;
C:/ti/simplelink_cc13xx_cc26xx_sdk_6_30_00_84/kernel/tirtos7/packages;
C:\ti\xdctools_3_62_01_15_core/packages'.  
Check that this path names a directory containing the necessary platform support 
and that the platform name is properly spelled.

Once again, the path list shows the same anomalies:  the final path is a duplicate of the first path except it is of mixed slashes/back-slashes.  All the other paths are in Linux format (/).

 Relative to that slash type, I found this:

In the Package Path, you control the XDCPATH portion. This prefix is a string
of ';' separated directories that contain packages.
XDCPATH may be specified as an environment variable or on the command
line of any tool that uses the Package Path. See the documentation of the
particular command-line tool to find the appropriate option.
IMPORTANT NOTE: All directories referenced in XDCPATH, whether in an
environment variable or a command line, must use forward slashes (/) as
separators instead of the Windows-standard backslash (\). For example,
use "c:/os;c:/drivers;c:/framework".
Relative paths in XDCPATH reference directories relative to the package
being built rather than the directory from which the command was invoked.
Thus, a relative path refers to a different repository for each package used.
Note: It is usually a mistake to use a relative path in the XDCPATH prefix.

Managing the XDCPATH Portion of the Package Path

So next I turned my attention to the paths created by the installers.  I noticed that when I hovered my mouse cursor over the XDCpath Package Repositories value in the project properties for the tirtos project upon which my project depends, I see a tooltip “Repository resolves to a location that does not exist.”  This project is the tirtos build specific to my hardware (SimpleLink CC13XX-CC26XX SDK).  If that project doesn’t build, obviously my application can’t build.

Examining that tirtos project, I found some warnings about some malformed paths.  Bear in mind that these paths were created automatically by the installation process, not by me.  This second screenshot shows the inconsistencies:

Notice that the first path is actually two semi-colon delimited paths, but when the environmental variable is expanded (presumably by the make file?), it resolves to a malformed path that has two colons after the drive letter.  (Compare the red-circled items.)

I attempted to correct this by splitting this path into two properly formed paths and moving them up in the search order.  And while this eliminated those two related warnings, two remained:  The path contains, “kernel\tirtos\packages” but as created by the installer, this path in actuality is “kernel\tirtos7\packages” on my hard drive.  I tried various combinations of changing the file system’s path to match either or both variations but all resulted in errors -- the same error message just reflecting the changed path name.  To rule out the possibility of different operations pointing to differing paths, I made an exact copy so identical versions exist as both tirtos and tirtos7.  This eliminated the final warnings but I still get:

js: "C:/ti/xdctools_3_62_01_15_core/packages/xdc/tools/Cmdr.xs", line 52: Error: xdc.tools.configuro: Error: Can't find the platform package 'ti.platforms.simplelink'.  TI platforms are no longer shipped as part of XDCtools (C:\ti\xdctools_3_62_01_15_core).  Please ensure you are either using a pre-3.30 version of XDCtools or you have added a product that includes your platform support along the path 'C:/ti/simplelink_cc13xx_cc26xx_sdk_6_30_00_84;C:/ti/xdctools_3_62_01_15_core/packages;C:/ti/simplelink_cc13xx_cc26xx_sdk_6_30_00_84/source;C:/ti/simplelink_cc13xx_cc26xx_sdk_6_30_00_84/kernel/tirtos/packages;C:/ti/simplelink_cc13xx_cc26xx_sdk_6_30_00_84/kernel/tirtos7/packages;C:\ti\xdctools_3_62_01_15_core/packages'.  Check that this path names a directory containing the necessary platform support and that the platform name is properly spelled. 

I’m rapidly running out of ideas here.  I'd be most appreciative if you could suggest some other approach or course of action.

Hi Brian,

Please excuse me for the delay, I have forwarded your issue to the team in charge of the development tools.

Regards,

Arthur

Just wondering if anyone is looking into this; the problem still hasn’t been solved.

One other datapoint:  The sysbios source files appear to be missing from the project so I tried running the Sys-Bios (TIRTOS) installer, “tirtos_cc13xx_cc26xx_setupwin32_2_21_01_08.exe” and installed the discovered product (under Preferences).  The project still doesn’t build.  It is reporting errors that seem to be incorrect:

Note that the screenshot shows the missing src/sysbios files (grayed-out in the Project Explorer on the left).

Overlaying that are the properties for the problem project:  it shows an ‘Invalid Location’ for a file called Board.html (which is merely general board information for the user).  Overlaying that is an expansion of the path and its variable.  Note that this resolves to the same path you see in the File Explorer I have inserted into the lower left of the screen; THE FILE TRULY EXISTS and I can view it, but it is not being identified propertly by the build scripts!

So the tirtos sysbios files exist on my hard drive but there seems to be a problem with the build tools or the tirtos build scripts recognizing them.

Again, I question this painful build process:  am I missing a more direct way to upgrade the SimpleLink SDK version of the Launchpad projects?  I can’t believe it should be this obtuse.  I hope someone can render some assistance here.

Brian,

In your screenshot, I see that the path variable 'COM_TI_SIMPLELINK_CC13XX_CC26XX_SDK_INSTALL_DIR' is defined in the project. However, some resources are referencing 'TI_COM_SIMPLELINK_CC13X2_CC26X2_SDK_INSTALL_DIR'. There is a variable mismatch.

I assume the crux of these issues is due to somewhere along the way, the SDK was renamed from CC13x2/CC26x2 to CC13xx/CC26xx. If you are coming from SDK version 4.x, you'd likely be running into this. Also, you are using TI-RTOS6 while the new SDK by default supports TI-RTOS7 (in addition to FreeRTOS).

Arthur - these are issues for the device/SDK experts (which I am not) to answer.

Thanks

ki

Thanks Ki, I hadn't noticed the 2's.  That and the TIRTOS versions give me something to work with.  Thanks so much for your input!  And hopefully a device/SDK person can chime in with an easier path forward.

Approaching this from a different angle, I decided to wipe CCS and all dependencies from my hard drive and perform another clean installation of CCS 12.1.  I then installed the SimpleLink SDK (6.40.00.13), the GCC Arm Toolchain (9.2.1), the TI Arm Compiler (2.01.02.00), and XDCTools (3.62.01.15).  My intention was to build the example projects (WsnNode and WsnConcentrator) upon which my project was originally based.  I reasoned that if I built these examples with the latest SDK, I could then systematically reapply all the customizations we had made to the examples under the old SDK and so bring the project into alignment with the newer TI-RTOS7 and SysConfig methodologies that would permit me to migrate from the old UART module to the new UART2.  (I require the RX callback features of UART2 hence the reason for this update to a newer SDK.)

I am encountering several problems however: 

First, I cannot find the original examples, WsnNode and WsnConcentrator.  After installing the SDK, Resource Explorer populates with what appear to be completely different examples.  Can anyone tell me if those two legacy examples have been ported to the newer RTOS/SDK?

The second problem is that when I import the demo project and attempt to build it, I get:

       Error: simplelink_cc13xx_cc26xx_sdk version 6.40.00.13 requires at least version 1.15.0 of SysConfig.

The SDK Package Info shows the version numbers of the components I listed above but also this line:

          Mandatory depdendency [sic]        sysconfig       1.15.0           Not installed, unavaliable [sic]

Aside from the typos, I wonder why SysConfig 1.15.0 is mandatory but unavailable for installation.  A compiler warning says:

          Product SysConfig v1.15.0 is not currently installed. A compatible version 1.14.0 will be used.

So the build script attempted to use the version of SysConfig that was installed with CSS 12.1 but evidently that failed.  Does anyone know why the latest CCS can’t download/install SysConfig 1.15.0, or when it will become available?

Hi Brian,

We are unfortunately seeing issues with the 6.40 SDK with regards to SysConfig indeed.

I would recommend you try to do the same procedure, but using the 6.20 SDK, for the moment as per that thread: https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1182347/cc1312r7-fail-to-run-syscfg-when-install-simplelink_cc13xx_cc26xx_sdk_6_40_00_13

I am suggesting 6.20 because EasyLink has been deprecated in the 6.30 version of the SDK, as per the release notes.

Regards,

Arthur

Thank you, Arthur; I wasn't aware of this.  I'll revert to 6.20 as you suggest.

Thanks for the advice,

Brian