To further aid fault analysis, an exception stack frame visualization option provides a snapshot of MCU register values at the time of the crash. Memory errors can include attempts of access an illegal location or rule violations of the memory protection unit (MPU). Usage faults are the result of illegal instructions or other program errors. Bus faults occur when an invalid access attempt is made across the bus, either of a peripheral or memory location. Faults are categorized broadly into bus, usage and memory faults. The user can then view the reasons for the error condition.
Within the debugger, after a fault has occurred, the code line where the fault happened will be displayed. Typically, this may include division by zero errors, accessing invalid memory locations or accessing memory locations on misaligned boundaries. Fault analyzer feature interprets information extracted from the Cortex-M nested vector interrupt controller (NVIC) in order to identify the reasons that caused the fault. For more information about “target” devices, please visit.
In addition, the software works with more than 80 evaluation boards and JTAG probes such as J-Link, ST-LINK and OSJTAG/Multilink. Programmers can use the TrueSTUDIO software to create code for ARM7, ARM9, Cortex-M0, -M0+, -M3, -M4(F), and -A5 processors available from manufacturers that include Atmel, Energy Micro, Freescale, Fujitsu, Infineon, NXP, STMicroelectronics, Texas Instruments and Toshiba. Customers also can buy licenses for five, 10, or more seats. For a single-seat network license, price: $US 3800.
įor a single seat TrueSTUDIO (with TrueINSPECTOR), price: $US 2595 for a single license with a dongle, price: $US 2800. For the TrueSTORE programs, please visit.
The Atollic TrueSTORE provides over 1000 free example projects to help programmers and engineers get started with their software project. For now, the software works with the Micrium uC/OS-III kernel. The overall TrueSTUDIO has improvements, too, that include debugging code for multicore processors, support for version-control built into the IDE, and awareness of a real-time operating system (RTOS) within your application code. A pie chart identifies types of problems and frequency of occurrence to help identify recurring errors and coding violations so programmers can specifically avoid them. So knowledge of code complexity can help you focus on sections that need a rewrite or restructuring (refactoring). Complicated code can thwart efforts to understand and debug it. The TrueINSPECTOR program also reports on code complexity of functions, commenting “level” within your code, and so on. For TrueINSPECTOR information, please visit. The rules divide into those required for MISRA compliance and those that provide advisory information about potential problems. When you pass code to the TrueINSPECTOR software, it scans for MISRA-C violations such as “loose” assembly-language inserted into the code, improperly formatted comments, incorrect use of the #pragma directive, using the char data type for other-than-character values, and so on. The MISRA-C:2004 specification includes 141 coding rules that purposely limit how programmers can write their C-language source code.
MISRA, the Motor Industry Software Reliability Association, has created and published standards for reliable code written in C. The new version of Atollic's TrueSTUDIO IDE can help because it now includes the company's TrueINSPECTOR, a static source-code analysis tool that checks for compliance with the MISRA-C:2004 coding standard. Thus their code can look “messy,” lack documentation, improperly reuse variables, incorrectly declare variables, leave unused code in functions, and so on. Īccording to Atollic, many programmers have not received a formal education in using the C language and to write good programs. fix new errors, back to the analysis tool, repeat… The Atollic TrueSTUDIO software eliminates several of those steps. When you write code for ARM processor cores, your steps likely include exporting code to an analysis tool that looks for errors, back to the integrated-development environment (IDE), fix bugs, recompile.