When trying to debug an application running on an RX64M (R5F564MFCDFB), the debugger always disconnects after a short while with the following message:
warning: Remote failure reply: E31Remote communication error. Target disconnected.: No error.Exception condition detected on fd 552
The debugger can connect to the device, program it, and I can single-step, set breakpoints and so on, but after a short while (less than a second when running without breakpoints) it always disconnects. Any ideas or hints on what's going on?
E2 Studio 4.02.008 on Windows 7, using an E1 with firmware version 2.04.00.001 (the same thing happens with an E20 emulator). The emulator is connected via JTAG, and changing the JTAG clock has no effect.
Sometimes once in a blue moon I have to reboot my PC, if all else fails. It happened today, I kept getting "disconnected from target debugger." Then I rebooted, did not change one thing, and I got a connection first try.
Fortunately in this case it turned out to just be a PEBKAC error. A software bug caused the CPU to unexpectedly turn off the power supply it was monitoring, but in our development environment the backup batteries were not connected and it turns out the RX64 can't run on good intentions alone.