Integration of the TASKING Software Trace Solution (“SWAT”) into an AUTOSAR Classic stack

𝗛𝗼𝘄 𝗱𝗼 𝘆𝗼𝘂 𝗶𝗻𝘁𝗲𝗴𝗿𝗮𝘁𝗲 𝘁𝗵𝗲 𝗧𝗔𝗦𝗞𝗜𝗡𝗚 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗧𝗿𝗮𝗰𝗲 𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻 (𝗦𝗪𝗔𝗧) 𝗶𝗻𝘁𝗼 𝗮𝗻 𝗔𝗨𝗧𝗢𝗦𝗔𝗥 𝗖𝗹𝗮𝘀𝘀𝗶𝗰 𝘀𝘁𝗮𝗰𝗸?

In this Tech Tues­day ses­sion, Mar­tin Supf, Appli­ca­tion Engi­neer at TASKING, walks through the full inte­gra­tion of the TASKING Soft­ware Trace Solu­tion (SWAT) into an AUTOSAR Clas­sic project based on Vec­tor MICROSAR. SWAT enables soft­ware-based tim­ing analy­sis with­out hard­ware trace ports, sup­port­ing AURIX, ARM, and RH850 devices.

𝗪𝗵𝗮𝘁 𝘆𝗼𝘂 𝘄𝗶𝗹𝗹 𝗹𝗲𝗮𝗿𝗻:

How to add the gen­er­at­ed files to your build and con­fig­ure the winIDEA ana­lyz­er

How SWAT fits into the TASKING trac­ing port­fo­lio along­side hard­ware trace solu­tions

Which archi­tec­tures and oper­at­ing sys­tems are sup­port­ed

How the SWAT observ­er, buffer man­ag­er, and winIDEA trace ana­lyz­er work togeth­er

How to con­fig­ure your AUTOSAR OS and gen­er­ate SWAT files using the iCHY addon in winIDEA

How to allo­cate the SWAT buffer in tar­get mem­o­ry using Da Vinci Con­fig­u­ra­tor

Speak to a TASKING Expert → SWAT (Soft­ware Trace Tool) →