CC2340R5: Migration issues (7.20 -> 8.40 + CCS)

vespaman

Part Number: CC2340R5
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

Hi,

So my old CCS installation ceased to work with my latest update of linux, so I did not see any way forward, but to bite the bullet and update CCS to 20.0.2 (was using CCS 12.3.0) and sdk from 7.20 (i think) to 8.40.

I have two problems.

1. One of my files are encoded to 8859-1, but CCS does not understand this. How/where to I tell CCS about file encodings? I searched hi and low...

2. I based my project off basic_ble, and so what I did now, was to create a new basic_ble, and move my stuff over. However, I get undefined symbols, that I don't recognize after doing that;

data-mode="text"> undefined first referenced in file ---------------- ./syscfg/ti_radio_config.o ./syscfg/ti_radio_config.o ./syscfg/ti_radio_config.o /home/x/bin/ti/simplelink_lowpower_f3_sdk_8_40_00_61/source/ti/ble5stack_flash/lib_projects/CC2340R5/OneLib/lib/ticlang/m0p/OneLib.a<OneLib_LL_ll_common.obj> /home/x/bin/ti/simplelink_lowpower_f3_sdk_8_40_00_61/source/ti/ble5stack_flash/lib_projects/CC2340R5/OneLib/lib/ticlang/m0p/OneLib.a<OneLib_LL_ll.obj> /home/x/bin/ti/simplelink_lowpower_f3_sdk_8_40_00_61/source/ti/ble5stack_flash/lib_projects/CC2340R5/OneLib/lib/ticlang/m0p/OneLib.a<OneLib_LL_ll_ae.obj> /home/x/bin/ti/simplelink_lowpower_f3_sdk_8_40_00_61/source/ti/ble5stack_flash/lib_projects/CC2340R5/OneLib/lib/ticlang/m0p/OneLib.a<OneLib_LL_ll_ae.obj> /home/x/bin/ti/simplelink_lowpower_f3_sdk_8_40_00_61/source/ti/ble5stack_flash/lib_projects/CC2340R5/OneLib/lib/ticlang/m0p/OneLib.a<OneLib_LL_ll.obj> /home/x/bin/ti/simplelink_lowpower_f3_sdk_8_40_00_61/source/ti/ble5stack_flash/lib_projects/CC2340R5/OneLib/lib/ticlang/m0p/OneLib.a<OneLib_LL_ll.obj> /home/x/bin/ti/simplelink_lowpower_f3_sdk_8_40_00_61/source/ti/ble5stack_flash/lib_projects/CC2340R5/OneLib/lib/ticlang/m0p/OneLib.a<OneLib_LL_ll_ae.obj> /home/x/bin/ti/simplelink_lowpower_f3_sdk_8_40_00_61/source/ti/ble5stack_flash/lib_projects/CC2340R5/OneLib/lib/ticlang/m0p/OneLib.a<OneLib_LL_ll_adv_end_causes.obj> /home/x/bin/ti/simplelink_lowpower_f3_sdk_8_40_00_61/source/ti/ble5stack_flash/lib_projects/CC2340R5/OneLib/lib/ticlang/m0p/OneLib.a<OneLib_LL_ll_isr.obj> /home/x/bin/ti/simplelink_lowpower_f3_sdk_8_40_00_61/source/ti/ble5stack_flash/lib_projects/CC2340R5/OneLib/lib/ticlang/m0p/OneLib.a<OneLib_LL_ll_adv_end_causes.obj> /home/x/bin/ti/simplelink_lowpower_f3_sdk_8_40_00_61/source/ti/ble5stack_flash/lib_projects/CC2340R5/OneLib/lib/ticlang/m0p/OneLib.a<OneLib_LL_ll_isr.obj> /home/x/bin/ti/simplelink_lowpower_f3_sdk_8_40_00_61/source/ti/ble5stack_flash/lib_projects/CC2340R5/OneLib/lib/ticlang/m0p/OneLib.a<OneLib_LL_ble.obj> /home/x/bin/ti/simplelink_lowpower_f3_sdk_8_40_00_61/source/ti/ble5stack_flash/lib_projects/CC2340R5/OneLib/lib/ticlang/m0p/OneLib.a<OneLib_LL_ble.obj> /home/x/bin/ti/simplelink_lowpower_f3_sdk_8_40_00_61/source/ti/ble5stack_flash/lib_projects/CC2340R5/OneLib/lib/ticlang/m0p/OneLib.a<OneLib_LL_ble.obj> /home/x/bin/ti/simplelink_lowpower_f3_sdk_8_40_00_61/source/ti/ble5stack_flash/lib_projects/CC2340R5/OneLib/lib/ticlang/m0p/OneLib.a<OneLib_LL_ble.obj> /home/x/bin/ti/simplelink_lowpower_f3_sdk_8_40_00_61/source/ti/ble5stack_flash/lib_projects/CC2340R5/OneLib/lib/ticlang/m0p/OneLib.a<OneLib_LL_ll.obj> /home/x/bin/ti/simplelink_lowpower_f3_sdk_8_40_00_61/source/ti/ble5stack_flash/lib_projects/CC2340R5/OneLib/lib/ticlang/m0p/OneLib.a<OneLib_LL_ll.obj> /home/x/bin/ti/simplelink_lowpower_f3_sdk_8_40_00_61/source/ti/ble5stack_flash/lib_projects/CC2340R5/OneLib/lib/ticlang/m0p/OneLib.a<OneLib_LL_ll.obj> /home/x/bin/ti/simplelink_lowpower_f3_sdk_8_40_00_61/source/ti/ble5stack_flash/lib_projects/CC2340R5/OneLib/lib/ticlang/m0p/OneLib.a<OneLib_LL_ll_rat.obj> unresolved symbols remain errors encountered during linking; "basic_ble_LP_EM_CC2340R5_freertos_ticlang.out" not built tiarmlnk command failed with exit code 1 (use -v to see invocation) [basic_ble_LP_EM_CC2340R5_freertos_ticlang.out] Error 1 recipe for target 'all' failed

