Re: [Flashforth-devel] Loop at Bootup : Pic18f45k20

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

Richard,
If you download FlashForth dated 17.9.2018, the PIC18 code is changed
so that the PROMPT vector that executes .ST is now executed after the 
first line after reset/abort has been interpreted.

So even if your eeprom is corrupted, you can give the command EMPTY as 
first command after reset. It will initialize the eeprom correctly.

I had moved the PROMPT the beginning of QUIT to get it before the first 
line is input, but that took some of the robustness away. But now it's 
fixed.
The PIC24 and Atmega still has the original behaviour.

BR Mikael

On 2018-09-17 18:29, Mikael Nordman wrote:
> Another possibility is that your eeprom initialization fails.
> After the first ok has been printed, FlashForth tries to execute the 
> .st word.
> That seems to fail because there is some garbage in the eeprom.
> 
> You need to set your device programmer to erase the eeprom to 0xff.
> I have my pickit set to erase all memories before programming.
> 
> Otherwise FlashForth initialization will fail to initialize the .st
> vector correctly.
> 
> BR Mikael
> 
> On 2018-09-17 17:17, Richard Burden wrote:
>> The full "gibberish" is as follows:
>> 
>> [[BP FlashForth 5 PIC18F45K20 20.03.2018[[ ok SP? ok61937 50418 AD?
>> ok27633 50420 AD? ok14336 50422 AD? ok769 50424 AD? ok14336 50426 AD?
>> ok769 50428 AD? ok143
>>