Hi Helge, A mystery, but given that, as far as I know, every (modern) build eventually uses avrasm2.exe to create the hex files, one that should be solvable. Given that you have an UNO build working, I can only think that your atmega2560 build is not finding all the needed files (or finding some it shouldn't) or that the build target is not actually an atmega2560.
I use a Makefile based build (on macos) that is based on the one that is part of the distribution. I can send you an archive with the Makefile, list file, etc. for you to check over. I don't have access to a Windows machine or I would try to replicate what you are doing. Kind regards, Tristan On 08Sep21 19:40, Helge Kruse wrote: > > On 08.09.2021 17:45, Tristan Williams wrote: > > Hi Helge, > > > > Glad you got AmForth to build with an atmega328p. > > > > Can you make avrasm2.exe output a list file, re-build and then check > > the list file for lines containing store-i ? > > > > For the atmega2560 I would expect > > > > .include "words/store-i.asm" > > .include "words/store-i_big.asm" > > > > For the atmega328p I would expect > > > > .include "words/store-i.asm" > > .include "words/store-i_nrww.asm" > > Well, the .lss doesn't show the source lines for the atmega2560. But I see > > atmega2560: > dict/nrww.inc(93): Including file 'words/store-i_big.asm' > > atmega328p: > dict/nrww.inc(95): Including file 'words/store-i_nrww.asm' > > as you expected. Further the core_8k.inc is included for the 256 instead > of the core_4k.inc for 328p. > > Should I send the .lss file (121k) or make it somewhere available? > > > Best regards, > Helge > > > > _______________________________________________ > Amforth-devel mailing list for http://amforth.sf.net/ > Amforth-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/amforth-devel > _______________________________________________ Amforth-devel mailing list for http://amforth.sf.net/ Amforth-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amforth-devel
