Tag Archives: IAR Systems

Post navigation

IAR Systems recently announced that its Embedded Workbench now supports a new generation of Microchip Technology 8-bit AVR microcontrollers. You can use Workbench with AVR microcontrollers to develop a wide range of low-power systems.

IAR Systems recently announced that IAR Embedded Workbench for ARM now supports microcontrollers based on ARM Cortex-M3/M4 and ARM Cortex-A15 that are targeted for connectivity and the Internet of Things (IoT).

IAR Embedded Workbench for ARM is a complete C/C++ compiler and debugger toolchain for developing embedded applications. The toolchain generates efficient code, which makes it well suited for developing energy-efficient, time-critical IoT applications.

Because the IAR Embedded Workbench for ARM toolchain is continuously updated with new microcontroller support, you are free from having to consider the choice of software in your selection of a microcontroller. Instead of using different tools for different microcontrollers, you can use the same toolchain from start to finish. IAR Embedded Workbench for ARM is available in several versions, including a product package for the ARM Cortex-M core family.

IAR Systems recently announced that IAR Embedded Workbench for ARM is now integrated with the NXP Semiconductors S32 Design Studio, which is an integrated development environment (IDE) for NXP’s automotive and ultra-reliable microcontrollers. In addition to functionality such as pin configurator, bootloader and motor control toolbox, it provides AUTOSAR Microcontroller Abstraction Layer (MCAL) support and AUTOSAR OS for the S32K product line tailored for automotive applications.

By letting S32 Design Studio generate a project connection with IAR Embedded Workbench, the IAR C/C++ Compiler and the extensive C-SPY Debugger can be used to develop the application. Adding a project connection will automatically include the generated code to the IAR Embedded Workbench project. If the files are changed from S32 Design Studio, they are updated automatically in IAR Embedded Workbench. Due to an integration of the build chain of IAR Embedded Workbench into the Eclipse-based S32 Design Studio, you can also opt to continue development within the S32 Design Studio while utilizing the IAR C/C++ Compiler.

IAR Systems recently announced an updated version of its C/C++ compiler and debugger toolchain for developing ARM-based embedded applications. IAR Embedded Workbench for ARM Version 7.60 adds flash breakpoints functionality and extended static analysis in C-STAT, which performs an analysis on the source code level. In addition to helping developers in ensuring the code quality early in the development cycle, it also detects defects, bugs, and security vulnerabilities as defined by CERT C/C++ and the Common Weakness Enumeration (CWE). It also helps keep code compliant to coding standards such as MISRA C:2004, MISRA C++:2008, and MISRA C:2012.

C-STAT is fully integrated in the IAR Embedded Workbench IDE. The new update extends the tool with approximately 150 new checks, including 90 new MISRA C:2012 checks and two new packages of checks. Furthermore, there are new options for enabling or disabling the false-positives elimination phase of the analysis and excluding files from the analysis.

The flash breakpoints enable developers to set an unlimited number of breakpoints when debugging the flash memory. With the C-SPY Debugger in IAR Embedded Workbench, you can set various types of breakpoints in the applications you’re debugging. If you use IAR Embedded Workbench with IAR’s I-jet debug probe, you can add an unlimited number of flash breakpoints for selected ARM Cortex-M devices. By setting breakpoints, investigating the status of an application and speeding up the debugging phase is straightforward.

IAR Embedded Workbench for ARM is a handy tool that incorporates a compiler, an assembler, a linker and a debugger into one easy-to-use IDE. It provides advanced and highly efficient optimization features and is tightly integrated with hardware, RTOS products, and middleware. C-STAT is available as an add-on product.

IAR Systems recently announced a new version of IAR Embedded Workbench for Renesas RL78. The new version features new functionality and increased code quality control for applications based on Renesas RL78 microcontrollers.

C-STAT—which features innovative analysis that can detect defects, bugs, and security vulnerabilities—is now supported. Static analysis enables you to find identify errors (e.g., memory leaks, access violations, arithmetic errors, etc.) early on. Also included is stack usage analysis. You can customize the analysis process to handle account constructs such as calls via function pointers and recursion. Moreover, IAR Embedded Workbench for RL78 includes code optimizations for fast, efficient code.

