etrice-dev

[etrice-dev] major re-factoring

hrr@xxxxxxx (Henrik Rentz-Reichert) — Tue, 22 May 2012 09:02:43 GMT

Hi developers,

I've factored out the etricegen model from the org.eclipse.etrice.generator plugin.
I moved it to the newly created org.eclipse.etrice.core.genmodel plugin.

The same applies similarly to the relevant unit tests.

Please update!

-Henrik

[etrice-dev] eTrice 0.2.0M2 published

hrr@xxxxxxx (Henrik Rentz-Reichert) — Mon, 21 May 2012 17:25:28 GMT

Hi all,

I've just published our second milestone for the upcoming 0.2.0 release of eTrice.

The new features are
- docu generation in LaTex
- replicated actors
- state machine inheritance
- many minor improvements and fixes

The new features aren't thoroughly tested and documented yet.
This is work left for the 0.2.0 release.

-Henrik

Re: [etrice-dev] Actor Attribute and message data with the same name

hrr@xxxxxxx (Henrik Rentz-Reichert) — Thu, 17 May 2012 17:41:57 GMT

Hi Thomas,

you propose to use a keyword for the data. But this wouldn't solve the problem since also this would be in conflict with possible attributes with the same name.
Actually this is a quite common problem. In Java you would solve this by writing this.data for the attribute. Just data would bind to the local variable.
That's how I would like to treat it. And I think the Generic Action Language can solve this (even with the current parser we could do that).

Kind regards,
Henrik

Am 17.05.2012 16:47, schrieb Thomas.Jung@xxxxxxxxx:

Hi all,

I am working with C and I saw the following “problem”:

