About

Part of DAS Installation

  • Allow to demonstrate and check the DAS operation
  • All tools are fully generic

           (no interface type or device type specific adaptation code inside)

  • MCD Basic Client uses the MCD library on top of DAS
  • MCD implements run control (start, stop, breakpoints, etc.)
  • MCD API is core centric and generic
  •  MCD implementation is device specific
  • MCDS Trace Viewer for AURIX™ Emulation Devices

Allows analysis of tool and device behavior

e.g. for debugging of the multi-tool setup itself

  • Needs to be started manually from DAS installation directory
  • Factor 10x-40x for DAS latency between visible and minimized console window > Tool becomes slow when not minimized

Part of DAS Installation

  • Allow to demonstrate and check the DAS operation
  • All tools are fully generic

           (no interface type or device type specific adaptation code inside)

  • MCD Basic Client uses the MCD library on top of DAS
  • MCD implements run control (start, stop, breakpoints, etc.)
  • MCD API is core centric and generic
  •  MCD implementation is device specific
  • MCDS Trace Viewer for AURIX™ Emulation Devices

Allows analysis of tool and device behavior

e.g. for debugging of the multi-tool setup itself

  • Needs to be started manually from DAS installation directory
  • Factor 10x-40x for DAS latency between visible and minimized console window > Tool becomes slow when not minimized

Documents

Design resources