Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
The Insider's Guide to Arm Cortex-M Development

You're reading from   The Insider's Guide to Arm Cortex-M Development Leverage embedded software development tools and examples to become an efficient Cortex-M developer

Arrow left icon
Product type Paperback
Published in Oct 2022
Publisher Packt
ISBN-13 9781803231112
Length 276 pages
Edition 1st Edition
Arrow right icon
Authors (3):
Arrow left icon
Jason Andrews Jason Andrews
Author Profile Icon Jason Andrews
Jason Andrews
Pareena Verma Pareena Verma
Author Profile Icon Pareena Verma
Pareena Verma
Zachary Lusiak Zachary Lusiak
Author Profile Icon Zachary Lusiak
Zachary Lusiak
Arrow right icon
View More author details
Toc

Table of Contents (15) Chapters Close

Preface 1. Part 1: Get Set Up
2. Chapter 1: Selecting the Right Hardware FREE CHAPTER 3. Chapter 2: Selecting the Right Software 4. Chapter 3: Selecting the Right Tools 5. Part 2: Sharpen Your Skills
6. Chapter 4: Booting to Main 7. Chapter 5: Optimizing Performance 8. Chapter 6: Leveraging Machine Learning 9. Chapter 7: Enforcing Security 10. Chapter 8: Streamlining with the Cloud 11. Chapter 9: Implementing Continuous Integration 12. Chapter 10: Looking Ahead 13. Index 14. Other Books You May Enjoy

Understanding the value of CI

CI is a best-practice framework for software development that aims to improve software quality while reducing development time and cost. It can best be described by contrasting it with the typical embedded software development flow, which we call desktop development.

In the desktop development situation, a team of software developers all works on the same code base at the same time, typically using GitHub or a private code repository. As each developer works, they send their modified code through their own non-standardized custom suite of tests with the hardware board on their desk, about once per day. This code is merged into a shared branch with their team. Developers then pull the shared branch back to their local environment to obtain changes from their team. At this point, the code may or may not be in a working state, and it is sometimes hard to identify the source of bugs that have been introduced by the interaction of different changes.

This...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image