Bad character sequence encountered: @https://www.eclipse.org/forums/index.php/mv/msg/162043/512293/#msg_512293
I'm developing software on an embedded controller.
I want to use special-function-register (SFR) of the microcontroller with a symbolic name, which addresses the SFR by its location:

The compiler and linker for that microcontroller handle that code perfectly.

So what have I to do, to either let CDT accept the code or ignoring the part '@ 0xFFF00' (or any number/address)?

Best regards
Dirk]]>Dirk Wibben2010-02-04T15:16:18-00:00Re: Bad character sequence encountered: @https://www.eclipse.org/forums/index.php/mv/msg/162043/515218/#msg_515218
]]>Dirk Wibben2010-02-18T08:49:16-00:00Re: Bad character sequence encountered: @https://www.eclipse.org/forums/index.php/mv/msg/162043/516968/#msg_516968
pointers to memory mapped hardware]]>Synopsis 2010-02-25T16:05:47-00:00Re: Bad character sequence encountered: @https://www.eclipse.org/forums/index.php/mv/msg/162043/517077/#msg_517077
]]>Dirk Wibben2010-02-26T06:26:57-00:00Re: Bad character sequence encountered: @https://www.eclipse.org/forums/index.php/mv/msg/162043/646726/#msg_646726
We've just started to use the eclipse IDE with CDT and we encountered the same warning message.

We are using the Cosmic compiler for Freescale micro controllers which uses or defines several special type qualifiers like @dir, @eeprom, @far, @near.

The type qualifier shall be used like this:
@dir volatile char sync;

For example, the @dir qualifier tells the liker, that the sync variable should be put into the direct memory page which can be addressed using 8 bit addresses. I know that sections can be defined with #pragma directives, so there is a workaround for this annoying issue. But, changing all SW modules in all of our actively developed projects would consume so much time and cost effort that this is not a selectable option for us.

I would like to ask for help on how can I extend CDT's parser to detect and parse correctly custom type qualifiers. It is enough for me if someone could tell which files to look for.

Thank you in advance for your kind help.]]>Tamas Kleiber2010-12-30T14:52:20-00:00Re: Bad character sequence encountered: @https://www.eclipse.org/forums/index.php/mv/msg/162043/690874/#msg_690874
We also use the combination of eclipse CDT and cosmic compiler and we are also looking for a solution or workaround for the "Bad character sequence encountered: @" warning issue of eclipse CDT.

@Tamas:
Did you already find a solution for this issue?

kind regards,
Martin]]>Martin2011-06-30T11:03:17-00:00Re: Bad character sequence encountered: @https://www.eclipse.org/forums/index.php/mv/msg/162043/690968/#msg_690968
I found a workaround Add the following definition to a header file which is included by all of your modules.

#ifdef COSMIC_AT
#define _at(n) @##n
#else
#define _at(n)
#endif

Among the compiler options, there is the -d<DEFINE> option. You can add the compiler option -dCOSMIC_AT="FIX_ME" to define the COSMIC_AT symbol at compilation time. This way, eclipse will not be aware of the symbol definition.

In the C files, you can define @tiny, @interrupt,@dir and other such parameters like this:

Regards
Dirk]]>Dirk Wibben2011-07-01T06:58:06-00:00Re: Bad character sequence encountered: @https://www.eclipse.org/forums/index.php/mv/msg/162043/693444/#msg_693444
https://bugs.eclipse.org/bugs/show_bug.cgi?id=237028
You still need to create and register a custom language variant for it, though. It's explained in the bug.

BTW, instead of
#ifdef COSMIC_AT

you could also use
#ifndef __CDT_PARSER__

This macro is only defined by the CDT parser.
HTH]]>Anton Leherbauer2011-07-06T13:40:22-00:00Re: Bad character sequence encountered: @https://www.eclipse.org/forums/index.php/mv/msg/162043/693460/#msg_693460