Erich Waelde <ew.fo...@nassur.net> writes:
> Hi,
>
> On 11/24/2013 07:13 PM, Enoch wrote:
>> Dear Matthias,
>>
>> I understand that Mikael ("FlashForth") represents "the competition" but
>> his point, in my opinion, cannot be ignored. All those frequently
>> changing variables from amforth-eprom.inc should not stay just EEPROM
>> based:
>>
>> EE_DP: ; Dictionary Pointer
>> EE_HERE: ; Memory Allocation
>> EE_EDP: ; EEProm Memory Allocation
>>
>> I intend to fix that in my amforth-shadow git but I prefer that you
>> would take the lead.
>>
>> The solution is simple, XT_DP, XT_HERE and XT_EDP should be RAM
>> variables that are initialized from the EEPROM on cold start. A new
>> immediate word, let's say "eesy" (EEPROM sync), would do the RAM to EE
>> sync. To be on the safe side let tools/amforth-shell.py issue this
>> "eesy" for us automatically before exit...
>
> Hmm. If I understand your approach correctly: *I* have to call eesy before
> powering down the controller. Otherwise my newly compiled words are lost?
> And *frequently* means exactly: every time the compiler is run or , and
> friends
> are called (I use up flash space).
>
> Do I miss something?
My workflow is probably different than yours. I do programming and
simple word test via amforth-shell.py but leave it often for a full
system test with a connected ANSI terminal emulator. Each time I leave
the shell the EEPROM would get in sync with the RAM.
> I can confirm what Matthias said earlier:
> I have a bunch of atmega32 controllers, which I use since I started with avr
> controllers 10 years ago. They are thus far not exhibiting any behaviour that
> would
> point to bad eeprom or flash.
>
> Just my 2 cent.
What does it prove... that you are both some very lucky guys ;-)
Cheers, Enoch.
------------------------------------------------------------------------------
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing
conversations that shape the rapidly evolving mobile landscape. Sign up now.
http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
_______________________________________________
Amforth-devel mailing list for http://amforth.sf.net/
Amforth-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amforth-devel
