world leader in high performance signal processing
Trace: » discussion

Discussion page (experimental)

executable start on target device

tool-setup
(rob) As pointed out here, an application that is started remotely via rsh does not output printfs until the program is finished. This is also valid when the program is started directly, i.e. without gdbserver, e.g. from a shell where rsh is invoked with the appropriate arguments. Any interactive shell as e.g. telnet operate OK in this respect, but this shell is interactive, and so not suitable for usage within Eclipse.

Regarding the alternative target program execution from the remote side: It would be great when this can be established also from an external tool entry. However, a remote program invocation will always send stdout to the host. Perhaps a trick could apply. Here is one proposal:

Target program execution with local printf output can be established with a modified rsh call:
rsh -l root 192.168.1.70 ./test ”>” /dev/ttyBF0
Doing /dev/stdout proved to fail. The host responds with “can't create”, despite presence of /dev/stdout in the target.

(rob) Follow-up rsh remote command invocation: when the target program started this way opens another program via a pipe (popen()), its stdout is output immediately (i.e. visible in Eclipse's console view. Just look at the screenshot below. It can be seen that both printf commands appear in the console window as final output.
Forcing local output as outlined above behaves correct (i.e. printf() outputs immediately)

Blackfin Debug Targets

tool-setup
(rob) Invocation of this entry: An internal error occurred during: “Launching test Debug”. java.lang.NullPointerException