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
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Hands-On Embedded Programming with C++17

You're reading from   Hands-On Embedded Programming with C++17 Create versatile and robust embedded solutions for MCUs and RTOSes with modern C++

Arrow left icon
Product type Paperback
Published in Jan 2019
Publisher Packt
ISBN-13 9781788629300
Length 458 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Maya Posch Maya Posch
Author Profile Icon Maya Posch
Maya Posch
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

Preface 1. Section 1: The Fundamentals - Embedded programming and the role of C++ FREE CHAPTER
2. What Are Embedded Systems? 3. C++ as an Embedded Language 4. Developing for Embedded Linux and Similar Systems 5. Resource-Restricted Embedded Systems 6. Example - Soil Humidity Monitor with Wi-Fi 7. Section 2: Testing, Monitoring
8. Testing OS-Based Applications 9. Testing Resource-Restricted Platforms 10. Example - Linux-Based Infotainment System 11. Example - Building Monitoring and Control 12. Section 3: Integration with other tools and frameworks
13. Developing Embedded Systems with Qt 14. Developing for Hybrid SoC/FPGA Systems 15. Best Practices 16. Other Books You May Enjoy

Avoiding real hardware

One of the biggest advantages of OS-based development on platforms such as embedded Linux is that it's so similar to a regular desktop Linux installation. Especially when running an OS such as a Debian-based Linux distribution (Armbian, Raspbian, and others) on SoCs, we have practically the same tools available, with the entire package manager, compiler collections, and libraries available with a few keystrokes.

This is, however, also its biggest pitfall.

We can write code, copy it over to the SBC, compile it there, run the test, and make changes to the code before repeating the process. Or, we can even write the code on the SBC itself, essentially using it as our sole development platform.

The main reasons why we should never do this are as follows:

  • A modern PC is much faster.
  • Testing on real hardware should never be done until the final stages...
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