FreeRTOS, the SWI_ALIAS pragma, and C++

Michael Holmes

Other Parts Discussed in Thread: HALCOGEN, TMS570LS1227

Hi,

I'm trying to add FreeRTOS to my TMS570LS1227 project. Most of my project is in C++. The hw layer created by HALCoGen and FreeRTOS are in C. The plan is to use C++ wrapper functions to call FreeRTOS to keep my project OS agnostic. I've started with xTaskCreate(). I wrap the FreeRTOS includes with an 'extern "C" '. The compilation error I get is...

"path_to_my_project/include/os_portmacro.h", line XXX: error #28: expression must have a constant value

The error(s) occur on the line(s) with the #pragma SWI_ALIAS statements.

I compile the HalCoGen output into a library and there are no issues compiling this. I get the error when I try to compile my cpp wrapping functions that include FreeRTOS.h. I've also tried compiling the library using the FreeRTOS download from sourceforge with similar results.

Any ideas on how to solve this problem? How can I integrate FreeRTOS into a C++ project?

Thanks,

Mike

over 12 years ago

0 Paul Blecher over 12 years ago

TI__Intellectual 1115 points

Hi Mike,

I've referred this question to our subject matter expert who should get back with you shortly.

Paul B

0 Haixiao Weng over 12 years ago

TI__Genius 13810 points

#pragma are different for c and c++.

Can you upload your ccs project? I can take a look.

Regards,

Haixiao

0 Michael Holmes over 12 years ago in reply to Haixiao Weng

Intellectual 550 points

Hi,

Here's a stripped down version of the project that shows the error. "vcm" is the top level project. It depends on the other projects. The error occurs when the "os" subproject is built.

"Z:\ws\workspace_ti\vc_spikes\vent\lib\hw\TMS570LS1227\include\os_portmacro.h", line 112: error #28: expression must have a constant value

My goal is to create a layer between my application and OpenRTOS, so the app does not depend on any particular OS. My secondary goal is to minimize the amount of C code and maximize the use of C++. I can work around the problem by making os.cpp -> op.c, but if there is another way, I'd like to know about it.