Fixed in space creator
Fixed in Space creator
Using the old editors, a model with two instances of the same device type (e.g. generic_serial.raw) in the same node generates an incorrect DeploymentView.aadl that contains duplicate definitions.
DEVICE generic_serial
EXTENDS ocarina_drivers::generic_serial
FEATURES
link : REFINED TO REQUIRES BUS ACCESS ocarina_buses::serial.generic {
Taste::coordinates => "631 1221";
};
PROPERTIES
Deployment::Help => "Write your ASN.1 configuration here";
Deployment::Config => "/home/assert/tool-inst/include/ocarina/runtime/polyorb-hi-c/src/drivers/configuration/serial.asn";
Deployment::Version => "0.1beta";
-- DUPLICATES!!
Deployment::Help => "Write your ASN.1 configuration here";
Deployment::Config => "/home/assert/tool-inst/include/ocarina/runtime/polyorb-hi-c/src/drivers/configuration/serial.asn";
Deployment::Version => "0.1beta";
-- end of duplicates
END generic_serial;
The build produces the following error:
DeploymentView.aadl:31:03: "Deployment::Help" conflicts with declaration at line 28
DeploymentView.aadl:32:03: "Deployment::Config" conflicts with declaration at line 29
DeploymentView.aadl:33:03: "Deployment::Version" conflicts with declaration at line 30
[ERROR] Deployment view is incorrect
Failed while executing:
"buildsupport" -x 100 -g --keep-case --gw --glue -i "/home/assert/tmp/test-dev1/InterfaceView.aadl" -c "DeploymentView.aadl" ocarina_components.aadl -d D_view_aadlv2.aadl --polyorb-hi-c --smp2 /home/assert/tool-inst/share/config_ellidiss/TASTE_IV_Properties.aadl /home/assert/tool-inst/share/config_ellidiss/TASTE_DV_Properties.aadl
I could not build the same model once saved with the new editors, but with a different error message.
__dv_1_3.aadl:24:41: ocarina_buses::serial.generic (entity reference) qualified reference name not found in 'with' statements of deploymentview::DV::Node1 (package specification)
__dv_1_3.aadl:38:41: ocarina_buses::serial.generic (entity reference) qualified reference name not found in 'with' statements of deploymentview::DV::Node1 (package specification)
[ERROR] Deployment view is incorrect
Failed while executing:
"buildsupport" -x 100 -g --keep-case --gw --glue -i "/home/assert/tmp/test-dev2/InterfaceView.aadl" -c "__dv_1_3.aadl" ocarina_components.aadl -d D_view_aadlv2.aadl --polyorb-hi-c --smp2 /home/assert/tool-inst/share/config_ellidiss/TASTE_IV_Properties.aadl /home/assert/tool-inst/share/config_ellidiss/TASTE_DV_Properties.aadl
Model with old editors test-dev1.tgz and with new editors test-dev2.tgz.
Hello,
We have an example with a "blackbox_device". Please find attached the Data, Interface and Deployment views. Example.zip
If we use TASTE commands, we can generate the executable. However, if we open the Deployment View with TASTE, it adds the following lineDeploymentView.aadl:
Actual_Processor_Binding => (reference (Processor_Board)) APPLIES TO Processor_Board_pbConnectionDock_driver;
Then, the executable generation fails. If we remove it, we can generate the executable.
Please, why is this line added?
Thanks in advance, Elena
A model with a serial bus fails to build with the new editors. The build script reports a missing file binary.c/DriversConfig/part_a/DeviceConfig-node1-generic-serial-raw.c. The DriversConfig directory does not exist. The model builds correctly with the old editors.
See the test with the old and new editors in attachment. serialtest_oldeditors.tgz serialtest_neweditors.tgz
When a tab different from the Interface View is selected, calling the menu entry "Tools/Generate code skeletons" produces a Tcl error:
couldn't change working directory to "/home/assert/ESROCOS/taste_tutorial/part3/DataView.aadl /home/assert/ESROCOS/taste_tutorial/part3": no such file or directory
couldn't change working directory to "/home/assert/ESROCOS/taste_tutorial/part3/DataView.aadl /home/assert/ESROCOS/taste_tutorial/part3": no such file or directory
while executing
"cd [file dirname $aadlFilePath]"
(procedure "generate_skeletons_internal" line 3)
invoked from within
"generate_skeletons_internal $aadlFilePath $aadlId"
(procedure "generate_skeletons::generate_skeletons" line 5)
invoked from within
"${pExternalTool}::$pExternalTool [getExternalToolParam $this] "
(procedure "HMIMenu::launchExternalTool" line 26)
invoked from within
"HMIMenu::launchExternalTool $this $pExternalTool $statusBarID """
(procedure "TasteHMI::launchExternalTool" line 6)
invoked from within
"TasteHMI::launchExternalTool .menu generate_skeletons"
invoked from within
".#menu.#menu#tools invoke active"
("uplevel" body line 1)
invoked from within
"uplevel #0 [list $w invoke active]"
(procedure "tk::MenuInvoke" line 50)
invoked from within
"tk::MenuInvoke .#menu.#menu#tools 1"
(command bound to event)
Hello,
We have exported and imported an interface view (created with taste-create-project) and it works, but the problem is that when you connect a provided interface with a required interface (with inherit from PI as false) , it is neccessary that the parameter name of both interfaces was the same. We think this complicates to work with exported models because you must rewrite code and rename parameters in model interfaces.
Besides if you try to rename the parameter, editor tool reports this message "You are not allowed to change the parameters of the RI unless you set the flag "Inherits from PI" to FALSE" although it is already false.
Thanks a lot.
Regards.
When editing the DataView.asn file in the embedded text editor, if a syntax error is introduced and the file is saved, the information bar at the bottom of the window shows "Error in dataview generation". However, no details about the error are visibly reported to the user.
I'm using version 2.0.11 of the editors.
This is solved in space creator - errors are reported directly while editing the ASN.1 model
Hello,
We are having problems when opening a Deployment View with TASTE GUI.
We created a Deployment View (DeploymentView1_ORIGINAL.aadl attached) and we want to open it with TASTE GUI. However, when the file is opended, TASTE GUI modifies it, for example:
When we define distributed systems, the problem gets worse. For example, in the DeploymentView2_ORIGINAL.aadl, the following information is removed (please, note that in that case we did not include the TASTE coordinates).
CONNECTIONS obj_PBConnectionDockprocessor_board_12 : BUS ACCESS PM_PB2_Bus -> processor_board.processor_board_PBConnectionDock_link; obj_PB2ConnectionDockprocessor_board_2_13 : BUS ACCESS PM_PB2_Bus -> processor_board_2.processor_board_2_PB2ConnectionDock_link; PROPERTIES Actual_Connection_Binding => (reference (PM_PB2_Bus)) applies to interfaceview.obj_processor_board_2_DataPublishing_Component2_impl_instdataT; Actual_Connection_Binding => (reference (PM_PB2_Bus)) applies to interfaceview.obj_processor_board_2_EventPublishing_Component2_impl_instc2_event; Actual_Connection_Binding => (reference (PM_PB2_Bus)) applies to interfaceview.obj_processor_board_DataPublishing_FDIR_impl_instFDIR_DataSet; Actual_Connection_Binding => (reference (PM_PB2_Bus)) applies to interfaceview.obj_processor_board_EventPublishing_FDIR_impl_instEvent_FDIR_Error; Actual_Connection_Binding => (reference (PM_PB2_Bus)) applies to interfaceview.obj_processor_board_2_DataPublishing_Component2_impl_inst_redundantdataT; Actual_Connection_Binding => (reference (PM_PB2_Bus)) applies to interfaceview.obj_processor_board_2_EventPublishing_Component2_impl_inst_redundantc2_event;
Is there any way to avoid that TASTE GUI modifies the input file? Can we avoid that it removes the connections and properties of distributed systems?
In both cases, we are able to generate the executable using TASTE tools.
DeploymentView1_ORIGINAL.aadlDeploymentView1_TASTE_GUI.aadlDeploymentView2_TASTE_GUI.aadlDeploymentView2_ORIGINAL.aadl
Thank you in advance, Elena
Hello,
I have udpated today to GUI v2.013.
I have created a consumer-producer example executing in two nodes and connected though a ethernet bus. I am able to bind the messages to the bus and save the Deployment View, but when I try to edit again the model this binding has desapeared.
If I try to build the model in any case I get this error:
producer_function_CV_Thread.aadl:14:02 Backends: fatal error : This OUT port is not connected to any destination
Failed while executing:
Find attached the model.
Regards.producer_consumer_ethernet.tar.gz
Javier
This was fixed with the new concurrency view generated by kazoo (system.aadl). closing
Jerome Legrand (ce2223a1) at 13 Dec 17:25
update the taste CV help file
Jerome Legrand (df67e72c) at 23 Nov 15:50
Merge branch 'master' of https://gitrepos.estec.esa.int/taste/ellid...
... and 1 more commit
Maxime Perrotin (a339cf81) at 11 Oct 12:37
Delete old versions of Ellidiss tools
Jerome Legrand (fbc252aa) at 01 Jul 16:03
TASTECV 1.3 : update AI to the last 1.8 version, small fixes
Jerome Legrand (13e26774) at 30 Jun 15:47
Jerome Legrand (3bff78df) at 22 Jun 15:00
forgot the updated timing analysis plugin