amforth-devel — Development discussion and user support

Re: [Amforth] AmForth Weekend 4

[Martin N. <amf...@mg...>]

On Fri, 07 Nov 2025 17:28:45 +0000
ho...@tj... wrote:
 
> It needs a lot more testing before it goes anywhere near the repo. If 
> you are willing to alpha test it, I will tidy it up.
> 

Certainly, send it over.

-- 
Regards,

Martin Nicholas.

E-mail: rep...@mg... (Address will be valid throughout 2025).

Re: [Amforth] AmForth Weekend 4

[<ho...@tj...>]

On 2025-11-05 08:46, Martin Nicholas via Amforth-devel wrote:
> On Sun, 02 Nov 2025 14:40:07 +0000

CUT

> You didn't ask for them, but I have a couple of ideas for
> amforth-shell.py:
> 
> 1.
> Have an "#ifndef FORTHWORD forthword.frt" directive. "#ifdef" also.
> 
> 2.
> Directives that take a path or filename will look for a partial path.
> i.e:	#require project1/main.frt
> 	#require project2/main.frt
> are considered different files.
> 
> If either of these can be achieved by some other means, then please
> chip in. I am aware of "#cd".

Hi Martin,

Thank you. Ideas are always welcome, and yours are very timely.

For 1. There might be an AmForth way or an amforth-shell way. Depends 
upon what we want to use #ifdef for.

AmForth way - with a "bigger" Forth than AmForth there would be the 
option of using [IF]..[ELSE]..[THEN]. AmForth does not have these 
extension words from [1] but it does have [DEFINED] and [UNDEFINED]. 
 From [2] on the website, a limited (by current SOURCE) Conditional 
Interpret can be achieved.

|S|    1|anew empty
|W|    2|
|S|    3|: ?\ ( f -- ) if postpone \ then ; immediate
|W|    4|
|S|    5|[defined]   3+ 0= ?\ : xx 3+ ;
|S|    6|[undefined] 3+ 0= ?\ : xx 2 + ;
|W|    7|
|S|    8|100 xx . cr
|O|    8|102
|W|    9|
|S|   10|: 3+ ( n -- n ) 3 + ;
|W|   11|
|S|   12|[defined]   3+ 0= ?\ : yy 3+ ;
|S|   13|[undefined] 3+ 0= ?\ : yy 2 + ;
|W|   14|
|S|   15|100 yy . cr
|O|   15|103

I *think* this can be extended a little

|S|   17|anew empty
|W|   18|
|S|   19|: ifdef  postpone   [defined] invert if postpone \ then  ; 
immediate
|S|   20|: ifndef postpone [undefined] invert if postpone \ then  ; 
immediate
|W|   21|
|S|   22|: zz
|S|   23|    ifdef  3+ 3+
|S|   24|    ifndef 3+ 2 +
|S|   25|;
|W|   26|
|S|   27|100 zz . cr
|O|   27|102
|W|   28|
|S|   29|: 3+ ( n -- n ) 3 + ;
|W|   30|
|S|   31|: zz
|S|   32|    ifdef  3+ 3+
|S|   33|    ifndef 3+ 2 +
|S|   34|;
|W|   35|
|S|   36|100 zz . cr
|O|   36|103

I've not tested this beyond the snippet above. It's not 
[IF]..[ELSE]..[THEN] by a long chalk but it's "all Forth" and it might 
do the job. Alternatively,

amforth-shell way - amforth-shell does some [pre|post]processing of 
serial streams to/from the mcu and can also interact using Forth with 
the mcu.  However, it has no conditional i.e. #ifdef ... capability. 
This is something I've wanted, but I've been putting off as

(a) amforth-shell.py is very reliable and I don't want to break it
(b) the serial "handshaking" needed is not easy - goto (a)

Recently, however, I have merged amforth-shell with a preprocessor. I've 
just added your idea, but renamed #ifdef to #ifword as #ifdef taken. 
Forth source can look like this. #dictionary queries mcu and fills local 
cache, #ifword queries local cache.

anew empty
#dictionary
: zz
     #ifword 3+
     3+
     #else
     2 +
     #endif
;
100 zz . cr
: 3+ ( n -- n ) 3 + ;
#dictionary
: zz
     #ifword 3+
     3+
     #else
     2 +
     #endif
;
100 zz . cr

which when uploaded to the mcu it looks like this. You only get to "see" 
what was left after the preprocessor has done its work.

|S|    1|anew empty
|S|    2|: zz
|S|    3|    2 +
|S|    4|;
|S|    5|100 zz . cr
|O|    5|102
|S|    6|: 3+ ( n -- n ) 3 + ;
|S|    7|: zz
|S|    8|    3+
|S|    9|;
|S|   10|100 zz . cr
|O|   10|103

It needs a lot more testing before it goes anywhere near the repo. If 
you are willing to alpha test it, I will tidy it up.

Best wishes,
Tristan

[1] 15.6.2 Programming-Tools extension words
     https://forth-standard.org/standard/tools

[2] 
https://amforth.sourceforge.net/TG/recipes/Conditional-Interpret.html

Re: [Amforth] AmForth Weekend 4

[Martin N. <amf...@mg...>]

On Sun, 02 Nov 2025 14:40:07 +0000
ho...@tj... wrote:

