e2 how to connect manually with rl78-elf-gdb.exe to e2-server-gdb.exe
e2 how to connect manually with rl78-elf-gdb.exe to e2-server-gdb.exe
Hi,
I am currently trying to debug my rl78 using gdb by hand. To achieve this goal I launched e2-server-gdb.exe by hand using the same command e2studio use :
./e2-server-gdb.exe -g E1 -t R5F104EH -p 61234 -d 61236 -umFreq=0 -usFreq=0 -umClock=1 -w 0 -usupplyVoltage=0 -ucommMethod=0 -usecurityID=00000000000000000000 -upermitFlash=1 -uuseWideVoltageMode=1 -ueraseRom=1 -uuseOnChipDebug=0 -uuseUserOptionByte=0 -ustopTimerEmu=0 -ustopSerialEmu=0 -umaskInternalResetSignal=0 -umaskTargetResetSignal=0 -n 0 -uverifyOnWritingMemory=1 -uTraceCapture=0
This command produce this output :
GDBServer for Renesas targets. Version 5.2.0.019 (Sep 15 2016 13:41:01)
Starting server with the following options:
Raw options : C:\Renesas\e2_studio\DebugComp\e2-server-gdb.exe -g E1 -t R5F104EH -p 61234 -d 61236 -umFreq=0 -usFreq=0 -umClock=1 -w 0 -usupplyVoltage=0 -ucommMethod=0 -usecurityID=00000000000000000000 -upermitFlash=1 -uuseWideVoltageMode=1 -ueraseRom=1 -uuseOnChipDebug=0 -uuseUserOptionByte=0 -ustopTimerEmu=0 -ustopSerialEmu=0 -umaskInternalResetSignal=0 -umaskTargetResetSignal=0 -n 0 -uverifyOnWritingMemory=1 -uTraceCapture=0
Warning: Rejecting illegal command line argument 13: 0Connecting to E1/E20, RL78 Target
GDBServer endian : little
Target power : off
Starting target connection
Finished target connection
This looks normal, but when I try to connect to it using rl78-elf-gdb.exe launching this command :
target remote :61234
I’ve got this error :
Remote debugging using :61234
warning: unrecognized item “swbreak” in “qSupported” response
warning: unrecognized item “hwbreak” in “qSupported” response
../../RL78_python_GDB/gdb/thread.c:85: internal-error: inferior_thread: Assertion `tp’ failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) [answered Y; input not from terminal]This is a bug, please report it. For instructions, see:
<http://www.gnu.org/software/gdb/bugs/>.../../RL78_python_GDB/gdb/thread.c:85: internal-error: inferior_thread: Assertion `tp’ failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) [answered Y; input not from terminal]This application has requested the Runtime to terminate it in an unusual way.
Please contact the application’s support team for more information.
Do you know what I need to do to connect to the e2-server-gdb.exe ?
Thanks for your time,
Best Regards,
Hello,
We recommend that you issue the command below, prior to executing the command “target extended-remote localhost:61234”, so we can try to isolate and identify the problem faster:
set non-stop on
The purpose of this command is to allow you to control threads explicitly in ways that are not possible in all-stop mode — for example, stepping one thread while allowing others to run freely, stepping one thread while holding all others stopped, or stepping several threads independently and simultaneously.
More information about this command can be found here : https://sourceware.org/gdb/onlinedocs/gdb/Non_002dStop-Mode.html
If you need help or directions on how to achieve this, or have any further questions, please let us know.
Best regards,
Andreea
The GNU Tools Team
Hello,
Please try “target extended-remote localhost:61234”. Please also check the GDB and GDB Server Traces in e2Studio as they contain other steps required for a successful connection and setup.
–
Best Regards,
Grigore Dobra,
The GNU Tools Team