Problems in OIL-File with new IMPLEMENTATION section

[a.spiller]

Hello,

I'm completly new with the EE OS and have already configured the make files for a new toolchain.

When i try to write a new "IMPLEMENTATION" section in my conf.oil file for the new mcu and board this message appears:

Code: Select all

ERROR > Unable to load "C:\Users\Alexander\workspace\COMP_TEST\conf.oil" caused by :OilReader: exception during the parse.
Encountered " "IMPLEMENTATION" "IMPLEMENTATION "" at line 1, column 1.
Was expecting one of:
    <EOF> 
    "OIL_VERSION" ...
    "CPU" ...

I think it has to do with the "Aktive OIL Implementation" in the background. The parser sees two "IMPLEMENTATION" sections and sends an error.
Is it possible to deaktivate or overwrite it?
I'm working on windows with the downloaded zip-archive.

Thanks in advance.

Alexander

[paolo.gai]

Hi!

Did you try to follow the instructions inside this page below?

http://erika.tuxfamily.org/wiki/index.p ... formations

PJ

[a.spiller]

Hello,

thanks for the link.

I've done the steps in the manual and the new MCU_DATA is visible in the discription of the MCA_DATA parameter in the conf.oil file (picture is in the attachment).
But there is still an error message:

Code: Select all

Rebuild the project COMP_TEST. Config file:
	/COMP_TEST/conf.oil
ERROR > Unable to load "C:\Users\Alexander\workspace\COMP_TEST\conf.oil" caused by :TM4C129X is an illegal value for MCU_DATA. Expected one of SAMSUNG_KS32C50100, unibo_mparm, XMEGA, MEGA, LPCXPRESSO, STELLARIS, STM32, ALLWINNER, TI, PIC30, PIC32, LATTICE_PLATFORM, MSP430, PPCE200ZX, RENESAS, S12XS, MC9S12, TRICORE.
Check and fill folder COMP_TEST/Debug
	COMP_TEST/Debug/make_launcher.bat	OK (overwritten)

There are some Errors.

The modified plugin is in the .rar-file in the attachment too.
I hope somebody sees what i missed.

Thanks in advance.

Alexander

[paolo.gai]

The code generator is not recognizing the plugin (the editor does because the OIL IMPLEMENTATION section is in the file itself). So I guess the problem is related to the plugin which is not proerly initialized in the system.

Nicola is currently in vacastion, so I guess he will answer around first weeks of september.

Let us know in the meantime if you did any progress..

Ciao,

PJ

[a.spiller]

Hi,

i'll work so long with a workaround with EE_OPT.

We will implement the OSEK in our control systems laboratory and our energie efficient cars at University of Applied Science in Trier (Germany).
The controller is the follow-up model of the Stellaris from TI you allready support. It's the TIVA TM4C129x series.

I'll talk with my professor if i'm allowed to make the code available for the community.
I'm using this board to verify my code. http://www.ti.com/tool/dk-tm4c129x
If i have enough time I'll write a few things for the board too.

Sincere regards,

Alexander

[paolo.gai]

Nice Project!

Of course we would welcome any contribution you can make to the ERIKA Project... Thanks again!

PJ

[nicola.serreli]

Hi,

I was looking in your plug-in files. I put them in the dropins folder (of eclipse installation) and then I started eclipse.
The result was an error parsing the tm4c129x.oil file (the error was reported in the eclipse log file, placed in <workspace>/.metadata/.log)

First: add few commas to the enum declarations

Code: Select all

ENUM[
	USE_ETHERNET,
	USE_CAN,
	USE_DISPLAY
]OPTIONS[];

Then, check your mcu and board enum declarations: currently they are not vectors:

Code: Select all

] MCU_DATA;

Code: Select all

] BOARD_DATA;

To check if everything is fine, you can open "Active Oil Implementation" view.

Now ... few answers to your previous questions:
* The parser parse only one file at time (unless it contains the keyword include). If the file is well formed, then it may be used to compose the "Active Oil Implementation"
* Moreover, if a file contains bot the Implementation and the Cpu sections, then the cpu section is checked against only the implementation defined in the same file.
* The core parser accepts only oil with no errors that are compatible with all other oil implementations. The Editor parser tries to parse everything and to delimit all found errors. I think that you were able to see the TM4C129X as valid element because the error was not in the declaration of TM4C129X as element of MCU_DATA, but was in its content.

Best regards (and thanks for your contribution)
Nicola

[a.spiller]

Hi,

sorry for the delayed reply.

I think now I understand the file generation steps and my OIL implementation is working and growing.
The TI compiler did make a few problems but now basic programms are running.

Thank you all very much for the answers.

Best regards

Alexander