Search icon CANCEL
Subscription
0
Cart icon
Cart
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Hands-On RTOS with Microcontrollers

You're reading from  Hands-On RTOS with Microcontrollers

Product type Book
Published in May 2020
Publisher Packt
ISBN-13 9781838826734
Pages 496 pages
Edition 1st Edition
Languages
Author (1):
Brian Amos Brian Amos
Profile icon Brian Amos
Toc

Table of Contents (24) Chapters close

Preface 1. Section 1: Introduction and RTOS Concepts
2. Introducing Real-Time Systems 3. Understanding RTOS Tasks 4. Task Signaling and Communication Mechanisms 5. Section 2: Toolchain Setup
6. Selecting the Right MCU 7. Selecting an IDE 8. Debugging Tools for Real-Time Systems 9. Section 3: RTOS Application Examples
10. The FreeRTOS Scheduler 11. Protecting Data and Synchronizing Tasks 12. Intertask Communication 13. Section 4: Advanced RTOS Techniques
14. Drivers and ISRs 15. Sharing Hardware Peripherals across Tasks 16. Tips for Creating a Well-Abstracted Architecture 17. Creating Loose Coupling with Queues 18. Choosing an RTOS API 19. FreeRTOS Memory Management 20. Multi-Processor and Multi-Core Systems 21. Troubleshooting Tips and Next Steps 22. Assessments 23. Other Books You May Enjoy

Chapter 6

  1. False. In this chapter, the ST-Link on the Nucleo development board was re-flashed to provide the same functionality as a J-Link.
  2. False. There are many ways to verify the timing requirements of a real-time system. Segger SystemView provides a means to measure response time, as does looking at system inputs and outputs via a traditional logic analyzer.
  3. False. An RTOS-aware debugger provides the ability to view all of the stacks in the system. This is also an option with any Open GDB-based debugging using Eclipse, as mentioned in the previous chapter.
  4. False. Each module that you write should be tested as thoroughly as possible to minimize any surprises and complex interactions when it is time to integrate the modules and perform a system-level test.
  5. Unit testing. In unit testing, each individual module is tested as it is developed. Integration testing is testing to ensure...
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 $15.99/month. Cancel anytime