> Dear AmForthers,
> 
> I liked Erich's "AmForth Weekend" format, so I'm sticking with
> it. This is AmForth Weekend 4. This weekend's motto is "Try not to
> break anything".
> 
> The focus is on AVR8, amforth-shell.py and the website.
> 
> No release yet, but some activity in trunk.
> 
> Let me know what works, and what does not.
> 
> Best wishes,
> Tristan
> 
> # SUMMARY
> 
> ## AMFORTH-SHELL.PY
> 
> amforth-shell.py has had some syntax warning fixes and one new
> feature. The syntax was correct at the time, but python has moved on.
> 
> A directive #stack has been added. This toggles on and off displaying
> the contents of the mcu data stack as a prompt (if the word .s exists
> on the device)
> 
> ## AVR8
> 
> Within the existing codebase, some minor fixes to a handful of .asm
> files that avra was rightly flagging with warnings about misalignment
> in word name .db statements. Whilst avra padded these out correctly,
> better to fix.
> 
> *Request for help* - I'm not a MS windows user, but I am keen that the
> existing build system still works for MS windows. If you are a MS 
> windows
> user I would be grateful if you could try and build AmForth from trunk
> and let me know if it still works for you.
> 
> ## WEBSITE
> 
> This wasn't top of my initial list of things to look at. However,
> without documentation, prebuilt hex files are of diminished
> use. AmForth's documentation is a very special resource.  Time and
> reST/Sphinx (the system that turns documentation source into html and
> the website), however, have moved on. Running the documentation
> through a modern Sphinx broke a few things on the site. These have
> been fixed. Some missing svg files that were produced from dia format
> files were salvaged from the 6.8 release. There remain some broken
> links to missing pdfs/frt on the recognizer page. The documentation
> source is available, but rebuilding requires a chain of personal
> system upgrades I'm not quite ready for yet.
> 
> As an apprentice piece in writing something with reST, I've added a
> post on the Opinion page.
> 
> ## WHAT IS NEXT
> 
> Reference card
> Prebuilt hex files for AVR8
> 
> ## COMMITS
> 
> r2458 change of maintainer
> 
> r2459 minor fixes to amforth-shell.py syntax warnings fixed, modify #!
> to a less fragile one
> 
> r2460 adds directive #stack to amforth-shell.py #stack toggles whether
> the mcu data stack is displayed to left of input prompt > Default is
> no.
> 
> r2461 fix .db padding warnings (from avra)
> 
> r2462 website update
> 
> 
> 
> _______________________________________________
> Amforth-devel mailing list for http://amforth.sf.net/
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel
> 
> 

Thanks Tristan. Efforts much appreciated.

You didn't ask for them, but I have a couple of ideas for
amforth-shell.py:

1.
Have an "#ifndef FORTHWORD forthword.frt" directive. "#ifdef" also.

2.
Directives that take a path or filename will look for a partial path.
i.e:	#require project1/main.frt
	#require project2/main.frt
are considered different files. 

If either of these can be achieved by some other means, then please
chip in. I am aware of "#cd".

-- 
Regards,

Martin Nicholas.

E-mail: rep...@mg... (Address will be valid throughout 2025).

[Amforth] AmForth Weekend 4

[<ho...@tj...>]

Dear AmForthers,

I liked Erich's "AmForth Weekend" format, so I'm sticking with
it. This is AmForth Weekend 4. This weekend's motto is "Try not to
break anything".

The focus is on AVR8, amforth-shell.py and the website.

No release yet, but some activity in trunk.

Let me know what works, and what does not.

Best wishes,
Tristan

# SUMMARY

## AMFORTH-SHELL.PY

amforth-shell.py has had some syntax warning fixes and one new
feature. The syntax was correct at the time, but python has moved on.

A directive #stack has been added. This toggles on and off displaying
the contents of the mcu data stack as a prompt (if the word .s exists
on the device)

## AVR8

Within the existing codebase, some minor fixes to a handful of .asm
files that avra was rightly flagging with warnings about misalignment
in word name .db statements. Whilst avra padded these out correctly,
better to fix.

*Request for help* - I'm not a MS windows user, but I am keen that the
existing build system still works for MS windows. If you are a MS 
windows
user I would be grateful if you could try and build AmForth from trunk
and let me know if it still works for you.

## WEBSITE

This wasn't top of my initial list of things to look at. However,
without documentation, prebuilt hex files are of diminished
use. AmForth's documentation is a very special resource.  Time and
reST/Sphinx (the system that turns documentation source into html and
the website), however, have moved on. Running the documentation
through a modern Sphinx broke a few things on the site. These have
been fixed. Some missing svg files that were produced from dia format
files were salvaged from the 6.8 release. There remain some broken
links to missing pdfs/frt on the recognizer page. The documentation
source is available, but rebuilding requires a chain of personal
system upgrades I'm not quite ready for yet.

As an apprentice piece in writing something with reST, I've added a post
on the Opinion page.

## WHAT IS NEXT

Reference card
Prebuilt hex files for AVR8

## COMMITS

r2458 change of maintainer

r2459 minor fixes to amforth-shell.py syntax warnings fixed, modify #!
to a less fragile one

r2460 adds directive #stack to amforth-shell.py #stack toggles whether
the mcu data stack is displayed to left of input prompt > Default is
no.

r2461 fix .db padding warnings (from avra)

r2462 website update

Re: [Amforth] Maintainer-lite

[<ho...@tj...>]

Fellow AmForthers,

Erich has very kindly given me admin access to the sourceforge repo, so 
I have the tools to be a maintainer-lite for the AmForth project. What I 
need to do now is to (a) practise some svn in a safe place (b) compile a 
TODO list for the next release.

Currently on the TODO list are

- a build process that makes use of an amended avra (from Mark )
- inclusion of prebuilt hex files in releases to be the norm
- bugs/patches/improvements (from Nicholas)
- AmForth RISC-V developments (from me)

I would be very happy to receive suggestions, opinions, patches from 
list members to add to the above. The more the merrier.

Best wishes,
Tristan

Re: [Amforth] Atmega32U4 microcontroller

[<ho...@tj...>]

Hi Jan,

If you want an AmForth operator prompt using the ATmega32u4's USB 
peripheral then the answer is no. However, if you are content to use the 
ATmega32u4's UART and have access to a USB to TTL serial adapter (of the 
appropriate voltage) then the answer is yes. The file 
/appl/arduino/leonardo.asm was setup to do this and I do remember 
running AmForth 6.8 on an Arduino Leonardo which uses the ATmega32u4.

Best wishes,
Tristan