What is this? It does not make much sense for me. I have isolated my own code pretty well, so I am confused how/if this can be traced back to me.

Hopefully this is a common thing :-)

6 months ago

0 Ryan Brown1 6 months ago

TI__Guru**** 217367 points

Hi vespaman,

Both ti_radio_config and OneLib are related to resources brought in by SysConfig. The v7.20 SDK supports SysConfig v1.17 whereas the v8.40 SDK supports SysConfig v1.22. If you copy/pasted your original v7.20 SDK SysConfig file into v8.40 then this likely caused issues. I recommend that you first build the v8.40 example in CCS v20 to ensure that your environment is set up correctly. Then you will need to use the existing v8.40 SysConfig file as-is and make changes in the SysConfig Editor which matches the configuration of the v7.20 version.

I will loop in a CCS expert to comment on the 8859-1 encoding, and here is the CCS User's Guide.

Regards,
Ryan

0 vespaman 6 months ago in reply to Ryan Brown1

Prodigy 170 points

Hi Ryan,

Yes, guilty as charged. I copy/pasted the sysconfig file, and opened+saved it in new sysconfig editor. I'll rebuild a new sysconfig from 8.40 scratch. I makes sense that this is the base problem.

Thanks a lot!

0 Ki 6 months ago

TI__Guru**** 464101 points

vespaman said:
1. One of my files are encoded to 8859-1, but CCS does not understand this.

What is meant by CCS "not understanding this"? Is it an editor formatting issue? Or a build issue?

0 vespaman 6 months ago in reply to Ki

Prodigy 170 points

Well, both. The editor tries to read it as utf8 (my guess), the strings are therefore broken, which leads to the build emits warnings, and of course the compiled file will not show the iso8859-1 character set.

