Hello,
I have been working (and reading extensively) with AmForth this past week
or so as I learn Forth from Starting Forth. I wanted to try to play with
some eeproms on an I2C bus and from reading here I drifted toward the
i2c-eeprom-block.frt
post. The problem is that it seems there is no defer.f
t;
> #require defer.frt
>
> to
>
> #require defers.frt
>
> in
>
> amforth-6.8/common/lib/forth2012/blocks/blocks.frt
>
> may help.
>
> Best wishes,
> Tristan
>
> [1]
> http://amforth.sourceforge.net/TG/recipes/I2C-EEPROM.html?highlight=eeprom
>
operly I suppose. In any
case, it seems that I (should) now have a way to play around with an I2C
bus.
Onward (until next time...)
Mark
On Sat, Jun 27, 2020 at 1:32 AM Mark Roth wrote:
> Thank you Tristan for the welcome and all of it.
>
> Yeah, I had done that. I guess pointing out
On Sun, Jun 28, 2020 at 5:29 PM Erich Wälde wrote:
>
> Dear AmForthers,
>
> due to some unlikely fluctuation in probability space (or some
> other excuse) I declared this weekend to be "AmForth weekend 1"
> --- for me at least. While being working on this I decided to let
> you know, what is happ
Hopefully this will get sent to the right place...
I have been poking around the Perl script that creates the Refcard and
managed to get it to spit out a new (well, not quite but...) refcard.rst
which can then be build into the webpage when using make to create the
htdocs. It works if I change the
Actually not really impressive, yet at least. Mostly I just changed the
locations for:
my $texdir="../doc/source/TG";
#my $asmdir="../avr8/words";
my $asmdir="../common/words";
so they pointed at the right place to be built. Then I yanked some old asm
files from release/5.1 to find out why the ne
Okay, I got a little bit of a chance to play with this tonight. I wanted to
hack out the $prevline variables and forcibly replace them with the actual
beginning lines from the file. This then shows all the asm files in
common/words that have issues that need to be dealt with. It's at best a
hack be
Super. I just patched my local repo. All I had to do was to add the
python3-serial package (debian buster) and change the defaults for the
serial port and it fired right up. I'll try it next time I'm passing files
around to see how things go here.
Thank you,
Mark
On Mon, Jul 6, 2020 at 12:53 PM T
So here is a working hack to make a refcard with both the avr8/works and
common/words directory. Since I don't even sort of speak Perl I'll leave
any real fixes to someone who does. However, I made a few notes pointing
out the things that were the issue before.
There is still the issue of files tha
ere...
all the best,
Mark
On Mon, Jul 13, 2020 at 10:09 PM Mark Roth wrote:
> So here is a working hack to make a refcard with both the avr8/works and
> common/words directory. Since I don't even sort of speak Perl I'll leave
> any real fixes to someone who does. However, I m
I do see that the lists don't get properly sorted either. Still very
rough...
___
Amforth-devel mailing list for http://amforth.sf.net/
Amforth-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amforth-devel
, Jul 13, 2020 at 10:19 PM Mark Roth wrote:
> I see there are a few duplicates but I'm not really sure why. Like
> RECOGNIZE from recognize.asm. It must have something to do with the way the
> msp430 header is formatted that is different from other ones since it isn't
> all
Williams wrote:
> Hello Mark,
>
> Brilliant! There are AmForth words there I hadn't realised it had.
>
> Best wishes,
> Tristan
>
> On 16Jul20 00:49, Mark Roth wrote:
> > It's almost there at least as a page that can temporarily replace the
> >
make-refcard-rst ; cd ../doc
> make htdocs
> #make onlyepub
> rm -r ../tempwords
It does the trick for me locally anyhow.
So that completes my AmForth conversion via AmForth Weekend 1
:P
All the best (until the next one),
Mark
On Thu, Jul 16, 2020 at 11:02 AM Mark Roth wrote:
>
ugh, ignore the ">" at the start of the script lines obviously. I had the
whole mess quoted so it made a mockery of things.
On Fri, Jul 17, 2020 at 12:40 PM Mark Roth wrote:
> I cleaned up my diff of the svn (amforth-code) and put it up to see if it
> would be helpful. Be s
lesser change in the first diff I posted.
Their fixes of adding the ",0" are on lines 12 and 15 respectively and
could just be fixed manually.
Now I'm really done and the weekend is still half a day away.
On Fri, Jul 17, 2020 at 1:20 PM Mark Roth wrote:
> ugh, ignore the "
I corrected a small error in the second diff in build-info.tmpl. There was
an extra db padding that wasn't needed since it wasn't a string but a
number. I fixed it in the padding.diff link.
On Fri, Jul 17, 2020 at 3:17 PM Mark Roth wrote:
> I may as well be complete.
> http:/
On Sat, Aug 1, 2020 at 10:50 PM Erich Wälde wrote:
> thread hijacked intentionally.
>
'Thar be pirates!
>
> today I spent some time trying to understand the "make-refcard*"
> scripts in some detail.
>
> The script works roughly like this:
>
>
> - the first three lines are comments expected to
Because the zip is the Release package and the SVN is the Dev package I
would guess. The end user that isn't going to do anything more than grab
the zip, add the AVR stuff, quick scan the readme, go to the
APPL directory, make a copy of the template, hit make install (hopefully
after reading what n
Hello Tristan, Erich and fellow lurking AmForthers (I really do like this
intro Tristan) :)
It really does seem that you may have caught the tiger by the tail Tristan.
For better or for worse even!
For the better (hey, you caught the tiger) :
I think your layout really goes a long way toward docu
Is there a reason that when using rshift or 2/ the most significant bit
isn't zero padded? lshift and 2* do this correctly. I was trying to
implement a simple back and forth led on a port by starting with a value of
1 in the the port. Moving from right to left in the port works perfectly
but when m
,
Mark
On Sat, Sep 19, 2020 at 9:55 AM George Herzog
wrote:
> It's a common display situation in Forth. Leading zeros aren't display,
> even when they exist.
>
> On Sat, Sep 19, 2020, 2:24 AM Mark Roth wrote:
>
> > Is there a reason that when using rshift or 2/ the m
t, Sep 19, 2020 at 9:55 AM George Herzog
wrote:
> It's a common display situation in Forth. Leading zeros aren't display,
> even when they exist.
>
> On Sat, Sep 19, 2020, 2:24 AM Mark Roth wrote:
>
> > Is there a reason that when using rshift or 2/ the most signi
m files
> > 2. Modify the perl script to write out refcard as desired in the desired
> formats
> > 3. Connect this to the build system
> > 4. Connect the pre-built hex files and their refcards to the main
> documentation
> >
> > All can be done for a local build setu
Hello Erich,
so you found the subtle difference between @ and c@, congrats! :-)
>
> Mark Roth writes:
> > So because of grabbing a word it seems that I was bringing in the PINB
> > register as well that had a value in it. So that is where the extra bits
> > came from.
Hello. If your High fuse is set to 0xDC that is probably your problem. From
what I see that gives you a 1k boot section and Amforth is probably trying
to blast past that. I have some strange fails when I first flashed my 1284p
chips. Checking with a fuse calculator it looks like that chip should be
On Wed, Jun 2, 2021 at 6:37 PM Tristan Williams wrote:
> Hi Michael,
>
> I used
>
> FUSE : -U lfuse:w:0xff:m -U hfuse:w:0x99:m -U efuse:w:0xff:m
>
> Best wishes,
> Tristan
>
> That makes sense. It's the same high fuse setting as I suggested but with
the jtag interface activated. I don't use that
Hello AmForth. It has been some time and quite weird things since last I've
been here. I am still using AmForth with my trusty atmega1284p and learning
the language as time permits. I remember having heard talk that avra had
gotten (almost) to the point of being able to compile the source tree here
arette writes:
>
> > That is awesome news!
> > Brian-in-ohio
> >
> >
> > On Thu, Aug 24, 2023 at 2:59 PM Mark Roth wrote:
> >
> >> Hello AmForth. It has been some time and quite weird things since last
> I've
> >> been here. I am sti
th my fork again in the hope to
> >> > eventually catch that problem of long term stability. There is
> >> > absolutely no reason, why I have to reprogram one or two of my
> >> > controllers a few times per year, because they do not start up
> >> > aft
; > Hello,
> >
> > Seems simple to use the avra compiler.
> > Is it posible to show example how the build is doing?
> >
> > Cheers,
> >
> > Jan
> >
> > Verstuurd vanaf mijn iPad
> >
> > > Op 28 aug. 2023 om 09:02 heeft Mark Roth
I've been playing around when I had some time and put up a mirror of the
git repo Erich put up with all the releases as branches.
It can be found at https://github.com/CableGuy67/AmForth
Everything is included to make a copy appl/template and work from that.
Granted, if you already have a project
Hello, Tristan (and all the rest of the community).
I am guessing you mean the SourceForge repo and the mailing list? I wish I
could offer more help with this but I am at a loss with the assembly stuff.
It would be nice to have the website info protected (amforth.sourceforge.net)
since there is so
Hello all.
I managed to day to cobble together my AmForth "computer" which is pretty
much the reason for avoiding using wine to build things. It consists of a
raspberry pi zero W v1(whatever point 5 maybe) as a base with raspian lite
on it. That has a usb hub, an old palm pilot folding keyboard th
> Talking of maintenance, I note that avra (on Sourceforge) hasn't been
> > updated since 2019. Maybe it's completed?
>
> At least the home page points to https://github.com/Ro5bert/avra which
> has seen some commits since 2019.
>
There were some PRs for that one that led to a development branch
Here is the clean link.
https://github.com/CableGuy67/avra
On Mon, Sep 25, 2023 at 8:30 AM Mark Roth wrote:
>
>
> > Talking of maintenance, I note that avra (on Sourceforge) hasn't been
>
>> > updated since 2019. Maybe it's completed?
>>
>> At le
Good morning AmForth'ers (feel free to adjust the greeting with your RTC).
disclaimer: I am going to cherry pick the commentary by Tristan for this
post. You can safely assume that the single quotes are their's and any
quoted quotes are mine unless noted. This thread is getting a little wound
up a
Hello AmForth'ers. I like to see this little blip of activity and hope more
of the less than usual suspects join in with their thoughts!
On Tue, Sep 26, 2023 at 7:06 PM Erich Wälde wrote:
> Hello all,
>
> good to see some interest in this project again.
>
>
>
> Mar
to. Granted, it is a much bigger
> machine, but at least it is not collecting dust.
>
> The warning with "'" missing a closing ' ... yes well. It does
> work in the end, so no sweat.
>
> Cheers,
> Erich
>
> Mark Roth writes:
>
> > Hello all.
&g
On Fri, Sep 29, 2023 at 5:26 PM Keith Amidon wrote:
> On 9/26/23 23:33, Mark Roth wrote:
> > Hello AmForth'ers. I like to see this little blip of activity and hope
> more
> > of the less than usual suspects join in with their thoughts!
>
> I'm one of those &quo
On Sat, Sep 30, 2023 at 9:46 PM Keith Amidon wrote:
> On 9/30/23 03:17, Mark Roth wrote:
> > Hello weekend AmForth'ers
> >
> > So, while waiting to see what will happen with the repo I have continued
> to
> > play with a git version for my own use. I have rewo
;
> [1] https://sourceforge.net/p/amforth/mailman/message/37112236/
All the best to you as well. It feels good to be polishing up the tools to
polish up the Forth that was starting to bit rot in my brain.
Mark
>
>
> On 30Sep23 22:30, Mark Roth wrote:
> > On Sat, Sep 30, 2023 at 9:46 PM
This is really great to see Tristan. Bravo to your efforts getting this
going!
On Sat, Apr 13, 2024 at 7:24 PM 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
43 matches
Mail list logo