Firmware is on shaky ground – let's see what it's made of
As an EE I love the idea of open firmware. I wish more companies would provide it - akin to the old TVs and other equipment that came with [full!] schematics inside. It would let me truly understand and modify the items that I purchased.<p>There is definitely a cost to it to the companies, which I fully expect to be passed down to me, but not in the form of a license agreement - in the form of an increase in base price.<p>The problem for companies is multifold. A big one is that the firmware is the piece that not only interacts with but also protects the hardware. If you are easily able to change the firmware, you are easily able to destroy the hardware, and if that&#x27;s under warranty, companies are going to be concerned. They&#x27;re also going to worry about IP; certainly I build products that lean on the work from previous projects. I would kind of hate handing that over to potential competitors. But some of that &#x27;hate&#x27; depends on the fact that my competitors don&#x27;t give their firmware code out either. Maybe I would love it if I could see how they implement things. Maybe it would push us all to deliver better things. Another impact - open firmware would definitely change sales models for equipment.<p>I imagine that if I had to start delivering open firmware for designs, I&#x27;d need to push some of the software control over product limitations into hardware. That might cost more, but is better anyway. Usually. And I&#x27;d try hard to figure out a way to install a &#x27;unverified firmware&#x27; hardware flag, maybe an efuse blown in a hard-to-replace component, so that we could know who broke things.<p>But I do like the idea. I want the firmware for my ${everything}.