Re: [Amforth] R: Re: R: Re: R: Re: R: Re: HW flow control

[Andreas Wagner]

On Mon, Aug 11, 2014 at 4:15 PM, Matthias Trute mtr...@web.de wrote:

 In an ideal world, at least. I like forth more than
 assembly.


amforth is Indirect-Threaded -- appropriate for a device with not much
flash space, but lately a lot of speed critical words have been re-written
in assembly which is sometimes an acceptable tradeoff for time-efficiency
but it means I need to reflash amforth every time I forget something among
other annoyances.

I have been thinking this past weekend -- why don't we have a word like
+dtc or a special colon such as dtc: to enable direct threaded
compilation of FORTH code for select words.

-Andreas
--
___
Amforth-devel mailing list for http://amforth.sf.net/
Amforth-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amforth-devel

Re: [Amforth] R: Re: R: Re: R: Re: R: Re: HW flow control

[Michael Kalus]

Good luck for your project.
Michael

Am 10.08.2014 um 16:22 schrieb Paolo Garro:

 Hi Michael,
 The Matthias implementation handles flow control once for each line.
 That's ok for me.
 Perhaps XON XOFF are not the right names... The goal is to manage a  
 ready/busy flag.
 The canonical SW flow control might work different but also the  
 echo control is not a standard.
 Using both of these we can write a good serial (custom) interface.
 Com device must be used with NO flow control being our a SW level  
 infomation rather than a communication state.

 Paolo

 Inviato da Samsung Mobile

  Original message 
 Subject: Re: [Amforth] R: Re:  R: Re:  R: Re:  HW flow control
 From: Michael Kalus mik.ka...@gmail.com
 To: Everything around amforth amforth-devel@lists.sourceforge.net
 CC:

 Never forget: xon/xoff is for *single* character exchange - send one,
 get echo,  check it, send another one...
 Sender must interpret *each* echo character immediately and stop at
 xoff at once.
 Use xon/xoff to connect two amforth devices via TXD/RXD.
 Or on a PC use a sending tool able to do that. amforth shell is such
 a tool.

 If you send ascii to amforth using a terminal emulator on your PC via
 a USB-serial converter, forget xon/xoff.
   There will be huge blocks of characters already send to the
 pipeline of USB, overrunning your forth target, before any terminal
 emulator will notice the xoff.

 Or do you have a USB-serial converter that handles xon/xoff ?

 Michael



 Am 10.08.2014 um 14:34 schrieb Paolo Garro:

 Hi Matthias,
 Does REFILL load a single line?
 In a multiline colon definition is it called for each line?
 If so I think the best place to handle XON/XOFF is QUIT itself.
 At the begin of the loop after calling REFILL assert XOFF and
 before closing the loop assert XON.
 That way transmission is blocked while the interpreter is working
 including the case of an error answer (xxx ?? -nn nn) and, on the
 other side, I will receive an XON at the end of each answer.

 Paolo

 Inviato da Samsung Mobilenull
 - 
 -
 
 ___
 Amforth-devel mailing list for http://amforth.sf.net/
 Amforth-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/amforth-devel


 -- 
 
 ___
 Amforth-devel mailing list for http://amforth.sf.net/
 Amforth-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/amforth-devel
 -- 
 
 ___
 Amforth-devel mailing list for http://amforth.sf.net/
 Amforth-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/amforth-devel


--
___
Amforth-devel mailing list for http://amforth.sf.net/
Amforth-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amforth-devel