Really I would think that simply running fs-cifs on your target and mounting a share on your windows machine would be 
easiest
to implement?  Then all your app needs to do it to telnet to your box and run the appropriate binary, loading it 
directly from
your windows disk.

Aleksandar Ristovski wrote:
> Pete Darnell wrote:
>> A debugging tool is precisely what I'm after. I want to do exactly what gdb/pdebug/qconn do now. I definitely don't 
want to create an OS image with my process in it, I want to interactively download my executable to an existing Neutrino
 target just as Momentics/gdb does. 
>> I would rather not reinvent the wheel with sockets if I don't have to. Is the pdebug interface not documented?
> 
> Pdebug 'talks' its own binary protocol; for communication it uses TCP/IP (sockets), serial line or std in/out. It 
would not be trivial to create your own client for pdebug. Qconn starts pdebug for debugging sessions. Maybe qconn has 
some higher level abstractions that would allow some scripting, but I am not too familiar with it, maybe Elena can give 
some insight.
> 
> However, if only downloading to the target is what you need, then you can use ftp. You will need ftp server on the 
target, and then you can use windows ftp client to transfer the binary to the target. 
> 
> If you need more control over your target, you can telnet to it and then you can run applications on it. If you want 
the connection to be secure, you can use ssh (but I think you would have to build it yourself, check our bazaar maybe 
there is a prebuilt binary).
> 
> What does this mean: "...and communicate data back and forth with the process while it runs on the NTO target"... what
 kind of data, and how is the communication done? Is it simply getting some input from command line and printing 
something as a result? If so, you can use ftp/Telnet combination described above.
> 
> 
> I hope this helps, but your description of what you want to do is somewhat vague. Please provide more detail on what 
exactly you want to do. 
> 
> 
> 
> 
> 
> _______________________________________________
> QNX Momentics Community Support
> http://community.qnx.com/sf/go/post10309
> 

-- 
cburgess@qnx.com

> If you want to do what qconn does use sockets - it is very simple
> If you want to USE qconn to transfer data using different client on host 
> site it is really easy too, what language do you want to write it on? I 
> can send you perl script that can upload and launch on target using 
> qconn daemon.

Thanks Elena. I want to do as little work as possible to get the job done. Using qconn would seem to be the best path if
 I can do it. C/C++ is my preferred language, but I'll take a perl script if that's what you have.

To give all you helpful folks the big picture, I am with Visual Solutions. We have an app, VisSim, which allows control 
engineers to draw diagrams of their control solution. VisSim can simulate the diagram which may contain differential 
equations, nasty feedback, digital filters, nonlinearities etc. We also allow C code generation from the diagram and 
automatic compile to a target app. Currently we target DSPs. The DSP solution allows automatic download to target, and 
lets the VisSim user provide inputs to target app via buttons, sliders from VisSim on PC Windows, and can view results 
from the target app via plots, meters, etc in VisSim. Historically, we have used JTAG and serial ports for this. We 
would like to extend this interface to QNX, and are looking for the best path.

I'm interested in this as well, could you send the Perl script to me?

Thanks.