Enoch,
> (1) A GPLv3 project can include GPLv2 pieces thus, formally, you don't
> need anyone's consent. Also, all my contributions, those that you
> accepted (as many more you have rejected) carried the following
> spirit: \ Software license: AmForth compliant, see ... which means,
>
Hi,
It's time to disclose the secret around the license change.
A few months ago I started playing with the naken_asm by
Mike Kohn to get rid of the Atmel assembler. The first
changes were easy, some things were difficult to achieve
but one show stopper finally kncked me out: The naken_asm
cann
Ronny,
The atmega256x are somewhat special, a better starting point than
the template could be the atmega2561 project (same directory). It
is the one that I use to check the sources. At least it compiles
cleanly (enogh), from time to time I put them on a controller
and found no problems so far.
T
Hi Ronny,
> I already looked at this directory , but in this directory , there's a
> build.xml.
> How to compile this folder ???
I use ant (a java build tool, not exactly a replacement
for make, but funny). The build.xml is roughly the same
as the Makefile is for make.
Matthias
Hi John and Brad,
> This cross-pollination
> should benefit both communities: MSP430/CamelForth and AVR/Amforth.
I hope so. Exchanging forth code would be great. Flashforth recently
imported the I2C routines from amforth. I haven't looked
at the details, but my impression is, that it was not a
Hi,
amforth goes social ;) Every page on the website
got a few social media links for the usual suspects.
There is no need to worry however. Neither I nor
Sourceforge nor the mentioned companies will track
you. Unless you hit the links, of course.
The magic behind the scene comes from the Germa
Hi,
Release 5.6 is out and it is by far the biggest change in amforth ever.
It is the first version that runs on two different controller types:
AVR Atmegas and the TI MSP430 (Launchpad G2553). That has been made
possible by the work of others: Brad Rodriguez with his Camelforth and
the 4€4th proj
Hi Jeff
and welcome to the list :)
> I have developed a package for AMFORTH 4.6 that causes the USB engine
> on the ARDUINO Micro to enumerate as a USB ACM Communication Device
> (CDC 1.2 PSTN). The goal is to provide a USB serial port that requires
> no special driver support on any operating sy
Hi Zbigniew,
> As an interesting exercise I'm going to recreate a little computer,
> whose design has been published on pages
> https://sites.google.com/site/retroelec/home
Cute
>
> There is a statement: "An ATMega microcontroller is a Harvard
> architecture machine. So to be able to load and
>
> Yes, I'm aware of this. I was hoping to get some help here, how to
> (re)configure AmForth to make it work with the thing the way I want.
I doubt that it is a reconfiguration only. You'll have to change
some very basic things in the heart of amforth.
> it's feasible when using indirect-thre
Am Samstag, den 31.01.2015, 19:27 + schrieb Andrew Holt:
> Or am I doing something stupid ?
>
> Hi,
>
> I have built amforth using the latest downloaded source.
>
> The target is a UNO R3, with the am328p. I am programming it with a
> usbtiny.
UNO sounds like arduino. Right?
The arduino
HI,
I just released a new version of amforth. For the
Atmega controllers it fixes a few regressions introduced
with 5.6. The MSP430 port made a few huge steps forward.
Most notably are an almost complete double cell number
support (thanks to Martin for some assembly words), and
many many small fix
> I would to ask you a question: there is a statement on amForth's
> GitHub page: >> amforth is influenced by (early versions of) avrforth
> from Daniel Kruszyna http://krue.net/avrforth/ and by the series of
> articles "Forth von der Pike auf" by Ron Minke published at the
> "vierte dimension" at
> ,
>
> Made the change (hfuse was 0xde, changed to 0xd9) and now it works.
Great.
>
> BTW does anybody know a place where these fuse setting are conscisely
> explained ?
Wanna hear some bad news? Read the datasheets of the controller. Every
Atmega has its own set. Blame Atmel for that. If you
Hi,
for many years I was certain that Atmel Inc won't
allow a redistribution of it's tools independently
from their own software portal. Turns out, I was wrong.
Deep inside the Atmel studio installation I found
a file called license.rtf that basically told me:
yes you can, if you obey the term
Am Samstag, den 07.02.2015, 13:15 +0100 schrieb Zbigniew:
> 2015-02-07 13:07 GMT+01:00, Matthias Trute :
>
> > For easy usage I put it on
> > the sourceforge download portal in a ready-to-use directory
> > structure. Just download the tgz file and unpack it inside
> &
> I am trying to use amforth 5.7 an atmega168pa, which usart0 is connected
> to PC COM-port via max 3232 UART-RS-232 converter.
>
> I could get "
> amforth 5.7 ATmega168PA
> >
> " text on PC terminal, but I couldn't get anything else. Everything
> seems
> to be connected correctly,
If you can
Hi,
The release 5.8 is on its way to the mirrors and should be
downloadable real soon.
It adds the http://goparallel.sourceforge.net/
___
Amforth-devel mailing list for http://amforth.sf.net/
Amforth-devel@lists.sourceforge.net
https://lists.sourceforge
Steve,
I like it to get the un-modified first frustration
from people absolutely new to amforth. Really. My
first reaction to your mail was get lost (well,
something less polite in fact).
Now I think about what went wrong. Amforth is nothing
I am ashamed of. That may surprise you, but it defini
> Hi,
>
> I just tried to compiled the template project according to the following
> manual.
> http://amforth.sourceforge.net/UG/linux.html
>
> The compilation failed. Some ASM files are not in the INCLUDE variable.
>
> INCLUDE=-I $(AMFORTH) -I $(AMFORTH)/devices/$(MCU) -I ../../common
>
Than
Steve,
English is (according to Oscar Wilde) the common language
that separates English an Americans, so I certainly expect
a whole bunch of misunderstandings for non-native
speakers like me. But sometimes... So I beg your (every
native speaker's) pardon for my English. English is *not* my
prima
Am Montag, den 20.04.2015, 22:17 -0500 schrieb Tom Maynard:
> > Can't someone here with a working Arduino Uno R3 help Steve?
>
> I haven't looked, but at least at the release level when I downloaded my
> first Amforth (v5.3?), there were HEX files for all supported hardware
> buried somewhere in t
Dennis,
> I just need to find time to work out the compatibility issues and get
> my LyX document printing again and I will publish the update, probably
> within my coinForth repository, since amforth’s GNU license requires
> it. Then the source code will be more accessible too.
Since you're not
Hi Paolo,
I glad that the others on the list could help you get
a running system (thanks!).
> > ' refill-xon is refill ?? -13 15
>
> I cannot figure out the reason or what those errors mean.
It's a bit cryptic, I admit. But easy to decode:
The ?? signals an error (technically an exception is
Ian,
> I found this:
> http://amforth.sourceforge.net/TG/recipes/Arduino-Analog.html
>
> Is this current?
I havn't tested it for quite some time, but it schould work.
> I could not find the code referenced in the article.
Oops. Just added it to the repository.
> If the recipe is not curre
Hi,
I've already briefly mentioned a new documentation
section, but would like to spent some more words about.
I collect links or full documentation for a single
not-trivial projects. For now, 3 such projects are listed:
a RS485 based sensor network from Erich Wälde, the
ARD101 Tutorial from Den
Dennis,
> You should link to my GitHub repository at
> https://github.com/DRuffer/coinForth rather than the older version of
> my paper.
>
>
> The newer version of that document is at coinForth/doc/ARD101/ARD101.pdf
Thanks for the update (and the nice work)
Matthias
---
Hi,
Am Freitag, den 29.05.2015, 13:01 +0200 schrieb Paolo Garro:
> Hello,
> the amforth reference guide says:
>
> um/mod ( ud u2 – rem quot) unsigned division ud / u2 with remainder
>
> so: two-numbers um/mod should leave two-numbers on the stack, remainder an
> quotient.
> This seems not to be
> Any updates I might have missed on the avra/native *NIX assembler for AVR?
> I see a bit of activity on the avr mailing list but I'm still getting the
> impression avra is out of date.
I think avra is a dead horse, not even a zombie any more. I tried
naken_asm, but could not make it work wit
Am Freitag, den 29.05.2015, 01:32 +0200 schrieb pito:
> Hi, I've seen your work in progress includes the for-next loop.
> I do not have amforth hw handy these days, but I would be interested to know
> what the amforth prints with
>
> : test 0 for i . next ;
It prints a lonely 0 . Under the hood
Am Donnerstag, den 28.05.2015, 23:56 +0200 schrieb pito:
> Hi, there is a "complete fp asm lib" for amforth at
> https://github.com/igor-m/Amforth-Floating-Point-in-ASM
Cool stuff
btw: flashforth from Mikael Nordman ported the FP code and it
runs now on a PIC as well. Thanks to the GPL (v3). We
s
> (ud u2) are 3-cells not 2, so I was wrong.
>
> Please forget my previous message.
> There is no stack underflow raised.
There is no check whether there are enough data items on
the stack available. The stack underflow happens only
inside um/mod. The interpreter checks the stack only after
the
Paolo,
> Hello, would it be possible to have the echo char sent only after it
> has been processed?
Currently a character is echo-ed when it got inserted into the
input buffer. That involves the following steps
1.the usart module received it. An interrupt is triggered
2 the interrupt routine rea
> Why not use amforth's assembler.frt for words with a need for speed? Right
> now I need to reflash the base image every time I forget some words that
> are implemented in assembly.
It's not a matter of speed, but a matter of bootstrapping the system.
The whole forth compiler is written in fort
> is it true that leon maurer's floating point code has been integrated
> with the default package.
> is it also true that the ip/tcp code has been integrated within the
> default package?
Both packages are written by independent authors. They are not part
of the default amforth installation, si
Paolo,
> > key? . < 0 ok
means "no unread key available" (the 0)
> > depth . < 0 ok
> > begin key? until < ok
begin and until make only sense inside
a colon definition. Used interactivly they
do the wrong thing. Namely
> > depth . < 1 ok
> > . < 4516 ok
place a flash address on the data stack
Vladimir,
my Russion needs probably some refresh. After your hint I
did some checks myself, and indeed the quotations did not
work. The problem was a wrong LITERAL, introduced with
release 5.6, that got fixed by re-using the previous
version of literal.asm. Done with svn rev1866.
Thanks for the h
Hi,
I've just released version 5.9 of amforth. It should fix
the last remaining regressions introduced with the new
microcontroller architecture. The most importatnt probably
is the LITERAL fix, that stopped quotations.
The MSP430 now really got the DEFERs and VALUEs, that I
promised for the l
Am Donnerstag, den 13.08.2015, 15:36 -0500 schrieb Ben Pharr:
> I have a genuine Italian Arduino Duemilanove. I downloaded Amforth 5.9
> and flashed it with the included Makefile, as well as setting the
> fuses. It works, but only at 38400, not 9600, as the FAQ suggests.
>
> The 'ms' word was miss
Hi,
I just packaged the release 60th release of amforth. It
brings the MSP430 in touch with the AVR8 code base. You
can use values and defers now as well as wordlists and
recognizers. They all work exactly the same way on both
platforms, thanks to common code. amforth is probably one
of the rare a
Hi cadar,
> All I get is,
> "E=Input character not echoed."
>
> Exact same setup worked for 5.8 and 5.9. (OSX 10.10)
Really strange. There were no changes to the shell or the
serial port setup.
Could you please try the older versions of the shell too?
Or try another terminal, even a simple on
Am Montag, den 21.09.2015, 23:54 +0300 schrieb Hannu Vuolasaho:
> Hi!
>
> Sorry I can't help, but I have future proposition.
>
> Could there be somewhere in UART drivers or similar place huge
> .if badrate = 9600
> .message "Serial port is 9600 8N1"
> elif ...
>
> .endif
>
> This seems
Hi cadar
> Do we trust naken_util when debugging amforth on msp430?
> Could this be a bug?
I never used it.
Can you please use the --debug-serial command line option
of the amforth-shell.py? If everything works as expected
it should look similar to
amforth-shell.py -p /dev/ttyACM0 --no-error-
> $ python amforth-6.0/tools/amforth-shell.py -s 115200 -p
How/Why did you change away from 9600? Has the mac something
like stty to change the serial port speed to 9600 8N1?
Matthias
--
Hi,
dead end. On my Linux box (freshly rebooted)
everything works as it should
mt@noname: $ stty -F /dev/ttyACM0
speed 9600 baud; line = 0;
-brkint -imaxbel
mt@noname: amforth-shell.py -s 9600 -p /dev/ttyACM0 --debug-serial
--no-error-on-out
|I=appl_defs: 0 loaded
|I=Entering amforth interactive
Hi
> In amforth-6.0/appl/arduino/Makefile
>
> AS_INCLUDE=-I $(ATMEL)/Appnotes2 -I$(CORE)
> Should be
> AS_INCLUDE=-I $(ATMEL)/Appnotes2 -I$(CORE) -I $(CORE)/devices/ -I
> $(AMFORTH)/common
>
> Otherwise it won't compile.
>
Thanks, fixed.
The Atmel directory with the AVR Studio files etc moved
Hi,
A new release of amforth is out: 6.1. It fixes
a nasty bug that affects DOES> (and some more words),
so upgrade is recommended. The MSP430 family got
two new members: the F5529 and the FR5969. Both
are sold by TI on launchpad eval boards and
have significant more resources available than the
Atommann,
Awesome. I always thought that opensource means I can
study the source code. The Chinese commands do really work
via Bluetooth? Way cool.
More of that, I like it :=) :=)
Matthias
PS: hmm. There are languages that use a right-to-left direction
for ... symbols (IIRC Arab). A nice challen
Hi
> interestingly, this behaviour repeats when running the same test
> again.
> Looking at the code makes "depth" or the handling of depth a
> candidate
> for misbehaving, however, I did not look too deep.
>
> Can anyone confirm?
freshly flashed and loaded
(ATmega16)> -1 VERBOSE !
ok
(ATmega
> I found that revision 2030 fixes the behaviour above except for
> a very minor "case-sensitive" glitch. Patch below.
> Thanks for this fast resolution :-)
Not to thank me, others did the job.
> svn diff common/lib/forth2012/tester/tester-amforth.frt
> Index: common/lib/forth2012/tester/tester-
Am Samstag, den 19.12.2015, 12:59 +0800 schrieb Richard Burden:
> Hi all,
>
> really happy with amforth but there are frustrations. Having just
> downloaded version 6.1 and tried to rebuild my version 5 here are
> some
> suggestions based on my experience:
>
> 1. Docs are wrong. The default baud
> I can confirm the files do-value.asm and do-defer.asm were included
> in
> the build after reviewing the list file. Can anyone help me on this
> please?
In addition to what Peter wrote: The error messages are short indeed.
The numbers come from the Forth 2012 standard (chapter Exceptions):
-1
Am Sonntag, den 20.12.2015, 19:49 +0800 schrieb Richard Burden:
> Thanks Matthias. I've learned a lot today from Peter and your
> responses. I
> now have the serial data flowing correctly into the satellite tuner
> board
> I'm trying to turn into a signal generator.
Craig Lindley did something si
Am Mittwoch, den 06.01.2016, 10:30 + schrieb Sven:
> Hi,
> I have a GPS module with serial NMA0183 output ( 4800 8n1 ) and a
> Arduino board with amforth installed.
> My idea is to read the NMEA data from the Arduino serial interface
> and display it on a LCD, but the serial port is normally us
Am Samstag, den 05.03.2016, 18:53 -0800 schrieb James Bowman:
> Revised version of common/lib/anew.frt is below.
> Changes:
> - use new word FIND-XT
> - fix stack action for word-not-found case
> - add dependency on marker.frt for MARKER
All applied, thank you James!
Modification: #require is a a
Hello Dieter,
On Mo, 2016-05-23 at 21:39 +, die...@schoen.or.at wrote:
> Hi list,
> I recently found amforth and wanted to give it a try. I prefer the
> approach of an embedded interpreter
> to a traditional edit-compile-download-test cycle.
> First, I had the usual troubles with the fuses (I
Hi Tristan,
> but I could not get it to work. Uploading the code onto a freshly
> flashed uno would result in a hanging interpreter, requiring
> re-flashing. I would be very grateful for any pointers as to what I
> am
> doing wrong.
hmm. At the first glance, everything looks fine. You save the
d
Hi Tristan,
It took some time (and I had to fix a problem with the
current trunk code tree), sorry.
The good news: your code works for me. The bad news: I
cannot reproduce
what you wrote.
Everything works as expected, no hangs no problems at all.
I was slightly confused by the 1 second delay, b
Am Montag, den 20.06.2016, 00:27 +0100 schrieb Tristan Williams:
> Hello Matthias,
>
> >
> > The good news: your code works for me. The bad news: I
> > cannot reproduce
> > what you wrote.
> My apologies. I did not explain myself well. My code worked for me
> also. It was the Cookbook example I c
Hello Franklin,
> Question:
> [1] Is anyone using the date-and-time.frt code with more updated
> code? At least code that tracks leapyear or whether a month is 31
> days or 30 days. Also, how would you handle time date interpretation
> on register rollover for the date-and-time.frt?
The communi
Am Donnerstag, den 30.06.2016, 10:54 +0100 schrieb Tristan Williams:
> Hello James,
>
> Thank you very much indeed. I needed to adjust for not (yet) having
> find-xt but exactly what I needed. Thank you.
The anew.frt is available in earlier versions too. Essentially the
find-xt used to be find-na
Hi,
It's been a long time since the last release but some strange
effects needed to be handled with the FRAM equipped MSP430 devices.
They behave much like a diva and are worse than the fuses of the
atmega's ;)
Most of the changes are for the MSP430 devices, I started to learn
the assembler progr
Am Montag, den 04.07.2016, 21:37 +0200 schrieb MIchael Kalus:
> Is there a link to a list of those strange behaving?
You can easily reproduce them: just copy a few lines of
(assembly) code around. Guess why the file init.asm
still exists, the two lines of code belong to the mcu-info
structure. But
Hi,
I need some independent tests, so I'd like to ask for volunteers.
The command prompt got its characters via a simple interrupt
routine. That works quite well for years now. However some users
wanted to replace this routine with some other (forth hll) code
and were unpleasantly surprised tha
Hi Ian,
Am Samstag, den 30.07.2016, 06:07 -0400 schrieb Ian Jefferson:
> Hi Matthias,
>
> What kind of hardware would you need?
Someone with higher skills to organize my hardware
depot ;) In fact: I've ordered a few quartzes by
now, spending a few more cents in an already
planned order. It only
Hi,
> 1. The assembler refused to configure a baudrate of 460800.
> Increasing baud_maxerror did not help. When it compiled (at
> 200 or so) the serial connection displayed garbage.
>
> I checked the data sheet. It seems to suggest that indeed a
> speed larger than 230400 is hard to
Hi,
The release 6.3 has changes for both controller types, some are
common some are specific. The MSP430 now supports the
hardware multiplier, if available and adds some more words from
the Forth 2012 standard. The AVR parts use a different terminal
IO, making it easier to adapt different serial
Hi Tristan,
> I was wondering if anyone has used AmForth as an I2C slave on ATmega
> uc(s)? I've written a couple of I2C slaves in C++ using ATtiny uc(s)
> and used AmForth as an I2C master to communicate with them. I really
> appreciate the forth interpreter here. Whilst doing this I thought
> th
Am Mittwoch, den 25.01.2017, 13:02 + schrieb Tristan Williams:
> I replaced my i2c files with those from the trunk r2209 and all of
> i2c.c! i2c.c@ i2c.n! i2c.n@ i2c.m!n@ give me what I was expecting.
I've essentially re-implemented the i2c words after release 6.3.
Maybe I should finish 6.4
Am Samstag, den 28.01.2017, 10:46 + schrieb Tristan Williams:
> I have successfully written a couple of forth words keypad? and
> keypad
> that use i2c (PCF8574A) and an interrupt to tell me if/what key has
> been pressed on my keypad. This is currently completely independent
> of
> the keyboar
Am Dienstag, den 31.01.2017, 08:51 + schrieb Tristan Williams:
> Hello Matthias,
>
> Thank you. >rx-buf is wonderful. I have high hopes of making the
> keypad appear as a subset of the keyboard so they can use exactly the
> same code.
>
> The PCF8574A + keypad + interrupt also seems to work w
Announcing release $40 of amforth
This is the 64th release of amforth in more than
10 years development. It does some fine-tuning
of the I2C library on the AVR platform. There is
now code to use amforth as a I2C slave. Furthermore
it adds the 'c' number input format and support for
program speci
Hi Meino,
> I am running a 64bit-GENTOO Linux and I am quite familiar with
> Linux.
> I want to run AmForth on a Arduino Pro Mini Atmega328p/3.3V.
> With my USB-to-serial adapter I flash my ProMinis with the
> Arduino-IDE successfully.
You definitely need a "real" programmer to flash amforth. A
Am Donnerstag, den 20.04.2017, 09:04 +0100 schrieb Tristan Williams:
> AVR8 watchdog (reset and interrupt) atmega328p
>
> I wanted to use the 128 kHz watchdog oscillator as an additional
> timer.
The watchdog creates a full reset cycle, that means that the full
startup sequence is performed. Your
Hi,
a new release of amforth is now available. It fixes a
really nasty bug in the interrupt handling on the
AVR plattform. Erich did an outstandig job discovering
and fixing the bug, that sometimes made interrupts
simply disappear. This happened very seldom and
under very limited cirumstances (act
Hi Tristan,
> >
> > It would be a great contribution for the cookbook. Esp if it works
> > with
> > Forth code.
> This made me think that writing 4 or 5 assembler words was not the
> best way. Instead, have one assembler word wd! to perform the timed
> write to WDTCSR and then have forth words fo
Hi Tristan,
I've put your code online, revision 2252 contains the new
file. There is only one change: I renamed the wd! into !wdc.
It tells "store to watchdog control" and follows the more
or less informal convention that ! and @ can be preceeded
with size information and followed by location info
Am Montag, den 08.05.2017, 16:54 +0100 schrieb Tristan Williams:
> Hello Matthias,
>
> Two build questions.
>
> 1)
>
> I have downloaded 2252 and run into this error when building for my
> uno
>
> amforth-6.5A/avr8\drivers/generic-isr.asm(28): error: jz: Unknown
> instruction or macro
Mea cul
Hi Tristan,
> I have been enjoying using AmForth on AVR hardware but have a project
> in which I would like to use a physically smaller processor than a
> AtMega328p 28 pin DIP. Before thinking about SMD I wondered if there
> was a smaller DIP packaged processor that would run AmForth in the
> MSP
Am Montag, den 26.06.2017, 12:36 +0100 schrieb Tristan Williams:
> Thank you.
>
> The small project I had in mind needs little in terms of resources.
> In
> my perfect world there would be an 8 pin DIP microprocessor capable
> of
> running AmForth :)
Well, 2 pins for power and ground, two for th
Hi,
amforth 6.6 is tagged, packaged, uploaded and released. The changes are
more of the nice-to have side of the world, it's recommended to update
nevertheless. Details are as always available at the website
amforth.sourceforge.net
I'd like to invite you to the upcoming Forth source repository
a
Am Dienstag, den 14.11.2017, 10:01 +0800 schrieb Richard Burden:
> I couldn't find the reason for the error but what I found follows:
>
> >
> > 15 buffer: test
> ok
> >
> > test 10 accept
> 123456789012
> ok
> >
> > test 15 type
> 1234567892 ok
>
> Should have been 1234567890
> The 2, being
Am Donnerstag, den 07.06.2018, 21:05 +0100 schrieb Tristan Williams:
> Hello,
>
> I am clearly not understanding how something works, and would be
> grateful for any help.
>
> I am decoding infrared remote control codes using the input capture
> mode of TIMER1 on an ATmega328P (UNO). This works s
Hi,
> Thee should be a NACK as indicated below, I believe.
I cannot currently test it, but your fix looks plausible. Applied
as of rev. 2300
Thank you
Matthias
--
Check out the vibrant tech community on one of the worl
Hi,
I've just tagged and published the release 6.7. It contains some
bugfixes for the existing platforms (thanks to Richard and Martin).
Due to a generous donation from the German Forth e.V. a RISC-V board
found it's way to my desk and I started porting amforth to it. As of
this release, only the
Hi Martin,
your mail hit my spam folder... Sorry
> Looks like there is a bug in file:
> /amforth-6.7/avr8/words/store-i_big.asm
> That is:
> > out_ rampz, zl
>
> should be:
> > out_ eind, zl
>
> EICALL and EIJMP both use this register for the extra bits.
>
I cannot test it right now, but you
Am Freitag, den 19.10.2018, 14:46 +0200 schrieb Tristan:
> Hello Martin,
>
> Very intriguing, just when I am away from my machine so I can’t test
> things out!
>
> If I remember correctly, the default Amforth avr build uses (rx,tx)
> interrupts to handle the serial prompt. If at the serial prompt
Hi,
when I look for a definition, a recursive grep is my best
friend, it is fed with the usual colon definition ": "
including proper whitespace. It's not completly foolproof
but works most the time
$:~/amforth$ grep -ri ": \.s " *
common/lib/forth2012/tools/dot-s.frt:: .s depth 0 ?do depth i -
>
> Is my simplistic picture correct?
Yes
> Or can the assembler words @ ! +!
> indeed be interrupted from within AmForth?
No
Matthias
___
Amforth-devel mailing list for http://amforth.sf.net/
Amforth-devel@lists.sourceforge.net
https://lists
Am Freitag, den 26.10.2018, 15:20 +0100 schrieb Tristan Williams:
> Jan,
>
> In release 6.2 [1] find-name was renamed to find-xt. I think the
> forth
> code for see has not been updated to reflect this. By editing see.frt
> and changing find-name to find-xt I was able to produce the
> following.
> : PWM_init
> PWM_A pin_output \ Set pin 9 (PB1) to output
> %1010 TCCR1A c!\ Store constant
> %00010001 TCCR1B c!\ Store constant
This stores a byte, &400 is beyond 8bits. Try ! instead
> &400 OCR1A c! \ Store constant
Matthias
_
> Is it correct that I can use this timer with his interrupts freely
> without any harm/restrictions for Amforth?
Yes, that's correct.
Matthias
___
Amforth-devel mailing list for http://amforth.sf.net/
Amforth-devel@lists.sourceforge.net
https://li
> I think some where in amForth TCNT1 is overwritten!
I can assure you, that there is no code in plain amforth
that overwrites your settings. It's either your code or
the hardware itself.
Matthias
___
Amforth-devel mailing list for http://amforth.s
> My leaving question is the word “f_cpu” in the code of Timer1.frt.
> When I execute it I get two values on the stack.
It's the current clock the controller is running at.
It's a double cell number, since the 16bit controllers
run too fast to keep this number in a single cell.
Matthias
___
Hi,
> When I do the command $1d c@ . I get a value of 0001000. How is that
> possible? Or do I something wrong?
Historically Atmel defined 32 special addresses
that together with
certain opcodes that are used for
some IO or CPU relevant things (e.g.
the machine
status register which is one of th
Am Dienstag, den 06.11.2018, 17:41 + schrieb Jan Kromhout:
> Hi,
>
> When I use for example gforth I can use the c, word. I wont to use
> this also in amForth in combination with c@.
It's a bit more complex...
, (comma) appends to the dictionary in flash memory. c@ cannot
access the flash ad
Am Freitag, den 09.11.2018, 15:49 + schrieb Jan Kromhout:
> Hi,
>
> I wont testing amForth on the Leonardo.
> What are are the fuse settings for the Leonardo?
The Makefile in appl/arduino contains some lines starting
with leonardo, that's probably a start.
Matthias
__
Am Dienstag, den 13.11.2018, 15:53 + schrieb Jan Kromhout:
> Hello,
>
> I are struggle with the buffer:
> As you can see I create two array’s.
> I expect that when I initialize this I can read the value.
> It's not true. As you can see, values are overwritten.
> Am I doing something wrong?
I'
Am Montag, den 03.12.2018, 18:22 + schrieb Jan Kromhout:
> Hello,
>
> I have this code in my program (Arduino IDE).
>
> // Standard ASCII 5x7 font
>
> static const unsigned char font[] PROGMEM = {
> 0x00, 0x00, 0x00, 0x00, 0x00,
> 0x3E, 0x5B, 0x4F, 0x5B, 0x3E,
> 0x3E, 0x6B, 0x4F, 0x6B, 0x3E,
Am Mittwoch, den 05.12.2018, 13:50 +0100 schrieb Jan Kromhout via
Amforth-devel:
> Hello
>
>
> I wont to use the forward declaration “forward:” to solve my
> recursive word roll.
>
> Is this use of forward: correct?
the forward declaration is for cases in which
one word calls another one before
1 - 100 of 534 matches
Mail list logo
