SANTA CLARA, CA --- Renesas Electronics Corporation offers the E2 Emulator, a next-generation on-chip debugging emulator. The E2 is intended as a development environment for the latest devices in the Renesas RH850, RX, and RL78 Families of microcontrollers (MCUs), and for a selection of automotive system(s)-on-chip (SoCs). The new emulator supports the extended debugging functionality of the RH850 Family and contributes to shortening the time required for CAN communication debugging and the current consumption debugging.
Recently, use of electronics for automotive control is increasing to improve the fuel efficiency, safety, and comfort of vehicles, and the number and variety of built-in sensors is growing. This leads to an increased size of control programs of MCUs used in electronic control units (ECUs). Since each ECU performs communication control via automotive networks such as CAN, LIN, and FlexRay®, and dozens of ECUs are installed in a single vehicle, communication control has become more complicated. Additionally, considering that many ECUs are installed in a vehicle, it has become more important to precisely understand current consumption when each ECU operates and optimizes the control programs to achieve low current consumption in automotive systems.
One challenge with existing ECU software development is that it is necessary to download the program from the emulator to the MCU. And each time debugging code needs to be added to the control program, it increases the program size and download time. In the case of CAN communication, a significant contributor to this repetitive debug cycle is the need to use a CAN analyzer along with the emulator—these devices have not traditionally operated synchronously. In the case of low power optimization, the emulator is typically used side-by-side with an ammeter or current probe, and it is difficult to link the current consumption peak specifically to the matching point of time in the running code.
To address this challenge, Renesas has integrated additional debugging features required for software development as solutions into the E2. Specifically, the new emulator reduces the time required to determine the cause of an error during CAN communication by providing a connection to the bus that allows message timing to be matched with executing code; it also makes it easier to determine the cause of current consumption peak by monitoring the current draw of the device and correlating that with the code. This enables system developers to potentially reduce development time in these areas to as little as one-tenth (Note 1) compared with the existing method of repeated program modification and downloads. Even when the modification/download cycle is necessary, the increased download speed of the E2 lessens its impact on the speed of the development cycle.
Key features of the new E2 Emulator:
(1) Download speed up to twice as fast
The new E2 Emulator features faster communication speeds between the MCU and emulator and parallelization of flash rewriting and data communication. These capabilities enable control program downloads up to twice as fast as Renesas’ existing E1 Emulator (Notes 2).
(2) Industry's first solution that combines instruction-level debugging with CAN communication monitoring
As a CAN communication debugging function, the new E2 Emulator can stop the program when it detects that the interrupt response time has exceeded a specified limit, and record and display trace data relating to CAN communication reception and interrupt response processing simultaneously (Note 4). The debugging function is provided as an industry first (Note 3) solution for measuring CAN communication response time that allows for clearer correlation between CAN communication and program operation.
This solution for measuring CAN communication response time can allow trace analysis of CAN communication and program operation to be performed by the emulator alone, and can significantly reduce the time required to determine the cause of an error.
(3) Easier determination of the cause of current consumption peak
The new E2 Emulator can detect the current consumption peak and stop the program when the emulator detects that the current consumption has exceeded set limits for a certain period of time. This allows system developers to determine the conditions in the program that cause it to exceed the expected current consumption levels. Additionally, the emulator can display the program operation and current consumption together, making it easier to identify areas where current reduction should be targeted. This shortens the tuning time (Note 5) for reducing current consumption.
The E2 Emulator offers a native hot plug connection on supported devices with no adapter required.
The E2 Emulator supports the CS+ integrated development environment, which is designed to make the inevitable cycles of editing, building, and debugging in the software development simple, easy to use, and secure (Note 6). Support is also planned for the e2 studio (Note 6) integrated development environment (based on the globally popular Eclipse), Green Hills Software’s MULTI® IDE, and IAR Systems’ IAR Embedded Workbench®. The board interface is compatible with that of the existing E1 Emulator boards for which can also be connected to the E2 Emulator.
Renesas also plans to provide E2 Emulator tracing solutions via the RH850 Debug interface and plans to offer a break solution that enables to break the program while debugging based on an external trigger signal in the future.
Renesas will continue to develop additional debugging solutions that will contribute to reduced embedded software development time.
The E2 Emulator is available now for the RH850 Family and a selection of automotive SoCs. The new emulator will be available for the RX Family and RL78 Family from July 2017 onwards. Additional debugging solutions for the E2 emulator will also be available from July 2017 onwards. (Availability is subject to change without notice.)
Learn more at http://www.renesas.com