Anonymous | Login | Signup for a new account | 2021-01-21 09:01 UTC | ![]() |
Main | My View | View Issues | Change Log | Roadmap |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||
0000809 | Taste | [All Projects] Buildsupport | public | 2018-10-09 08:09 | 2018-10-09 08:11 | ||||||
Reporter | tiago_gmv | ||||||||||
Assigned To | maxime | ||||||||||
Priority | normal | Severity | minor | Reproducibility | N/A | ||||||
Status | assigned | Resolution | open | ||||||||
Platform | TASTE VM | OS | OS Version | ||||||||
Summary | 0000809: Semantic checks (CoRA activity/dmt branch) | ||||||||||
Description | There are a few semantic checks that might be important to perform, others only nice to have. Some checks that came to mind, in my view from more to less important, are: 2) Each configuration enumerated in the dedicated DV Enumerated type is assigned to at least one Function Block, this to avoid calling on a reconfiguration which as no functionality associated 3) Check that Function blocks with some FPGA configurations defined are implemented only in the HW supported languages: VHDL, C, Simulink 4) Check size of IV property (aadlstring) holding the FPGA configurations, since for parsing it we are allocating an array with a certain size (at dispatcher level) While the 3 and 4 seem possible to implement with not much effort in ./buildsupport/c/semantic_checks.c, since they only Do you see a simple way to get this info from the DV in semantic_checks.c? | ||||||||||
Tags | No tags attached. | ||||||||||
Attached Files | |||||||||||
![]() |
|||
Date Modified | Username | Field | Change |
2018-10-09 08:09 | tiago_gmv | New Issue | |
2018-10-09 08:09 | tiago_gmv | Status |
new => assigned |
2018-10-09 08:09 | tiago_gmv | Assigned To |
=> maxime |
2018-10-09 08:11 | tiago_gmv | Note Added: 0003479 |
Copyright © 2000 - 2011 MantisBT Group |