Sometimes what appears to be unlikely bedfellows ends up being a great marriage. That was the case (at least in my mind) when I heard about the partnership between Data I/O and IAR Systems. My first reaction was, what do these companies have in common that requires a partnership, and what is gained by the formal arrangement that couldn’t be had otherwise?
For background, Data I/O, headquartered in Redmond, WA, provides security provisioning and programming systems for flash memory, microcontrollers (MCUs), and logic devices. Markets the company currently plays in include automotive, IoT, medical, consumer, industrial, and so on. IAR, based in Sweden, is a provider of embedded development tools, including the popular Embedded Workbench product. It operates in similar markets.
As is was explained to me by Anthony Ambrose, the CEO of Data I/O, designers that employ the products of both companies appear to be spending too much development time converting completed MCU firmware into production-ready first articles.
The first point of contention is recognizing that there actually is a problem with the current conditions, and recognizing that there must be a better way to handle this phase of the development process. Once that point is clear, the solution should lie in a seamless workflow to ensure resource efficiency and a faster time to market, all while maintaining (or improving) the level of quality and the required level of security.
And that’s precisely where the partnership between the two companies makes sense—to efficiently ease the transition of MCU firmware design from development to manufacturing for OEMs by making the connection between the IAR design flow and the Data I/O manufacturing flow more seamless. Once you have it explained to you, it’s an “oh yeah, that makes a lot of sense” moment.
The reason for the formal partnership is to allow the direct communication between the two companies so that any potential obstacles can be removed and the development process can be further automated before the OEM even begins the design flow. It also allows IAR and Data I/O to establish a shared vision for a modern workflow that incorporates architecture, design, first article, and manufacturing, rather than requiring the OEM to navigate these tricky waters on his own.
And, according to Stefan Skarin, IAR’s CEO, the two companies have committed to integrate future processes and tools, giving developers the confidence that’s needed to incorporate the workflow.
At the end of the of the day, it appears to be a marriage that makes sense.
About the AuthorFollow on Twitter Follow on Linkedin Visit Website More Content by Rich Nass