Project

General

Profile

Bug #4037

Memory Utilization Pattern erroneously uses task RAM instead of Flash requirements

Added by Simon Barner 3 months ago. Updated 20 days ago.

Status:
New
Priority:
Normal
Assignee:
Category:
-
Start date:
07/01/2020
Due date:
% Done:

0%

Estimated time:

Description

The attached examples are based on a platform architecture with two ECUs with 1000 bytes flash memory each

  • ACC_task_flash_reqs.af3_23 * Defines one task with a flash memory requirement of 2000 bytes. * The DSE defines a memory utilization constraints (up to 100 % usage for both ECUs), hence the DSE should be infeasible. However, erroneously, a solution is found.
  • ACC_task_ram_reqs * As above, but with a RAM memory requirement of 2000 bytes * Now the memory utilization constraint works as one would expect in the configuration above * Note: the constraint pattern editor' description refers to flash memory, and also the flash size of the ECUSs is correctly displayed

History

#1 Updated by Simon Barner 3 months ago

  • Assignee changed from Simon Barner to Johannes Eder

For re-assignment

#2 Updated by Alexander Diewald 3 months ago

My two cents: We should support both. Checkbox or by providing two distinct patterns.

#3 Updated by Simon Barner 3 months ago

Fully agreed. However, I wanted to separate the bugfix from the feature (see #4038).

#4 Updated by Alexander Diewald 20 days ago

FYI, the name "Memory Utilization Pattern" is confusing: When fixing the issue, use the names "Flash Memory Utilization Pattern" and "RAM Utilization Pattern"

Also available in: Atom PDF