<?xml-stylesheet type="text/xsl" href="https://community.element14.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Op Ed: A Microcontroller Course for Everyone!</title><link>/learn/publications/b/blog/posts/op-ed-a-microcontroller-course-for-everyone</link><description>If you&amp;#39;ve been in electronics for any time at all, it is easy to see a pattern develop between hardware and firmware/software engineers. As soon as a problem crops up, it is instantly clear to the hardware team that it is the code that needs f...</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Op Ed: A Microcontroller Course for Everyone!</title><link>https://community.element14.com/learn/publications/b/blog/posts/op-ed-a-microcontroller-course-for-everyone</link><pubDate>Sun, 13 Oct 2013 05:53:06 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:ccd13014-3025-4b89-856c-d68ddabf76bb</guid><dc:creator>rohitrangwani</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;&lt;span&gt; “it&amp;#39;s their problem”&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span&gt;nic one&lt;br /&gt;&lt;/span&gt;&lt;/p&gt;&lt;img src="https://community.element14.com/aggbug?PostID=16634&amp;AppID=45&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: Op Ed: A Microcontroller Course for Everyone!</title><link>https://community.element14.com/learn/publications/b/blog/posts/op-ed-a-microcontroller-course-for-everyone</link><pubDate>Mon, 07 Oct 2013 19:04:17 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:ccd13014-3025-4b89-856c-d68ddabf76bb</guid><dc:creator>DAB</dc:creator><slash:comments>2</slash:comments><description>&lt;p&gt;Hi Dave,&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;I completely agree.&amp;nbsp; As soon as you begin to learn about an MCU you will find that you need to do your homework on both the software (SW) AND the hardware (HW).&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Back in the 1970&amp;#39;s we used to have great screaming matches over deciding if the HW or the SW was at fault.&amp;nbsp; Most of it was just good clean fun, though it scared the hell out of management.&amp;nbsp; Both sides lacked the proper tools to locate and resolve a lot of the problems we encountered.&lt;/p&gt;&lt;p&gt;Remember these are days before good logic analyzers were available.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;My best story is about a system I programmed and was due to go through acceptance testing while I was on vacation.&lt;/p&gt;&lt;p&gt;When I returned there were half a dozen people outside my office screaming that the ATP failed because of my software.&amp;nbsp; So I asked the question &amp;quot;It worked fine when I left, what did you do to the system?&amp;quot;&amp;nbsp; The reply was &amp;quot;Nothing, we just fixed the Hardware!&amp;quot;&lt;/p&gt;&lt;p&gt;It turned out that their &amp;quot;Nothing&amp;quot; made the test signals incredibly stable, which forced the device under test to miss the discrete signal changes.&amp;nbsp; I had build the DUT with noice detection software filtering that looked for consistent signal changes and ignored single level changes.&amp;nbsp; It worked fine in the field as the noise from all the other electronics kept toggling the values to the point where it would detect the changes and position the equipment.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;The end of the story was that I had to add software to the test unit to simulate signal noise so that the DUT would work normally.&lt;/p&gt;&lt;p&gt;So much for fixing the hardware.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;It was experiences like these that encouraged me to get my BS in Computer Engineering.&amp;nbsp; At the time, it was the only degree field that enabled you to get both HW and SW exposure so that you could successfully interface machines together.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;So I encourage anyone new to MCU devices to get the training in both as you will find the rest of your life trying to resolve where the problem really is caused and wheather you can fix it with a few compontents or some software changes.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;As the Chinese say &amp;quot;May you live in interesting times!&amp;quot;&amp;nbsp; I believe this was a curse, but then I don&amp;#39;t speak Chinese. &lt;span&gt;[View:/resized-image/__size/16x16/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-ccd13014-3025-4b89-856c-d68ddabf76bb/contentimage_5F00_938.png:16:16]&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;So I am glad that they are training people to appreciate the interface issues.&amp;nbsp; With devices like the PSOC, the lines between HW and SW are getting even more blurred.&amp;nbsp;&amp;nbsp; Or is it just my vision?&amp;nbsp; Oh well.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Good Post,&lt;/p&gt;&lt;p&gt;DAB&lt;/p&gt;&lt;img src="https://community.element14.com/aggbug?PostID=16634&amp;AppID=45&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item></channel></rss>