Re: [Flashforth-devel] PIC18fxxk90

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

There is no support in FF-PIC18 for the second UART.

It should be easy to change the uart1 registers to uart2 registers
in the source code. Some support in the config could even be introduced 
for that.

I am reluctant to increase the code size in FF-PIC18 because then users 
have to select between
multiple linker files.

There has been a request before to add better error handling.
There was suggestion to have a unique error string like ???
so that the uploader script could pause and ask if the upload should be
abandoned.

Igor wrote a Teraterm uploader script for that.
https://github.com/igor-m/EXPERIMENTAL_ZZ/blob/master/shell/Upload2FF.ttl

A deferred word is flexible and it could have a default value of "emit 
?"

I could put in a deferred word for the error printout.
It would be global a ram defer initialized at warm start.
You would need to defer it again in turnkey if you want to have 
automatic initialization.

It could also have a default string to be set at compilation time.

One problem with the bell is that it will sound once for every missing 
marker,
which not an error as such.
It will also sound for redefinition of words.

BR Mikael

On 26.04.2016 01:01, zd...@al... wrote:
> Hi, everyone,
>
> Two months after my start with FF I finally have the combination I've
> been looking for: PIC18F65K90 working in FF.
> http://www.alara.hr/images/K90.jpg
> Debugging with 66K22 has paid off and this time it worked on the 
> first
> try. There is FTDI USB to UART which also supplies 3.3V for PIC, and
> just 10 capacitors + 5 resistors. Totally Plug@Play. It can be used 
> for
> anything as the most of PIC pins can be accesed via 2 x 16 pin
> connectors. I'll put a custom LCD on it, battery supply, quartz for 
> real
> time clock, and move communication to UART2 because LCD needs UART1
> pins.
> As the PICs 24 and bigger have support for both UART, hope this will 
> not
> be a big problem to implement.
>
> There is one thing that I'm not happy with: FF error reporting. It is
> hard to notice a question mark(s) when you compile 200 lines, and I
> would like to have a 'beep' for each error. Is it possible to make a
> vector which is executed on each error so I can choose if it just 
> prints
> "?" (by default) or add a character like ctrl-g which makes sound on
> terminal, or attributes for inverted or flashing letters?
> Does it make sense?
>
> Zdravko
>
>
> 
> ------------------------------------------------------------------------------
> Find and fix application performance issues faster with Applications 
> Manager
> Applications Manager provides deep performance insights into multiple
> tiers of
> your business applications. It resolves application problems quickly 
> and
> reduces your MTTR. Get your free trial!
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> _______________________________________________
> Flashforth-devel mailing list
> Fla...@li...
> https://lists.sourceforge.net/lists/listinfo/flashforth-devel