CC3235MODASF: Migration to clang

Cedric Gerber

Part Number: CC3235MODASF
Other Parts Discussed in Thread: SYSBIOS

Hi,

I'm trying to migrate our projects to tiarmclang as explained there: https://software-dl.ti.com/codegen/docs/tiarmclang/compiler_tools_user_guide/migration_guide/index.html

The migration was done ok. The project.log shows only non problematic warning.

However when I try to compile I get the following output:

**** Build of configuration Release__TICLANG for project cc32xx_roomz_lib ****

"C:\\ti\\ccs1000\\ccs\\utils\\bin\\gmake" -k -j 8 all -O 
 
Building file: "../release.cfg"
Invoking: XDCtools
"C:/ti/ccs1000/xdctools_3_62_00_08_core/xs" --xdcpath="C:/ti/simplelink_cc32xx_sdk_5_10_00_02/source;C:/ti/simplelink_cc32xx_sdk_5_10_00_02/kernel/tirtos/packages;C:/ti/simplelink_cc32xx_sdk_5_10_00_02;" xdc.tools.configuro -o configPkg -t ti.targets.arm.elf.M4 -p ti.platforms.simplelink:CC3235SF -r release -c "C:/ti/ti-cgt-armllvm_1.3.0.LTS" "../release.cfg"
configuring release.xem4 from package/cfg/release_pem4.cfg ...
generating custom ti.sysbios library makefile ... 
Starting build of library sources ...
making C:/workspace/ccs_v3/cc32xx_roomz_lib/src/sysbios/sysbios.aem4 ...
clem4 C:/ti/simplelink_cc32xx_sdk_5_10_00_02/kernel/tirtos/packages/ti/sysbios/BIOS.c ...
Build of libraries failed.
subdir_rules.mk:19: recipe for target 'build-660403727-inproc' failed
C:/Users/gerbe/AppData/Local/Temp/make4492-3.sh: 1: C:/Users/gerbe/AppData/Local/Temp/make4492-3.sh: C:/ti/ti-cgt-armllvm_1.3.0.LTS/bin/armcl: not found

It seems that xdc tools is still configured to use armcl and does not find it in clang folder...

When I look into Release__TICLANG/configPkg/package.mak I see the reference to armcl.

release.xem4: package/cfg/release_pem4.oem4 
	$(RM) $@
	@$(MSG) lnkem4 $@ ...
	$(RM) $(XDCCFGDIR)/$@.map
	$(ti.targets.arm.elf.M4.rootDir)/bin/armcl -fs $(XDCCFGDIR)$(dir $@). -q -u _c_int00 --silicon_version=7M4 -z --strict_compatibility=on  -o $@ package/cfg/release_pem4.oem4   package/cfg/release_pem4.xdl  -w -c -m $(XDCCFGDIR)/$@.map -l $(ti.targets.arm.elf.M4.rootDir)/lib/libc.a

I have searched how to configure xdc to use clang, but without success.

How can I change this?

Cédric

over 4 years ago

0 Kobi Leibovitch over 4 years ago

TI__Guru 63006 points

Hi Cédric,

I will need to consult on this and come back to you.

One option that may be easier is to start from a clang project (as can be found in the latest SDKs) and replace the sources.

Br,

Kobi

0 Kobi Leibovitch over 4 years ago in reply to Kobi Leibovitch

TI__Guru 63006 points

can you open the project in CCS?

if yes, what compiler is defined in the Project Properties -> General -> Project ?

If you don't see "TI Clang ..." try to switch to one.

0 Cedric Gerber over 4 years ago in reply to Kobi Leibovitch

Expert 2310 points

Hi Kobi,

It's set to TI clang. When I look at the compiler properties it correctly shows clang config.

0 Kobi Leibovitch over 4 years ago in reply to Cedric Gerber

TI__Guru 63006 points

what do you see in the Properties -> Build -> Arm Compiler -> Command ?

0 Kobi Leibovitch over 4 years ago in reply to Kobi Leibovitch

TI__Guru 63006 points

0 Cedric Gerber over 4 years ago in reply to Kobi Leibovitch

Expert 2310 points

It's set to clang as in yours.

I'm not sure if the xdc tools part is correct.

0 Kobi Leibovitch over 4 years ago in reply to Kobi Leibovitch

TI__Guru 63006 points

that's mine... (very similar).

I suggest that you use a clang project as a reference and search for the difference (or use it for your project and just replace the sources).

br,

Kobi

0 Cedric Gerber over 4 years ago in reply to Kobi Leibovitch

Expert 2310 points

After some fiddling with example projects, I found that they had ti.targets.arm.clang.M4 instead of ti.targets.arm.elf.M4 in the flag (along with compiler parameters). With this modification it now passes this step OK.

It could be interesting to add this in the migration tool.

I also had some issue due to the #include_next <sys/types.h> /* toolchain header file */ in ti/posix/ticlang/sys/types.h

After some shuffling of compiler search path it now compiles ok.

0 Kobi Leibovitch over 4 years ago in reply to Cedric Gerber

TI__Guru 63006 points

Hi Cedric,

Thanks for the resolution info.

BTW. where did you update the flag?

Br,

Kobi

0 Cedric Gerber over 4 years ago in reply to Kobi Leibovitch

Expert 2310 points

I edited it in XDCtools => summary of flags set

At the bottom there is an "edit Flags" button.

Now I have an issue with linking.

My projects are all using a static library project. The static library is compiling ok with clang and its output can be used by the main project without clang.

But when I migrate the main project to clang. I get some undefined symbols.

undefined first referenced
symbol in file
--------- ----------------
__vla_alloc C:/workspace/ccs_v3/cc32xx_roomz_lib/Release/cc32xx_roomz_lib.lib<http_setza.obj>
__vla_dealloc C:/workspace/ccs_v3/cc32xx_roomz_lib/Release/cc32xx_roomz_lib.lib<http_setza.obj>
main_func_sp C:\ti\simplelink_cc32xx_sdk_5_10_00_02\kernel\tirtos\packages\ti\targets\arm\rtsarm\lib\boot.aem4<boot.oem4>

I could not find a .a file which defines those.

0 Kobi Leibovitch over 4 years ago in reply to Cedric Gerber

TI__Guru 63006 points

Http_setza is a file in your library?

I would again suggest that you compare your library settings to one of the clang libraries in the SDK. Probably a missing compile/archive flag there.

0 Cedric Gerber over 4 years ago in reply to Kobi Leibovitch

Expert 2310 points

Yes, it is.

I've spend some time comparing between the example project and my projects:

- Compiler setting

- Linker settings

- Link path

- targets

Without success for now.

I'll pick this up again after the holidays.

0 Kobi Leibovitch over 4 years ago in reply to Cedric Gerber

TI__Guru 63006 points

Thanks for the update.

Wi-Fi

Wi-Fi forum

CC3235MODASF: Migration to clang