Re: [Flashforth-devel] free flash memory on atmega devices
Brought to you by:
oh2aun
From: Donald G. <dgo...@sb...> - 2015-11-16 16:47:54
|
I don't think a 32 bit version of FlashForth would be necessary. You can build a very complex application in Forth just using the 16 bit implementation. If you need a request for extended memory words, I will vote yes they are needed. Users can then put arrays, small databases of sensor data logging, etc. in this space... I will need these words in the future, myself. Great job on the design of FlashForth, keep up the good work!Don On Sunday, November 15, 2015 11:00 AM, Mikael Nordman <mik...@fl...> wrote: You are right that extended memory words could be made for data storage or even for code in flash. But I have chosen not to implement that, since there has been no demand. All my FF programs have been fairly compact fitting well within the 16-bit limits. One reason to support the larger chips is to get access to the peripherals, even if all memory cannot be adressed. Another alternative would be to implement a 32-bit FF. Then all memory would be adressable. BR Mikael On 15.11.2015 19:41, Donald Golding wrote: > You should have an extended memory word to address all of memory, > right? > > Since this is a 16 bit Forth implementation, it is understandable > that > it can only address 64K words. However, we should be able to address > all of the memory for data in the processor. > > I haven't started using FlashForth yet, so my comments are not based > on knowledge of FlashForth. > > Don > ------------------------------------------------------------------------------ _______________________________________________ Flashforth-devel mailing list Fla...@li... https://lists.sourceforge.net/lists/listinfo/flashforth-devel |