Included with the toolchain is Renesas AP4 for RL78. You can use the standalone tool (formerly named Applilet) to automatically generate control programs for peripheral modules in accordance with user-defined settings. Renesas AP4 for RL78 supports code generation for IAR Embedded Workbench for RL78, and the generated modules are incorporated via the IAR Project Connection mechanism.

IAR Embedded Workbench for RL78 includes the IAR C/C++ Compiler, assembler, linker, library tools and the C-SPY Debugger in an easy-to-use IDE. It is available in several editions, including a Functional Safety version.

IAR Systems recently announced a starter kit for the state machine toolset IAR visualSTATE. Aimed at developers interested in exploring state machine-based embedded development, it includes evaluation versions of IAR visualSTATE as well as the embedded development toolchain IAR Embedded Workbench. The kit’s evaluation board comprises an STMicroelectronics STM32F429 and an I-jet Lite debug probe.

You can use IAR visualSTATE to develop design from a high level. In addition, the tools offer advanced formal verification, analysis, and validation. It contains an easy-to-use evaluation board that can be powered via the included debug probe I-jet Lite, which provides JTAG and SWD debug interfaces.

IAR visualSTATE is completely integrated with the powerful C/C++ compiler and debugger toolchain IAR Embedded Workbench. When using the tools together, full state machine debugging on hardware is available.

IAR Systems recently launched IAR Connect, which is a portal that presents product development platforms and serves as hub intended to connect innovators interested in the Internet of Things (IoT) and other emerging technologies.

One of the first members of IAR Connect is Renesas Electronics. Customers using the Renesas Synergy Platform can begin product development at a high level of abstraction and focus completely on designing innovative features for embedded applications and connected devices.

“The best way to take advantage of the possibilities of the new connected world is by providing new technology offerings, sharing knowledge and establishing strategic alliances, such as our strong partnership with Renesas. With IAR Connect, we enable innovation by connecting people and technologies. I invite everyone to connect, get inspired and explore the potential of the Internet of Things and the connected world at www.iarconnect.com”, said IAR Systems CEO Stefan Skarin in a released statement.

IAR Systems is proud to announce that its complete C/C++ development toolchain IAR Embedded Workbench now supports more than 10,000 devices, from all major microprocessor vendors. This unparalleled wide support puts IAR Embedded Workbench in a class of its own, enabling users to work with the same user-friendly development tools for virtually any device on the market.

In order to provide support for the largest number of 8-, 16- and 32-bit devices, IAR Systems has established strategic partnerships with leading microprocessor vendors such as Renesas, Atmel, STMicroelectronics, Freescale and Texas Instruments. The strong relationships and longstanding knowledge sharing with partners enables IAR Systems to deliver the market’s most comprehensive processor support by a wide margin. This has made it possible for some of the world’s largest corporations and thousands of small and mid-sized companies to standardize their development on IAR Systems’ software, gaining unique flexibility and freedom from having to consider the choice of software in their selection of microprocessor. The fact that IAR Systems’ customers are able to maintain their development environment when changing processor platform and reuse most of their code saves them both time and money.

“10,000 supported devices is a milestone for us and we are really proud to provide our customers with the unique flexibility that this record confirms,” comments Mats Ullström, Chief Operating Officer, IAR Systems. “It is a fact that no other embedded toolchain comes close to offering such a broad device support, and in addition, we provide leading code performance and excellent code quality. Developers can build what they want in the platform of their choice and always feel confident that we support the device.”

IAR Embedded Workbench is a powerful development toolchain that incorporates a compiler, an assembler, a linker and a debugger into one completely integrated development environment. Find all supported devices at www.iar.com/device-search.

IAR Systems, the leading vendor of embedded development tools, is proud to introduce its latest product innovation C-STAT. C-STAT provides powerful static analysis and is now available fully integrated in the high-performance development toolchain IAR Embedded Workbench for Texas Instruments’s (TI) MSP430 MCUs.

