RH850 Family for Automotive

The RH850 is Renesas Electronics' latest automotive microcontroller family that offers high performance balanced with very low power consumption over a wide and scalable range of products. This family offers the rich functional safety and embedded security features needed for new and advanced automotive applications.

iSYSTEM provides comprehensive debug and trace support for the entire Renesas RH850 Controller Family. The iSYSTEM BlueBox On-Chip-Analyzers connect via any available debug and trace interface of this family (see below). Complex AUTOSAR applications can be analyzed and optimized to ensure that timing constraints are fulfilled.

Simplified, generic RH850 Debug/Trace Block Diagram
Figure 1: Simplified, generic RH850 Debug/Trace Block Diagram

 

Features

  • Debug Access via JTAG and LPD
  • On-Chip FLASH Programming
  • Debug support for RH850 Cores and Intelligent Cryptographic Units (ICU)
  • Single-/Multi-Core Debug & Trace
  • Trace support
    • RH850 Software Trace Streaming via LPD-4 Interface
    • On-Chip Trace RAM on “Large Memory” Devices
    • Nexus Trace Interface on Emulation Devices
    • AURORA Trace Interface on Emulation Devices

BlueBox Solutions

 Connection to the target Base Unit Picture

JTAG & LPD Debug (LPD4 Software Trace)
14-Pin 2.54 mm

RH850 JTAG Adaptor

iC5000, iC5700

Nexus Trace & Debug
38-Pin Mictor

RH850 Nexus Trace Adaptor

iC5000, iC5700

AURORA Trace & Debug
34-Pin ERF8 Samtec

RH850 AURORA Adaptor
iC6000

Typical Debug/Trace Configurations

 

Debug + Software Trace via LPD4 – iC5000

  • Basic and compact System
  • Debug Access via JTAG/LPD
  • Software Trace Support via LPD-4
  • Trace into On-Chip Trace RAM (on “Large Memory” Devices)
  • Optional IOM2 Analog/Digital I/O Module
Sample Debug/Trace Tool Configuration based on iC5000
Figure 2: Sample Debug/Trace Tool Configuration based on iC5000

 

Debug + Nexus Trace – iC5700

  • High-Performance, versatile System
  • Debug Access via JTAG/LPD
  • Software Trace Support via LPD-4
  • Trace into On-Chip Trace RAM (on “Large Memory” Devices)
  • Nexus Trace Port on Emulation Devices
  • Optional IOM6 Add-On Modules (ADIO, CAN/LIN)
Sample Debug & Nexus Trace Tool Configuration based on iC5700
Figure 3: Sample Debug & Nexus Trace Tool Configuration based on iC5700

 

Debug + Trace via AURORA – iC6000

  • Highest Trace Performance Ideally suited for long-term multi-core Program & OS Trace
  • Debug Access via JTAG/LPD
  • Optional high-speed AURORA Trace Support
Sample Debug & AURORA Trace Tool Configuration based on iC6000
Figure 4: Sample Debug & AURORA Trace Tool Configuration based on iC6000

RH850-specific Debug/Trace Features

Simplified Block Diagram of the RH850 Trace Architecture (without Nexus/AURORA Port)
Figure 5: Simplified Block Diagram of the RH850 Trace Architecture (without Nexus/AURORA Port)

 

RH850 Software Trace

About RH850 Software Trace: Software Trace is a RH850-specific trace solution based on Code Instrumentation. Software Trace messages are generated when the CPU executes dedicated instructions, DBCP, DBTAG and DBPUSH. The Software Trace messages can either be stored in an on-chip trace RAM (if available) or can be streamed out via the LPD-4 interface, operating in Software Trace streaming mode.

Sample AUTOSAR OS and Runnable Profile recorded via Software Trace
Figure 6: Sample AUTOSAR OS and Runnable Profile recorded via Software Trace

Timing & Performance Measurement Unit (TPU)

Features:

  • On-chip Counter Structure to measure Time (Clock Cycles) and Performance Metrices
  • Can be controlled (start/stop) by means of Trigger Event Unit (TEU)
  • Counter increment by Stop Events or Debug Clock (JTAG / LPD Clock)
  • Optional CPU Break on Counter Threshold and/or Overflow
  • Two Sub-Units: Time Measurement & Performance Measurement

Sample TPU Measurement:

Measure Runtime of Function "EE_RUN_Runnable_R1"

  • Number of Calls
  • Min/Max Execution Time per Call
  • Accumulated Execution Time (to calculate average Execution Time)
Unit 0:  Unit 1: Unit 2: Unit 3:
Accumulated Execution Time Minimum Execution Time Maximum Execution Time Number of Function Calls
Sample TPU Measurement Configuration
Figure 7: Sample TPU Measurement Configuration

ADIO & CAN Trace

A trace recording via the Nexus port allows a time correlation with Analog/Digital or CAN/LIN bus signals captured by means of the ADIO and/or CAN/LIN Add-On Module of the iC5700.

Figure 8 shows a correlated Nexus Trace and CAN bus recording. The trace was recorded on a Sensor Fusion demonstrator platform, based on RH850/F1H, created within a cooperation project between the companies INCHRON, OpenSynergy and iSYSTEM. The profiler timeline shows a combined trace of CAN bus, program flow, microCOQOS Hypervisor virtual machines and multiple AUTOSAR OS Tasks.

Profiler Timeline of a correlated RH850/F1H Nexus Trace and CAN Bus Trace
Figure 8: Profiler Timeline of a correlated RH850/F1H Nexus Trace and CAN Bus Trace

If you require further help to understand which BlueBox On-Chip Analyzer would best suit your needs, why not get in touch using the contact link on the right.

ActiveProbe for AURIX DAP Contact