R32C (R5F64112) device continually resets after loading program with E30A emulator

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:

  1. Cycled power to the E30a emulator.
  2. Restarted my computer ( :-) )
  3. Verified the NSD line (no shorts, etc.) on both units.
  4. Reverted back to an older SW build, same issue occurs.
  5. Tried multiple addresses for "Work Area For Monitor Program" setting on the MCU "Init" window tab.

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?

Parents
  • 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.


    BR

    Frank

  • Frank,

    How do i verify the reset was triggered by the watchdog?

    I removed all monitored variables from the watch list.

    Thanks,

    Mike

  • 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.

Reply
  • 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.

Children