topic "Syntax error" message in compiler in LPCXpresso IDE

"Syntax error" message in compiler

lpcware — Wed, 15 Jun 2016 21:45:55 GMT

Content originally posted in LPCWare by JohnR on Mon Aug 05 14:32:40 MST 2013
Hi All,

I am using Red Suite 5 (NXP Edition) in an dual M4/M0 LPC4350 project.

In the following code the array, helvr10_bits, is marked "Syntax error" in the editor when the array is placed in RamAHB32 using the __DATA macro.

The phrase, cr_section_macros.h, is actually surrounded by <> but the editor here seems to remove them and the text inside them?


#include cr_section_macros.h

#include "lpc_types.h"
#include "lpc_helvr10.h"

/* Font character bitmap data. */
//static UNS_16 helvr10_bits [] =
__DATA(RamAHB32) static UNS_16 helvr10_bits[] =
{
......................
};

Similarly, in another file, the same error is marked

//uint32_t result[2][MAX_COUNT];
__DATA(RamAHB32) uint32_t result[2][MAX_COUNT];

The program compiles and runs fine, so I am not sure why the message shows up?

Does anyone know why this is happening?

Thanks in advance,

JohnR

Re: "Syntax error" message in compiler

lpcware — Wed, 15 Jun 2016 21:45:55 GMT

Content originally posted in LPCWare by lpcxpresso-support on Tue Aug 06 00:38:42 MST 2013
You probably just need to rebuild the index (right click on the project in the project explorer view).

Note that you really should be using the __BSS macro rather than the __DATA macro on the result array definition.

Regards,
LPCXpresso Support

Re: "Syntax error" message in compiler

lpcware — Wed, 15 Jun 2016 21:45:56 GMT

Content originally posted in LPCWare by JohnR on Tue Aug 06 04:09:15 MST 2013
Hi Support

Thanks - that fixed it.

JohnR

Re: "Syntax error" message in compiler

lpcware — Wed, 15 Jun 2016 21:45:56 GMT

Content originally posted in LPCWare by JohnR on Tue Aug 06 04:18:40 MST 2013
Hi

I spoke too soon.

The tag did get removed after recompiling but when I closed the compiler and restarted it, the tag reappeared.

It's not a big deal since the code compiles and runs but is irritating.

I changed the macro as suggested.

Thanks again.

JohnR