I have been experiencing continually resets after i download my program and run. This is a new issue, as i have been able to use the emulator for ~2 months without any problems. I have confirmed this issue on two separate units. I am able to connect to my device(s) and download my program, the issue occurs when I run (select "GO") my program. It will reset over and over and HEW says it loses communication.
Things I've tried:
I have ordered a replacement 50 ohm coaxial cable to see if that resolves the issue. Any other suggestions? Has this happened to anyone else?
Note: I am able to load the same image via the FDT tool and it works fine.
So from what I can gather,
Debugger is disconnecting, but the device can run in stand-alone mode without any problems.
A couple of questions then:
Is the right device selected in the debugger settings?
Does your application have a watchdog timer?
Are you using a software reset?
Is the right device selected in the debugger settings? Yes. The settings have not been changed.
Does your application have a watchdog timer? Yes.
Are you using a software reset? Can you elaborate?
Can you check if the reset is triggered by the watchdog timer?
Do you use monitoring of variables with automatic updates? Variable updating will interrupt your application, and then the interval between watchdog timer refreshs may be to long causing the WDT to overflow.
How do i verify the reset was triggered by the watchdog?
I removed all monitored variables from the watch list.
You can reset the MCU by writing a value to a SFR. It's usually write protected by another SFR in memory.
If there's a pointer which is going crazy, and the conditions are right, it may reset the device. It's a small possibility, but something to consider nevertheless.
Since you say you have a watchdog; instinct says the watchdog is causing the behavior you are observing.
I would recommend that you put preprocessor definitions around the watchdog enabling instructions to disable it, while creating a new build configuration ("Hardware Debug 2", may be?).
That should help you figure out if the watchdog is causing the system to reset with the debugger connected.
I disabled the watchdog and it is now working.
What would cause the device to reset only when attached to the emulator?
Does the emulator satisfy the WDT (I assume yes) and is there settings for this in HEW?
The debugger will introduce minor delays in execution.
If you are using the E8A Debugger then there is some useful information available in the Additional Document to the E8A Emulator when connected to the R32C MCU. Look for section 5.3 in the document E8a Emulator
Additional Document for User's Manual documentation.renesas.com/.../r20ut0607ej0700_e8a_r32c.pdf
I'm using the E30a. We don't have an E8A :(.
All the E30a manual says is: "A user program can be debugged by using the MCU’s internal watchdog timer if so desired. When the watchdog timer is active, the debug monitor program refreshes it as necessary."
Not sure why this isn't working all of the sudden...
I see two options here. Either try out an E8A or create a ticket with TechSupport : am.renesas.com/.../tech_support
I submitted a ticket last week with not much traction...
Thanks for the help, hopefully it will get resolved. For now i just disabled the WDT in my code and it's working.