Re: [Flashforth-devel] PIC production question

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

I have never tried this procedure but I guess it should work if you just
remember to save and program the flash and eeprom contents.

Eeprom contains the turnkey pointer and the memory allocation pointers.

If you just leave the turnkey as $ffff of an empty deleted eeprom,
FF will reset the memory allocation pointers and the trunkey will be lost.

I would also recommend to have a turnkey word that disables writes to 
flash and eeprom with FL- .

Mike

On 07.05.2015 21:38, Daniel LaRue wrote:
> Folks,
>
> The interactive nature of Forth has many development advantages.  But I
> am curious how people are putting their Forth code into production?
> Loading a PICs flash with a hex file is the traditional way to put code
> into production.  Sending ascii based source files into the Forth
> interpreter seems error prone. Maybe the following steps are a way…
>
> 1.Send source into Forth interpreter via serial port.
>
> 2.Read flash via a PIC programmer to create a hex file image of Forth
> and all compiled words.
>
> 3.Test code to verify proper operation.
>
> 4.Put hex file from step 2 into production.
>
> Thanks for any discussion on practices.
>
> Dan