|
From: <joe...@t-...> - 2007-03-30 08:19:35
|
Hi pix,
-----Original Message-----
> Date: Thu, 29 Mar 2007 01:28:25 +0200
> Subject: Re: amforth-upload.py
> From: pix
> To: "joe...@t-..."
> this is probably a dumb question, but does communication normally work
> in programs like minicom? my program is assuming that the tty is
> already set up with the right speed etc (running minicom will normally
> do that for you).
>
> have you tried uploading a very small, simple file, with perhaps just
> a simple definition, rather than a huge file? if you could do this and
> send me the file and the result of trying to upload it, that would be
> more helpful.
>
> eg:
>
> : inc 1 + ;
>
I appendet the output: of :
/usr/bin/python2.3 amforth-upload.py -v blocks/pytest.frt > output.txt
because it's long (stays in a loop...) I interrupted after waiting 10s
by
hitting ^C. The terminal output was:
joh@laptop:~/amforth/amforth-1.6$ /usr/bin/python2.3 amforth-upload.py
-v blocks/pytest.frt > output.txt
processing blocks/pytest.frt
sending line: : inc 1 + ;
((thats it))
((after pressing ^C))
Traceback (most recent call last):
File "amforth-upload.py", line 187, in ?
main(sys.argv[1:])
File "amforth-upload.py", line 181, in main
write_file_flow(in_file,tty_dev)
File "amforth-upload.py", line 120, in write_file_flow
write_line_flow(line,dest)
File "amforth-upload.py", line 55, in write_line_flow
i = dest.read(1)
KeyboardInterrupt
joh@laptop:~/amforth/amforth-1.6$
(minicom was not started, sending by the send.txt script (which was
proposed
by Matthias) works)
greetings
joh |