Re: [Flashforth-devel] Flashfort and UNO-TFT display/ili9341

[Peter H. <p.h...@we...>]

Hello Mikael,
Our Gold Day is over and the guests have left.

Thanks for the rest of the routines. The do ... loop does not run for
the 328P and would probably have to be adapted?
I took it out and after a lot of trouble (I tested all 3 baud rates and
also old ff_uno.hex) as well as a better programme structure, the
complete 1100 lines run cleanly and without errors to the end on all 4
FF variants.
The old ff_uno.hex seems to perform slightly better than the current
version, but the TFT still does not display anything. In addition to my
Win/DOS terminals, I also communicated via TeraTerm and MyFFshell -->
the same results everywhere. As a Forth greenhorn, I'm at my wit's end!

I have now reduced the programme to bases & rectangles. Behaviour is
similar to the complete program/1100 lines.
If this short program can be realised in FF, the other basic functions
and programs will probably also work.

best regards
Peter
PS: Programme control via OptiForth/115200Bd is ok (runtime Win/DOS =>
12/8s )!


Am 22.08.2024 um 22:53 schrieb Peter Höhne:
>
> Hello Mikael,
> Thank you very much for the quick help.
>
> I am very pressed for time --> my wife's birthday is tomorrow and we
> are also celebrating our golden wedding anniversary!
>
> Nevertheless, I have installed/tested all the new functions. The do
> ... loop for the 2560 runs smoothly.
> I cannot judge whether it is correct for the 328P?
> The program has > 1100 lines and of course does not run through yet!
> Unfortunately I also noticed 3 missing functions: *mtst0 swap- sqr*. 
> But that should be it.
>
> Maybe you can check for these again?
>
> best regards
> Peter
> PS: We have a full house from tomorrow, as soon as I have free time
> again I will take a closer look at the processes.
>
>
> Am 22.08.2024 um 13:40 schrieb Mikael Nordman:
>>
>> Unfortunately the DO..LOOP is not for ATMEGA256 if you plan to use
>> that, but I could create it.
>>
>> 0until and 0if could be created, but could you give  a reference to
>> those words.
>> Google could not find it immediately.
>>