so, it's not offlist at all, sigh.
Oh, well.
E.
Erich Wälde writes:
> [[PGP Signed Part:Undecided]]
> Hello Tristan,
>
--
May the Forth be with you ...
___
Amforth-devel mailing list for http://amforth.sf.net/
Amforth-devel@lists.source
key:
pub rsa4096 2020-12-12 [SC]
03D05884448B9F17B9EC536ADBA0681A2AFE4FE1
uid [ultimate] Erich Wälde (AmForth project)
-- next part --
h...@tjnw.co.uk writes:
> A risc-v update.
>
> AmForth-RV update
>
> Good progress made with
Hello all,
good to see some interest in this project again.
Mark Roth writes:
> Good morning AmForth'ers (feel free to adjust the greeting with your RTC).
>snip<<
>> Tristan wrote, if I'm not mistaken
>>
>> The fact is that this project is still useful.
>>
>> I completely agree.
As promised.
The file is plain ascii .org mode format:
--- Howto-make-a-release.org ---
# 2020-10-12 amforth/erwaelde
* How to properly make a release?
Somewhat machine readable version.
** Intro
#+begin_quote
1. check all version numbers in trunk
Hi Mark,
Mark Roth writes:
> Here is the clean link.
>
> https://github.com/CableGuy67/avra
Thanks for pulling this together.
I can successfully build the executable on debian 12, gcc 13.2
on a riscv64 machine. :)
I would kindly suggest to increase the version number, or add
some local
Hello Mark, hello all,
congrats to your hack-box! :)
This is very close to what I am currently using (software wise).
I had ordered a Hifive Unmatched, a riscv64 computer in miniITX
Format. And once I got it going with Debian unstable, I
installed: avra, minicom (terminal), avrdude (burner),
Hello Brian and Mark,
very nice to see emails on this list :)
Compiling amforth with avra?
I have made numerous experiments a long time ago and again more
recently. If memory serves me well:
- Amforth had been good with avra, at least in the 4.x range.
- However, avrasm2.exe could do more
ably not a good estimate. So, speak up, make yourself heard.
Thanks!
Cheers,
Erich
Erich Wälde writes:
> Dear AmForthers,
>
> I am herewith stepping down from the maintainer role of AmForth. For details,
> read on. If anyone is interested to take over, get in
Erich Wälde writes:
> [[PGP Signed Part:Undecided]]
>
> Dear AmForthers,
>
> I am herewith stepping down from the maintainer role of AmForth. For details,
> read on. If anyone is interested to take over, get in touch with me.
>
>
> In 2020 I received the logins
Dear AmForthers,
I am herewith stepping down from the maintainer role of AmForth. For details,
read on. If anyone is interested to take over, get in touch with me.
In 2020 I received the logins of amforth.sourceforge.net, basically because I
was lucky enough to have met Matthias personally a
Hello Stephen,
Stephen Simmons writes:
> I have been trying to get the 644P 'sanguino' to build and run, but it
> never initializes uart0 properly. Leaves out the initialization of the
> UBRR. The baud rate is defined in the INC. I believe that I have gone
> through the instructions as
Hello Stephen,
welcome to the list!
Stephen Simmons writes:
> I have been trying to get the 644P 'sanguino' to build and run, but it
> never initializes uart0 properly. Leaves out the initialization of the
> UBRR. The baud rate is defined in the INC.
Well, the 644 has *two* serial
Hello Helge,
Helge Kruse writes:
> 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):
&
Hello Helge,
welcome to the list!
I'm late to the show, but anyways ...
I personally would not use the serial console for something
else, but rather use a atmega644 or similar, which features two
separate serial interfaces.
Replicating code is imho most easy, if a controller is read back
via
Hello Michael,
Michael Picco writes:
> Hello!
>
> I finally have figured out how to efficiently interact with Amforth on my
> mega2560 and have installed much of the I2C stuff on it.
Good!
>
> Question:
>
> Has anyone worked out how to talk to the BME280 sensor using Amforth? Wading
> through
I took the liberty to snip off the thread.
Hello Michael,
Michael Picco writes:
> Hello!
>
> I seem to have stumbled across an issue.
>
> First code I wrote was to blink the LED onboard. This worked just fine.
> Then I went to add 'marker'. Entered it line-by-line ... got the 'Ok' after
>
Hello Michael,
welcome to the club!
Michael Picco writes:
> Hello,
>
> I am attempting to use the mega2560 as a nicely featured development platform
> for AmForth-6.9. The machine I'm using is a Win10 box, with Microchip Studio
> version 7 installed.
>
> In the zip file, under
Dear AmForthers,
despite Dieters excellent demonstration of how to deal with branches:
> Dear Erich,
> One of the easiest ways to look for the evolution of a file is
> $ git log --all --graph
> This lists all commits, where was changed, and rather nice ascii-art graphs.
> The --all flag
Ok, found an omission,
> $ git push --set-upstream origin master
is not enough, it will push only master. So I issued
> $ git push --all
now all branches show up in
https://git.sr.ht/~amforth/code/refs
and in
git pull
git branch -a
Cheers,
Erich
Erich =?utf-8?Q?W=C3=A4lde?= writes:
> Dear
Dear AmForthers,
I have added the public key of Carsten Strotmann to
https://sr.ht/~amforth
This grants write access to any aspect of the repository.
I know Carsten personally since probably 2007 iirc. We first met
on the "Linux-Tag" while it was in Berlin for the first time.
Since then we
Dear AmForthers,
I forgot to "document", how I did it, in case someone else finds
this useful.
Cheers,
Erich
working on Debian 10 (buster), amd64
cd path/to/svn/working/tree
svn up
svn info
# Path: .
# Working Copy Root Path: /home/ew/eGeek/sourceforge.net/amforth-code
# URL:
Dear AmForthers,
I have just now converted r2457 of
svn://svn.code.sf.net/p/amforth/code
via svn2git and pushed it to
https://git.sr.ht/~amforth/code/tree
If you would please be so kind as to give it a try.
Test your usual workflow.
Are all files in the expected places?
Can you assemle your
Dear AmForthers,
long time no hear. Yes I know. All I can say is: I was very un-motivated to do
anything involving atmega microcontrollers or AmForth. When I packed
everything away in September 2020, I was very frustrated. I wanted to
implement a new version of my data collector stuff, and it
Hello,
as promised, I added the script "pd2amforth" to the source tree,
see amforth/trunk/tools/partdescription/...
> $ svn commit . -m 'added tools/partdescription'
> Password:
> Sendingdoc/source/index.rst
> Adding tools/partdescription
> Adding
Hello Stephen,
welcome to the list!
Stephen D writes:
> Hi all,
> would like to try running amforth on one of the new AVR processors, the
> AVR128DA48 to be exact. A Curiosity Nano board turned up this week and I'm
> keen to give it a try.
>
> Am a total newb with regards to amforth and forth
Dear AmForthers,
2020-11-02 I wrote:
> 3. Add testing scripts --- I have a set of scripts for that, but I
>have not run this stuff yet. However, in my opinion adding a
>working test suite is far more important at the moment, than
>anything else.
>
>This includes preparing some
Hello Tristan,
Tristan Williams writes:
> Hello AmForthers,
>
> With the season's TV not to everybody's taste and ownership of the
> remote control contested, having an alternative activity is a good
> idea. Over the decades there have been many good Forth papers written,
> but finding
Hallo David,
long time no see :)
well, unfortunately ...
I have tried to assemble amforth-6.9 for atmega8.
The uart thing is quite simple to fix, as has been pointed out:
in template.asm:
-.include "drivers/usart_0.asm"
+.include "drivers/usart.asm"
And you made some progress on the "Overlap
Dear AmForthers,
Monday evening doing a little AmForth related stuff, how is that?
Full disclosure: I am using emacs/org-mode. So I created a habit
for Monday. And boy those red colored bars saying "not done"
become annoying quickly. So better do something :)
Contemplating the Test Cases
Hello Carsten,
Carsten Strotmann writes:
> please find attached two patches for the amForth website
> source, ARM pages.
thank you for the patches. I have committed them and updated the
web site --- not without deleting it first, sigh.
> My editor (Emacs) cleans the whitespace, if that is an
Dear AmForthers,
some time ago (2020-08-02), Mark Roth suggested to come up with a
"road map". Now while mapping unknown territory is a challenge of
sorts, it might be not that difficult in this case.
This my personal point of view, it might change anytime without prior
notice.
1. Accumulate
Hello Jim,
Jim Tittsler writes:
> On Mon, Oct 19, 2020 at 2:46 AM Erich Wälde wrote:
>> One thing remains: the "download the latest release" Button still
>> points to 6.8 --- I have no idea, where to look. Oh well.
>
> As project administrator, visit
> https:
Dear AmForthers,
today I called it "release 6.9".
The "commits" part is quite simple.
- r2452 -- only doc/source/index.rst
- r2453 -- copy of trunk as release/6.9
- r2454 -- in trunk increment version strings (3 files)
There is some more work in creating the tar balls.
I have decided to
Dear AmForthers,
I tend to disagree on some of this ...
What you argue for is a "architecture and project-specific"
"reduced" refcard. At least this is, what I understand.
I have used the refcard extensively in the beginnings of my
AmForth journey. And I would argue any time, that the refcard
Hello Mark,
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.
>
> : cylon
>> $ff ddra c! 1
resend to list.
Hello Tristan,
thank you indeed for pointing this out!
> Erich Wälde writes:
>> Tristan Williams writes:
>>> Erich Wälde writes:
>>> After that all the remaining hex files could be built.
>>> ONLY arduino/leonardo.hex is missing.
>>
>
Hello Brian,
after the stunt getting leonardo to build a similar stunt makes
the butterfly building again :-)
> Erich Wälde writes:
>> Brian writes:
>> I am running the latest version of amforth on an avrbutterfly.
>
> Oh, cool! You made me curious. This is a atmega169 contr
Dear AmForthers,
as previously announced I made this weekend the official
AmForth Weekend 3 / 2020-08-29,30
So what happened?
- Commits
r2450: one line whitespace fix in amforth-shell.py (2020-08-04)
https://sourceforge.net/p/amforth/code/2450/
r2451: one line python2->3
Dear AmForthers,
I asked:
> - How do I actually create a new release? Copying the files is
>one thing, but where do I need to change the version? There
>is more than one place, I'm afraid. I also happen to know
>that after 6.9 there cannot be 6.10 due to a limitation
>created
Hello Tristan,
Tristan Williams writes:
> A one line patch for amforth-shell.py to correct a python2/python3
> syntax error. It occurs when using the --no-error-on-output
> option. Below is a unified diff against r2450/trunk/tools/amforth-shell.py
>
> --- amforth-shell.py
> +++ new-shell.py
>
eed a lot (a real lot) of extra packages. The real
> question is, "How are the zips created?"
Yes, agreed, and probably part of the bigger question:
How (in detail) did Matthias roll up an official release?
Well, I'll find out.
Cheers,
Erich
> All the best,
> Mark
>
> On Th
Hello all,
Martin B. found out that the content of the download.zip files
is different from the content of the svn checkout. For example
./doc/Makefile is not present. However, the zip file has more
files alltogether:
$ find releases/6.8 -type f | wc -l
2389
$ find ./amforth-6.8 -type f |
Dear AmForthers,
as previously announced I made this weekend the official
AmForth Weekend 2 / 2020-08-01,02
So what happened?
- Commits
r2447: tools/amforth-shell.py ported to python3
the corresponding patch was kindly contributed by Tristan
Williams, thank you!
Hello Tristan,
Tristan Williams writes:
> Is it possible to build the current AVR AmForth so that it can
> co-exist with a bootloader?
>
> There is a reference in the documentation to changes that would be
> required
>
> http://amforth.sourceforge.net/TG/AVR8.html?highlight=bootloader
>
> and
Dear AmForthers,
I had pointed out that I use an old version of amforth-upload.py,
because newer ones did not work for me. So I spent some time with
this.
Short version for "trunk":
The expanded path of the filename given as argument is not passed on
to be opened. Please find two patches
Hello Tristan,
Tristan Williams writes:
> Hello,
>
> I have modified amforth-shell.py to run under python3 and put up a
> patch here
>
> https://tjnw.co.uk/new-shell/doc/
>
> as the patch seemed a little too large for a mailing list.
Thanks for the patch. Commit r2447 is yours.
The patch is
Hello Brian,
thanks for your message!
> ... to the arm based systems where the 'real' work can be
> done.
Well observed imho. I read a book on PIC microcontrollers many
years back, where the authors made a case that if need be,
counted loops (in asm, no matter which way through the if
Hello Mark,
short answer: I'm impressed!
I'm still fairly fluent in perl, so I expect this can be fixed
to produce a refcard again. And yes I also expect to fix up the
source .asm files. Regarding those headers: IFF the files were
indeed generated from forth code, then I would like to include
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 happening, and what is going around in my head
regarding AmForth.
fcard from
sources? Probably, it just sounds like quite a bit of work.
After that we can see, how to accomodate the generation of the
refcard across targets.
If anyone feels like spending some time on this, please go ahead
and please report your findings here on this list.
Cheers,
Erich
Hello Martin,
Martin Nicholas via Amforth-devel writes:
> Somehow this has gone from the RH menu:
> http://amforth.sourceforge.net/TG/refcard.html
Good point, thanks for the report.
Some time back I had a conversation with Matthias about the
reference card.
- it has grown unbelievably
- it
Hello,
tur bine writes:
> Hi just wished to expand my knowledge base with forth, the stack pointer
> increases during runtime and does not decrease unless using certain
> commands if etc, can somebody explain what happens when sp and thus the
> stack gets full please
Martin has answered your
Hello Tristan,
back to mulitasking on AmForth.
I spend an afternoon to create a background task, which does some
output by itself (see code below). There is nothing really new in
this. If I equip the background tasks with base and pointers to emit
(and emit?), it does work, including pictured
Hello Tristan,
Tristan Williams writes:
> Hello Erich,
>
> Within task-init from multitask.frt I think a task's entire tcb/user
> area is filled with zeros and then only the values from the task's
> (flash) tib are copied across to the task's tcb/user area. A value for
> BASE is not stored
Hello Tristan,
thanks for your message.
My below answers/comments only regard AVR8. I have currently no
idea, how this is similar or different in the other 3 targets.
> I revisited "Redirecting emit from within a task in AmForth",
> as I still like the idea of having a self contained task
Dear AmForthers,
so I "jumped" and actually wrote new content to the amforth
repository and project web site.
D0> has been fixed.
I added a new section "Opinion" to the website, sort of a blog.
There I added a entry describing how I went about fixing "D0>".
If you find errors, things not
Dear AmForthers,
I'm quite certain, that many of you have noticed Matthias'
unusual silence. Since July 2019 he was fighting a serious
health issue. His wife has informed me that Matthias has
left this planet for good on Wednesday evening (2020-03-25).
We wish him an exceptionally pleasant
Dear AmForthers,
to my knowledge noone has ever complained that " -jtag " ceased to
work after version 5.5. Is it only me using this command?
Short version:
Since version 6.2 the content of the files
> releases/*/avr8/devices/*/words/no-jtag.asm
is essentially an empty function. This can be
Hello Martin,
> Also, a bug in D0>:
> Hmmm, something wrong here I feel:
>
>> (ATmega2560)> decimal 1553994000. d0> . 1572137999. d0> .
>> -1 0 ok
yes there is.
Short answer:
The assembly version produces the wrong result,
when the MostSignificantBit of the lower *word* is set.
>
d
> then respond to (or poll) its sensor and also output the result. This
> I could do by writing directly (not via EMIT) to their output medium
> (display, leds, sound) for each sensor. I think doing this by
> redirecting EMIT within the task would be a better solution - but not
> on
Hello Tristan,
I need to look into my stuff, but that won't happen before next
week. If I understand you correctly, you want to "shut down the
output of the task, no matter what." I think, I have done this
somewhere ... but I do not remember the details. You need to
place " ' drop " in the
Hello Tristan,
> Thanks again for your help.
You are welcome!
> I managed to modify applturnkey to read from internal EEPROM,
> which was the missing part of my project to have AmForth use
> the RC oscillator as a clock source.
Glad I could help. It is often only a tiny piece of information,
Hello Tristan,
>
> In avr8/amforth-eeprom.inc the top line is
>
> .dw -1 ; EEPROM Address 0 should not be used
>
> Does this mean that $0 is reserved and used by AmForth internally or
> $0 is not to be used because historically it has been used by other
> programs e.g. storing
Hello Tristan,
Tristan Williams writes:
> Hello,
>
> I would like to modify my AVR build of AmForth to read/write a byte
> from a known fixed EEPROM address, perhaps from applturnkey. This byte
> may be written outside of AmForth. Is there a safe area of EEPROM
> from which to do this or a way
Dear Jan,
thanks for your message.
see my answer below the text.
Jan Kromhout via Amforth-devel writes:
> Hello,
>
>
> After trying for a while, I failed to get these three words together.
> Do not master the bitmask. Despite the examples and the email. Can someone
> please help me with
Hello Jan,
> I need to do a bitmask on register.
>
> These are the constants, and mask
>
> $24 constant ddrb
> $25 constant portb
>
> \ bit masks
> %000100 constant mSS ( PB2 )
> %10 constant mSCK ( PB5 )
>
> I wont
> 1. to set the bits in ddrb with the bitmask mSS
> 2. to clear bits in
Dear Jan,
allow me to observe the following things:
> // enable SPI.Master
> SPI.setDataMode(SPI_MODE0);
> SPI.setBitOrder(MSBFIRST);
> SPI.setClockDivider(SPI_CLOCK_DIV4);
> SPI.begin();
The words and the concepts behind them are documented in great
detail in the datasheet of your
gt;
> Jan
>
>
>
>
>> Op 7 jun. 2019, om 19:50 heeft Erich Wälde het
>> volgende geschreven:
>>
>> Hello Jan,
>>
>>
>> Jan Kromhout writes:
>>
>>> Hi Tristan,
>>>
>>> What to load in the right sequence
Hello Jan,
Jan Kromhout writes:
> Hi Tristan,
>
> What to load in the right sequence to fellow the examples in
> http://amforth.sourceforge.net/TG/recipes/SPI.html ?
> If I have the right sequence of loading the screens I will start as you
> mentiod.
>
> Kind regards,
>
> Jan
>
>
>
> Op 7
Hello Jan,
Jan Kromhout writes:
> I have create a turnkey project, how can I remove the turnkey
> so it will not start at start-up?
:-)
Well, let's see. How did you "register" the turnkey application?
forth> ' my-turnkey to turnkey
maybe with "is" instead of "to". So the question reduces
Hello Fred,
f.zelders--- via Amforth-devel writes:
> I created a word that converts a positive double-precision number to an 8
> character string like this:
>
> : dpNumberToString ( d -- address count )
> <# # # # # # # # # #> ;
> This works fine for positive numbers.
> However I want
Hello,
Peter C. Hauser writes:
> If you want hardware serial you cannot really use the Arduino
> Uno as the ATmega328 microcontroller only has one UART, which
> is used by Forth for its communication.
atmega644p has 2 serial interfaces. It is the same package as
the 328p. I have toyed around
Hello Jan,
> Where can I find some description of the used error numbers?
>
> I have now -4
read the fine document at
http://amforth.sourceforge.net/TG/Architecture.html#exceptions
:-)
Erich
--
May the Forth be with you ...
___
Amforth-devel
Hello,
for those who like to read other peoples Forth code, I have added
another clock to the commented projects/clockworks. It features a DCF77
radio receiver and reads the time information from there. However, this
code is lengthy.
Hello Jan,
Jan Kromhout via Amforth-devel writes:
> Hello,
>
> I was looking into some words (.asm).
> Can someone explain me why the content of the first data word is different.
> PLUSSTORE => .dw $ff02
> RSHIFT => .dw $ff06
> PLUS => .dw $ff01
I'm sure this is explained somewhere, maybe in
Hello Jan,
>
> Found the float.fth file.
> After loading the neccesary files tried to compile the filed
>
> Two things are missing and can’t find them in the AmFort-6.7 directory.
> 1. What is the definition of d>s
That was answered before:
: d>s drop ;
@martin: just adding a 0 to TOS on "s>d"
Hello Jan,
Jan Kromhout writes:
> Hi,
>
> Flashing the Arduino Uno is giving no problems.
>
> Try to flash the Leonardo.
> I’m using the Pololu AVR programmer v2.1
> This is my command.
>
> MacBook-Pro-van-Jan-10:avrdude jankromhout$ avrdude -p m32u4 -c avrispv2 -P
> /dev/tty.usbmodem00230362
Hello Fred,
> The word s>d is in the common/words/ folder but d>s ins't :-(
: d>s ( d -- s ) drop ;
Assuming that the high number (2 Bytes) resides on top-of-stack, the low
number below that.
Cheers,
Erich
>
>
> Groet!
>
>
> Fred
>
>
>> Op 11 dec. 2018, om 13:24 heeft Matthias Trute het
Hello Jan,
you were faster than I could think of your problem.
Yes, /everything/ needs to be initialized on reset.
And yes, very strange things can happen, if you
miss one little thing.
Glad you found it!
Erich
Jan Kromhout writes:
> Hi,
>
> Also find the problem.
> In my program I use
Hello Jan,
> The i2c scanner is seeing $38, should i still shift to $70?
Don't be afraid of just trying this. There is nothing that
breaks, if you happen to use a different i2c address.
So I dont' think so, but let me check
> | $ ls -l /dev/ttyUSB0
> | crw-rw 1 root dialout 188, 0
Hello Jan,
> Where can I download the software of the articles of Clock Works.
> The link https://wiki.forth-ev.de/doku.php/projects:clockworks ...
Thanks for reminding me, that there is a broken link in the
game. This one is better:
Hello Jan,
your i2c address: "$38", is this the 7bit address? You might
need to shift it by one position to "$70".
Just an idea.
Cheers,
Erich
Jan Kromhout writes:
> Hi,
>
> This is my first step on the I2C road.
> I have a Gravitech shield for the Arduino, that work well.
> The code is very
Hello Jan,
Jan Kromhout writes:
> Hi,
>
> I have this simple Arduino program thats put a PWM signal to port 9 of the
> Arduino.
> Checked with my RIGOL and the PWM is changed when I change the value of ppm.
>
> #define PWM_A 9 /* Pin-9 on Arduino Board */
>
> void setup() {
>
Hello Dimitri,
> It's always nice to introduce oneself together with a silly
> problem.
We would not have known about you without that :-)
Welcome to the club!
And happy Forthing,
Erich
--
May the Forth be with you ...
Hello Frank,
welcome on the list!
Eye ball inspection and comparing to a project of mine and
mulittask-test.frt did not show a problem to me, however
instead of
> $20 $20 $10 task: task_demo
try
> $40 $40 $10 task: task_demo
just in bloody case. Allthough 16 cells sound like a lot, its
Hi Richard,
thanks for your message.
> I'm updating the earlier version of amforth I used to control a Si4133 PLL
> chip on a satellite tuner board. With a 2 line LCD it allows me to generate
> test signals from about 800MHz to 1600 MHz in steps as small as 10kHz. A
> very crude instrument but
Hi Richard,
> I tried this twice for two projects and no errors in the assembly were
> noted. Once again thanks for putting me on the right track.
Congratulations! And thanks for reporting back on this.
I do know, that setting up stuff to play with microcontrollers,
can be a source of endless
Hello Richard,
disclaimer: I do not use Windows myself ...
> I create a batch file, make.bat, containing the following line:
> avrasm2.exe -fI -o myproj.hex -e myproj.eep -l myproj.lst -I .\ -I
> amforth\common -I amforth\avr8 -I include -v0 myproj.asm
>
> My project structure now looks like
>
Hello Meino,
tu...@posteo.de writes:
> Hi,
>
> Before I install a lot of software on my GENTOO-Linux only
> to recognize I had done the wrong assumptions I would like
> ask, whether I have the needed prerequisites for AmForth:
>
> I am running a 64bit-GENTOO Linux and I am quite familiar with
>
Hello all,
Matthias Trute writes:
> 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
Hello Tristan,
welcome to the club :-)
Tristan Williams writes:
> Hello,
>
> I have only recently found AmForth, and have, over the last month or
> so, been making led flash, getting the time from rtc, displaying
> things on an lcd etc. It really has been a most enjoyable and
> educational
Hello Andrew,
Andrew Read writes:
> Dear AmForth developers,
>
>
> Whilst compiling AmForth for the atmega644 I receive a number of misalignment
> warnings of the form:
>
>>>".cseg .db misalignment - padding zero byte"
>
>
> for example:
>>> amforth-6.1\avr8\words/nfa2cfa.asm6
>
> that
Hi Matthias,
Matthias Trute writes:
> 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
Hello all,
when testing a bunch of code with AmForth 6.1/trunk and
trunk/common/lib/forth2012/tester/tester-amforth.frt
it seems to me that the first test in any run fails:
> amforth-upload.py -t /dev/ttyUSB0 ../../05_amforth_recipes/unixtime_test.fs
> marker --unix-time--
> ok
> ~60> \
Atommann,
Congratulations!
I'm very impressed with what you and your team mates came up,
especially the Forth code with Chinese commands. Very nice
project! You should be proud!
Cheers,
Erich
Atommann writes:
> Hi,
>
> About two weeks ago I met a pretty lady in our office, she told me
>
Hello Ian,
Ian Jefferson writes:
Question:
I found this:
http://amforth.sourceforge.net/TG/recipes/Arduino-Analog.html
Is this current? I could not find the code referenced in the article.
I did find in ewlib (Erich?) adc.fs and the adc.frt in the butterfly app
but both of those
Enoch,
Enoch writes:
daruf...@gmail.com writes:
Enoch,
I repeat, I am not going to get into a licensing debate with anyone, but I
believe I have satisfied the GPLv3 requirements.
DaR
I don't question your compliance Dennis, I leave that task to the
copyright holder :-)
Hello,
Atommann writes:
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
Hello gp2, hello all,
so I chime in late, but nevertheless.
1. The road to amforth on controller X
Yes, that road is definitely long and windy. I sometimes give
classes on exactly that. There are so many pieces that *must*
work together, before the first ok prompt shows up.
You did a great
99 matches
Mail list logo