On 2025-09-16 07:40, dx...@gm... wrote:
> Not tried it myself, but there's an implementation including hex file
> for the Arduino Leonardo under the folder:
> 
> amforth-6.9\appl\arduino\
> 
> ________________________________
> From: Jan Kromhout via Amforth-devel 
> <amf...@li...>
> Sent: Tuesday, September 16, 2025 12:38 AM
> To: Amf...@li... 
> <amf...@li...>
> Cc: Jan Kromhout <jan...@ic...>
> Subject: [Amforth] Atmega32U4 microcontroller
> 
> Hello,
> 
> Is there a version of am forth for the ATmega32U4 AVR microcontroller?
> If available where can I download this version, or is it a Parth of a 
> whole?
> 
> Thanks for any help.
> 
> Jan Kromhout
> 
> 
> _______________________________________________
> Amforth-devel mailing list for http://amforth.sf.net/
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel
> 
> _______________________________________________
> Amforth-devel mailing list for http://amforth.sf.net/
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel

Re: [Amforth] Atmega32U4 microcontroller

[<dx...@gm...>]

Not tried it myself, but there's an implementation including hex file for the Arduino Leonardo under the folder:

amforth-6.9\appl\arduino\

________________________________
From: Jan Kromhout via Amforth-devel <amf...@li...>
Sent: Tuesday, September 16, 2025 12:38 AM
To: Amf...@li... <amf...@li...>
Cc: Jan Kromhout <jan...@ic...>
Subject: [Amforth] Atmega32U4 microcontroller

Hello,

Is there a version of am forth for the ATmega32U4 AVR microcontroller?
If available where can I download this version, or is it a Parth of a whole?

Thanks for any help.

Jan Kromhout


_______________________________________________
Amforth-devel mailing list for http://amforth.sf.net/
Amf...@li...
https://lists.sourceforge.net/lists/listinfo/amforth-devel

[Amforth] Atmega32U4 microcontroller

[Jan K. <jan...@ic...>]

Hello,

Is there a version of am forth for the ATmega32U4 AVR microcontroller?   
If available where can I download this version, or is it a Parth of a whole?

Thanks for any help.

Jan Kromhout

Re: [Amforth] Maintainer-lite

[Brian K N. <bkn...@gm...>]

Thanks for the work. Love amforth and especially when I don't have to use
wine under linux
brian-in-ohio

On Sat, Sep 13, 2025 at 11:01 AM Erich Wälde <ew....@na...> wrote:

> Mark Roth <cab...@gm...> writes:
>
> > lol, that's mine.
> >
> > It's where I parked stuff when I was trying to get the avra
> > stuff working. I bashed the avra (enough of) into it last year
> > or whenever that was. :)
>
> I'm using that version of avra! :)
> With versions 5.0 .. 5.5 of avra.
>
> Thanks, Mark!
> Erich
>
> >
> > On Fri, Sep 12, 2025 at 4:41 PM Martin Nicholas via Amforth-devel <
> > amf...@li...> wrote:
> >
> >> On Sun, 31 Aug 2025 14:45:52 +0100
> >> Tristan wrote:
> >>
> >> > Fellow AmForthers,
> >> >
> >> > Nice to see some activity on the mailing list, which highlights
> >> >
> >> > (a) There is still some interest in AmForth from people new to the
> >> > list. (b) There are still some existing AmForth list members who read
> >> > the list.
> >> > (c) AmForth still does not have a maintainer.
> >> >
> >> > Regarding (c) I'm putting myself forward as a "maintainer-lite" for
> >> > AmForth. For those not on the list at the time, the links [0..2]
> >> > below give some history. Without somebody performing the maintenance
> >> > role, even in a limited way, it is hard to address some of the issues
> >> > raised on the mailing list. In short, I think a maintainer-lite would
> >> > (hopefully!) be better than no maintainer at all, and I have the time
> >> > now to do that. I would, however, be delighted if anyone wanted to
> >> > join me.
> >> >
> >> > Let me know what you think.
> >> >
> >> > Kind regards,
> >> > Tristan
> >> >
> >> >
> >>
> >> All in favour. I am still working with AmForth and have some
> >> bugs/patches/improvements waiting for a maintainer.
> >>
> >> BTW, I found a fork of AmForth on GitHub whilst looking for a Python3
> >> version of amforth-shell.py:
> >> https://github.com/CableGuy67/AmForth
> >> Probably there is more good stuff there.
> >>
> >> --
> >> Regards,
> >>
> >> Martin Nicholas.
> >>
> >> E-mail: rep...@mg... (Address will be valid throughout 2025).
> >>
> >>
> >> _______________________________________________
> >> Amforth-devel mailing list for http://amforth.sf.net/
> >> Amf...@li...
> >> https://lists.sourceforge.net/lists/listinfo/amforth-devel
> >>
> >
> > _______________________________________________
> > Amforth-devel mailing list for http://amforth.sf.net/
> > Amf...@li...
> > https://lists.sourceforge.net/lists/listinfo/amforth-devel
>
> --
> May the Forth be with you ...
>
>
> _______________________________________________
> Amforth-devel mailing list for http://amforth.sf.net/
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel
>

Re: [Amforth] Maintainer-lite

[Erich W. <ew....@na...>]

Mark Roth <cab...@gm...> writes:

> lol, that's mine.
>
> It's where I parked stuff when I was trying to get the avra
> stuff working. I bashed the avra (enough of) into it last year
> or whenever that was. :)

I'm using that version of avra! :)
With versions 5.0 .. 5.5 of avra.

Thanks, Mark!
Erich

