CCSTUDIO: Cannot build for cc1312r1....only for cc1312r1f3

Hi Gullik,

please help me to clarify the issue.

In the latest SDK (8.30.1.1) the projects are available for CC1312R1 LaunchPad by default. This refers to this LaunchPad: https://www.ti.com/tool/LAUNCHXL-CC1312R1

The CC1314 R10 RGZ should be soldered on a CC1312R1 LaunchPad and the project should be migrated following the migration guide: https://dev.ti.com/tirex/explore/content/simplelink_cc13xx_cc26xx_sdk_8_30_01_01/docs/ti154stack/html/cc13xx_cc26xx/devices_without_launchpads.html?highlight=cc1314r10# 

I can select the configuration in SysConfig in CCS20.1 and CCS12.

Could you help me to better understand your issue? Which migration would you like to perform?

Kind regards,
Theo

Hello Theo,

On my development board there is a 48 pin IC mounted which I believe is a CC1312R1.

In the CCS 12.8.X development system this works fine, and I have the same processor

on my own boards. I am trying to move to CCS 20.1.0, that I have installed on another

machine. When I start a new project I get prompted for board or device.

If I select the board (CC1312R launchpad) and try to create a project using norts / gcc

(as my old config is / was) I can only select TI-RTOS7, TI-RTOS and freeRTOS as kernel,

norts is not an option. So, I select freeRTOS and CCS-GCC.

I select an empty example and hit create.

I now get "No GNU compilers supporting the CC1312R1F3 are installed" and no project is

created. This is for migrating my current/old design.

When I select the "upgraded design" I also am met with the no compilers installed but for

CC1314R10 (which is the chip I have on my board 48-pin) CC1314R106T0RGZR from the data

sheet.

So no GCC compilers. No nortos...

Hard to migrate old projects and to start new ones when CCS 20.1.0 does not want the parameter

I initially had....

Move from CCS 12.x to CCS 20.1.0. (software update)

Manage BOTH cc1312 and cc1314 (design migration)

BTW operating environment is Xubuntu Linux 24.04 LTS

Hi Gullik,

I understand, let me go through this.

CC1312R1 is only available in the 7x7 package and is following as 7x7 package on the LaunchPad.

CC1314R10 is available as 7x7 (RGZ) and 8x8 (RSK). The CC1314R10 LaunchPad has the 8x8 variant soldered on and because of that the 7x7 variant needs to be soldered on a CC1312R1 LaunchPad following the migration guide.

When you start a new project in CCS 20.1 I would suggest you to use File -> Import project. then you can navigate to your SDK installation directory -> examples -> nortos and select for CC1312R1 an example from the CC1312R1_LAUNCHXL directory and for CC1314R10RGZ an example from the LP_EM_CC1314R10 directory. With the empty example you get an empty project.

For the software project LP_EM_CC1314R10 you can then perform the device migration to CC1314R10 RGZ on CC1314R10 on CC1312R1 RGZ LaunchPad following: https://dev.ti.com/tirex/explore/content/simplelink_cc13xx_cc26xx_sdk_8_30_01_01/docs/ti154stack/html/cc13xx_cc26xx/software-on-cc13x4-26x4-rgz-devices.html#sec-ccxxx4rgz 

Regarding the arm gcc compiler. I couldn't find a download option as it was implemented in CCS 12.1 but you can manually download the arm gnu toolchain: https://developer.arm.com/downloads/-/gnu-rm and install it. Then you can add the compiler in CCS 20.1 under File -> Preferences -> Code Compoer Studio Settings -> General -> Compilers. You need to first add the installation directory of the compiler as compiler discovery path and then click on the discovered compilers reload icon to update the list. With this I was able to import a gcc project and compile it.

I will check internally if there is a better approach to solve this and then update this thread.

Kind reagards,
Theo

Hi Gullik,

I'm glad to hear that you could get started with this. Please reach out if you encounter further issues. 

Also when work working with the freeRTOS projects I recommend you to import them directly from the installed SDK instead of using the resource explorer to avoid confusion.

Kind regards,
Theo

Hi again,

So, I installed the latest GCC kit arm-ggc 14.3 into /armgcc directory.

I then added a compiler via file->preferences->general->compilers by adding a compiler discovery path

of /home/webjorn/armgcc/

I then click on the little icon right of discovered compilers, but no compilers are found.

I tried traversing the directory structure but CCS does not find any compilers.....

looking into the kit structure I find a lot of .exe files, which leads me to believe this kit is a dud,

.exe files belong to windows, right ???

webjorn@ThinkPad:~$ ls armgcc/aarch64-none-linux-gnu/bin/
ar.exe as.exe ld.bfd.exe ld.exe ld.gold.exe nm.exe objcopy.exe objdump.exe ranlib.exe readelf.exe strip.exe
webjorn@ThinkPad:~$

I will try another kit, where should the compile discovery path point to, would /home/webjorn/armgcc be correct?

Regards,

Gullik

Hi Gullik, 

I tried it with this version and it worked: https://developer.arm.com/-/media/Files/downloads/gnu-rm/10.3-2021.10/gcc-arm-none-eabi-10.3-2021.10-aarch64-linux.tar.bz2?rev=b748c39178c043b4915b04645d7774d8&hash=572217C8AFE83F1010753EA3E3A7EC2307DADD58

Yes the .exe files are for windows, I am not sure for the install of the latest version 14.

I will research that a bit more.

Kind regards,
Theo

Ok, I will go back to the EXACT versions you have tested. Right now I have major

problems getting a compile to work with latest GCC kit. Errors come up in very strange ways.

Variables that are accepted in some lines are NOT accepted a few lines down, but undefined.

Weird, bad compiler kit???

Gullik

Hi Gullik,

I checked what we recommend in the software release of the SDK:
  - https://software-dl.ti.com/simplelink/esd/simplelink_cc13xx_cc26xx_sdk/8.30.01.01/exports/release_notes_simplelink_cc13xx_cc26xx_sdk_8_30_01_01.html

For the 8.30.1.1 SDK the ARM GCC version gcc-arm-none-eabi-9-2019-q4-major should be used. You can try different versions but if you want to use the recommended one please install this version.
   - https://developer.arm.com/downloads/-/gnu-rm#panel6a

I think this will give you the most stable results.

Kind regards,
Theo

Thanks again Theo,

I have successfully moved the project using the CC1314R10 to ccs 20.1.0. Using TI C language compiler.  One problem was that when creating the NVS ( user for settings storage) with sysconfig the examples do not mention that I have to declare the flashBuf0 character array used by the NVS driver. It is not mentioned by name, and compilation is OK, but not linking.

Also the #pragma statements were omitted. You also have to "locate" the buffer properly by setting the section offset manually in the sysconfig tool. The usage/examples should be clearer on this, would have saved me a day. More testing is still required, but I a can run the resulting code on my Launchpad. It still needs to be tested out on the end product PCB.

I will proceed with the older CC1312 version along these lines, to migrate that as well.

Since the TI C compiler behaves reasonably, I guess the "latest" GCC compiler is not ready for production use.

Again, many thanks,

Gullik

Hi Gullik,

thank you for the update and your feedback.
I will note if for when we're updating the examples.

Please reach out again if you encounter further issues.

Kind regards,
Theo