Start/Stop Function Setting Disabled in debugging with E2 Lite on FPB-RA2E1

Hi Vikram,

As far as I know this function is not available for the RA devices, but you can do something similar using the Breakpoint Actions menu on the Breakpoint properties. 

See more about it here:
Calling (Debugging with GDB)
Set Breaks (Debugging with GDB)

Thank you,

Andre

Dear Andre,

Thanks for your reply.

I however, don't understand how a timer can be stopped while triggering a breakpoint placed in an unrelated code area.

This is of critical importance because we are triggering thyristors with the timer outputs and hardware one-shot mode is not available in the RA2E1 and we depend upon timer interrupts to stop the timer from triggering the thyristors again. 

If the timer runs uncontrollably, say when the program execution is stopped while debugging, either by a breakpoint or by a manual "Suspend" command, the power circuits will be damaged.

Please let me know if anything can be done to prevent this issue.

Regards,

Vikram.

Dear Vikram,

Thank you for your query.

To help us investigate this further, could you please provide the following details:

1. Which version of e² studio and FSP are you using?

2. Have you tried checking this option with any other RA device or a different debugger?

3. Could you briefly describe your project setup...for example, are you using the Timer module through FSP or configuring it manually?

These details will help us check if the behavior is specific to your setup and suggest suitable alternatives.

Kind regards,

PS

Dear PS,

Thanks for your reply. 

We are using the E2 Studio 2024-07 and FSP version 5.4.0.

We are using the Timer Module (GPT) through FSP but can write code manually if needed.

It is clearly stated in FSP Documentation that the One-Shot mode is implemented in Software:

One-Shot Mode

The GPT timer does not support one-shot mode natively. One-shot mode is achieved by stopping the timer in the interrupt service routine before the callback is called. If the interrupt is not serviced before the timer period expires again, the timer generates more than one event. The callback is only called once in this case, but multiple events may be generated if the timer is linked to the Transfer (r_dtc).

Please advise on the same,

Thanks and Warm Regards,

Vikram.

Hi Vikram,

Thank you for your response!

The start/stop facility is not supported on devices that do not feature a Cortex-M33 or Cortex-M4 core. This is because the feature relies on a debug monitor interrupt, which is only available on these cores.

For a detailed explanation, please refer to the official Renesas document's page 43 of this document:

E2 Emulator, E2 Emulator Lite Additional Document for User's Manual (Notes on Connection of RA Devices)

specifically outlines the limitations and conditions under which the start/stop facility can be used. We recommend reviewing that section for complete clarity on this feature's applicability.

Kind regards,

PS

Hi Vikram,

To be clear, I never tested it with RA2E1, but it works for RA6T2. 
Check the attached file.

Thank you

Andre

RA6T2_Breakpoint.pptx