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
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.
Brian-in-ohio
On 8/31/21 05:37, George Herzog wrote:
Martin Nichols has offered the simplest solution.
On Tue, Aug 31, 2021 at
Martin Nichols has offered the simplest solution.
On Tue, Aug 31, 2021 at 5:03 PM Martin Nicholas via Amforth-devel <
amforth-devel@lists.sourceforge.net> wrote:
> On Tue, 31 Aug 2021 06:27:50 +0200
> Helge Kruse wrote:
>
> > Hello, I am new to amForth.
> >
> > amForth is an interactive Forth.
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
On Tue, 31 Aug 2021 06:27:50 +0200
Helge Kruse wrote:
> 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
Hello and welcome Helge,
> 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.
This is the usual way AmForth is used. However it is possible to write
words in AVR
