Diagnostic Communication Manager [DCM] is a autosar module in ECU software which handles the tester diagnostics functionalities like UDS, KWP and OBD etc. This is pre-requisite video for flow control and first video in DCM tutorial series. Previous to this UDS videos were uploaded. Please watch this playlist for flow control video series: https://www.youtube.com/watch?v=8NQ4lkEqtWE&list=PL7RbKI2JHDnIOuom0pTQfiQaWULt3MWja DCM series, this is part 1 video. part 2 video: coming soon

Diagnostic Communication Manager [DCM] is a autosar module in ECU software which handles the tester diagnostics functionalities like UDS, KWP and OBD etc. In this video we will understand DCM and entire diagnostic stack functionality and co-relate it to OSI model. This is pre-requisite video for flow control and first video in DCM tutorial series. Previous to this UDS videos were uploaded. Please watch this playlist for flow control video series: https://www.youtube.com/watch?v=8NQ4lkEqtWE&list=PL7RbKI2JHDnIOuom0pTQfiQaWULt3MWja DCM part 1 video link: https://youtu.be/Dq3jnUOw8j4 This is DCM part 2 video

Explains the basics of transport protocols and compares the two major options: UDP and TCP. Updated version with QUIC: https://www.youtube.com/watch?v=y8xHJJWwJt4 00:00 Intro 00:07 About transport protocols 02:11 User Datagram Protocol 04:08 Transmission Control Protocol 09:00 So which one is better? == Further reading == How can BitTorrent run reliable file transfers over UDP? - http://arstechnica.com/uncategorized/2008/12/utorrents-switch-to-udp-and-why-the-sky-isnt-falling/ - https://en.wikipedia.org/wiki/Micro_Transport_Protocol == Acknowledgements == The thumbnail of this video uses an icon by Dmitry Baranovskiy from The Noun Project. The icons that are used throughout the video are credited to their respective authors at the end of the video.

Operating System #27 Hardware Locks: Spinlock & its Usage Complete Operating Systems Lecture/ Tutorials from IIT @ https://goo.gl/GMr3if MATLAB Tutorials @ https://goo.gl/EiPgCF High Level Constructs • Spinlock • Mutex • Semaphore 15:40 Spinlocks Usage: • One process will acquire the lock • The other will wait in a loop repeatedly checking if the lock is available • The lock becomes available when the former process releases it Issues with Spinlocks • No compiler optimizations should be allowed – Should not make X a register variable • Write the loop in assembly or use volatile • Should not reorder memory loads and stores • Use serialized instructions (which forces instructions not to be reordered) • Luckly xchg is already implements serialization • No caching of (X) possible. All xchg operations are bus transactions. – CPU asserts the LOCK, to inform that there is a ‘locked ‘ memory access • acquire function in spinlock invokes xchg in a loop…each operation is a bus transaction … huge performance hits.

In this webinar we will take a detailed look into OS and RTE profiling of an MICROSAR OS based application. Specifically, we will utilize the Vector OS timing hooks to record task states and ISRs, as well as the VBF trace hooks to record Runnable events. The demo will be done on an Infineon TC399XE based application, but the knowledge is applicable to the other architectures mentioned above. Timeline: 0:00 Intro 8:45 Thread State Profiling via OS Timing Hooks (data trace) 9:35 Trace Configuration Helper iTCHi 26:29 Thread State Profiling via OS Timing Hooks (Renesas RH850 software trace) 26:40 What is software trace? 33:17 Runnable Profiling via RTE VFB Trace Hooks