Welcome to a six-part series on “Making embedded processing development easy.” Over six weeks, we introduce you to considerations to aid with embedded processor design. This series is derived from the expertise of embedded processor software experts from Texas Instruments (TI) and is meant to provide an objective view of easing software design.
Part 1: Henry Wiechman, software product manager, embedded processing, TI, answers the question: I’ve not spent a lot of time developing in an embedded processing environment. How should I get started with this?
Part 2: Nick Lethaby, a manager in TI’s software development organization, answers the question:Do I need an operating system for my embedded design? If yes, which operating system should I select?
Part 3: Steven Magee, software architect, embedded processing, Texas Instruments, provides the answer to the question: I really would like to protect my software investment and re-use my code. What’s the best way to do this?
Part 4: Jason Kridner, software architecture manager, embedded processing, Texas Instruments answers the question: How do I properly take advantage of open source software for my embedded software design, and should I rely on the community?
Part 5: Nick Lethaby, a manager in TI’s Software Development Organization, answers the question: There seem to be increasing expectations for embedded devices to have state-of-the-art Human Machine Interfaces (HMIs). How can embedded software offerings make this easier and which are the best options for my application?
Part 6: Erik Welsh, a security architect in TI’s Application Specific Products Organization answers the question: I’m not sure I need to secure my embedded design? If I do, how do I begin and which type of security should I enable?