User story #1754: Ranges not working for signals from custom types (introspection) - MARTe2-core - F4E-CODAC - redmine

User story #1754

Ranges not working for signals from custom types (introspection)

Added by Giuseppe Ferro 10 months ago. Updated 7 months ago.

Status:

Closed

Priority:

Normal

Assignee:

Target version:

Start date:

05.06.2024

Due date:

% Done:

Estimated time:

Git branch (link):

Git merge to develop (link):

SVN commit (link/?p=rev):

Description

Even if basic type members of custom types, the ByteSize computed by the RealTimeApplicationBuilder does not take in account the Ranges

RealTimeApplicationConfigurationBuilderTest.cpp:2561

//allocate memory without considering ranges because it is considered as a struct
signalNumberOfBytes = (numberOfElements * signalTypeDescriptor.numberOfBits) / 8u;

It is clear also from the tests:
Normal Signal:
" \"0\" = {"
" QualifiedName = \"ProcessedSignals.Signal1\""
" Type = \"uint32\""
" NumberOfDimensions = \"2\""
" NumberOfElements = \"4\""
" Alias = \"SineWave\""
" Ranges = { { \"0\" \"0\" } { \"3\" \"3\" } } "
" DataSource = \"DDB1\""
" Default = \"{1 2 3 4}\""
" FullType = \"uint32\""
" DataSourceNumber = \"0\""
" ByteSize = 8"
" ByteOffset = { { 0 4 } { 12 4 } } "
" }"

Custom signal:
" \"3\" = {"
" QualifiedName = \"ADCs.Signal3.c2\""
" Type = \"float32\""
" NumberOfDimensions = 1"
" NumberOfElements = 3"
" FullType = \"TestStructC.float32\""
" MemberSize = 12"
" DataSource = \"Drv1\""
" Alias = \"ADCs1234.c2\""
" Ranges = { { \"0\" \"0\" } } "
" Samples = \"2\""
" DataSourceNumber = \"1\""
" ByteSize = 12"
" ByteOffset = { { 0 4 } } "
" }"