An unrivalled feature-set and unprecedented integration

Transcription

1 Atollic TrueSTUDIO

2 An unrivalled feature-set and unprecedented integration ARM and x86 C/C++ build and debug tools (GNU) for development of embedded MCU and PC applications Parallel compilation and multi-core debugging System analysis and real-time tracing (SWV/SWO as well as ETM/ETB) Live variable & expression view RTOS-aware debugger with crash analyzer MISRA-C checker and code complexity analysis Code review & review meeting features Version control system clients (GIT, SVN, CVS) Bug database client (Trac, Bugzilla, )

3 Target support Supported CPU cores: ARM7 /ARM9 Cortex -M0/M0+/M1/M3/M4 Cortex-R4/R5/R7 Cortex-A5/A7/A8/A9/A15 VFP/Neon Supported device manufacturers: Atmel EnergyMicro Freescale Fujitsu Infineon NXP Renesas STMicroelectronics Texas Instruments Toshiba Supported RTOS vendors (KA debugging): ExpressLogic FreeRTOS HCC-Embedded Micrium Quadros Segger TOPPERS µitron MQX (partial support) Atollic TrueSTUDIO supports almost 2000 devices, over 100 evaluation boards and includes over 1000 free example projects!

4 How to analyse a crashed system (Cortex-M) with Atollic TrueSTUDIO

5 Tool automated solution Debugger can show where and why CPU crashed automatically No need to manually perform the steps described on previous pages MUCH more convenient than the manual approach

6 System analysis with Serial Wire viewer (SWV) real-time tracing (Not available in all Cortex devices)

7 Printf() redirection using ITM Re-direct printf() output to the IDE printf() redirection implemented with a simple C macro using ITM interface on JTAG cable 32 available ITM ports (consoles/channels) Different software routines can print to different ports. For example: Application prints to channel 0 RTOS prints to channel 1 TCP/IP stack prints to channel 2 Benefits: No need for USB / RS232 or external display Up to 32 independent output channels ITM can also be used for other tasks, i.e. generic software instrumented trace

8 Speed optimization with statistical profiling Non-intrusive PC sampling during system execution See how much execution time is spent in each function Based on periodic sampling so not 100% accurate, but becomes more and more reliable as execution time increase. Benefits: Analyze where most execution time is spent Prioritize optimization efforts Done without speed penalty (maintains full real-time behavior since no instrumentation).

9 Exception & Interrupt tracing See how interrupts occur in real-time in your application What exception source/peripheral? What interrupt handler? Time spent in interrupt? Any interrupt nesting? When do interrupts occur? Understand interrupt handler performance How much execution time is spent in each interrupt handler? Shortest/Average/Longest runtime?

10 Real-time data monitoring Real-time watch of mem./vars. while target is running at full speed See memory/variable value in real-time See the complete memory access history Double-click on a memory access -> open code line that made specific memory access Real-time data graph makes it easy to understand variable values Zoom in / out Take screenshots Toggle between cycles/time Broken patterns found easily

11 Record execution flow using ETM/ETB instruction tracing Inspect recorded data to understand what the CPU was doing before a bug leads to a crash (Not available in all Cortex devices)

12 ETM trace (record data) Instruction tracing collects an enormous amount of data (1s exec time on Cortex-M4 is ~100MB binary packed, or 5-10GB human readable). Trace Triggers are used to start/stop tracing in order to reduce the massive amount of data collected Event triggered start/stop (on PC or memory access) Breakpoint triggered start/stop

13 ETM trace (analyse data) Show the recorded execution history on different abstraction ( zoom ) levels: Function trace C trace Mixed C/Asm trace Asm trace

14 Debug RTOS-based applications

15 Kernel aware debugging An RTOS have internal object states you need to study during debugging Tasks, semaphores, mailboxes, timers, etc. You need to peek into the RTOS and see how kernel objects changes when debugging the system Your debugger needs to have RTOS views for the kernel objects in your RTOS

16 An alternative approach: Avoid introducing bugs in the first place

17 Reduce bugs by writing better code Check code for MISRA-C compliance Reduce the number of bugs by follow ing a best-practice coding standard developed by industry experts. Measure and manage code complexity Measure cyclomatic value of code complexity, and refactor (simplify) complex functions. Benefits: Complexity level > Where to rew rite & refactor? Low complexity > Low probability of errors Low complexity > Low cost for maintenance Low complexity > Easy to test

18 Reduce bugs with peer reviews Source code reviews Colleagues study each other s code, trying to find problems and suggest improvements. Typically a 3-phase process: Individual review phase study the code Team discussion phase code review meeting Individual rew ork phase fix problems assigned to me

19 More information: EUROPE & WORLDWIDE Atollic AB Science Park Gjuterigatan 7 SE Jönköping Sweden USA & AMERICAS Atollic Inc 241 Boston Post Road West 1st Floor Marlborough Massachusetts (973) info@atollic.com sales.usa@atollic.com