Re: [Flashforth-devel] re V 3.8 runing in 4550

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

No need to send me the project files.

The startup sequence in WARM is such that if turnkey contains something else
than 0 or FFFF, it assumed to be a valid word address.
If it is some crap you normally get cyclic restarts.

If turnkey contains FFFF, then EMPTY is executed in startup.
This is the case when you have erased the eeprom.

So your eeprom turnkey contained neither zero or FFFF when you had the 
problem.

You test this by
$ffff is turnkey <cr>
warm <cr>

After this you should have an empty device.

Now, when you set the eeprom to 00, FlashForth itself did not reprogram 
the eeprom.
So in this case it must be that the hex file contained the correct 
eeprom info
which your programmer put into the eeprom.

BR Mike

On 10/20/2013 10:31 AM, Neil Shuker-Harris wrote:
>
> Hi Mikael,
>
> Thank you for your reply.
>
> Executing empty fixed the problem completely.
>
> Your suggestion about the eeprom not getting programmed correctly had 
> me look at the way I had programmed the device. I found that 
> mikroelektronicas mikroprog suite defaults to putting FF in all 256 
> eeprom memory locations if you do not load it with anything else. I 
> have never had a problem with this in the past with other pic projects 
> so never thought to change it. I erased the eeprom using the facility 
> in mikropro , set the locations to 00 and reprogrammed the device and 
> worked first time with no need to execute empty.
>
> As this is now working do you still want the mplab project, 
> particularly as I am only using it to create the hex file.
>
> Neil
>
> *From:*Mikael Nordman [mailto:mik...@pp...]
> *Sent:* 19 October 2013 21:47
> *To:* fla...@li...
> *Subject:* Re: [Flashforth-devel] re V 3.8 runing in 4550
>
> It seems to me that for some reason the EEPROM does not get
> programmed correctly.
>
> Try to after ESC as the first command  give EMPTY.
> It should correct the EEPROM.
>
> Are you using FF3.8 or some development version from git ?
>
> Are you using  a bootloader ?
>
> If you can zip your exact mplab project to me, I can have a look.
>
> BR Mike
>
> On 10/19/2013 10:54 PM, Neil Shuker-Harris wrote:
>
>     Hi All,
>
>     With some direct help from Craig Bair I have succeed today in
>     compiling and loading FF into a 18f4550. My set up is an easypic 7
>     dev board 8mhz crystal oscillator. I am using the uart version of
>     FF with a mikroElektronika supplied usb to serial driver called
>     VCP for a FTDI FT232RL to a putty terminal which communicates in
>     both directions as expected.
>
>     When I switch the board on I get a the following line on screen
>
>     ESCFlashForth V3.8
>
>     which repeats around once per second.
>
>     I can interrupt this by pressing esc to get the interpreter as
>     suggested in the manual, but then about the only things I can do
>     then is type words which performs as expected by printing the
>     dictionary and ' .' which gives an 0 ok. 1 2 + . gives nothing
>     and  as with the other trials the above ESC etc starts scrolling
>     again. I do not have turnkey set as this is a new install and I
>     have as yet done nothing with it other than turn it on and the above.
>
>     Any ideas as to what this might be and how to fix it would be
>     welcomed.
>
>     Neil
>
>
>
>
>     ------------------------------------------------------------------------------
>
>     October Webinars: Code for Performance
>
>     Free Intel webinars can help you accelerate application performance.
>
>     Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
>
>     the latest Intel processors and coprocessors. See abstracts and register >
>
>     http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
>
>
>
>
>     _______________________________________________
>
>     Flashforth-devel mailing list
>
>     Fla...@li...  <mailto:Fla...@li...>
>
>     https://lists.sourceforge.net/lists/listinfo/flashforth-devel
>