Important concerns for embedded developers today include adherence to coding standards, as well as increased application complexity that might interfere with code quality. Using a flexible static code analysis tool like C-STAT addresses both these issues by detecting potential code errors in complex applications and by ensuring compliance with coding standards applicable for embedded applications in various segments.

C-STAT is a powerful static analysis tool that executes fast and provides analysis results directly in the IAR Embedded Workbench IDE. It checks compliance with rules as defined by coding standards including MISRA C:2004, MISRA C++:2008 and MISRA C:2012, as well as hundreds of rules based on, for example, the Common Weakness Enumeration (CWE) and CERT C/C++. Users can easily select which rule-set or which individual rules to check the code against. The tool detects potential code errors including for example memory leaks, access violations, arithmetic errors and array and string overruns. By finding such errors early, developers can take full control of their code and lower the risk of breaking the budget and deadline for a project.

IAR Systems will host two seminar days during ARM TechCon 2014 in Santa Clara, CA on October 1 and 2, 2014. The free seminars will include lectures and hands-on training.

On October 1, IAR Systems will offer five sessions (11:00 am to 4:50 pm) on topics such as: Mastering Stack and Heap for System Reliability; Safety Traps in Embedded Software Engineering; Runtime Analysis Demystified; Advanced Debugging Techniques; and Efficient Programming. On October 2, IAR Sysetms will offer sessions within the technical training program IAR Academy.

Peter’s correct answer was randomly selected from the pool of responses that correctly identified an error in the code. Peter answered:

Line 35: Should not end with semi-colon

You can see the complete list of weekly winners and code challenges here.

What is the CC Weekly Code Challenge?
Each week, Circuit Cellar’s technical editors purposely insert an error in a snippet of code. It could be a semantic error, a syntax error, a design error, a spelling error, or another bug the editors slip in. You are challenged to find the error. Once the submission deadline passes, Circuit Cellar will randomly select one winner from the group of respondents who submit the correct answer.

The CC Weekly Code Challenge ran from June 3rd through December 30th, 2013. Subscribe to our CC.Post newsletter to stay informed of other contests and challenges, as well as recent news, new issue availability, and more!

Gait’s correct answer was randomly selected from the pool of responses that correctly identified an error in the code. Gait answered:

Line 31: should be digits % 3 instead of digits / 3

You can see the complete list of weekly winners and code challenges here.

What is the CC Weekly Code Challenge?
Each week, Circuit Cellar’s technical editors purposely insert an error in a snippet of code. It could be a semantic error, a syntax error, a design error, a spelling error, or another bug the editors slip in. You are challenged to find the error.Once the submission deadline passes, Circuit Cellar will randomly select one winner from the group of respondents who submit the correct answer.

We have a winner of last week’s CC Weekly Code Challenge, sponsored by IAR Systems! We posted a code snippet with an error and challenged the engineering community to find the mistake!

Congratulations to Gordon Margulieux of Oregon, United States for winning the CC Weekly Code Challenge for Week 29! Gordon will receive an Elektor 2012 & 2011 Archive DVD.

Gordon’s correct answer was randomly selected from the pool of responses that correctly identified an error in the code. Gordon answered:

Line 10: Conditional should be “if (number == 0)” instead of number < 0

You can see the complete list of weekly winners and code challenges here.

What is the CC Weekly Code Challenge?
Each week, Circuit Cellar’s technical editors purposely insert an error in a snippet of code. It could be a semantic error, a syntax error, a design error, a spelling error, or another bug the editors slip in. You are challenged to find the error.Once the submission deadline passes, Circuit Cellar will randomly select one winner from the group of respondents who submit the correct answer.

You can see the complete list of weekly winners and code challenges here.

What is the CC Weekly Code Challenge?
Each week, Circuit Cellar’s technical editors purposely insert an error in a snippet of code. It could be a semantic error, a syntax error, a design error, a spelling error, or another bug the editors slip in. You are challenged to find the error.Once the submission deadline passes, Circuit Cellar will randomly select one winner from the group of respondents who submit the correct answer.