ObjectGeode

ObjectGeode [11] is completely supported. To begin with, ObjectGeode offers the easiest possible mapping of data types: SDL [13] directly supports ASN.1 data types, so asn2dataModel is almost a no-op for this modeling tool. aadl2glueC on the other hand, has the normal workload for SDL (just as it did for SCADE, Rhapsody, Ada, etc). It generates a set of MACROs that are used by ObjectGeode-generated code, which allow for

• Declarations and definitions of transfer buffers for each ASN.1 type: These are used by the ObjectGeode code (hpostdef.h) to statically reserve the necessary space for the exchanged messages (at compile time).
• ASN.1 Decoders/mappers and readers/ASN.1 encoders: These are used by the message-sending / signal-receiving parts of the ObjectGeode code (vm_if.c, hpostdef.h) to perform the ASN.1 marshalling as well as the data mapping between the data structures of ObjectGeode and those generated by the ASN.1 compiler.

Using these ``glue'' layers, the ObjectGeode generated code is effortlessly communicating with the other APLCs over the VM.

More information about the ObjectGeode mappers are in Chapter 11.