RAMSES-2 issueshttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues2020-12-28T18:54:25Zhttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/10Add Ev3dev features and add it to maven build and update site2020-12-28T18:54:25ZEtienne BordeAdd Ev3dev features and add it to maven build and update siteEtienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/13Initialize threads entrypoints (activation/deactivation/initialization)2020-12-29T15:23:16ZEtienne BordeInitialize threads entrypoints (activation/deactivation/initialization)Etienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/34shared-resources test2021-01-22T14:31:42ZOriane Salaméshared-resources testshared-resources test should be documented (segfault on freertos due to a mutex non-initialization)shared-resources test should be documented (segfault on freertos due to a mutex non-initialization)Etienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/19Change signature of recovery entrypoint to use a runtime_addr_t, which is set...2020-12-29T15:23:03ZEtienne BordeChange signature of recovery entrypoint to use a runtime_addr_t, which is set to the calling thread context (error_code can be removed: accessible from config)Etienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/11Add FreeRTOS features and add it to maven build and update site2020-12-28T18:54:22ZEtienne BordeAdd FreeRTOS features and add it to maven build and update siteEtienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/7Initialize error port when defined in AADL models2020-12-25T17:52:50ZEtienne BordeInitialize error port when defined in AADL modelsEtienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/1Launch from instance models2020-09-03T14:55:26ZEtienne BordeLaunch from instance modelsRAMSES launch from an instance model does nothing...RAMSES launch from an instance model does nothing...Dominique BlouinDominique Blouinhttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/4BA subclauses resolution fails when chaining transformations2021-02-11T21:10:46ZEtienne BordeBA subclauses resolution fails when chaining transformationsDominique BlouinDominique Blouinhttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/24Delete task semaphores when stopping the task2021-02-11T21:10:54ZEtienne BordeDelete task semaphores when stopping the taskOriane SalaméOriane Salaméhttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/28Only add -lpthread -lrt options in generated makefile if target is posix-like...2021-01-26T13:54:53ZEtienne BordeOnly add -lpthread -lrt options in generated makefile if target is posix-like (linux, ev3dev, freertos with posix port)Etienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/29Add EV3DEV to integration all workflow2021-01-11T18:19:40ZEtienne BordeAdd EV3DEV to integration all workflowEtienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/27Makefile generation2021-01-05T21:06:34ZOriane SalaméMakefile generationTargets for compiling source files appear before "all" target and $(OBJECT) definition for FreeRTOS and possibly for Linux.Targets for compiling source files appear before "all" target and $(OBJECT) definition for FreeRTOS and possibly for Linux.Etienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/22Import and adapt the mine_pump example (porposed by the standardization commi...2020-12-30T16:20:05ZEtienne BordeImport and adapt the mine_pump example (porposed by the standardization committee)Etienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/9Impossible to call Raise_Error from subprogram with AADL code generation conv...2020-12-30T14:05:01ZEtienne BordeImpossible to call Raise_Error from subprogram with AADL code generation conventionEtienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/5Improve support for mode changes in generated applications2020-12-30T14:05:39ZEtienne BordeImprove support for mode changes in generated applicationsEtienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/8Initialize recovery_entrypoint2020-12-29T13:48:24ZEtienne BordeInitialize recovery_entrypointEtienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/18Change signature of runtime functions to replace void * with runtime_addr_t2020-12-29T13:48:51ZEtienne BordeChange signature of runtime functions to replace void * with runtime_addr_tEtienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/2Instance model is not updated when relaunching RAMSES from outline view2020-12-24T11:01:33ZEtienne BordeInstance model is not updated when relaunching RAMSES from outline viewTo reproduce the issue, launch RAMSES from the outline view. Modify the input model (e.g. add a property to a component). Relaunch RAMSES from the outline view. The instance model should contain the modification (e.g. added property)... ...To reproduce the issue, launch RAMSES from the outline view. Modify the input model (e.g. add a property to a component). Relaunch RAMSES from the outline view. The instance model should contain the modification (e.g. added property)... But it does not.
It seems the input resource is cached into memory and is not updated when re-launching RAMSES.Dominique BlouinDominique Blouinhttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/3Sometimes, launching RAMSES with nxtOSEK as a target will fail2020-11-16T06:58:31ZCloé LacombeSometimes, launching RAMSES with nxtOSEK as a target will failLaunching RAMSES with nxtOSEK as the target platform several times in a row will start to fail at some point (the number of launches before RAMSES fail seems random). A pop up error will appear with a stack trace on eclipse console and R...Launching RAMSES with nxtOSEK as the target platform several times in a row will start to fail at some point (the number of launches before RAMSES fail seems random). A pop up error will appear with a stack trace on eclipse console and RAMSES will not generate anything. The problem will be persistent unless the project is deleted and re-created (from the file system).https://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/17Add validation rule to make sure classifiers referenced as entrypoint (init, ...2021-01-11T17:11:43ZEtienne BordeAdd validation rule to make sure classifiers referenced as entrypoint (init, activation, etc.) have no featureEtienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/25Extend possible Portable_Architecture values for FreeRTOS configuration2021-01-26T12:39:27ZEtienne BordeExtend possible Portable_Architecture values for FreeRTOS configurationOriane SalaméOriane Salaméhttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/23Add examples for FreeRTOS2021-01-06T11:10:08ZEtienne BordeAdd examples for FreeRTOSEtienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/16Add validation rule to make sure the FreeRTOS port is defined in input model2021-01-06T10:21:23ZEtienne BordeAdd validation rule to make sure the FreeRTOS port is defined in input modelEtienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/36Close sockets properly when terminating processes2021-02-11T21:10:26ZEtienne BordeClose sockets properly when terminating processeshttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/6Add an example with modes2020-12-30T14:45:46ZEtienne BordeAdd an example with modesEtienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/14Missing thread name in initialization of thread config2020-12-29T13:11:28ZEtienne BordeMissing thread name in initialization of thread configEtienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/15Add access to generated context from generic thread_config_t2020-12-29T16:05:51ZEtienne BordeAdd access to generated context from generic thread_config_tEtienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/39Missing Base_Types in with clauses2021-11-10T14:01:09ZEtienne BordeMissing Base_Types in with clausesEtienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/41Duplicate pok_kernel_error in generated code2021-11-11T13:59:56ZEtienne BordeDuplicate pok_kernel_error in generated codeEtienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/42Requirement to have process bound to a memory seems an overshoot2021-11-11T14:00:33ZEtienne BordeRequirement to have process bound to a memory seems an overshootEtienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/32Locks with ICPP policy is not implemented2021-01-19T13:22:54ZEtienne BordeLocks with ICPP policy is not implementedEtienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/20Add an example with error management2020-12-30T14:45:19ZEtienne BordeAdd an example with error managementEtienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/21add a user_defined_config field to thread_config_t2020-12-29T15:23:46ZEtienne Bordeadd a user_defined_config field to thread_config_thttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/12Add integration tests for FreeRTOS target2021-03-04T08:27:38ZEtienne BordeAdd integration tests for FreeRTOS targetOriane SalaméOriane Salaméhttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/26When is dispatch_time set?2021-01-05T10:21:52ZEtienne BordeWhen is dispatch_time set?https://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/30Add integration test with Dispatch_Offset2021-01-12T12:47:23ZEtienne BordeAdd integration test with Dispatch_OffsetEtienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/31Remove references to start_time when computing dispatch_time (absolute time i...2021-01-19T20:26:54ZEtienne BordeRemove references to start_time when computing dispatch_time (absolute time including start_time remains consistent for dates comparison)Etienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/33timed-eventport test's execution traces2021-01-19T17:38:57ZOriane Salamétimed-eventport test's execution tracesTest execution traces on the targets linux, freertos and pok vary and should be checked.Test execution traces on the targets linux, freertos and pok vary and should be checked.Oriane SalaméOriane Salaméhttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/35modal-port-connection test's trace2021-01-19T17:43:09ZOriane Salamémodal-port-connection test's tracethe expected results of the execution are not clear and need to be verifiedthe expected results of the execution are not clear and need to be verifiedOriane SalaméOriane Salaméhttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/37Handling ACTIVE_THREAD_HANDLING_PROTOCOL property2021-02-11T08:31:42ZOriane SalaméHandling ACTIVE_THREAD_HANDLING_PROTOCOL propertyProperty ACTIVE_THREAD_HANDLING_PROTOCOL must be taken into account in the model.Property ACTIVE_THREAD_HANDLING_PROTOCOL must be taken into account in the model.Etienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/38Dispatch_Trigger property is never used2021-04-09T13:46:04ZEtienne BordeDispatch_Trigger property is never usedWright now, all ports are considered as provoking a dispatch. If a dispatch_trigger property is used, only a subset of ports may provoke a dispatch.Wright now, all ports are considered as provoking a dispatch. If a dispatch_trigger property is used, only a subset of ports may provoke a dispatch.https://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/40Filter issue for paramater connections in thread2021-11-10T14:02:37ZEtienne BordeFilter issue for paramater connections in threadEtienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/43Message dialog for successful RAMSES Run is not shown2023-06-07T16:31:06ZRakshit MittalMessage dialog for successful RAMSES Run is not shownAt the moment, if a RAMSES run/analysis is successful, the user is not intimated.
The user is only intimated if there is a problem with the analysis.
Some users were confused if the analysis was successful or not, because there was no me...At the moment, if a RAMSES run/analysis is successful, the user is not intimated.
The user is only intimated if there is a problem with the analysis.
Some users were confused if the analysis was successful or not, because there was no message.