Re: [Flashforth-devel] building larger program words -- arduino mega2560 FF5

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

Craig,
The symptoms seems to point to that you are writing in to places you 
shud not.

When you upload your code. Are you sure there are no errors ?

"ESC" means there is a turnkey value greater than zero and less than 
$ffff.
Does it point somewhere meaningful ?

If your ms is too slow, you have written something into
$44(TCCR0A==2),$45(TCCR0B==3),$47(OCR0A==$f9) or $6e(TIMSK0==2)
Check that the values are as indicated above.
  hex 44 c@ 45 c@ 47 c@ 6e c@

Not reacting to incoming UART data can be caused by the RX0 interrupt 
vector being overwritten in ram.
But, it is inited in "warm" so probably it is OK.

Slowness in the code can also be caused by using a variable that is 
located in flash or eeprom.
That could wear them out quite fast.
I have a habit of using "fl-" in the beginning of my main word, it will 
lock
the flash and eeprom writes and restart FF in case there are attempts to 
write to either one.
In case you have code that that writes to flash or eeprom in a loop, the 
chip will start to malfunction,
as the memory wears out.

BR Mikael


On 2021-04-05 02:25, craig bair via Flashforth-devel wrote:
> I did an "empty" and started over.  I've got my basic survival extras
> (without the vt100 emu) in a file so I can just run it into the system
> first thing.  I then loaded in the part I posted and that went ok.  I
> added the routines to convert the raw data to temp&Humidity numbers
> then cold restarted it.  It announces its system & compile date then
> the next line says "ESC" the cursor stays there and nothing else comes
> out.  The led blips with each entered keystroke, but nothing seems to
> be happening.  I'll probably have to wipe it and run the systen .HEX
> file into it when I get back to work in the morning.  I think I'll set
> up a second duino as a backup at the same time.