Skip to Main Content
Cloud Platform

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive a notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

If you encounter any issues accessing the Ideas portals, please send email describing the issue to for resolution.

For more information about IBM's Ideas program visit

Status Future consideration
Created by Guest
Created on May 24, 2018

RSARTE Debug -- GNU MCU C/C++ J-Link Debugging

Somewhat recently RSARTE 2018 become incompatible with respect to debugging RSARTE generated ARM microcontroller projects.

We develop CortexM4/7 firmware using RSARTE. For a long time we could debug and have peripheral registers visible in the debugging session via the GNU MCU C/C++ Eclipse plugins.

Somewhat recently an incompatibility has developed between the C++ source directories RSARTE generates (and in particular the .cproject file therein) and GNU MCU C/C++ J-Link Eclipse plugins so that the processor device type can no longer be selected via the C++ project preferences and as a result the peripheral function registers are no longer visible.

I have found that right before debugging I can replace the .cproject file in the RSARTE generated project with one created with the GNU MCU plugins including the J-Link & Packs plugins installed and the appropriate microcontroller pack selected.

This GNU MCU project is created by Eclipse RSARTE>File>Project...>C/C++>C++ Project/ARM Cross GCC. Then the microcontroller device type in the newly created ARM Cross GCC project is selected by: Eclipse RSARTE>Properties>C/C++ Build>Settings/Devices/...

Idea priority High
RFE ID 120481
RFE Product Rational Software Architect Real Time Edition
  • Guest
    Aug 13, 2018

    It turns out that one can enable the MCU peripheral registers debugging by
    1. Setting the generated project's properties "C/C++ Build/Tool Chain Editor>Current Toolchain" to "ARM Cross GCC"
    2. Setting the generated project's properties "C/C++ Build/Settings>Devices Tab" to

    No enhancements are needed to RSARTE.

  • Guest
    May 24, 2018

    Attachment (Description): Debugger screenshot of the peripheral register functionality.

  • Guest
    May 24, 2018

    Attachment (Description): .cproject file from an RSARTE C++ project. This project file disables microcontroller peripheral register visibility.

  • Guest
    May 24, 2018

    Attachment (Use case): .cproject file from an ARM Cross GCC project. This project file enables microcontroller peripheral register visibility.