Maybe, (I guess) it will work if I compile outside CCS, using make file build. I have not tried this, but I can't see why wouldn't work. But it is a bit tedious. And there have to be a way to do this inside CCS, like every other editors, I'd guess. I just can't find it.

0 Ki 6 months ago in reply to vespaman

TI__Guru**** 464101 points

vespaman said:
And there have to be a way to do this inside CCS, like every other editors, I'd guess. I just can't find it.

Perhaps try setting this in the properties?

0 vespaman 6 months ago in reply to Ki

Prodigy 170 points

Yes, that looks about right! But I don't have that setting.. ?

This is my version;

0 Ki 6 months ago in reply to vespaman

TI__Guru**** 464101 points

Ah, sorry. I thought you were using CCS Eclipse.

For CCS 20, you can try the option mentioned below:

https://stackoverflow.com/questions/38528384/how-to-setup-visual-studio-code-to-detect-and-set-the-correct-encoding-on-file-o

0 vespaman 6 months ago in reply to Ki

Prodigy 170 points

So that did something - the content changed, but still not to 8859-1, but something else. And it still give issues in build, therefore.

I have not tried if setting the default to 8859-1 as per the older suggestion in stack overflow will work.

I'll have to go now, but I will try more tomorrow. Thanks so far!

0 vespaman 6 months ago in reply to vespaman

Prodigy 170 points

So with regards to the editor iso8859-1 issue, I think I have it working now, I added a comment in the first row of the file, that included some 8859-1 characters.

But:- I still get warnings when I build.

The code used to compile without warnings on 7.20/CCS eclipse with this pragma line in the beginning of the file.

#pragma -Wno-invalid-source-encoding

Yet now I get warning: illegal character encoding in string literal [-Winvalid-source-encoding]

Isn't this pragma supported any longer?

0 vespaman 6 months ago in reply to Ryan Brown1

Prodigy 170 points

Hi Ryan,

So I installed a fresh basic_ble again, and it built without any problems.

Then I added my settings manually from the old sysconfig (having it open on another computer), and immediately when I had done this, I get the same build issues again. (without adding any of my own source code files).

Sine it is quite some settings to enter (doing it again does not sound fun) - is there any to see what is creating these errors?

0 Ryan Brown1 6 months ago in reply to vespaman

TI__Guru**** 217367 points

Thanks for reverting and confirming the example build works. All of the errors (LRF_* and RCL_*) are pointing to radio issues, this could either be the BLE, RF Design, or RCL modules in SysConfig. When you "added settings manually" was this using a Text Editor to directly modify the SysConfig source file or are you using the SysConfig Editor GUI? You should be able to isolate the issue to a few radio-related changes which we can then further investigate.

Regards,
Ryan

0 vespaman 6 months ago in reply to Ryan Brown1

Prodigy 170 points

OK, so I started scratch again, and built after each change, and finally arrived to RCL, which in my old build was not created (don't remember if I removed it myself, more likely it was never added). So in 8.40, it needs to be added.

After re-adding it, the build goes through. Now I will continue to re-add my own source files again, and clean up all the test mess.

The only remaining issue from this thread now, is the non-working #pragma.

Thanks for your help

0 Ryan Brown1 6 months ago in reply to vespaman

TI__Guru**** 217367 points

I don't have an answer for the pragma issue, here are some more resources from TI:

https://software-dl.ti.com/ccs/esd/documents/sdto_cgt_pragmas_you_can_understand.html
https://software-dl.ti.com/codegen/docs/tiarmclang/rel2_1_0_LTS/compiler_manual/c_cpp_language_implementation/pragmas.html

Regards,
Ryan

0 vespaman 6 months ago in reply to Ryan Brown1

Prodigy 170 points

OK, thanks. I'll see what changes has been made. Perhaps also there's some compiler version history.

Bluetooth®︎

Bluetooth forum

CC2340R5: Migration issues (7.20 -> 8.40 + CCS)