Welcome to the Biomed Boston & ESC Boston 2019 Presentation Store. Here you can view and download conference and/or show floor theater presentations before, during, and after the event. If you’re looking for a presentation from a specific session that you’re unable to find here, note that it’s likely because the presenter has not provided permission for external use or has not yet shared their presentation with us. Please check back after the event for a more complete catalogue of available presentations.
Jean Labrosse (Software Architect, Silicon Labs)
Date: Wednesday, May 15
Time: 8:00 am - 9:00 am
Track: ESC Boston, Track E: Focus on Fundamentals, ESC Boston, Track B: Embedded Software Design & Verification
Vault Recording: TBD
There are many reasons to use an RTOS in an embedded product, especially when using a 32-bit (or larger) CPU. An RTOS should be used if:
- You have time-sensitive code
- You are using protocol stacks such as TCP/IP, USB, Bluetooth and other
- You have a team of software developers working on different aspects of your system: communications, control, user interface, etc.
- Code reuse and portability is important
- You need to speed up development time and thus reduce time-to-market
Although an RTOS provides all of the above benefits, an RTOS can introduce its own drawbacks such as:
- Properly setting task priorities
- Mutual exclusion
- Priority inversions
- Meeting deadlines
- RTOS overhead
- Stack overflows
This class will explore how some of these issues can be detected and avoided by using tools that have been designed specifically to circumvent these drawbacks. These tools are readily available and in most case, you can obtain free versions of these tools.
Understand how you can detect and correct RTOS related issues such as starvation, priority inversions, deadlocks and more. Know where you can find free version of RTOS-specific tools.
Embedded developers tasked with debugging RTOS-based systems
Students and professors.