Skip to main content
Knowledgebase
Home
Renesas Singapore - Knowledgebase

Is it possible to debug internal processing via PDG V.2 or HEW?

Latest Updated:11/10/2015

Question:

Is it possible to debug internal processing by the library (Renesas Peripheral Driver Generator Library) called by the functions the Peripheral Driver Generator V.2 generates under CubeSuite+ or the High-performance Embedded Workshop?

Answer:

Source-level debugging of the library provided with a product becomes possible if you switch to the version of the library that includes debugging information (referred to as the debug version below).

In this FAQ, Peripheral Driver Generator V.2 and Renesas Peripheral Driver Generator Library are referred to as PDG and RPDL, respectively.

The library for debugging supports the following series of the RX family.
RX62G, RX62N/621, RX62T, RX630, RX63N/631, RX63T, RX210, and RX220

  1. Open the project in which the PDG is used.

  2. Change the RPDL file registered as the library for the project to the debug version.

    • For CubeSuite+:
      In [Property] of the CC-RX (build tool), select the [Frequently Used Options (for Link)] option and change the registered library to the debug version of the library in [Using libraries].

    • For the High-performance Embedded Workshop:
      Select [Build]→[RX Standard Toolchain] and change the library registered in the [Link/Library] tabbed page of the [RX Standard Toolchain] dialog box to the debug version of the library.

    The filename of the debug version is the same as that of the non-debug version, except that "_debug" is appended to the end of the name.
    The library is placed in lib\(device name) in the folder where the PDG is installed.

    Example:
    Normal version: RX62N_library_100_little.lib
    Debug version: RX62N_library_100_little_debug.lib

  3. For CubeSuite+

    For users of the High-performance Embedded Workshop, see description 4 below.

    (1) In the project, register the source files where the functions to be debugged are defined.
    The source files are stored in source\RX\(device name)\(module name)\(function name).c in the folder where the PDG is installed.
    The names of the files for most functions are obtained by appending "ALL" to the end of the name of the function that is called.

    For example, if you want to check the source code of an R_CGC_Set() function for the clock module, you will find it in \RX\RX62N\CGC\R_CGC_SetAll.c.

    (2) For the source file registered in (1) above, select [No] for [Set as build-target] in [Build Settings] of [Property] of the file.

    (3) Run a build and a download.

    (4) On stepping in to a function of the RPDL during debugging, the function in the source file registered in (1) above will be displayed.

  4. For the High-performance Embedded Workshop

    (1) Run a build and a download.

    (2) On stepping in to a function of the RPDL during debugging, a dialog box for selecting the source file will appear. Select the name of the source file where the function is defined.
    The source files are stored in source\RX\(device name)\(module name)\(function name).c in the folder where the PDG is installed.
    The names of the files for most functions are obtained by appending "ALL" to the end of the name of the function that is called.
    For example, if you want to check the source code of an R_CGC_Set() function for the clock module, you will find it in \RX\RX62N\CGC\R_CGC_SetAll.c.

    (3) The function defined in the specified source file is then displayed.

Suitable Products
CS+ (formerly CubeSuite+)
High-performance Embedded Workshop
Peripheral Driver Generator
Renesas Peripheral Driver Library