This setup has been working for months now.
Suddenly I get this error
GDB Server for Renesas targets. Version 9.0.0.v20221226-025508 [2de64c59] (Jan 6 2023 16:58:54)
Starting server with the following options: Raw options : C:\Users\sperlm\.eclipse\com.renesas.platform_1435879475\DebugComp\\RA\e2-server-gdb -g E2LITE -t R7FA2E1A9 -uConnectionTimeout= 30 -uClockSrc= 0 -uAllowClockSourceInternal= 1 -uInteface= SWD -uIfSpeed= auto -w 0 -z 33 -uIdCodeBytes= FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF -uResetCon= 1 -uLowPower= 1 -uresetOnReload= 1 -n 0 -uFlashBp= 0 -uhookWorkRamSize= 0x400 -ueraseRomOnDownload= 0 -ueraseDataRomOnDownload= 0 -uTraceMTB= 0 -uTraceSizeMTB= 1024 -uProgReWriteIRom= 0 -uProgReWriteDFlash= 0 -uOSRestriction= 0 -uTimeMeasurementEnable= 1 -uMemRegion= 0x00000000:0x20000:FLASH:e -uMemRegion= 0x40100000:0x1000:DATA_FLASH:e -l -uCore= SINGLE_CORE|enabled|1|main -uSyncMode= async -uFirstGDB= main --english --gdbVersion= 7.2
Connecting to E2LITE, ARM target GDBServer endian : little Target power from emulator : Off Starting target connectionGDB action 'connect to target', has failed with error report, Error 0x00030806: First communications connection with the target MCU cannot be made normally.DAP cannot be found in the connection target.Check the connection target or lower the JTAG/SWD clock frequency.
force_kill_gdb()Disconnected from the Target Debugger.
Does this mean I have blown my board?
The existing program is still running fine.
Hello!Thank you for your message and reaching through our Renesas Community. First, would like to confirm the hardware module that you are currently using. Can you also tell me more of what happened prior to error being observed? Anything, unusual in particular? Details on this would be helpful with your concern.Nevertheless, this thread my also help you out. This says there is some issues with your IDE and some EMC concern with the HW. https://community.renesas.com/tools/e2studio/f/e2studio-forum/29970/error-0x00030806---how-to-recoverHope this helps.
If this response, or one provided by another user, answers your question, please verify the answer. Thank you!
Renesas Engineering Community Moderatorhttps://community.renesas.com/https://academy.renesas.com/https://en-support.renesas.com/knowledgeBase/
A similar issue was caused because of a damaged cable connection between the board and the emulator: