Re: [Amforth] Made some progress
Tristan, Thank you for the prompt reply! Please see my comments below On Tue, Apr 30, 2019 at 12:01 PM Tristan Williams wrote: > > I am interested to know what eval hardware you are using. > I am using an Olimex AVR-CAN: https://www.olimex.com/Products/AVR/Development/AVR-CAN/ > > I have not used this device, but I think > amforth-6.8/avr8/devices/at90can128/at90can128.frt has the constants > and these can be sent to the mcu with various tools, including > amforth-shell.py which can do many other things too. > > http://amforth.sourceforge.net/TG/recipes/Upload.html?highlight=upload > > > A lot more words are available as forth code, rather than built-in. > To use them send the forth code to the mcu as above. From amforth-6.8 > directory > > find . -name *.frt > > will show where the files are. amforth-shell.py helps a lot with > including files. > > I also found the technical guide and cookbook really helpful. > > http://amforth.sourceforge.net/TG/TG.html > http://amforth.sourceforge.net/TG/Cookbook.html > > Kind regards, > Tristan > I will try that. Thank you for pointing me in the right direction. Terry ___ Amforth-devel mailing list for http://amforth.sf.net/ Amforth-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amforth-devel
Re: [Amforth] Made some progress
Hello Terry, > I moved my builds to Linux and I can now build a working set of .hex files > that run on my eval hardware without errors or warnings. I am interested to know what eval hardware you are using. > Though there are some parts that appear to be missing, in particular > the various PORTX constants I have not used this device, but I think amforth-6.8/avr8/devices/at90can128/at90can128.frt has the constants and these can be sent to the mcu with various tools, including amforth-shell.py which can do many other things too. http://amforth.sourceforge.net/TG/recipes/Upload.html?highlight=upload > and the words that operate on them (like pinport). A lot more words are available as forth code, rather than built-in. To use them send the forth code to the mcu as above. From amforth-6.8 directory find . -name *.frt will show where the files are. amforth-shell.py helps a lot with including files. I also found the technical guide and cookbook really helpful. http://amforth.sourceforge.net/TG/TG.html http://amforth.sourceforge.net/TG/Cookbook.html Kind regards, Tristan ___ Amforth-devel mailing list for http://amforth.sf.net/ Amforth-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amforth-devel
[Amforth] Made some progress
I moved my builds to Linux and I can now build a working set of .hex files that run on my eval hardware without errors or warnings. Though there are some parts that appear to be missing, in particular the various PORTX constants and the words that operate on them (like pinport). When looking at the .lst file generated as part of the build process I see that last .set for each port is: .set WANT_PORTA = 1 >From my understanding this is all that should be needed to get the constants included. My Makefile defines the MCU as: MCU=at90can128 Any idea what I am missing? Thanks Terry ___ Amforth-devel mailing list for http://amforth.sf.net/ Amforth-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amforth-devel
