Introduction to embedded software engineering

Visit the Learner Help Center. Physical Science and Engineering. Electrical Engineering. Alex Fosdick. Enroll for Free Starts Jan Offered By. About this Course 60, recent views. Flexible deadlines. Shareable Certificate. Intermediate Level. Hours to complete. Available languages. Instructor rating. Offered by. University of Colorado Boulder CU-Boulder is a dynamic community of scholars and learners on one of the most spectacular college campuses in the country.

Week 1. Video 10 videos. Introduction to the Course 3m. Introduction to the Module 3m. Introduction to Embedded Systems 5m.

Embedded Software Engineering 8m. C-Programming Review 11m. Introduction to Software Configuration Management 5m. C Standardization and Team Coding Standards 8m. Development Environments Overview 8m. Development Kits and Documentation 10m. Version Control 12m. Quiz 1 practice exercise. Week 2. Video 9 videos. Compiling and Invoking GCC 11m. Preprocessor Directives 10m. Creating Header and Implementation Files 9m. Makefiles Part 1 7m.

Makefiles Part 2 10m. Recommended Articles. Article Contributed By :. Easy Normal Medium Hard Expert. Writing code in comment? Please use ide. Load Comments. What's New. We use cookies to ensure you have the best browsing experience on our website. Start Your Coding Journey Now! No, that's too low-level for getting started with embedded software. Interfacing to common sensors? No, that's too high-level, it requires too much knowledge to start there. I think the right fundamental level is the embedded microprocessor.

You don't need to understand physics or electrical engineering to use an embedded microprocessor, nor do you need to be a programming expert. This post is part of a series. Check out the complete Embedded Software Engineering series here.

Read on for more background and details. Embedded Software Engineering is intended for: New college grads with a computer science, computer engineering, or electrical engineering background who are interested in embedded systems. So that's where we'll start next time.