Re: [Flashforth-devel] FF tutorial and guide

[Mikael N. <mik...@pp...>]

Myself, I have never used an USB-UART bridge with FlashForth.
I suppose one would use SW flow control with that.
Maybe some extra TX delays could be needed for that, if the latency of 
the bridge is high.

Mike

On 10.10.2012 15:52, Peter Jacobs wrote:
> Mike, Pete,
>      Thanks for the useful and very encouraging comments.
> I'll probably get to work on this again over the weekend when
> I'll dust off an old Windows machine and try out the various
> terminal programs that the students are likely to use.
>      So far, I've been concentrating on just using the UART
> interface on the MCU and in all cases have used one of
> several USB-to-UART bridges that I have available.  Much
> of the custom instrumentation that interests me is timing
> sensitive and I want to minimize the number of things that
> the MCU has to deal with.
>      You are most welcome to put the documents on the FF
> web.  In the next few days (hopefully), I'll clean up the
> issues that you've identified.
> Cheers,
> Peter J.
>
>
> On 09/10/12 06:02, Mikael Nordman wrote:
>> Hi Peter,
>> Firstly, I want to say what a nice tutorial it is.
>> --
>> About the tutorial and flow control.
>>
>> In the cutecom picture you combine the USB with SW flow control.
>> With the USB interface one must use HW flow control.
>> The intercharacter delay is not needed.
>>
>> With the UART and SW flow control, no delays should be needed
>> when you set the UART into low latency mode(linux)
>> or remove the UART FIFOs from use(windows).
>>
>> Having the delay there makes the serial operation just work, but it also
>> makes loading of files quite slow.
>>
>> --
>> About the hitchikers guide.
>>
>> Do not call VALUE VNAME a variable, but just call it value VNAME.
>> Explain that TO sets a new value into the VNAME.
>>
>> Formatted strings are constructed before the PAD in the end of TIB.
>> Not in PAD which has 0 as default size.
>>
>> If you are using the default values of the p18f-main.cfg
>> the following is valid for the UART  version.
>> SRAM is further subdivided as:
>> $f000 - $f03f 64-byte flash write buffer
>> $f040 - $f05f 32-byte used internall by FF
>> $f060 - $f06f 16-byte interrupt parameter stack
>> $f070 - $f093 36-byte RX an TX buffers
>> $f094 - $f09d 10-byte mirror of turnkey, dp, latest
>> $f09e - $f09f 2-byte interrupt vector
>> $f0a0 - $foa1 2-byte user pointer
>> $f0a2 - $f1b1 user area for operator task
>> $f1b2 - $ff5f free for application use (up to RAM HI)
>> $ff60 - $ffff special function registers
>>
>> --
>> May I store copies of these documents on the FF web ?
>>
>> / Mike
>>
>>
>
>
> ------------------------------------------------------------------------------
> Don't let slow site performance ruin your business. Deploy New Relic APM
> Deploy New Relic app performance management and know exactly
> what is happening inside your Ruby, Python, PHP, Java, and .NET app
> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> http://p.sf.net/sfu/newrelic-dev2dev
> _______________________________________________
> Flashforth-devel mailing list
> Fla...@li...
> https://lists.sourceforge.net/lists/listinfo/flashforth-devel
>