Project

General

Profile

0.2

Finish L0 portability and linting.

100%

41 issues   (41 closed — 0 open)

Time tracking
Estimated time 114.00 hours
Spent time 0.00 hour
Issues by
Test

1/1
Meeting

1/1
User story

39/39
Related issues
Test #165: MARTe2 QA-audit (v0.2)
Meeting #175: MARTe 2 Sprint report (v0.2)
User story #103: MARTe-EX-D-1.2.1: The framework shall offer multi-threading support to application developers.
User story #104: MARTe-EX-F-1.2.2: A framework developer shall be capable of specifying the affinity of any thread.
User story #105: MARTe-EX-F-1.2.3: A framework developer shall be capable of specifying the size of the stack associated to any thread.
User story #106: MARTe-EX-F-1.2.5: A framework developer shall be capable of associating a name to a thread instantiated by the framework.
User story #107: MARTe-EX-F-1.2.9: A framework developer shall be capable of querying the affinity of any thread that was instantiated by the framework.
User story #108: MARTe-EX-F-1.2.7: A framework developer shall be capable of querying the state of any thread that was instantiated by the framework.
User story #109: MARTe-EX-F-1.2.4: A framework developer shall be capable of changing, at any time, the priority of any thread.
User story #110: MARTe-EX-F-1.2.6: A framework developer shall be capable of terminating (i.e. killing) a thread.
User story #111: MARTe-EX-F-1.2.8: A framework developer shall be capable of querying the priority of any thread that was instantiated by the framework.
User story #112: MARTe-EX-F-1.2.10: A framework developer shall be capable of querying the identity of the caller thread.
User story #113: MARTe-EX-F-1.2.11: A framework developer shall be capable of putting the executing thread to sleep for a specified amount of time.
User story #114: MARTe-EX-D-1.3.1: The framework shall allow developers to protect shared resources using mutex semaphores.
User story #115: MARTe-EX-F-1.3.4: Framework developers shall be capable of waiting on any type of semaphore with a infinite timeout (i.e. "forever").
User story #116: MARTe-EX-F-1.3.6: When awaiting on any type of semaphore the framework developer shall know if the lock was released due to a timeout or due to any type of error.
User story #117: MARTe-EX-F-1.3.5: Framework developers shall be capable of waiting on any type of semaphore with a finite timeout.
User story #119: MARTe-EX-D-1.3.3: The framework shall allow developers to protect shared resources using memory polling semaphores.
User story #122: MARTe-EX-F-1.1.7: A framework developer shall be capble of querying the number of CPU cores available in the system where MARTe is running.
User story #123: MARTe-EX-F-1.1.8: A framework developer shall be capble of querying the family and model of the CPU where MARTe is running.
User story #127: MARTe-EX-F-1.1.13: The framework shall provide portable methods to access the high resolution timer value of any supported CPU.
User story #133: MARTe-EX-D-1.4.1: The framework shall offer portable memory management functions (malloc, realloc, free, compare and move) to developers.
User story #141: MARTe-NE-F-1.1.14: The framework shall provide a method to convert the High Resolution Timer in elapsed time from the epoch
User story #142: MARTe-EX-F-1.1.15: The framework shall offer portable support for basic console operations.
User story #144: Lint: Atomic
User story #145: Lint: BasicConsole
User story #146: Lint: Endianity
User story #147: Lint: EventSem
User story #148: Lint: FastMath
User story #149: Lint: FastPollingMutexSem
User story #150: Lint: HighResolutionTimer
User story #151: Lint: LoadableLibrary
User story #152: Lint: Memory
User story #153: Lint: MemoryStatisticsDatabase
User story #154: Lint: MutexSem
User story #155: Lint: ProcessorType
User story #156: Lint: Processor
User story #157: Lint: Sleep
User story #158: Lint: StringHelper
User story #159: Lint: StringPortable
User story #163: Lint: TimeoutType