Re: [Amforth] uploading files on arduino UNO

[Erich W. <ew....@na...>]

Hi,

I just remembered that I received a package of stuff the other
day and got out a brand new uno ...

>
> 2.
> the controller goes out of reset and starts the amforth
> system. The last thing it does is printing out
>
> amforth 4.6 ATmega328P
>  >
>
> The first line is the output of ver. The second line is
> the ok prompt. Nothing new here.
>
> HOWEVER, at this point in time you are NOT connected
> with amforth-upload.py. (You may be connected with minicom,
> then you see this output).
>
> 3.
> Now (assuming no minicom or other terminal is connected)
> amforth-upload.py opens the serial port and reads the above
> characters *again*. They are not sent, when amforth-upload.py
> opens the serial port. I suspect, that there is a fifo-buffer
> in the usb-serial stuff not being cleared.

This may be wrong. I observe that connecting to the Uno with
minicom will *always* produce this output.

amforth 4.6 ATmega328P Forthduino
 >

Whereas a duemilanove will not.

As a quick test I added 37 statements (I didn't grok how to write a
for(i=0; i<37; i++) { read one char; } statement in python ;-)

         i = tty_dev.read(1)

between line
	tty_dev = file(tty_dev_name,"r+",0)

and lines
	if len(args)<1:
		if verbose:
			print >>sys.stderr, "processing stdin"
		write_file_flow(sys.stdin,tty_dev)
	else:

And *drum roll*
$ make marker CONSOLE=/dev/ttyACM0
amforth-upload.py  -t /dev/ttyACM0 lib/misc.frt
: erase
  ok  0 fill
  ok;
  ok
 > : .(
  ok   [char] ) word count type
word ?? -13 16
 >

Well almost. It fails on something else now.


> One key difference between the duemilanove and the uno is its
> connection from serial (controller) to the USB plug of the board.

So it seems to me, connecting to the uno will cause it to reset.
Strange concept.


Cheers,
Erich