CC1310 to CC1350 Fails

Tim Simerly

Other Parts Discussed in Thread: CC1350, CC1310

Dear Support:

I downloaded the SDK for the TI-15.4 stack v2.0.0.25. I noticed that the projects are built for the CC1310. However when I go to the properties for the project and change the device to the CC1350F128 for the CC1350 launchpad that it fails during the linking stage with the following message using CCS:

undefined first referenced

symbol in file

--------- ----------------

heapEnd <whole-program>

heapStart <whole-program>

error #10234-D: unresolved symbols remain

error #10010: errors encountered during linking; "coprocessor_cc13xx_lp.out" not built

gmake: *** [coprocessor_cc13xx_lp.out] Error 1

>> Compilation failure

makefile:176: recipe for target 'coprocessor_cc13xx_lp.out' failed

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

**** Build Finished ****

And then when I try to go back and select the CC1310 that it fails also with the same message. The only way I found to recover is to delete the project and go back to the original version in order to be able to build again using the CC1310. Do you know what is the problem? Please advise.

Thanks,
Tim

over 9 years ago

0 YiKai Chen over 9 years ago

Guru 735695 points

If you intend to run TI 15.4 MAC on CC1350, you don't have to change any project setting from CC1310 to CC1350.

0 Tim Simerly over 9 years ago in reply to YiKai Chen

TI__Genius 9985 points

Hey Yikai:

That is strange and bothersome. In general, we specify the part number from the properties of the project using the General selection and picking the device from the drop down list for a CC1350F128 device for the CC1350 launch pad. So why wouldn't I do this for the board at hand? And then why upon selecting this for the CC1350, when I change it back to the CC1310, I can no longer build the project anymore. I don't have this problem when doing this from a project using the BLE SDK. What is wrong with the projects in this TI-MAC SDK that is preventing me from changing to the proper device for the board I am using? Please advise.

Thanks,
Tim

0 YiKai Chen over 9 years ago in reply to Tim Simerly

Guru 735695 points

You should select "cc1310lp.cmd" in Linker command file field.

0 Tim Simerly over 9 years ago in reply to YiKai Chen

TI__Genius 9985 points

Hey YK:

I am using a CC1350 launch pad. Why wouldn't I select a CC1350F128 device and rebuild? I can do this with CC1350 projects with the BLE SDK. Why can't I do this with the TI 15.4 SDK?

Tim

0 YiKai Chen over 9 years ago in reply to Tim Simerly

Guru 735695 points

There is some modifications in cc1310lp.cmd even compare with default cc13x0f123.cmd and it's the same for CC1350 to include those changes.

0 Tim Simerly over 9 years ago in reply to YiKai Chen

TI__Genius 9985 points

YK:

I don't understand what you mean by this. What are you saying I need to do? I change the device to CC1350F128 or no? And if so, I need to do something to the .cmd file as well?

Tim

0 YiKai Chen over 9 years ago in reply to Tim Simerly

Guru 735695 points

Yes, you can change device to CC1350 but you should select cc1310lp.cmd as Linker command file.

0 Tim Simerly over 9 years ago in reply to YiKai Chen

TI__Genius 9985 points

YK:

And why do I need to use that .cmd file?

Tim

0 YiKai Chen over 9 years ago in reply to Tim Simerly

Guru 735695 points

It's because your cmd file doesn't define heapStart and heapEnd. The alternative is to replace SRAM related settings in your .cmd file.

GROUP > SRAM
{
.data
.bss
.vtable
.vtable_ram
vtable_ram
.sysmem
.nonretenvar
} LOAD_END(heapStart)

.stack : > SRAM (HIGH) LOAD_START(heapEnd)

0 Tim Simerly over 9 years ago in reply to YiKai Chen

TI__Genius 9985 points

Hey YK:

Ok, understand - thanks for making that clear. And indeed that does fix the problem.

Thanks,
Tim

0 YiKai Chen over 9 years ago in reply to Tim Simerly

Guru 735695 points

You are welcome.

Sub-1 GHz

Sub-1 GHz forum

CC1310 to CC1350 Fails