[Amforth] Compiling for a headless target

2021-08-30 Thread Helge Kruse
Hello, I am new to amForth. amForth is an interactive Forth. The compiler runs on the target and writes to the flash memory of the device. This requires to send all the source code through the UART interface. I want to develop a Forth application for a target that uses the ATmeage256 USART for t

Re: [Amforth] Compiling for a headless target

2021-08-31 Thread Helge Kruse
On 31.08.2021 10:41, Martin Nicholas via Amforth-devel wrote: I want to develop a Forth application for a target that uses the ATmeage256 USART for the application data. In that case it would be desired to compile the application, create a hex file and use USBasp to flash it to the target. How

Re: [Amforth] Compiling for a headless target

2021-08-31 Thread Helge Kruse
On 31.08.2021 18:40, BK Navarette wrote: May be you could do a memory dump using avrdude terminal mode after building the application interactively then flash that file to the next avr. This might work. Thanks for this idea. Of cause, it's not absolutely necessary to create the hex file with fr

Re: [Amforth] Compiling for a headless target

2021-09-04 Thread Helge Kruse
On 31.08.21 11:29, Helge Kruse via Amforth-devel wrote: But I want to create a hex file with a real turnkey application that I can flash on another ATmega2560 device. After running all Forth source code to my "development" board I find the flash filled with the code. It should be p

Re: [Amforth] Compiling for a headless target

2021-09-05 Thread Helge Kruse
Am 04.09.2021 um 14:38 schrieb Erich Wälde: Using the serial interface for a rs485 connection ... now, that I can understand :-) I have a collection of controllers "online", descriptions start here (German text): Vierte Dimension 2011/1 https://forth-ev.de/wiki/res/lib/exe/fetch.php/vd-archiv:4d

Re: [Amforth] Compiling for a headless target

2021-09-06 Thread Helge Kruse
On 05.09.2021 18:08, Erich Wälde wrote: Hmmm, you sure??? If I look at my code ... usart-isr-rx.asm ... see below. No. I was wrong. I wrote the mail without the documentation at hand. I remembered incorrectly that the address is compared by the microcontroller. That was wrong. The MPC checks onl

[Amforth] Building amForth with Microchip Studio 7

2021-09-07 Thread Helge Kruse
I am a newby to amForth. I want to use it at ATmega 2560. For the first steps I want to use the more common board Arduino UNO. I flashed the files uno.hex and uno.eep.hex from the directory amforth-6.9\appl\arduino to my Arduino UNO. This gives me a greeting amforth 6.9 ATmega328P Forthduino >

Re: [Amforth] Building amForth with Microchip Studio 7

2021-09-08 Thread Helge Kruse
On 08.09.2021 08:06, Tristan Williams wrote: Hi Helge, I don't use studio, but from the command line you give below avrasm2.exe -fI -o my.hex -e my.eep -S my.tmp -W+ie -I"D:/Program Files (x86)\Atmel\Studio\7.0\Packs\atmel\ATmega_DFP\1.6.364\avrasm\inc" -I"amforth-6.9\avr8" -I"amforth-6.9\avr8

Re: [Amforth] Building amForth with Microchip Studio 7

2021-09-08 Thread Helge Kruse
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/stor

Re: [Amforth] Building amForth with Microchip Studio 7

2021-09-12 Thread Helge Kruse
On 09.09.2021 09:37, Tristan Williams wrote: 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. I absolutely agree. And the Studio 7 comes with avrasm2. There is a version update from 2.1.