This site collects the different distributed versions of the CONTREX Eclipse Plug-in (CONTREP in short). It also provides examples in order to get familiarized with the tool.
The plug-in is distributed as a local update site packaged into a zip file. Although the zip file is encrypted, CONTREP can be obtained and used for research and non-commercial purposes under a NDA. Please, contact us in order to get access to it.
|Plug-in Link||Date||Short Description|
|contrep_enc_2016_10_10||10-10-2016||Fix on makefiles for native target (when no project path provided in model). Configuration compacted and enabling power traces.|
|contrep_enc_2016_09_22||22-09-2016||Enables external path constraints, not owned by one component and applicable to several ones|
|contrep_enc_2016_09_14||14-09-2016||Simplifies use of m/eSSYN configuration on wrapper configuration. Fix on Makefile generation (redefinition of interface function names).|
|contrep_enc_2016_09_09||09-09-2016||Fixes on XML generation associated to PpUnit and related to use of Verification View|
|contrep_enc_2016_08_29||29-08-2016||First release available online|
Notes on the installation:
If you experience a problem of the type “need PK compat. v5.1 (can do v4.6)” when extracting the file, you can try installing p7zip-full and use the command “7z x contrep_enc_XX_XX_XX.zip“. The program will ask you to input the password and, if it is correct, it will properly extract a folder called ucCommon.update.site.
You only need to point to this folder when you add a local update site for the update of your CONTREP setup.
Complete instance of Eclipse+Acceleo+CONTREP
Links are protected by a keyword. Please contact with Eugenio Villar to request it.
|Eclipse Contrep 64b||02-03-2017||complete instance of Eclipse+Acceleo+CONTREP (Linux 64b)|
|Eclipse Contrep 32b||02-03-2017||complete instance of Eclipse+Acceleo+CONTREP (Linux 32b)|
|Essyn DCGen||02-03-2017||Essyn DCGen|
|VIPPE v2.3||18-10-2016||VIPPE 2.3|
|prueba_1ms_1rtos||Two components each with an internal periodical function. One component with an initialization function. One component implements and provides a service required by the other component. Both , components mapped to one memory space, in turn mapped to the same operative system.|
|prueba_2ms_1rtos||As prueba_1ms_rtos example, but the two components are mapped to different memory spaces. Both memory spaces are mapped to the same operative system.|
|prueba_2ms_2rtos_shared_reg||As prueba_2ms_1rtos, but the two memory spaces are mapped to different RTOS, in turn running on different processors, buses, and thus memory maps. As the communication traverses two memory spaces, no channel based communication is used in this case, but it is based on a shared memory directly mapped for both sides. (Generation and run of simulation model supported and relying on the modeling of directly mapped physical memory of VIPPE. Generation of native model requires code adaptation).|
|prueba_2ms_2rtos_ppunit||As prueba_2ms_2rtos_shared_reg, but the shared memory access traversing 2 RTOS and 2 buses (memory maps) is encapsulated and made explicit in the UML/MARTE model through 2 PpUnits (one for each memory space). (Generation and run of simulation model supported and relying on the modeling of directly mapped physical memory of VIPPE. Generation of native model requires code adaptation).|
|prueba_2ms_2rtos_socket_com||As prueba_2ms_1rtos, but the two memory spaces are mapped to different RTOS, in turn running on different processors., buses, and this memory maps . In this case, the channel based communication is preserved, but by specifying a socket based communication. (Code generation is supported. VIPPE support of socket on-goin at the time this example was uploaded).|