If an Actor has an Attribute like:

             Structure {

                    external Port ControlPort

                    SAP timer: PTimer

                    Attribute id: uint16

                    Attribute data:MyDataClass

And a receiving message has a parameter (which is defined in the protocol) like:

       ProtocolClass PButtonController {

             incoming {

                    Message setId(data: uint16)

             }

             outgoing {

                    Message pressed()

The C Code generator produces the following output:

/* Action Codes */

static void action_TRANS_tr0_FROM_waitForId_TO_released_BY_setIdControlPort(ButtonController* self, InterfaceItemBase ifitem, uint16 data) {

       self->id=self->data;

       PTimerConjPort_startTimeout(&self->constData->timer, 50);

}

In this case „data“ will be interpreted as the Attribute and you can never access the parameter which is sent to actor.

This is not a major problem but could be avoided by defining a keyword for the parameter which is sent via a message. In this case it would no longer be necessary (possible) to define your own name for a message data. You would access the received data always via the defined keyword (which is nothing more than a fixed name for the message data).

The problem with the current solution is that you may use the same Protocol class at several ActorClasses.

Can we solve this by using the action language???

If not, do you think we should change that??

Best Regards

Thomas

Thomas Jung, Senior Developer Embedded Systems
Tieto ES GmbH,
email thomas.jung@xxxxxxxxxxx, Telefon +49 89 78 722 352, Mobil +49 160 90 77 23 61,
Schertlinstraße 8, 81379 München

Tieto ES GmbH, Schertlinstraße 8, 81379 München
Geschäftsführung: Olaf Dicker, Willem Huisman
Sitz der Gesellschaft: München, Amtsgericht München HRB 188002

Wichtiger Hinweis: Diese E-Mail und etwaige Anlagen können Betriebs- oder Geschäftsgeheimnisse, dem Anwaltsgeheimnis unterliegende oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen der Status dieser E-Mail bekannt. Bitte benachrichtigen Sie uns in diesem Fall sofort durch Antwort-Mail und löschen Sie diese E-Mail nebst etwaigen Anlagen von Ihrem System. Ebenso dürfen Sie diese E-Mail oder seine Anlagen nicht kopieren oder an Dritte weitergeben. Vielen Dank.
_______________________________________________
etrice-dev mailing list
etrice-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/etrice-dev

-- 
______________________________

Dr. Henrik Rentz-Reichert

mailto:hrr@xxxxxxxxx
+49-7551-831365

Am Bacheck 7A
D-88662 Überlingen-Deisendorf

[etrice-dev] Actor Attribute and message data with the same name

Thomas.Jung@xxxxxxx (Thomas.Jung) — Thu, 17 May 2012 14:47:10 GMT

Hi all,

I am working with C and I saw the following “problem”:

If an Actor has an Attribute like:

Structure {

external Port ControlPort

SAP timer: PTimer

Attribute id: uint16

Attribute data:MyDataClass

And a receiving message has a parameter (which is defined in the protocol) like:

ProtocolClass PButtonController {

incoming {

Message setId(data: uint16)

}

outgoing {

Message pressed()

The C Code generator produces the following output:

/* Action Codes */

static void action_TRANS_tr0_FROM_waitForId_TO_released_BY_setIdControlPort(ButtonController* self, InterfaceItemBase ifitem, uint16 data) {

self->id=self->data;

PTimerConjPort_startTimeout(&self->constData->timer, 50);

}

In this case „data“ will be interpreted as the Attribute and you can never access the parameter which is sent to actor.

This is not a major problem but could be avoided by defining a keyword for the parameter which is sent via a message. In this case it would no longer be necessary (possible) to define your own name for a message data. You would access the received data always via the defined keyword (which is nothing more than a fixed name for the message data).

The problem with the current solution is that you may use the same Protocol class at several ActorClasses.

Can we solve this by using the action language???

If not, do you think we should change that??

Best Regards

Thomas

Thomas Jung, Senior Developer Embedded Systems
Tieto ES GmbH,
email thomas.jung@xxxxxxxxxxx, Telefon +49 89 78 722 352, Mobil +49 160 90 77 23 61,
Schertlinstraße 8, 81379 München

Tieto ES GmbH, Schertlinstraße 8, 81379 München
Geschäftsführung: Olaf Dicker, Willem Huisman
Sitz der Gesellschaft: München, Amtsgericht München HRB 188002

Wichtiger Hinweis: Diese E-Mail und etwaige Anlagen können Betriebs- oder Geschäftsgeheimnisse, dem Anwaltsgeheimnis unterliegende oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen der Status dieser E-Mail bekannt. Bitte benachrichtigen Sie uns in diesem Fall sofort durch Antwort-Mail und löschen Sie diese E-Mail nebst etwaigen Anlagen von Ihrem System. Ebenso dürfen Sie diese E-Mail oder seine Anlagen nicht kopieren oder an Dritte weitergeben. Vielen Dank.

Re: [etrice-dev] major eTrice changes pushed

hrr@xxxxxxx (Henrik Rentz-Reichert) — Wed, 16 May 2012 12:46:36 GMT

Hi Peter,

you can install MinGW using the installer
http://sourceforge.net/projects/mingw/files/Installer/mingw-get-inst/
(I have used mingw-get-inst-20110530).

You can find instructions about how to use the installer on
http://www.mingw.org/wiki/Getting_Started

Hope that helps,
Henrik

Am 16.05.2012 12:17, schrieb Karlitschek, Peter:

Hello Henrik,

I managed to update to your latest version. I only have a problem with the c tests. They don't build, since I haven't MinGW installed on my machine. (see console output below).

Where can I get a suitable MinGW distribution and are there any hints on installing it?

Thanks for your help

Peter

**** Build of configuration Debug for project org.eclipse.etrice.generator.c.tests ****

**** Internal Builder is used for build ****

**** WARNING: The "Debug" Configuration may not build ****

**** because it uses the "MinGW GCC" ****

**** tool-chain that is unsupported on this system. ****

From: etrice-dev-bounces@xxxxxxxxxxx [mailto:etrice-dev-bounces@xxxxxxxxxxx] On Behalf Of Henrik Rentz-Reichert
Sent: Dienstag, 15. Mai 2012 12:23
To: eTrice developer mailing list
Subject: [etrice-dev] major eTrice changes pushed

Hi developers,

I just have pushed a bunch of changes related to the inheritance of state machines.
The RefinedState formerly pointed to a BaseState. This was too narrow since RefinedStates should be able to target RefinedStates themselves (even if in practice these cases might be rare).
I also fixed and completed the State Diagram editor which is now capable of showing inherited items at the positions they have in the base class.
Position changes in the base class are reflected in the derived class (only if the derived editor is re-opened).
Volunteers for testing of the new features (or even better writing unit tests) are very welcome!

Please commit your changes locally before pulling and be prepared for conflicts.

In case of any questions related to those changes or problems

-Henrik

---
This communication contains confidential information. If you are not the intended recipient please return this email to the sender and delete it from your records.

Diese Nachricht enthaelt vertrauliche Informationen. Sollten Sie nicht der beabsichtigte Empfaenger dieser E-mail sein, senden Sie bitte diese an den Absender zurueck und loeschen Sie die E-mail aus Ihrem System.
_______________________________________________
etrice-dev mailing list
etrice-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/etrice-dev

-- 
______________________________

Dr. Henrik Rentz-Reichert

mailto:hrr@xxxxxxxxx
+49-7551-831365

Am Bacheck 7A
D-88662 Überlingen-Deisendorf

Re: [etrice-dev] major eTrice changes pushed

Peter.Karlitschek@xxxxxxx (Karlitschek, Peter) — Wed, 16 May 2012 10:18:11 GMT

Hello Henrik,

I managed to update to your latest version. I only have a problem with the c tests. They don't build, since I haven't MinGW installed on my machine. (see console output below).

Where can I get a suitable MinGW distribution and are there any hints on installing it?

Thanks for your help

Peter

**** Build of configuration Debug for project org.eclipse.etrice.generator.c.tests ****

**** Internal Builder is used for build ****

**** WARNING: The "Debug" Configuration may not build ****

**** because it uses the "MinGW GCC" ****

**** tool-chain that is unsupported on this system. ****

From: etrice-dev-bounces@xxxxxxxxxxx [mailto:etrice-dev-bounces@xxxxxxxxxxx] On Behalf Of Henrik Rentz-Reichert
Sent: Dienstag, 15. Mai 2012 12:23
To: eTrice developer mailing list
Subject: [etrice-dev] major eTrice changes pushed

Hi developers,

I just have pushed a bunch of changes related to the inheritance of state machines.
The RefinedState formerly pointed to a BaseState. This was too narrow since RefinedStates should be able to target RefinedStates themselves (even if in practice these cases might be rare).
I also fixed and completed the State Diagram editor which is now capable of showing inherited items at the positions they have in the base class.
Position changes in the base class are reflected in the derived class (only if the derived editor is re-opened).
Volunteers for testing of the new features (or even better writing unit tests) are very welcome!

Please commit your changes locally before pulling and be prepared for conflicts.

In case of any questions related to those changes or problems

-Henrik

---
This communication contains confidential information. If you are not the intended recipient please return this email to the sender and delete it from your records.

Diese Nachricht enthaelt vertrauliche Informationen. Sollten Sie nicht der beabsichtigte Empfaenger dieser E-mail sein, senden Sie bitte diese an den Absender zurueck und loeschen Sie die E-mail aus Ihrem System.

[etrice-dev] major eTrice changes pushed

hrr@xxxxxxx (Henrik Rentz-Reichert) — Tue, 15 May 2012 10:23:30 GMT

Hi developers,

I just have pushed a bunch of changes related to the inheritance of state machines.
The RefinedState formerly pointed to a BaseState. This was too narrow since RefinedStates should be able to target RefinedStates themselves (even if in practice these cases might be rare).
I also fixed and completed the State Diagram editor which is now capable of showing inherited items at the positions they have in the base class.
Position changes in the base class are reflected in the derived class (only if the derived editor is re-opened).
Volunteers for testing of the new features (or even better writing unit tests) are very welcome!

Please commit your changes locally before pulling and be prepared for conflicts.

In case of any questions related to those changes or problems

-Henrik

[etrice-dev] tracking down generator errors

hrr@xxxxxxx (Henrik Rentz-Reichert) — Mon, 30 Apr 2012 13:09:47 GMT

Hi,

if you encounter a generator problem showing up as

The details button doesn't give really much information

But if you open the Errors View you will see a corresponding entry with a complete stack trace

-Henrik

-- 
______________________________

Dr. Henrik Rentz-Reichert

mailto:hrr@xxxxxxxxx
+49-7551-831365

Am Bacheck 7A
D-88662 Überlingen-Deisendorf

Re: [etrice-dev] SPPs in ANSI C

hrr@xxxxxxx (Henrik Rentz-Reichert) — Mon, 30 Apr 2012 13:07:02 GMT

Hi Thomas,

yes, SPPs are always generated as replicated ports regardless whether they are connected several times, once or even not at all.

-Henrik

Am 30.04.2012 14:44, schrieb Thomas.Jung@xxxxxxxxx:

Hi Henrik,

I am writing a Timing Service for C and I have a short question.

Do you always generate the SPPs as replicated ports?

Background:

The Timing Service must save the index of the port that is requesting a timed message. Therefore I have to access the index of the receiving port and save it to a timer struct for later use.

If there is just one SAP it would not be necessary to generate the SPP as replicated port, but within the code of the timing service you do not have this information.

So it is necessary to have a pointer to a “etReplSubPort”, regardless if there is just one SAP which is using the Service.

Thanks

Thomas

Thomas Jung, Senior Developer Embedded Systems
Tieto ES GmbH,
email thomas.jung@xxxxxxxxxxx, Telefon +49 89 78 722 352, Mobil +49 160 90 77 23 61,
Schertlinstraße 8, 81379 München

Tieto ES GmbH, Schertlinstraße 8, 81379 München
Geschäftsführung: Olaf Dicker, Willem Huisman
Sitz der Gesellschaft: München, Amtsgericht München HRB 188002

Wichtiger Hinweis: Diese E-Mail und etwaige Anlagen können Betriebs- oder Geschäftsgeheimnisse, dem Anwaltsgeheimnis unterliegende oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen der Status dieser E-Mail bekannt. Bitte benachrichtigen Sie uns in diesem Fall sofort durch Antwort-Mail und löschen Sie diese E-Mail nebst etwaigen Anlagen von Ihrem System. Ebenso dürfen Sie diese E-Mail oder seine Anlagen nicht kopieren oder an Dritte weitergeben. Vielen Dank.
_______________________________________________
etrice-dev mailing list
etrice-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/etrice-dev

-- 
______________________________

Dr. Henrik Rentz-Reichert

mailto:hrr@xxxxxxxxx
+49-7551-831365

Am Bacheck 7A
D-88662 Überlingen-Deisendorf

[etrice-dev] SPPs in ANSI C

Thomas.Jung@xxxxxxx (Thomas.Jung) — Mon, 30 Apr 2012 12:44:49 GMT

Hi Henrik,

I am writing a Timing Service for C and I have a short question.

Do you always generate the SPPs as replicated ports?

Background:

The Timing Service must save the index of the port that is requesting a timed message. Therefore I have to access the index of the receiving port and save it to a timer struct for later use.

If there is just one SAP it would not be necessary to generate the SPP as replicated port, but within the code of the timing service you do not have this information.

So it is necessary to have a pointer to a “etReplSubPort”, regardless if there is just one SAP which is using the Service.

Thanks

Thomas