[E0001]unidentified symbol and [e0300] errors in portasm.asm using TM4C1294+FreeRTOS

Jin Seo

Expert 1130 points

Hi,

Compiler ver: TI v5.1.6

CCS 6.0.1

Lwip1.4.1

freeRTOS 7.0.2

I have hit by unknown errors after adding Macro in FreeRTOSConfig.h

extern void vAssertCalled( unsigned long ulLine, const char * const pcFileName );
#define configASSERT( ( x ) ) if( ( x ) == 0 ) vAssertCalled( __LINE__, __FILE__ )

In portasm.asm

xPortPendSVHandler:

mov r0, #configMAX_SYSCALL_INTERRUPT_PRIORITY//------------>> unidentified symbol,but it is defined in FreeRTOSConfig.h

Because of that, any codes reference configASSERT( ) give me errors.

Also, there is warning [e1000] .cdecls C, NOLIST, WARN, "FreeRTOSConfig.h"

"Symbol names are not case significant " is checked in properties.

What's wrong with configurations?

Jin

over 10 years ago

0 Amit Ashara over 10 years ago

TI__Guru**** 244400 points

Hello Jin,

How have you included the file FreeRTOSConfig.h in the ASM code?

Regards
Amit

0 Jin Seo over 10 years ago in reply to Amit Ashara

Expert 1130 points

Hi Amit,

.cdecls C, NOLIST, WARN, "FreeRTOSConfig.h" in portasm.asm

Thanks
Jin

0 Amit Ashara over 10 years ago in reply to Jin Seo

TI__Guru**** 244400 points

Hello Jin

Can you please send your CCS project?

Regards
Amit

0 Jin Seo over 10 years ago in reply to Amit Ashara

Expert 1130 points

Hi Amit,

Here are my ccs project files 5734.ccsproject.zip. I am not sure what files you ask me for, so I attached three files.

Thanks,

Jin

0 Amit Ashara over 10 years ago in reply to Jin Seo

TI__Guru**** 244400 points

Hello Jin,

The entire CCS project as it is in the workspace

Regards
Amit

0 Jin Seo over 10 years ago in reply to Amit Ashara

Expert 1130 points

Hi Amit,

I am not allowed to post the entire project due to my company's policy, but I can see the same errors using another project(senshub_iot.zip) which is an example in ekTM4C1294 provided by TI.

I just add the following codes in FreeRTOSConfig.h:

extern void vAssertCalled( unsigned long ulLine, const char * const pcFileName );

#define configASSERT( ( x ) ) if( ( x ) == 0 ) vAssertCalled( __LINE__, __FILE__ )

Also, add vAssertCalled() in senshub_iot.c.

Thanks,

Jin

ps: Anyone is working on the below issue? since TI have not given a clear response for the issue.

0 Amit Ashara over 10 years ago in reply to Jin Seo

TI__Guru**** 244400 points

Hello Jin

The project is giving compilation error for the addition of the define

"C:/Users/a0876236/workspace_v6_0/senshub_iot/FreeRTOSConfig.h", line 113: error #41: expected an identifier

Also I noticed the vAssertCalled has 2 additional closing braces at the end in the zip file you sent?

Regards
Amit

0 Jin Seo over 10 years ago in reply to Amit Ashara

Expert 1130 points

Hi Amit,

Sorry for the an unconscious mistake, but it's not a origin of errors. Even if two braces get rid of it still gives me same errors.
I know where the error happens. My question is why this macro can not be recognized in TM4c1294.

what the freertos said "There is no CCS port for the M4 in the FreeRTOS download, so it is not
an official FreeRTOS file." "There may well be a CCS port in the coming months though".

By the way, how about the other link? someone in TI works on this?

Thanks,
Jin

0 Amit Ashara over 10 years ago in reply to Jin Seo

TI__Guru**** 244400 points

Hello Jin,

If there is no support for CCS port, it does not mean that it is not being used, as rest of the sensub_iot still works. For me to be able to get it working the first thing I need to resolve is the basic define error, that is causing my compilation to not even reach the actual error. You may however can ask on the CCS Forum (and check the forum database via search).

Regards
Amit

Arm-based microcontrollers

Arm-based microcontrollers forum

[E0001]unidentified symbol and [e0300] errors in portasm.asm using TM4C1294+FreeRTOS