Quote:
Originally Posted by davidfor
Add the following to the config file:
Code:
[DeveloperSettings]
EnableDebugServices=true
This writes to a file in the .kobo directory with name including the timestamp, such as "syslog-2015.06.10-20.41.21". It gets written when you restart or connect to the PC. Plus the last two or three firmware versions have a button to save the log on the "Device information" page of the settings.
If anyone you add this, watch the battery. This also enables telnet and if WiFi is active, it doesn't time out and the auto sleep/power off doesn't kick in. A sleep cover still works. |
Cool. I'll have to try this later.
Another Question....
I see in the KOBO-labs git hub repository, that the cross compiler binaries are also compiled with remote gdb capability. eg: arm-linux-gnueabihf-gdb and arm-none-linux-gnueabi-gdb both exist that will run on an x86PC but should debug an arm binary remotely.
So, these ought to be ready to talk to a gdb proxy on the Kobo, and allow me to do debugging remotely (at least on programs I compile myself with -ggdb3).
But -- i don't see a gdbstub, or gdbproxy binary compiled for Arm in the repository.
Do you know where the GDB proxy binary might be found, or how it could be enabled, so I can do remote debugging ?