AUTOSAR OS and RTE Profiling of Vector MICROSAR Applications with Instrumentation

In this webi­nar we will take a detailed look into OS and RTE pro­fil­ing of an MICROSAR OS based appli­ca­tion. Specif­i­cal­ly, we will uti­lize the Vec­tor OS tim­ing hooks to record task states and ISRs, as well as the VBF trace hooks to record Runnable events.

The use-case is rel­e­vant for micro­con­trollers that have lim­it­ed trace capa­bil­i­ties, such as the RH850 fam­i­ly with Soft­ware Trace, and micro­con­trollers that have a lim­it­ed trace band­width or num­ber of data trace com­para­tors, such as Cor­tex-M based devices with SWO trace. How­ev­er, even on micro­con­trollers with more trace capa­bil­i­ties, such as the Infi­neon AURIX Emu­la­tion Devices, instru­men­ta­tion may be required to record a Runnable trace for extend­ed peri­ods of time.

The goal of this webi­nar is to give users a full under­stand­ing of the steps nec­es­sary to record the OS and RTE behav­ior of their MICROSAR appli­ca­tion via instru­men­ta­tion. We go through the dif­fer­ent con­fig­u­ra­tion steps in DaVin­ci Con­fig­u­ra­tor, the TASKING trace con­fig­u­ra­tion helper (iTCHi), and final­ly winIDEA. The demo will be done on an Infi­neon TC399XE based appli­ca­tion, but the knowl­edge is applic­a­ble to the other archi­tec­tures men­tioned above. 

Who: Felix Mar­tin, Sys­tems Engi­neer, TASKING USA

Time­line:

• 8:45 - Thread State Pro­fil­ing via OS Tim­ing Hooks (data trace)
• 9:35 - TASKING Trace Con­fig­u­ra­tion Helper iTCHi
• 26:29 - Thread State Pro­fil­ing via OS Tim­ing Hooks (Rene­sas RH850 soft­ware trace)
• 26:40 - What is soft­ware trace?
• 33:17 - Runnable Pro­fil­ing via RTE VFB Trace Hooks

Addi­tion­al infor­ma­tion:  Appli­ca­tion Notes

If you are not famil­iar with AUTOSAR based tim­ing analy­sis, you can start by watch­ing our webi­nar AUTOSAR CLASSIC Tim­ing Analy­sis - Hard­ware Trace Based Real-Time Analy­sis.