>
> On Fri, Sep 12, 2025 at 4:41 PM Martin Nicholas via Amforth-devel <
> amf...@li...> wrote:
>
>> On Sun, 31 Aug 2025 14:45:52 +0100
>> Tristan wrote:
>>
>> > Fellow AmForthers,
>> >
>> > Nice to see some activity on the mailing list, which highlights
>> >
>> > (a) There is still some interest in AmForth from people new to the
>> > list. (b) There are still some existing AmForth list members who read
>> > the list.
>> > (c) AmForth still does not have a maintainer.
>> >
>> > Regarding (c) I'm putting myself forward as a "maintainer-lite" for
>> > AmForth. For those not on the list at the time, the links [0..2]
>> > below give some history. Without somebody performing the maintenance
>> > role, even in a limited way, it is hard to address some of the issues
>> > raised on the mailing list. In short, I think a maintainer-lite would
>> > (hopefully!) be better than no maintainer at all, and I have the time
>> > now to do that. I would, however, be delighted if anyone wanted to
>> > join me.
>> >
>> > Let me know what you think.
>> >
>> > Kind regards,
>> > Tristan
>> >
>> >
>>
>> All in favour. I am still working with AmForth and have some
>> bugs/patches/improvements waiting for a maintainer.
>>
>> BTW, I found a fork of AmForth on GitHub whilst looking for a Python3
>> version of amforth-shell.py:
>> https://github.com/CableGuy67/AmForth
>> Probably there is more good stuff there.
>>
>> --
>> Regards,
>>
>> Martin Nicholas.
>>
>> E-mail: rep...@mg... (Address will be valid throughout 2025).
>>
>>
>> _______________________________________________
>> Amforth-devel mailing list for http://amforth.sf.net/
>> Amf...@li...
>> https://lists.sourceforge.net/lists/listinfo/amforth-devel
>>
>
> _______________________________________________
> Amforth-devel mailing list for http://amforth.sf.net/
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel

-- 
May the Forth be with you ...

Re: [Amforth] Maintainer-lite

[Mark R. <cab...@gm...>]

lol, that's mine.

It's where I parked stuff when I was trying to get the avra stuff working.
I bashed the avra (enough of) into it last year or whenever that was. :)

On Fri, Sep 12, 2025 at 4:41 PM Martin Nicholas via Amforth-devel <
amf...@li...> wrote:

> On Sun, 31 Aug 2025 14:45:52 +0100
> Tristan wrote:
>
> > Fellow AmForthers,
> >
> > Nice to see some activity on the mailing list, which highlights
> >
> > (a) There is still some interest in AmForth from people new to the
> > list. (b) There are still some existing AmForth list members who read
> > the list.
> > (c) AmForth still does not have a maintainer.
> >
> > Regarding (c) I'm putting myself forward as a "maintainer-lite" for
> > AmForth. For those not on the list at the time, the links [0..2]
> > below give some history. Without somebody performing the maintenance
> > role, even in a limited way, it is hard to address some of the issues
> > raised on the mailing list. In short, I think a maintainer-lite would
> > (hopefully!) be better than no maintainer at all, and I have the time
> > now to do that. I would, however, be delighted if anyone wanted to
> > join me.
> >
> > Let me know what you think.
> >
> > Kind regards,
> > Tristan
> >
> >
>
> All in favour. I am still working with AmForth and have some
> bugs/patches/improvements waiting for a maintainer.
>
> BTW, I found a fork of AmForth on GitHub whilst looking for a Python3
> version of amforth-shell.py:
> https://github.com/CableGuy67/AmForth
> Probably there is more good stuff there.
>
> --
> Regards,
>
> Martin Nicholas.
>
> E-mail: rep...@mg... (Address will be valid throughout 2025).
>
>
> _______________________________________________
> Amforth-devel mailing list for http://amforth.sf.net/
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel
>

Re: [Amforth] Maintainer-lite

[Martin N. <amf...@mg...>]

On Sun, 31 Aug 2025 14:45:52 +0100
Tristan wrote:

> Fellow AmForthers,
> 
> Nice to see some activity on the mailing list, which highlights
> 
> (a) There is still some interest in AmForth from people new to the
> list. (b) There are still some existing AmForth list members who read
> the list.
> (c) AmForth still does not have a maintainer.
> 
> Regarding (c) I'm putting myself forward as a "maintainer-lite" for 
> AmForth. For those not on the list at the time, the links [0..2]
> below give some history. Without somebody performing the maintenance
> role, even in a limited way, it is hard to address some of the issues
> raised on the mailing list. In short, I think a maintainer-lite would 
> (hopefully!) be better than no maintainer at all, and I have the time 
> now to do that. I would, however, be delighted if anyone wanted to
> join me.
> 
> Let me know what you think.
> 
> Kind regards,
> Tristan
> 
>

All in favour. I am still working with AmForth and have some
bugs/patches/improvements waiting for a maintainer.

BTW, I found a fork of AmForth on GitHub whilst looking for a Python3
version of amforth-shell.py:
https://github.com/CableGuy67/AmForth
Probably there is more good stuff there.

-- 
Regards,

Martin Nicholas.

E-mail: rep...@mg... (Address will be valid throughout 2025).

Re: [Amforth] Maintainer-lite

[Mark R. <cab...@gm...>]

It's nice to hear from you Tristan and I will also mirror the good
sentiment that there are still people out there interested in AmForth.
Granted, there have been less than a dozen messages over the last year but
for every message there must be what, 10 or 20 thousand that don't respond?
;)

In all seriousness though I thought perhaps Erich would have chimed in. I
saw this mail show up at the tail end of my summer vacation after, oddly
enough, thinking of your Risc-V project when playing around with the newer
esp32-c6s. That day this mail popped in. I should also add that with my
eyes getting older I thought it said, "maintainer LIFE" not "lite".

One of the reasons, apart from the fact that I still use my local instance
of AmForth on my atmel random bitstream thing, that the project was in mind
is that someone has been trying to catch up the avra project to the point
where the person (Rob3rt iirc) that had the repo allowed in a collaborator
that was interested in bringing things up to date. In fact they originally
offered to give them the repo. When the conversation turned to forks etc I
chimed in with what I'd done last year (or whenever that was) to get avra
working for us here. Sadly though, it has only been fits and starts with
that although it seems maybe something will come of it. Possibly.

