I am using the E2 programmer with e2 studio and RX700 processor from my windows 10 64 bit PC
Most of the time this runs fine, however some times the debug session does not close properly and it prompts to try again or clear.
When I get this, I usually find that e2-studio-gdb.exe is frozen and even task manager cannot kill it.
The only way to get the debugger running again is to restart the PC.
However, when I restart the PC, the shutdown always gives a blue screen with DRIVER_POWER_STATE_FAILURE message.
Has anyone else had this lockup occur, how did you get around it?
My E2 Studio is latest and E2 emulator is up to date with latest firmware.
Version: 2024-01.1 (24.1.1)
Build Id: R20240125-1623
GNU gdb (GDB) 7.8.2-20231014
Bazza,
Can't say that I have seen this before. My suggestioin is when it hangs try unplugging the USB cable from the debugger or power down the target to exit the debug mode and see if that helps get around this issue.
Hello, unplugging and plugging in the USB cable makes no difference, the e2-gdb-server.exe stays running and the only way to stop it is to restart the PC. When I restart the PC, I get a blue screen hardware error because the USB is blocked by the e2-gdb-server.exe
Should also add, debugger is not powering the target and un powering the target also does not clear the debugger from hanging. The Debugger itself is directly connected to a motherboard USB port on windows 10 PC< it is not via a hub,
Do you use dynamic printf or the virtual console? does it just happen occasionally?
Some times, yes I have used the Virtual Console, and no I have not seen this happen.
I have sent a query to development to see if they have any comments.