|Anonymous | Login | Signup for a new account||2019-12-10 01:28 UTC|
|Main | My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000458||Taste||[All Projects] TASTE-IV/DV||public||2015-09-18 09:52||2019-07-02 14:42|
|Priority||normal||Severity||major||Reproducibility||have not tried|
Prevent mismatch of drivers vs processor
We need a mechanism to prevent the user from using a driver that is not compatible with the HW target platform in the deployment view.
For example on Leon processors, it must not be possible to select he po_hi_c.generic_socket driver. The one that works is leon.ethernet_raw.
|Tags||No tags attached.|
|Attached Files|| Boards.PNG [^] (61,980 bytes) 2018-12-19 16:42
For this one, I think the best option would be to use the standard AADLv2 property
The Allowed_Processor_Binding_Class property specifies a set of virtual processor, processor and system classifiers. These component classifiers constrain the set of candidate virtual processors and processors for binding to the subset that satisfies the component classifier.
From that, one could say for each device the list of processor it can be bound to. A device bound to a processor is the way we associate (in Ocarina, thus at CV level) a device driver (in the device) to a processor (hence a node in the system)
Then, a check using REAL or LMP and voila !
Pierre, what do you think ?
Yes, if these properties can specified within the HW library, we can do this check a priori, while building the DV model.
Where can i find the compatibility rules?
It is not yet defined. A better option, discussed with Pierre is the following
for the moment, the code generation uses the property Execution_Platform, attached to a processor, to configure the OS.
An easy to implement solution is to attach the same property to a device driver.
This requires an update on the component library, let me know first if this could work for you.
Finally, it was decided to (re-)introduce the concept of "board" in the DV editor, as they are now supported by the Ocarina library:
Version 2.2 of the TASTE editors (outcome of COO7) now supports:
Important upwards compatibility notes:
|2015-09-18 09:52||maxime||New Issue|
new => assigned
|2015-09-18 09:52||maxime||Assigned To||
|2015-09-18 16:00||hugues||Note Added: 0002441|
|2015-09-18 16:42||ellidiss||Note Added: 0002442|
|2016-10-17 13:55||ellidiss||Note Added: 0002725|
|2016-10-19 07:45||hugues||Note Added: 0002728|
|2018-12-19 16:41||ellidiss||Note Added: 0003554|
|2018-12-19 16:42||ellidiss||File Added: Boards.PNG|
assigned => resolved
open => fixed
|Copyright © 2000 - 2011 MantisBT Group|