Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000809Taste[All Projects] Buildsupportpublic2018-10-09 08:092022-12-05 20:05
Assigned Tomaxime 
PlatformTASTE VMOSOS Version

Semantic checks (CoRA activity/dmt branch)


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:
1) Ensure the IV property (aadlstring) holding the FPGA configurations contains only configurations enumerated in the dedicated Enumerated type in the DV ‘FpgaConfiguration’

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
require to compare fields in the Function Block itself, for which there are already examples there (do you agree?), 1 and 2 seem however more tricky, since the check has to get the possible values from the DV Enumerated type.

Do you see a simple way to get this info from the DV in semantic_checks.c?
Or should we think of a way to implement these checks also in the dmt module? (e.g. /dmt/ is getting the values of an Enumerated from the DV)

TagsNo tags attached.
Attached Files

- Relationships

-  Notes
tiago_gmv (reporter)
2018-10-09 08:11

DV here meaning Data View (not Deployment)

maxime (administrator)
2022-12-05 20:05

Since this ticket was on buildsupport I closed it. I don't know the status wrt kazoo and the latest developments in CoRA. Please re-open/create a new ticket if this has not already been addressed

- Issue History
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
2022-12-05 20:05 maxime Note Added: 0003819
2022-12-05 20:05 maxime Status

assigned => closed

2022-12-05 20:05 maxime Resolution

open => fixed

Copyright © 2000 - 2011 MantisBT Group
Powered by Mantis Bugtracker