2015-01-31 10:12 GMT+01:00, Matthias Trute <mtr...@web.de>: > Thus if you want to place them at different memories, that would > require changes in the core system: the inner interpreter, > the words , (comma), compile, >body and execute. Maybe a few > more as well.
Yes, I'm aware of this. I was hoping to get some help here, how to (re)configure AmForth to make it work with the thing the way I want. >> You know, what >> I'm after: to have "basic" Forth system burned into FlashRAM, and then >> - as usual - to interactively develop the software for the little >> machine using that 128 KB SRAM the guy selected for his design. > > To keep it simple(r), I'd recommend to separate the memories. Leave > the flash for forth, and let the 6502 operate the RAM. The initial > RAM content may come from flash. The flash may provide a block > storage service for the 6502 system as well (floppy emulator?). But I don't need 6502 emulation layer; I will examine it, it's nice thing, but it's not what I'm after. I would to use AmForth as OS for the little machine. It's possible - I'm during analysis of the text recommended by Erich - just it's not that easy for me. But now I know, it's feasible when using indirect-threaded Forth. So giving up the Flash would be a waste. Why? What for? Certainly it can and should work the way I require. -- Z. ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Amforth-devel mailing list for http://amforth.sf.net/ Amforth-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amforth-devel