So (get to it old man) in any case I'm glad to hear you are putting your
hand up to maintain things. I would reiterate though that it should be on
some flavor of git as opposed to here on sourceforge. I think Erich did
that part some time ago. I know I have a bunch of git repos locally that I
think I got from that time that managed to keep the history intact for the
most part. Mine is a bit butchered up I think from when I more or less just
wanted to make sure I had access to the codebase non-locally.

(oof, i'm long winded these days)

In any case Tristan, I would be happy to offer whatever assistance I could
if you move forward with any of this. Now that the good weather will start
winding down I should have a bit more time to offer in that respect.

All the best,
Mark

On Sun, Aug 31, 2025 at 4:51 PM <ho...@tj...> wrote:

> Fellow AmForthers,
>
> Nice to see some activity on the mailing list, which highlights
>
> (a) There is still some interest in AmForth from people new to the list.
> (b) There are still some existing AmForth list members who read the
> list.
> (c) AmForth still does not have a maintainer.
>
> Regarding (c) I'm putting myself forward as a "maintainer-lite" for
> AmForth. For those not on the list at the time, the links [0..2] below
> give some history. Without somebody performing the maintenance role,
> even in a limited way, it is hard to address some of the issues raised
> on the mailing list. In short, I think a maintainer-lite would
> (hopefully!) be better than no maintainer at all, and I have the time
> now to do that. I would, however, be delighted if anyone wanted to join
> me.
>
> Let me know what you think.
>
> Kind regards,
> Tristan
>
> [0] https://sourceforge.net/p/amforth/mailman/message/36959799/
> [1] https://sourceforge.net/p/amforth/mailman/message/37649964/
> [2] https://sourceforge.net/p/amforth/mailman/message/37894180/
>
>
> _______________________________________________
> Amforth-devel mailing list for http://amforth.sf.net/
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel
>

[Amforth] Maintainer-lite

[<ho...@tj...>]

Fellow AmForthers,

Nice to see some activity on the mailing list, which highlights

(a) There is still some interest in AmForth from people new to the list.
(b) There are still some existing AmForth list members who read the 
list.
(c) AmForth still does not have a maintainer.

Regarding (c) I'm putting myself forward as a "maintainer-lite" for 
AmForth. For those not on the list at the time, the links [0..2] below 
give some history. Without somebody performing the maintenance role, 
even in a limited way, it is hard to address some of the issues raised 
on the mailing list. In short, I think a maintainer-lite would 
(hopefully!) be better than no maintainer at all, and I have the time 
now to do that. I would, however, be delighted if anyone wanted to join 
me.

Let me know what you think.

Kind regards,
Tristan

[0] https://sourceforge.net/p/amforth/mailman/message/36959799/
[1] https://sourceforge.net/p/amforth/mailman/message/37649964/
[2] https://sourceforge.net/p/amforth/mailman/message/37894180/

[Amforth] [SPAM] Amforth for Arduino Mega 2560

[<dx...@gm...>]

As there appeared to be no official hex files for the Arduino Mega, I set about building from source.

Hex files, fuse values, source templates and general instructions are provided in AMF2560.ZIP which may be downloaded from:

https://drive.google.com/drive/folders/1kh2WcPUc3hQpLcz7TQ-YQiowrozvxfGw

Should anyone try it and notice problems, please let me know.  Thanks.

Ed

Re: [Amforth] error uploading ports-standard.frt

[J. B. <jpu...@gm...>]

Thanks, Martin + Tristan.

After reading »synonym is available since amforth 5.0« I did expect that it
is included already.

so I've tried ports-standard.frt . Worked after \-ing analog.6 and analog.7
.
Perhaps a somewhat more explicit comment would help.

PS: the PDF from Trute is very nice, because I have a lot of info in 1
document.
PS2: 'drop' is not(?) for removing defined words, it's forget → marker
empty (?)
PS3: it's ports-standard.frt, not ports-arduino.frt as per documentation.
PS4: perhaps we could add the library path to amforth-shell.py - making it
easier for beginners(?)

Kind regards, Jochen





Am Sa., 9. Aug. 2025 um 15:03 Uhr schrieb Martin Nicholas via Amforth-devel
<amf...@li...>:

> On Sat, 9 Aug 2025 13:57:33 +0200
> "J. Barth" <jpu...@gm...> wrote:
>
> > Hi, my name is Jochen,
> > I've tried to upload ports-standard.frt to my (arduino) uno to access
> > the adc.
> >
> > Did use amforth-6.9 with uno.hex and uno.eep.hex (manually, done
> > before reading the manual).
> >
> > (Had to add -I /home/user_xyz/.../amforth-6.9/common/lib , without it
> > did not find some #require files)
> >
> > see below:
> >
> > ./amforth-shell-upload.sh $(./amforth-dependencies.pl
> > ports-standard.frt)
> > + ../amforth-6.9/tools/amforth-shell.py -p /dev/ttyUSB0 -I
> > /home/jb/forth/amforth-6.9/common/lib
> > ../amforth-6.9/appl/arduino/blocks/ports-standard.frt
> > |I=appl_defs: 0 loaded
> > |I=getting filenames on the host
> > |I=  Reading .
> > |I=  Reading /home/jb/forth/amforth-6.9/common/lib
> > |I=using ../amforth-6.9/appl/arduino/blocks/ports-standard.frt
> > verbatim **** /home/jb/forth/my-amforth
> > |I=getting MCU name..
> > |I=successfully loaded register definitions for atmega328p
> > |I=getting filenames on the host
> > |I=  Reading /home/jb/forth/amforth-6.9/avr8/devices/atmega328p
> > |I=  Reading /home/jb/forth/amforth-6.9/avr8/lib
> > |I=  Reading .
> > |I=  Reading /home/jb/forth/amforth-6.9/common/lib
> > |F=../amforth-6.9/appl/arduino/blocks/ports-standard.frt
> > |C|    1|\
> > |C|    2|\ port definitions for Atmegas as found on the Arduino
> > Standard |C|    3|\ Atmega168, Atmega328p
> > |C|    4|\
> > |S|    5|decimal
> > |W|    6|
> > |S|    7|PORTD 0 portpin: digital.0
> > |S|    8|PORTD 1 portpin: digital.1
> > |S|    9|PORTD 2 portpin: digital.2
> > |S|   10|PORTD 3 portpin: digital.3
> > |S|   11|PORTD 4 portpin: digital.4
> > |S|   12|PORTD 5 portpin: digital.5
> > |S|   13|PORTD 6 portpin: digital.6
> > |S|   14|PORTD 7 portpin: digital.7
> > |W|   15|
> > |S|   16|PORTB 0 portpin: digital.8
> > |S|   17|PORTB 1 portpin: digital.9
> > |S|   18|PORTB 2 portpin: digital.10
> > |S|   19|PORTB 3 portpin: digital.11
> > |S|   20|PORTB 4 portpin: digital.12
> > |S|   21|PORTB 5 portpin: digital.13
> > |W|   22|
> > |S|   23|PORTC 0 portpin: digital.14
> > |S|   24|PORTC 1 portpin: digital.15
> > |S|   25|PORTC 2 portpin: digital.16
> > |S|   26|PORTC 3 portpin: digital.17
> > |S|   27|PORTC 4 portpin: digital.18
> > |S|   28|PORTC 5 portpin: digital.19
> > |W|   29|
> > |C|   30|\ some digital ports have an alternative use
> > |C|   31|\ synonym is available since amforth 5.0
> > |S|   32|synonym SPI:SS   digital.10
> > |E= ?? -13 7
> > **** /home/jb/forth/amforth-6.9/appl/arduino/blocks
> >
> > Kind regards, Jochen
> >
> > _______________________________________________
> > Amforth-devel mailing list for http://amforth.sf.net/
> > Amf...@li...
> > https://lists.sourceforge.net/lists/listinfo/amforth-devel
> >
> >
>
> Have a look at:
> https://amforth.sourceforge.net/faq.html#what-means
> https://forth-standard.org/standard/tools/SYNONYM
>
> Error -13 means "Word not found". You need to load:
> ./common/lib/forth2012/tools/synonym.frt
>
> You can faultfind this sort of thing
> by typing the following:
> " ' synonym drop"
> An error means synonym isn't found. The above snippet avoids executing
> synonym should it actually be present.
>
> Hope this helps.
>
> --
> Regards,
>
> Martin Nicholas.
>
> E-mail: rep...@mg... (Address will be valid throughout 2025).
>
>
> _______________________________________________
> Amforth-devel mailing list for http://amforth.sf.net/
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel
>

Re: [Amforth] error uploading ports-standard.frt

[Martin N. <amf...@mg...>]

For a numerical list of exceptions:
https://forth-standard.org/standard/exception

-- 
Regards,

Martin Nicholas.

E-mail: rep...@mg... (Address will be valid throughout 2025).

Re: [Amforth] error uploading ports-standard.frt

[<ho...@tj...>]

Hi Jochen and welcome.

AmForth is complaining when you upload ports-standard.frt because it 
cannot find the word synonym. This is not a built-in word and so needs 
to be uploaded before trying to upload ports-standard.frt
synonym can be found in this file

./common/lib/forth2012/tools/synonym.frt

To use the ADC will require some additional Forth words. Below is a link 
in the AmForth documentation (if you have not already found it)

https://amforth.sourceforge.net/TG/recipes/Arduino-Analog.html?highlight=adc

The ADC unit on the ATmega328P, the mcu which powers the UNO, does have 
more to offer than is made available in the above words. Whether that is 
important to you depends upon what you want to do and your appetite for 
reading the datasheet and modifying this set of Forth words.

> (Had to add -I /home/user_xyz/.../amforth-6.9/common/lib , without it 
> did
> not find some #require files)

tools/amforth-shell.py --help

amforth-shell.py can use the environment variable AMFORTH_LIB which 
helps with this.

Let us know how you get on.

Kind regards,
Tristan


On 2025-08-09 12:57, J. Barth wrote:
> Hi, my name is Jochen,
> I've tried to upload ports-standard.frt to my (arduino) uno to access 
> the
> adc.
> 
> Did use amforth-6.9 with uno.hex and uno.eep.hex (manually, done before
> reading the manual).
> 
> (Had to add -I /home/user_xyz/.../amforth-6.9/common/lib , without it 
> did
> not find some #require files)
> 
> see below:
> 
> ./amforth-shell-upload.sh $(./amforth-dependencies.pl 
> ports-standard.frt)
> + ../amforth-6.9/tools/amforth-shell.py -p /dev/ttyUSB0 -I
> /home/jb/forth/amforth-6.9/common/lib
> ../amforth-6.9/appl/arduino/blocks/ports-standard.frt
> |I=appl_defs: 0 loaded
> |I=getting filenames on the host
> |I=  Reading .
> |I=  Reading /home/jb/forth/amforth-6.9/common/lib
> |I=using ../amforth-6.9/appl/arduino/blocks/ports-standard.frt verbatim
> **** /home/jb/forth/my-amforth
> |I=getting MCU name..
> |I=successfully loaded register definitions for atmega328p
> |I=getting filenames on the host
> |I=  Reading /home/jb/forth/amforth-6.9/avr8/devices/atmega328p
> |I=  Reading /home/jb/forth/amforth-6.9/avr8/lib
> |I=  Reading .
> |I=  Reading /home/jb/forth/amforth-6.9/common/lib
> |F=../amforth-6.9/appl/arduino/blocks/ports-standard.frt
> |C|    1|\
> |C|    2|\ port definitions for Atmegas as found on the Arduino 
> Standard
> |C|    3|\ Atmega168, Atmega328p
> |C|    4|\
> |S|    5|decimal
> |W|    6|
> |S|    7|PORTD 0 portpin: digital.0
> |S|    8|PORTD 1 portpin: digital.1
> |S|    9|PORTD 2 portpin: digital.2
> |S|   10|PORTD 3 portpin: digital.3
> |S|   11|PORTD 4 portpin: digital.4
> |S|   12|PORTD 5 portpin: digital.5
> |S|   13|PORTD 6 portpin: digital.6
> |S|   14|PORTD 7 portpin: digital.7
> |W|   15|
> |S|   16|PORTB 0 portpin: digital.8
> |S|   17|PORTB 1 portpin: digital.9
> |S|   18|PORTB 2 portpin: digital.10
> |S|   19|PORTB 3 portpin: digital.11
> |S|   20|PORTB 4 portpin: digital.12
> |S|   21|PORTB 5 portpin: digital.13
> |W|   22|
> |S|   23|PORTC 0 portpin: digital.14
> |S|   24|PORTC 1 portpin: digital.15
> |S|   25|PORTC 2 portpin: digital.16
> |S|   26|PORTC 3 portpin: digital.17
> |S|   27|PORTC 4 portpin: digital.18
> |S|   28|PORTC 5 portpin: digital.19
> |W|   29|
> |C|   30|\ some digital ports have an alternative use
> |C|   31|\ synonym is available since amforth 5.0
> |S|   32|synonym SPI:SS   digital.10
> |E= ?? -13 7
> **** /home/jb/forth/amforth-6.9/appl/arduino/blocks
> 
> Kind regards, Jochen
> 
> _______________________________________________
> Amforth-devel mailing list for http://amforth.sf.net/
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel

Re: [Amforth] error uploading ports-standard.frt

[Martin N. <amf...@mg...>]

On Sat, 9 Aug 2025 13:57:33 +0200
"J. Barth" <jpu...@gm...> wrote:

> Hi, my name is Jochen,
> I've tried to upload ports-standard.frt to my (arduino) uno to access
> the adc.
> 
> Did use amforth-6.9 with uno.hex and uno.eep.hex (manually, done
> before reading the manual).
> 
> (Had to add -I /home/user_xyz/.../amforth-6.9/common/lib , without it
> did not find some #require files)
> 
> see below:
> 
> ./amforth-shell-upload.sh $(./amforth-dependencies.pl
> ports-standard.frt)
> + ../amforth-6.9/tools/amforth-shell.py -p /dev/ttyUSB0 -I
> /home/jb/forth/amforth-6.9/common/lib
> ../amforth-6.9/appl/arduino/blocks/ports-standard.frt
> |I=appl_defs: 0 loaded
> |I=getting filenames on the host
> |I=  Reading .
> |I=  Reading /home/jb/forth/amforth-6.9/common/lib
> |I=using ../amforth-6.9/appl/arduino/blocks/ports-standard.frt
> verbatim **** /home/jb/forth/my-amforth
> |I=getting MCU name..
> |I=successfully loaded register definitions for atmega328p
> |I=getting filenames on the host
> |I=  Reading /home/jb/forth/amforth-6.9/avr8/devices/atmega328p
> |I=  Reading /home/jb/forth/amforth-6.9/avr8/lib
> |I=  Reading .
> |I=  Reading /home/jb/forth/amforth-6.9/common/lib
> |F=../amforth-6.9/appl/arduino/blocks/ports-standard.frt
> |C|    1|\
> |C|    2|\ port definitions for Atmegas as found on the Arduino
> Standard |C|    3|\ Atmega168, Atmega328p
> |C|    4|\
> |S|    5|decimal
> |W|    6|
> |S|    7|PORTD 0 portpin: digital.0
> |S|    8|PORTD 1 portpin: digital.1
> |S|    9|PORTD 2 portpin: digital.2
> |S|   10|PORTD 3 portpin: digital.3
> |S|   11|PORTD 4 portpin: digital.4
> |S|   12|PORTD 5 portpin: digital.5
> |S|   13|PORTD 6 portpin: digital.6
> |S|   14|PORTD 7 portpin: digital.7
> |W|   15|
> |S|   16|PORTB 0 portpin: digital.8
> |S|   17|PORTB 1 portpin: digital.9
> |S|   18|PORTB 2 portpin: digital.10
> |S|   19|PORTB 3 portpin: digital.11
> |S|   20|PORTB 4 portpin: digital.12
> |S|   21|PORTB 5 portpin: digital.13
> |W|   22|
> |S|   23|PORTC 0 portpin: digital.14
> |S|   24|PORTC 1 portpin: digital.15
> |S|   25|PORTC 2 portpin: digital.16
> |S|   26|PORTC 3 portpin: digital.17
> |S|   27|PORTC 4 portpin: digital.18
> |S|   28|PORTC 5 portpin: digital.19
> |W|   29|
> |C|   30|\ some digital ports have an alternative use
> |C|   31|\ synonym is available since amforth 5.0
> |S|   32|synonym SPI:SS   digital.10
> |E= ?? -13 7
> **** /home/jb/forth/amforth-6.9/appl/arduino/blocks
> 
> Kind regards, Jochen
> 
> _______________________________________________
> Amforth-devel mailing list for http://amforth.sf.net/
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel
> 
> 

Have a look at:
https://amforth.sourceforge.net/faq.html#what-means
https://forth-standard.org/standard/tools/SYNONYM

Error -13 means "Word not found". You need to load:
./common/lib/forth2012/tools/synonym.frt

You can faultfind this sort of thing
by typing the following:
" ' synonym drop"
An error means synonym isn't found. The above snippet avoids executing
synonym should it actually be present.

Hope this helps.

-- 
Regards,

Martin Nicholas.

E-mail: rep...@mg... (Address will be valid throughout 2025).

[Amforth] error uploading ports-standard.frt

[J. B. <jpu...@gm...>]

Hi, my name is Jochen,
I've tried to upload ports-standard.frt to my (arduino) uno to access the
adc.

Did use amforth-6.9 with uno.hex and uno.eep.hex (manually, done before
reading the manual).

(Had to add -I /home/user_xyz/.../amforth-6.9/common/lib , without it did
not find some #require files)

see below:

./amforth-shell-upload.sh $(./amforth-dependencies.pl ports-standard.frt)
+ ../amforth-6.9/tools/amforth-shell.py -p /dev/ttyUSB0 -I
/home/jb/forth/amforth-6.9/common/lib
../amforth-6.9/appl/arduino/blocks/ports-standard.frt
|I=appl_defs: 0 loaded
|I=getting filenames on the host
|I=  Reading .
|I=  Reading /home/jb/forth/amforth-6.9/common/lib
|I=using ../amforth-6.9/appl/arduino/blocks/ports-standard.frt verbatim
**** /home/jb/forth/my-amforth
|I=getting MCU name..
|I=successfully loaded register definitions for atmega328p
|I=getting filenames on the host
|I=  Reading /home/jb/forth/amforth-6.9/avr8/devices/atmega328p
|I=  Reading /home/jb/forth/amforth-6.9/avr8/lib
|I=  Reading .
|I=  Reading /home/jb/forth/amforth-6.9/common/lib
|F=../amforth-6.9/appl/arduino/blocks/ports-standard.frt
|C|    1|\
|C|    2|\ port definitions for Atmegas as found on the Arduino Standard
|C|    3|\ Atmega168, Atmega328p
|C|    4|\
|S|    5|decimal
|W|    6|
|S|    7|PORTD 0 portpin: digital.0
|S|    8|PORTD 1 portpin: digital.1
|S|    9|PORTD 2 portpin: digital.2
|S|   10|PORTD 3 portpin: digital.3
|S|   11|PORTD 4 portpin: digital.4
|S|   12|PORTD 5 portpin: digital.5
|S|   13|PORTD 6 portpin: digital.6
|S|   14|PORTD 7 portpin: digital.7
|W|   15|
|S|   16|PORTB 0 portpin: digital.8
|S|   17|PORTB 1 portpin: digital.9
|S|   18|PORTB 2 portpin: digital.10
|S|   19|PORTB 3 portpin: digital.11
|S|   20|PORTB 4 portpin: digital.12
|S|   21|PORTB 5 portpin: digital.13
|W|   22|
|S|   23|PORTC 0 portpin: digital.14
|S|   24|PORTC 1 portpin: digital.15
|S|   25|PORTC 2 portpin: digital.16
|S|   26|PORTC 3 portpin: digital.17
|S|   27|PORTC 4 portpin: digital.18
|S|   28|PORTC 5 portpin: digital.19
|W|   29|
|C|   30|\ some digital ports have an alternative use
|C|   31|\ synonym is available since amforth 5.0
|S|   32|synonym SPI:SS   digital.10
|E= ?? -13 7
**** /home/jb/forth/amforth-6.9/appl/arduino/blocks

Kind regards, Jochen

[Amforth] A RISC-V update

[<ho...@tj...>]

A risc-v update for CH32V307

AmForth-RV can now compile to flash directly rather than saving a word 
already compiled in ram as before. This is better and much more like the 
approach taken by the AVR code base. However, it does need an mcu that 
is able to do this. The flag field in the dictionary is used more, which 
simplifies and optionally declutters word listings. I think this was 
something that was intended, but not fully implemented. Being able to 
call C library functions from Forth has helped with beginning to add 
IEEE-754 floating point to AmForth-RV. There is a link to a pre-built 
hex file on [1] and the development board seems to be available in the 
EU from [2]. More details in the project logs [3].

Best wishes,
Tristan

[1] https://tjnw.co.uk/amforth-rv/pages/building.html
[2] 
https://www.elektor.com/products/wch-ch32v307v-evt-r1-risc-v-development-board
[3] https://tjnw.co.uk/amforth-rv/pages/logs.html

[Amforth] A RISC-V update - USB

[<ho...@tj...>]

A RISC-V update - USB

AmForth-RV now has a USB operator prompt. I've put a small video of it
working on YouTube (link below).

https://www.youtube.com/watch?v=JRXCS4dm84U

Best wishes,
Tristan

Re: [Amforth] A RISC-V update

[Martin N. <amf...@mg...>]

On Tue, 16 Apr 2024 19:34:13 +0100
ho...@tj... wrote:

> Thoughts/fixes very much welcomed. Currently struggling with USB.


There is a library for flashforth, see below. It's for an Atmega
32u4, However I quickly came to the conclusion that it had some flaws
and shelved attempts to get it working.

https://sourceforge.net/p/flashforth/code/ci/master/tree/avr/forth/usbcdc.fs

-- 
Regards,

Martin Nicholas.

E-mail: rep...@mg... (Address will be valid throughout 2024).

Re: [Amforth] A RISC-V update

[Mark R. <cab...@gm...>]

This is really great to see Tristan. Bravo to your efforts getting this
going!

On Sat, Apr 13, 2024 at 7:24 PM <ho...@tj...> wrote:

> A RISC-V update.
>
> AmForth-RV is now self-supporting (no C libraries required) for the
> WCH CH32V307. Source and a pre-built hex file are here [0]
>
> Best wishes,
> Tristan
>
> [0] https://tjnw.co.uk/amforth-rv
>
>
>
> _______________________________________________
> Amforth-devel mailing list for http://amforth.sf.net/
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel
>

Re: [Amforth] A RISC-V update

[<ho...@tj...>]

Thoughts/fixes very much welcomed. Currently struggling with USB.

Best wishes,
Tristan



On 2024-04-13 18:25, Martin Nicholas via Amforth-devel wrote:
> Thanks for your work. I've just ordered a development board.
> 
> M.
> 
> On Sat, 13 Apr 2024 17:08:53 +0100
> ho...@tj... wrote:
> 
>> A RISC-V update.
>> 
>> AmForth-RV is now self-supporting (no C libraries required) for the
>> WCH CH32V307. Source and a pre-built hex file are here [0]
>> 
>> Best wishes,
>> Tristan
>> 
>> [0] https://tjnw.co.uk/amforth-rv
>> 
>> 
>> 
>> _______________________________________________
>> Amforth-devel mailing list for http://amforth.sf.net/
>> Amf...@li...
>> https://lists.sourceforge.net/lists/listinfo/amforth-devel
>> 
>>