Sometime back, I attended a seminar in Bangalore on using new tools for embedded development and testing. It all started nicely in a nice hotel and all. But, after sometime, my brian decided to go for a break (and never return till the end of the day). I was taking notes in the beginning and then the below happened... I am typing what I wrote for my own understaing in later years (the original is also loaded for your reference ;-) )
120 Engineers, project leaders and test heads; all trying to understand why in the world should one use JTAG to debug embedded systems and why no the history proven (and cheap) process of using printf and LED indicators. Mr. P. Seshan spoke for most of the 6 hours trying just that. I do not know how it was for others, but for me, it was the whole session just about grazed my hair while going over it.
The morning session started with topics on conventional methods of debugging like ICE, printf, etc. People at that time were pretty enthusiastic and started asking questions. Some who thought they had a good question and some who actually had a proper query both raised the stakes of the seminar. Suddently, there was an onrush of lame questions that a professor (who happened to attend the seminar) told Mr. Seshan how to put a stop to such questions by asking him to tell what the scope of the discussion was. It seemed to have silenced the people for some time.
This gave the speaker much needed time to actually go to the topics he had originally intended. Then started the concept of JTAG and what it is, how it works, etc, etc. That was when my brain started to go into suspend mode. Then all I heard was
... blah blah blah blah JTAG... blah blah blah blah memory blah blah blah blah blah processor blah blah blah blah blah JTAG... and (at this point everything else faded into oblivion)...