Timing-Analysis within AUTOSAR Classic systems

This webi­nar shows how the dynam­ic behav­ior of the soft­ware archi­tec­ture can be mea­sured at run-time with no or only min­i­mum over­head and eval­u­at­ed off the tar­get ECU.

Watch live record­ing here.

Effi­cient Run-Time Analy­sis of AUTOSAR Clas­sic Projects with OS and RTE Trac­ing

This webi­nar shows how the dynam­ic behav­ior of the soft­ware archi­tec­ture can be mea­sured at run-time with no or only min­i­mum over­head and eval­u­at­ed off the tar­get ECU.

Many multi-core fea­tures and tech­niques to uti­lize ECUs result in inter­ven­ing into the sched­ul­ing behav­ior. With ongo­ing ECU project develop­ment, mul­ti­ple soft­ware ven­dors as well as a con­sid­er­able amount of con­fig­u­ra­tion para­me­ters to play with, the effects of those after inte­gra­tion at run-time become hard­ly fore­see­able.

An opti­mal solu­tion is to trace the OS and RTE behav­ior with the trace debug­ger from iSYS­TEM and eval­u­ate the trace mea­sure­ment after­wards offline with TA Tool Suite from Vec­tor.

Agen­da

• Record­ing the sys­tem behav­ior with­out or with only min­i­mal instru­men­ta­tion code via hard­ware trac­ing
• Run-time analy­sis of the soft­ware archi­tec­ture
• Cal­cu­la­tion of resource con­sump­tion para­me­ters, such as CPU load, response time and other met­rics
• Regres­sion test­ing of tim­ing require­ments through com­plete automa­tion
• Nec­es­sary steps to inte­grate this solu­tion