
Search found 24 matches
- Sat Aug 31, 2013 1:27 pm
- Forum: [E] Support
- Topic: Next step after telnet access?
- Replies: 37
- Views: 22957
Re: Next step after telnet access?
yeah, probably i should finally give this library injection tool of yours a try 

- Sat Aug 31, 2013 12:13 pm
- Forum: [E] Support
- Topic: Next step after telnet access?
- Replies: 37
- Views: 22957
Re: Next step after telnet access?
well, debugging somehow works. i think it's sufficient for now but it's still a tedious process because lots of reboots are involved, requiring me to manually run the telnet enabler, memjack, gdbserver, micom, putty and whatnot after each reboot. at some point i got fed up so i suspended my little p...
- Sun Aug 18, 2013 5:43 pm
- Forum: [E] Support
- Topic: Next step after telnet access?
- Replies: 37
- Views: 22957
Re: Next step after telnet access?
remote debugging still doesn't work but I'm one step closer to getting it to work. Theres a binary, 'micom', on my ESXX6100 which has "undocumented" commands, such as "watchdog_off" which lets you turn off the watchdog. This allows exeDSP to be debugged without the TV rebooting. ...
- Sat Aug 17, 2013 1:55 pm
- Forum: [E] Support
- Topic: Next step after telnet access?
- Replies: 37
- Views: 22957
Re: Next step after telnet access?
thanks. appears to work better but my tv still reboots, due to a watchdog i guess? I've been told in a PM that additional libraries need patching.
- Sat Aug 17, 2013 12:47 pm
- Forum: [E] Support
- Topic: Next step after telnet access?
- Replies: 37
- Views: 22957
Re: Next step after telnet access?
breakpoints seem to not be handled correctly. I tried debugging with the armlinux_server binary that is shipped with IDA. It works better than gdb for me but still, breakpoints aren't handled correctly (and so isn't single stepping). I.e. the debugging client is not being notified about a breakpoint...
- Sat Aug 17, 2013 8:54 am
- Forum: [E] Support
- Topic: Next step after telnet access?
- Replies: 37
- Views: 22957
Re: Next step after telnet access?
good :) memjack worked fine for me after I had adjusted the patch structure to my exeDSP version, so it does not cause my TV to reboot due to having detected a debugger. Still, I haven't been able to properly debug exeDSP using IDA and gdbremote. Also haven't yet figured out why it doesn't work and ...
- Thu Aug 15, 2013 5:40 pm
- Forum: [E] Support
- Topic: Next step after telnet access?
- Replies: 37
- Views: 22957
Re: Next step after telnet access?
Thanks, it works using the samsung toolchain 

- Thu Aug 15, 2013 1:32 pm
- Forum: [F] Software
- Topic: samyGOso (.so injection - patching exeDSP/exeAPP)
- Replies: 127
- Views: 152543
Re: .so injection
Hmm.. found this via google as well. I think I'll just try the samsung toolchain. Thanks!
edit: the samsung toolchain worked flawlessly, thanks!
edit: the samsung toolchain worked flawlessly, thanks!
- Thu Aug 15, 2013 1:13 pm
- Forum: [E] Support
- Topic: Next step after telnet access?
- Replies: 37
- Views: 22957
Re: Next step after telnet access?
the one from svn that you pointed me to.
edit: the samsung toolchain did it, thanks
edit: the samsung toolchain did it, thanks

- Thu Aug 15, 2013 12:58 pm
- Forum: [F] Software
- Topic: samyGOso (.so injection - patching exeDSP/exeAPP)
- Replies: 127
- Views: 152543
Re: .so injection
I'm currently stuck at trying memjack to compile (I have stated this in another thread but I think this thread should be more appropriate). dennis@ubuntu:~/Downloads/memjack$ make arm-v7a8v2r2-linux-gnueabi-gcc memjack.o util.o procutils.o -o memjack arm-v7a8v2r2-linux-gnueabi-gcc: selected multilib...