Webinars

Below are several recorded webinars. Since they are done live they all differ slightly in content and in Q/A session. Contact us and request a live webinar for your company

 

Getting Started with TrueSTUDIO

Learn how to create your first project, configure project and build settings, import a project from another Eclipse/GDB/GCC tool, use the debugger, and much more. Each webinar is unique because we cover different topics and then answer questions from the attendees.
Getting started with Atollic TrueSTUDIO - webinar archive video - Jan. 27, 2016 (60:00)
Getting started with Atollic TrueSTUDIO - webinar archive video - Feb. 10, 2016 (60:00)
Getting started with FreeRTOS and Kinetis - webinar archive video - June 16, 2016 (60:36)
 

 

Atollic TrueSTUDIO Pro Feature Overview

Learn about the Pro features that can be unlocked in your Atollic TrueSTUDIO Lite IDE. Save time and frustration by finding problem areas quickly and easily, gain new insights into the performance of your system, analyze your code to improve quality and maintainabilty.

Get More Out of Your Debugger

Webinar archive from March 16, 2016 (57:22)
The challenge of debugging embedded systems is that traditional techniques such as printf(f) statements and blinking LEDs offer a very limited window into what is actually happening with the code. As our embedded systems become more complex with more code, new peripherals, and multiple communications stacks, the more opportunity for unintended or unknown interactions between code blocks. Highly experienced embedded developers have become somewhat adept at working around these limitations, even with rudimentary tools. But what about the rest of us? Shouldn’t the IDE do more to help us see what is really happening in our systems?
  • RTOS-aware debugging: see the state of tasks and other kernel objects at breakpoints
  • Real time exception and interrupt analysis: understand how your exceptions and interrupts are performing
  • Memory access history trace: monitor read/write for any variable
  • Measuring execution time: how does your system spend its time
  • Live variable watch: watch the contents of variables, structures, and arrays, live during debug
  • Hard fault analysis (quickly find what happened, why it happened and what code caused the fault)
  • Instruction trace: using ETM trace to record your program's execution, instruction-by-instruction
  • Printf() redirection to a debugger console window (no UART)