Menu
▾
▴
amforth-devel — Development discussion and user support
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
(5) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
|
Feb
(6) |
Mar
(41) |
Apr
(23) |
May
(11) |
Jun
(2) |
Jul
|
Aug
|
Sep
(9) |
Oct
(2) |
Nov
(1) |
Dec
(1) |
| 2008 |
Jan
(6) |
Feb
(1) |
Mar
(23) |
Apr
(18) |
May
(21) |
Jun
(13) |
Jul
(34) |
Aug
(5) |
Sep
(1) |
Oct
(4) |
Nov
|
Dec
(4) |
| 2009 |
Jan
|
Feb
(5) |
Mar
(5) |
Apr
(10) |
May
(1) |
Jun
(11) |
Jul
(1) |
Aug
|
Sep
|
Oct
(2) |
Nov
(3) |
Dec
(13) |
| 2010 |
Jan
(10) |
Feb
(4) |
Mar
(28) |
Apr
(3) |
May
(38) |
Jun
(22) |
Jul
(92) |
Aug
(154) |
Sep
(218) |
Oct
(45) |
Nov
(20) |
Dec
(1) |
| 2011 |
Jan
(33) |
Feb
(15) |
Mar
(32) |
Apr
(33) |
May
(48) |
Jun
(35) |
Jul
(7) |
Aug
|
Sep
(11) |
Oct
(5) |
Nov
|
Dec
(7) |
| 2012 |
Jan
(56) |
Feb
(11) |
Mar
(6) |
Apr
|
May
(128) |
Jun
(59) |
Jul
(21) |
Aug
(16) |
Sep
(24) |
Oct
(39) |
Nov
(12) |
Dec
(12) |
| 2013 |
Jan
(14) |
Feb
(61) |
Mar
(97) |
Apr
(46) |
May
(13) |
Jun
(23) |
Jul
(12) |
Aug
(25) |
Sep
(9) |
Oct
(81) |
Nov
(73) |
Dec
(45) |
| 2014 |
Jan
(36) |
Feb
(57) |
Mar
(20) |
Apr
(41) |
May
(43) |
Jun
(11) |
Jul
(14) |
Aug
(32) |
Sep
(9) |
Oct
(27) |
Nov
(21) |
Dec
(6) |
| 2015 |
Jan
(14) |
Feb
(23) |
Mar
(1) |
Apr
(19) |
May
(40) |
Jun
(11) |
Jul
(1) |
Aug
(2) |
Sep
(14) |
Oct
(10) |
Nov
(9) |
Dec
(13) |
| 2016 |
Jan
(4) |
Feb
(3) |
Mar
(7) |
Apr
|
May
(4) |
Jun
(13) |
Jul
(8) |
Aug
(3) |
Sep
(4) |
Oct
(1) |
Nov
|
Dec
|
| 2017 |
Jan
(6) |
Feb
(1) |
Mar
(1) |
Apr
(7) |
May
(10) |
Jun
(5) |
Jul
(7) |
Aug
(9) |
Sep
|
Oct
(1) |
Nov
(5) |
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
(5) |
Apr
|
May
|
Jun
(3) |
Jul
(6) |
Aug
|
Sep
(2) |
Oct
(54) |
Nov
(47) |
Dec
(53) |
| 2019 |
Jan
(23) |
Feb
(24) |
Mar
(19) |
Apr
(15) |
May
(5) |
Jun
(34) |
Jul
(9) |
Aug
(9) |
Sep
(3) |
Oct
(2) |
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
(7) |
Apr
(7) |
May
(5) |
Jun
(15) |
Jul
(22) |
Aug
(28) |
Sep
(13) |
Oct
(9) |
Nov
(17) |
Dec
(13) |
| 2021 |
Jan
(5) |
Feb
(1) |
Mar
(1) |
Apr
(9) |
May
(21) |
Jun
(9) |
Jul
|
Aug
(6) |
Sep
(16) |
Oct
|
Nov
(1) |
Dec
(6) |
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
(7) |
May
(6) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(11) |
Sep
(21) |
Oct
(5) |
Nov
(1) |
Dec
(1) |
| 2024 |
Jan
(1) |
Feb
(4) |
Mar
|
Apr
(7) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
|
From: Matthias T. <mt...@we...> - 2008-01-28 13:04:10
|
Hi Erich, > [case ... endcase] So richtig habe ich in meinem alten Code nicht mehr durchgeblickt, da habe ich mich zu einer Radikalkur entschlossen. Die Definitionen f=FCr case und Co sind erst mal rausgeflogen und in eine Forth Sourcelib gewandert. F=FCr den Kernsystem braucht man die eh nicht und das Debuggen ist im Forth Quelltext einfacher. Wenn man dann einen befriedigenden Stand hat, kann man ja =FCber die Wiedereinf=FChrung nachdenken. Der Einfachheit halber habe ich das Eaker CASE aus dem Usenet herausgekramt, ohne es allerdings n=E4her zu testen. Selbige Implementation wurde allerdings von Ullrich Hoffman seinerzeit als nicht problemfrei charakterisiert, warum genau lie=DF er aber offen... > [serial-io und buffer] Da konnte ich noch nicht nachschauen, aber die restlichen =C4nderungen am Kernsystem haben mich bewogen, trotzdem ein neues Release zu machen. Gru=DF Matthias |
|
From: Erich W. <ew....@on...> - 2008-01-22 19:38:24
|
Hallo Matthias, > you have a very subtle method to describe bugs ;=) Natürlich hab ich das :-))) Schließlich bin ich ja *nicht* der Forth Crack, auch wenn ich der kurzen Zeit schon das eine oder andere verstanden habe :-) [case ... endcase] ich hab in endcase.asm nachgesehen. Da steht auch ein ".dw XT_DROP" drin. Aber ich habe nicht gesehen, ob das wirklich erreicht wird, oder ob's da noch ein zweites drop braucht ... da es ja einen wörkerraund gibt, ist das kein Problem. [serial-io und buffer] ja, ich kann weiterhin mit dem Kontroller reden, auch wenn diese verstümmelten strings kommen. In welcher Ecke befindet sich denn das mit dem buffer? Vielleicht kann ich ja doch mithelfen. Mir gefällt amforth ganz gut. Den Prompt würde ich anders machen, so wie bei gforth: " ok\n" hinten an die Zeile und dann eine neue Zeile anfangen. Aber das ist ja wohl Geschmacksache. Am meisten fehlen mir die '$' (hex), '&' oder '#' (decimal), '%' (binary) Vorsetzel für die Zahleneingabe. Albert Nijhof hatte ja einen Artikel geschrieben zu dem Thema. Vielleicht sollte ich das mal versuchen. Ich hab allerdings keine Ahnung, ob "die reine Lehre" state-aware Worte erlaubt oder nicht. Aber egal, Hauptsach 's funktioniert, oddrrr? Ich bin von dem r8c Kontroller inzwischen weg, weil mir der Programmspeicher nun doch zu klein war. Auf dem atmega32 hab ich jetzt den i2c-Bus, multitasker, die timeup-Uhr und die DCF Uhr am laufen. Und dann ist da noch massig Platz übrig. Also meiner Wetterstation in Forth steht nicht viel im Weg --- außer der stets zu knappen Zeit, versteht sich. Vielen Dank für amforth! Und einen schönen Abend, Erich PS. Fährst Du (Fahren Sie, wie immer gewünscht) zur Forth Tagung? Ich ringe noch mit mir, aber das wär vielleicht ein echter Grund. |
|
From: Matthias T. <mt...@we...> - 2008-01-20 10:52:20
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Erich, you have a very subtle method to describe bugs ;=) > I found that "case ... endcase"(1) leaves its argument on > the stack and I must explicitly drop it after "endcase". > This behaviour is different from gforth, so I was wondering > whether it is intented or not. I once intended to use case and friends in the core routines to ease handling of the throw codes. Soon I changed my mind and the case/endcase group of words is left mostly in a development state without beeing properly tested. > Comments? They should work like any other case, hopefully next week I'll find the time to fix it. It can be as little as adding a drop to endcase but I'll check it first (or anybody out there sends me a patch 8=) ) Matthias -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHkyfb9bEHdGEMFjMRAoTzAJ9KmNlPUhOY+X8juuso0up3v102UQCdGzUV KOudl61t77DifRGD5HfIg1k= =qENO -----END PGP SIGNATURE----- |
|
From: Erich W. <ew....@on...> - 2008-01-20 09:34:04
|
Hello, I found that "case ... endcase"(1) leaves its argument on the stack and I must explicitly drop it after "endcase". This behaviour is different from gforth, so I was wondering whether it is intented or not. Comments? Erich (1) yes, sure, I have to add "case", "endcase", "of", and "endof" to my application dictionary in dict_appl.inc. |
|
From: Matthias T. <mt...@we...> - 2008-01-09 21:01:47
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Erich,
> and it does exactly, what it should. However, calling the
> contents of message "manually", fails to show on the terminal:
>
> > ." c2_null_from_prompt"
> ok
>
> Note that the string did not show up. Is this a bug or a
> feature? This looks like a feature to me.
Quoting ANS94
- -----------------
6.1.0190 ."
dot-quote CORE
Interpretation: Interpretation semantics for this word are
undefined.
Compilation: ( "ccc<quote>" -- )
Parse ccc delimited by " (double-quote). Append the run-time semantics
given below to the current definition.
Run-time: ( -- )
- ------------------
I agree that most systems support an interpretation semantic similar to
the run-time of the compiled word, but I decied against. Mostly to have
a system that runs on 8 KB flash...
> Now I start the tasker. I expect the count in c0 to increase,
> and occasionally the message to show up.
>
> > c0 @ u.
> 50964 ok
> > multi
> ok
> > c0 @ u.
> 53896 ok
>
> The counter does increase indeed, however, the message does show
> up only partially.
>
> > >
> > c2_
> -------^ stops here! no " ok", no newline, no "> "
Does the system still accept any commands (simply hit <ret>)?
> It looks like the string is not handled correctly, since calling
> message manually does work:
>
> > message
>
> c2_null_msg ok
>
> Is this a bug or a feature? Looks like a bug to me anyway.
Me too. But not in the multitasker. The serial O code (output
part) was inteded to use a queue, but it turns out, that the
code only looks like using a queue, but in fact does not use it
at all. I'll fix it, but only ASAP ....
Matthias
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHhTYi9bEHdGEMFjMRAtoeAJ9ZtSh3E5mfed1IYoJ7og4Pzp4t9QCfbYaI
Kp+VDcJA+++4nrzpE9/Qehw=
=DagZ
-----END PGP SIGNATURE-----
|
|
From: Erich W. <ew....@on...> - 2008-01-09 19:51:21
|
Hello amforth'ers,
I'm trying to get the multitasker coming with amforth doing
something useful, but I have hit a problem.
I create one task in addition to "the input handling". It
increments a counter, and occasionally a message should be
written to the (serial) terminal. I dont care if it would
interfere with my typing. Consider this code:
#include ../../lib/multitask.frt
decimal
: message
cr ." c2_null_msg"
;
variable c0 0 c0 !
: task0 ( tid -- )
activate
begin
1 c0 +!
c0 @ 8 /
0= if message then
pause
again
;
onlytask
20 20 task ( -- tid0 )
dup task-sleep ( -- tid0 )
dup alsotask ( -- tid0 )
task0 ( -- )
I upload the program
user@box$ amforth-upload.py -t /dev/ttyS1 taskdemo.frt
and connect to the controller (<ret> is the return key):
user@box$ minicom -o atmega
...
<ret>
ok
> tlist<ret>
96 running rp0= 2143 TOR= 43784 sp0= 2063 TOS= 96
sp= 2057
297 running rp0= 361 TOR= 14597 sp0= 341 TOS= 357
sp= 339
Multitasker is not running ok
I can call message:
> message
c2_null_msg ok
and it does exactly, what it should. However, calling the
contents of message "manually", fails to show on the terminal:
> ." c2_null_from_prompt"
ok
Note that the string did not show up. Is this a bug or a
feature? This looks like a feature to me.
Now I start the tasker. I expect the count in c0 to increase,
and occasionally the message to show up.
> c0 @ u.
50964 ok
> multi
ok
> c0 @ u.
53896 ok
The counter does increase indeed, however, the message does show
up only partially.
> >
> c2_
-------^ stops here! no " ok", no newline, no "> "
It looks like the string is not handled correctly, since calling
message manually does work:
> message
c2_null_msg ok
Is this a bug or a feature? Looks like a bug to me anyway. Am I
doing something wrong? Is IO on the serial terminal somehow
colliding with the tasker? Interestingly, the output from tlist
is processed ok. Also interestingly, leaving "activate" and
"pause" out of "task0" and running it "in the foreground" (no
tasks involved), does work as well. Any insight would be
appreciated.
FWIW: I'm running this on a atmega32 with a 11.05920 MHz crystal
clock.
Cheers,
Erich W.
|
|
From: Matthias T. <mt...@we...> - 2007-12-06 19:20:16
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I just prepared a new release of amforth and it's library. The core system got mostly bugfixes and contains two documentations: Karl's User Guide and a more technical description. The last one is far from beeing complete but should illustrate some design decisions. The library got a cooperative multitasker and a new memory dump utility. Users can now load the code to create own deferred words too. The applications did not change much, but got the version number 2.5 as well. Have fun with it Matthias -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHWEto9bEHdGEMFjMRArK3AKCSYsKhX8B9XvODE0LO/kWP2sSr9ACg8KmA yrJ2WsXcxXKFE7F0mhWUS9U= =enOx -----END PGP SIGNATURE----- |
|
From: Matthias T. <mt...@we...> - 2007-11-28 10:39:01
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, in the last few days I've extended the upload tool from pix. He has written a nice python script to ease (and speed up) the sending of forth source code to amforth without running into trouble due to lost characters etc. You can find the script in the subversion repository (re-connect the link if broken), the next release of amforth will contain it as well (if I do not forget to include it) http://amforth.svn.sourceforge.net/viewvc/amforth/tools/amforth-upload.py?view=markup It has two enhancements which are related: first it scans the uploaded text for a command named #include. When it detects this command, it will take the next word as a filename and send it's content insted of the two words. That looks like the following excerpt: - -----8<--------8<--------8<- ... #include ans94/marker.frt #include bitnames.frt marker _hello_ : hello_world ." Hello World " ; hello_world - ---------8<---------8<--------8< As you may notice, subdirectories can be used. But no spaces in the (file)names. The syntax is modelled after the C preprocessor (and not something forth-ish) since the code cannot be used without that preprocessing, it is not really forth. The other enhancement is the introduction of an environment variable AMFORTH_LIB. This variable works like PATH. It contains a double-colon separated list of directories the upload tool looks for the files if it does not find them in the current working directory. This list is iterated sequentially from left to right until the first file is found. If not file is found, the tool aborts with an error message and the controller may need some cleanup. in bash it looks like export AMFORTH_LIB=~/projects/amforth/trunk/devices:~/lib/amforth Note: the . (current working directory) is always preprended to this list. Note2: amforth-upload.py has help screen, call it with -h and enjoy Please test it and feel free to comment. Matthias -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHTUU99bEHdGEMFjMRAvHsAJ0X6cVvI6rP/xEE79W4Njkxw9ny6wCePwEB MCVB1ioPuA8xGRWY9+RIWkw= =VxhR -----END PGP SIGNATURE----- |
|
From: Matthias T. <mt...@we...> - 2007-10-10 19:09:27
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all! To celebrate the 1st anniversary of amforth I just prepared a new release :=)) The details what's changed are as always on the homepage, long term users may notice that the usart settings have changed considerably: The EEPROM contains no longer the baudrate but the calculated register values. Future releases may put the usart-b and -c register values into EEPROM as well, let me know what you think about it. The code for the applications is left untouched.. Let's party, Matthias -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHDSNc9bEHdGEMFjMRAqVSAJ9K5qqsPdlTeaSn7n2HG8X+x9bnQQCgyOkJ wwSKd5eNjlh/lnSJk/zTEug= =dr/I -----END PGP SIGNATURE----- |
|
From: Matthias T. <mt...@we...> - 2007-10-03 06:49:24
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, Karl Lunt has written an excellent User's Guide for amforth. I've just put it on the homepage and I'd recommend it for everyone. Karl, thank you very much. Matthias -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD4DBQFHAztu9bEHdGEMFjMRAjDPAJwMAJE+PHkoB9X33hFowbQepiajwgCYuWjw gLLUG0Vtu5f4GDYLJE5PNw== =fovZ -----END PGP SIGNATURE----- |
|
From: robi <r.g...@vi...> - 2007-09-20 18:38:04
|
Finally, I found enough time to set up fuses and now amforth is working properly on mega8 at 8Mhz quartz! Thanks a lot Feusag and Matthias! excellent piece of sw!! best regards, Robert On Sat, 2007-09-15 at 20:21 +0200, robi wrote: > Thank you Matthias! > I will check my fuses according this web site. > Can You send me hex files for mega8 at 8mhz with external quartz? > Also I will try programing on other programmer. > Thanks a lot, > Robert > > On Fri, 2007-09-14 at 13:43 +0200, Matthias Trute wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > r.g...@vi... schrieb: > > > Hi to all! > > > After changing user initialisation routine, installing quartz and without any answer > > > from my mega8 > > > > I've just checked the sources with an Atmega8: With an 8 MHz quartz > > everything works fine. > > > > - ------------------------------ > > Welcome to minicom 2.2 > > > > OPTIONS: I18n > > Compiled on Mar 7 2007, 15:10:03. > > Port /dev/ttyS0 > > > > Press CTRL-A Z for help on special keys > > > > amforth 2.4 ATmega8 > > > words > > d2/ d>s s>d up! up@ 0 1ms >< cmove> i! i@ unloop i sp! sp@ rp! rp@ +! ... > > > > > > > - ------------------------------- > > > > If you do not depend on 1MHz you may change the fuses to use the 8MHz > > internal RC oszillator (http://palmavr.sourceforge.net/cgi-bin/fc.cgi > > can be helpful to get the correct fuse values) > > > > Greetings > > Matthias > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v1.4.6 (GNU/Linux) > > > > iD8DBQFG6nPI9bEHdGEMFjMRAoDMAKC0pglXgvQrcg+/A3uvD48baSO9XQCdEV9J > > 7iDprF9UU7aU37TtlIlxhdY= > > =OQR1 > > -----END PGP SIGNATURE----- > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2005. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > Amforth-devel mailing list > > Amf...@li... > > https://lists.sourceforge.net/lists/listinfo/amforth-devel > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Amforth-devel mailing list > Amf...@li... > https://lists.sourceforge.net/lists/listinfo/amforth-devel > |
|
From: robi <r.g...@vi...> - 2007-09-15 18:19:06
|
Thank you Matthias! I will check my fuses according this web site. Can You send me hex files for mega8 at 8mhz with external quartz? Also I will try programing on other programmer. Thanks a lot, Robert On Fri, 2007-09-14 at 13:43 +0200, Matthias Trute wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > r.g...@vi... schrieb: > > Hi to all! > > After changing user initialisation routine, installing quartz and without any answer > > from my mega8 > > I've just checked the sources with an Atmega8: With an 8 MHz quartz > everything works fine. > > - ------------------------------ > Welcome to minicom 2.2 > > OPTIONS: I18n > Compiled on Mar 7 2007, 15:10:03. > Port /dev/ttyS0 > > Press CTRL-A Z for help on special keys > > amforth 2.4 ATmega8 > > words > d2/ d>s s>d up! up@ 0 1ms >< cmove> i! i@ unloop i sp! sp@ rp! rp@ +! ... > > > > - ------------------------------- > > If you do not depend on 1MHz you may change the fuses to use the 8MHz > internal RC oszillator (http://palmavr.sourceforge.net/cgi-bin/fc.cgi > can be helpful to get the correct fuse values) > > Greetings > Matthias > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > > iD8DBQFG6nPI9bEHdGEMFjMRAoDMAKC0pglXgvQrcg+/A3uvD48baSO9XQCdEV9J > 7iDprF9UU7aU37TtlIlxhdY= > =OQR1 > -----END PGP SIGNATURE----- > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Amforth-devel mailing list > Amf...@li... > https://lists.sourceforge.net/lists/listinfo/amforth-devel > |
|
From: Matthias T. <mt...@we...> - 2007-09-14 11:43:18
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
r.g...@vi... schrieb:
> Hi to all!
> After changing user initialisation routine, installing quartz and without any answer
> from my mega8
I've just checked the sources with an Atmega8: With an 8 MHz quartz
everything works fine.
- ------------------------------
Welcome to minicom 2.2
OPTIONS: I18n
Compiled on Mar 7 2007, 15:10:03.
Port /dev/ttyS0
Press CTRL-A Z for help on special keys
amforth 2.4 ATmega8
> words
d2/ d>s s>d up! up@ 0 1ms >< cmove> i! i@ unloop i sp! sp@ rp! rp@ +! ...
>
- -------------------------------
If you do not depend on 1MHz you may change the fuses to use the 8MHz
internal RC oszillator (http://palmavr.sourceforge.net/cgi-bin/fc.cgi
can be helpful to get the correct fuse values)
Greetings
Matthias
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFG6nPI9bEHdGEMFjMRAoDMAKC0pglXgvQrcg+/A3uvD48baSO9XQCdEV9J
7iDprF9UU7aU37TtlIlxhdY=
=OQR1
-----END PGP SIGNATURE-----
|
|
From: <r.g...@vi...> - 2007-09-10 11:50:10
|
Hi to all!
After changing user initialisation routine, installing quartz and without any answer
from my mega8, I try to check source in avr studio simulator and found out that
after 1507 clock ticks avr simulator execute wrong opcode and reset.
After tracing in which routine I came to this:
; ( i*x -- j*x )
; R( -- )
; runtime of defer
;VE_DOEDEFER:
; .db $0a, "(defer)", 0
; .dw VE_HEAD
; .set VE_HEAD = VE_DOEDEFER
XT_DODEFER:
.dw PFA_DODEFER
PFA_DODEFER:
call_ DO_DODOES
.dw XT_DUP
.dw XT_1MINUS
.dw XT_SWAP
.dw XT_1PLUS
.dw XT_IFETCH
.dw XT_EXECUTE
; .dw XT_EXECUTE
.dw XT_EXIT
On second XT_execute aperas executing wrong opcode, so after commenting
out this line in simulator works ok.
This evening I will try in real Mega....
Is there falut or not?
>
> Od: <r.g...@vi...>
> Datum: 2007/09/05 sri PM 02:23:05 GMT+01:00
> Za: <amf...@li...>
> Naslov: [Amforth-devel] mega8 installation problem
>
> Dear all,
> I will need a help from you as I have a problem with installing amforth2.3 on
> atmega8.
> Assembling with avr studio 4 is performed without any error. I put cpu
> frequency t
> o 1Mhz (internal rc oscilator) , baud rate at 9600. After programming with hex
> and
> eeprom files, nothing hapened, on hyper terminal is nothing writen neider
> typing on
> kbd helped.
> I'm using internal oscilator seted to 1Mhz, with rs232 attached to pin 2 and 3
> of
> atmega8. If I load atmega8 with any program (writen in C or asm) for serial
> communication (simly sending and receiving characters from hyperterminal),
there
> is print out on hyperterminal so rs232 chip is properly
> connected to avr.
> Does anyone have any ideo what is wrong?
> I was very happy when found amforth and now it does not want to work...... :-(
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Amforth-devel mailing list
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel
>
>
|
|
From: Feusag M. <feu...@go...> - 2007-09-07 13:36:25
|
Hi Robert,
It looks like I had some problems posting my original response, and
unfortunatley the layout of the diff is not very clear...
Anyway, here is the complete text of my modified uart initialize route
from words/usart.asm - starting around line 50. This is just a
prototype of the change so it has literal values for the new register
values and very few comments, but it should let you get running.
; ( -- ) Hardware Access
; R( --)
; initialize usart0
VE_USART0:
.db $06, "usart0",0
.dw VE_HEAD
.set VE_HEAD = VE_USART0
XT_USART0:
.dw DO_COLON
PFA_USART0: ; ( -- )
.dw XT_ZERO
.dw XT_DOLITERAL
.dw usart0_tx_in
.dw XT_CSTORE
.dw XT_ZERO
.dw XT_DOLITERAL
.dw usart0_tx_out
.dw XT_CSTORE
.dw XT_ZERO
.dw XT_DOLITERAL
.dw usart0_rx_in
.dw XT_CSTORE
.dw XT_ZERO
.dw XT_DOLITERAL
.dw usart0_rx_out
.dw XT_CSTORE
.dw XT_F_CPU
.dw XT_D2SLASH
.dw XT_D2SLASH
.dw XT_D2SLASH
; .dw XT_D2SLASH ; We are going for 2X, so remove one
of these...
.dw XT_ROT
.dw XT_UMSLASHMOD
.dw XT_SWAP
.dw XT_DROP
.dw XT_1MINUS
.dw XT_DUP
.dw XT_DOLITERAL
.dw BAUDRATE0_LOW
.dw XT_CSTORE
.dw XT_BYTESWAP
.dw XT_DOLITERAL
.dw BAUDRATE0_HIGH
.dw XT_CSTORE
.dw XT_DOLITERAL
.dw $02 ; U2X
.dw XT_DOLITERAL
.dw $2B ; UCSRA
.dw XT_CSTORE
.dw XT_DOLITERAL
.dw (1<<UMSEL01)|(3<<UCSZ00)
.dw XT_DOLITERAL
.dw USART0_C
.dw XT_CSTORE
.dw XT_DOLITERAL
.dw (1<<TXEN0) | (1<<RXEN0) | (1<<RXCIE0)
.dw XT_DOLITERAL
.dw USART0_B
.dw XT_CSTORE
; set IO
.dw XT_DOLITERAL
.dw XT_TX0
.dw XT_DOLITERAL
.dw XT_EMIT
.dw XT_DEFERSTORE
.dw XT_DOLITERAL
.dw XT_TX0Q
.dw XT_DOLITERAL
.dw XT_EMITQ
.dw XT_DEFERSTORE
.dw XT_DOLITERAL
.dw XT_RX0
.dw XT_DOLITERAL
.dw XT_KEY
.dw XT_DEFERSTORE
.dw XT_DOLITERAL
.dw XT_RX0Q
.dw XT_DOLITERAL
.dw XT_KEYQ
.dw XT_DEFERSTORE
.dw XT_DOLITERAL
.dw XT_NOOP
.dw XT_DOLITERAL
.dw XT_SLASHKEY
.dw XT_DEFERSTORE
.dw XT_EXIT
Enjoy ;o)
Feusag
|
|
From: <r.g...@vi...> - 2007-09-07 10:01:53
|
Hi Feusag, thanks for fast response! I changed init usart routine as You recomended, but I'm not shure that understand You right! Can You send complete routine to me? thanx, Robert > > Od: "Feusag Mhor" <feu...@go...> > Datum: 2007/09/05 sri PM 06:22:08 GMT+01:00 > Za: amf...@li... > Naslov: Re: [Amforth-devel] mega8 installation problem > > Hi, > > I had the same problem and traced it to the baud rate calculation. > > It turns out that there is a 7% error at 9600 baud with a 1MHz system clock > (see table 60 in the datasheet) and this is out of spec for you PC UART to > read. > > I changed the baud rate on line 22 of template.asm to 4800 (0.2% error) and > everything was OK. > > I have also prototyped the following change to armforth/words/usart.asm to > use the U2X double speed mechanism. > With this change the error at 9600 baud is 0.2% with a 1MHz clock and works > perfectly. > > Index: usart.asm > ================================================================== = > --- usart.asm (.../vendor/amforth/2.3/words/usart.asm) > +++ usart.asm (.../trunk/forth/amforth/words/usart.asm) > @@ -81,7 +81,7 @@ > .dw XT_D2SLASH > .dw XT_D2SLASH > .dw XT_D2SLASH > - .dw XT_D2SLASH > +; .dw XT_D2SLASH ; We are going for 2X, so > remove one of these... > .dw XT_ROT > .dw XT_UMSLASHMOD > .dw XT_SWAP > @@ -96,7 +96,14 @@ > .dw XT_DOLITERAL > .dw BAUDRATE0_HIGH > .dw XT_CSTORE > + > .dw XT_DOLITERAL > + .dw $02 ; U2X > + .dw XT_DOLITERAL > + .dw $2B ; UCSRA > + .dw XT_CSTORE > + > + .dw XT_DOLITERAL > .dw (1<<UMSEL01)|(3<<UCSZ00) > .dw XT_DOLITERAL > .dw USART0_C > > > > I hope this helps. > > Cheers > > Feusag > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Amforth-devel mailing list > Amf...@li... > https://lists.sourceforge.net/lists/listinfo/amforth-devel > > |
|
From: Feusag M. <feu...@go...> - 2007-09-05 17:22:06
|
Hi, I had the same problem and traced it to the baud rate calculation. It turns out that there is a 7% error at 9600 baud with a 1MHz system clock (see table 60 in the datasheet) and this is out of spec for you PC UART to read. I changed the baud rate on line 22 of template.asm to 4800 (0.2% error) and everything was OK. I have also prototyped the following change to armforth/words/usart.asm to use the U2X double speed mechanism. With this change the error at 9600 baud is 0.2% with a 1MHz clock and works perfectly. Index: usart.asm =================================================================== --- usart.asm (.../vendor/amforth/2.3/words/usart.asm) +++ usart.asm (.../trunk/forth/amforth/words/usart.asm) @@ -81,7 +81,7 @@ .dw XT_D2SLASH .dw XT_D2SLASH .dw XT_D2SLASH - .dw XT_D2SLASH +; .dw XT_D2SLASH ; We are going for 2X, so remove one of these... .dw XT_ROT .dw XT_UMSLASHMOD .dw XT_SWAP @@ -96,7 +96,14 @@ .dw XT_DOLITERAL .dw BAUDRATE0_HIGH .dw XT_CSTORE + .dw XT_DOLITERAL + .dw $02 ; U2X + .dw XT_DOLITERAL + .dw $2B ; UCSRA + .dw XT_CSTORE + + .dw XT_DOLITERAL .dw (1<<UMSEL01)|(3<<UCSZ00) .dw XT_DOLITERAL .dw USART0_C I hope this helps. Cheers Feusag |
|
From: Feusag M. <feu...@go...> - 2007-09-05 17:20:50
|
Hi, I had the same problem and traced it to the baud rate calculation. It turns out that there is a 7% error at 9600 baud with a 1MHz system clock (see table 60 in the datasheet) and this is out of spec for you PC UART to read. I changed the baud rate on line 22 of template.asm to 4800 (0.2% error) and everything was OK. I have also prototyped the following change to armforth/words/usart.asm to use the U2X double speed mechanism. With this change the error at 9600 baud is 0.2% with a 1MHz clock and works perfectly. Index: usart.asm =================================================================== --- usart.asm (.../vendor/amforth/2.3/words/usart.asm) +++ usart.asm (.../trunk/forth/amforth/words/usart.asm) @@ -81,7 +81,7 @@ .dw XT_D2SLASH .dw XT_D2SLASH .dw XT_D2SLASH - .dw XT_D2SLASH +; .dw XT_D2SLASH ; We are going for 2X, so remove one of these... .dw XT_ROT .dw XT_UMSLASHMOD .dw XT_SWAP @@ -96,7 +96,14 @@ .dw XT_DOLITERAL .dw BAUDRATE0_HIGH .dw XT_CSTORE + .dw XT_DOLITERAL + .dw $02 ; U2X + .dw XT_DOLITERAL + .dw $2B ; UCSRA + .dw XT_CSTORE + + .dw XT_DOLITERAL .dw (1<<UMSEL01)|(3<<UCSZ00) .dw XT_DOLITERAL .dw USART0_C I hope this helps. Cheers Feusag |
|
From: <r.g...@vi...> - 2007-09-05 13:23:05
|
Dear all, I will need a help from you as I have a problem with installing amforth2.3 on atmega8. Assembling with avr studio 4 is performed without any error. I put cpu frequency t o 1Mhz (internal rc oscilator) , baud rate at 9600. After programming with hex and eeprom files, nothing hapened, on hyper terminal is nothing writen neider typing on kbd helped. I'm using internal oscilator seted to 1Mhz, with rs232 attached to pin 2 and 3 of atmega8. If I load atmega8 with any program (writen in C or asm) for serial communication (simly sending and receiving characters from hyperterminal), there is print out on hyperterminal so rs232 chip is properly connected to avr. Does anyone have any ideo what is wrong? I was very happy when found amforth and now it does not want to work...... :-( |
|
From: Steward <vv...@oz...> - 2007-06-12 18:02:35
|
News Hits! New R&D Facility Engaged! Chan-On International Inc. Symbol: CAON Close: $0.73 News hits today on CAON and trading continues to warm up. Hitting highs of $0.90 today, we can see this building. Read the release and get on CAON first thing Tuesday. We can see this climbing all week! I backed up and then felt the car just stop. All in all therefore, it looks as though Bill Clinton could be in for an interesting couple of weeks. And our squid didn't die in the making of the video, as the Japanese squid did. Here are some of my tips on what to see and do when you get there. You can return to the current blog at any time by clicking the Cancergiggles logo at the top. htmThe following sources were used to put the blog together:sitemaps. I came home with a big smile and was genuinely happy to know that my recently acquired pain was due to gall stones. THAT HURTST-I-G-G-E-RBODY FOR SALEA Little EncouragementTHE PILLSHELEN IN THE TOWERFLEW? I could have written some beautifully crafted, grammatically correct essays but I hope you will understand, that when I say "I don't have a lot of time" I mean it far more literally than you do. I'm easy - just drop me a note. Perhaps it is a sign of advanced lunacy, but I really enjoy these visits to TumoursRus and find that regardless of the outcome of discussions, I always come away invigorated. Don't take any chances. See the article for a feature-by-feature comparison chart. The RSS Blog by Randy Charles Morin blogs about RSS, OPML and the XML platform. Above, Leroy poses in the Forest Preserve. I plan to enjoy the process of discovery regardless. An auto dealer with an RSS-enabled website can publish their inventory in real time to edgeio's network. I've spent some time looking through the Cingular forum but only found a solution for a PC laptop. Above, Leroy poses in the Forest Preserve. He asks Kishanlal to take the blame and assure him that he would take care of his family and support them financially. If you want to rent an RV for the event, you'd better hurry up, they sell out fast! Please follow the link below. Always excepting the Swiss Guard of the Vatican, the Chileans must be the most nostalgic armed force in the world. Just click this link for a pain-free shopping experience. So check out Elliott's article - you might get some ideas. A blogger can publish an item for sale and have it listed on edgeio within a matter of seconds. It is a powerfull tool that helps you to create and keep up-to-date sitemaps for your websites. As far as I am aware this is something of an innovation and I have to say that I am very impressed. Could my continued existence be due to my strict health regime? |
|
From: Matthias T. <mt...@we...> - 2007-05-20 16:15:55
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hans, Hans H=FCbner schrieb: > while checking out the repository, I found that you decided to move=20 > appl and lib out of the trunk path. Is that really what you > intended? Yes. The reason is that I do not really want the applications be seen as part of amforth. They may be a source of inspiration. > That way, it would be easier to check out the full tree and also it > would be easier to snapshot the lib and appl directories when a > release is made. I do not intent to make the applications a part of the amforth releases. The amforth release should be as clean as possible, the applications may have different release cycles (if any). So they may reference specific amforth release. > Also, such a revised layout would be more in line what SVN=20 > repositories generally look like, so it would be less suprising to > use for people with SVN experience. And I have seen a lot of svn repositories without the propagated trunk/releases/branches structure which work really well. The current structure is simply my _current_ best idea how the organise the project. But your feedback is very welcome! Bye Matthias -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGUHRV9bEHdGEMFjMRAk2sAKCOP7SPysQZn9o8zWixKxZUOmu0lQCfcBvN MaP0bLdEFYoxkc3PXv9ViX8=3D =3Dtkn+ -----END PGP SIGNATURE----- |
|
From: Matthias T. <mt...@we...> - 2007-05-20 16:15:27
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hans, Hans H=FCbner schrieb: >=20 > Something else: How do you (as in everyone) handle bitwise I/O with > amforth? see lib/bitnames.frt. Thanks to Michael Kalus who has written the documentation and made some subtle but very useful improvemnts to my prior design. > The AVR has the very useful SBI/CBI instructions that can be > used to set and clear individual bits without affecting the state of > the other bits in a port. The bit number is coded into the > instruction, so I am a bit at loss when it comes to defining a proper > amforth word to do it. Obviously, having cbi and sbi words ( bit port > -- ) would be just great. Any ideas? The sbi/cbi work for the IO address _only_, so they are of very limited use for a general ATmega design. Matthias -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGUHRG9bEHdGEMFjMRAhzNAKDExllhsWYS+0J0xRvdspkxum6+wwCeKn9G fZBIimalkTi25Cz2DUypRIc=3D =3Ddgrx -----END PGP SIGNATURE----- |
|
From: <ha...@hu...> - 2007-05-20 14:05:25
|
Hi Matthias, while checking out the repository, I found that you decided to move appl and lib out of the trunk path. Is that really what you intended? It is certainly your decision, but I would think that it would make more sense to put appl, lib and amforth under trunk (creating a new amforth directory and moving everything under trunk there). That way, it would be easier to check out the full tree and also it would be easier to snapshot the lib and appl directories when a release is made. With the current layout, this would not be easily possible. Also, such a revised layout would be more in line what SVN repositories generally look like, so it would be less suprising to use for people with SVN experience. Thanks! Hans 2007/5/20, Matthias Trute <mt...@we...>: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > Today I've changed the repository structure. There are two new > directories at the top level: appl and lib. The directories blocks and > target within trunk are gone together with the makefile there. > > Why these changes? amforth itself is basically useless. It needs > a few information about the environment it will run. I call this > an "appl(ication)". In this directory you can find a collection of > targets: AVR Butterfly, the Evaluation Boards and (new!) thanks to > Alexander Haucks impressive work an application to use a tv with > minimal hardware (2 resistors!). > > These applications have all that's needed to build and burn the hex > files: a makefile, speed definition files (the former target/xy.asm) > and some useful forthcode specific for this environment. The build > process includes the amforth source tree like a library. It is up > to the developer to decide which version is be used. trunk > is always the lastest and newest, maybe useless version. release/x.y > is stable in a sense that it is never changed. > > The lib directory contains forth code snippets that may be useful > across applications. Currently it contains some definitions for > an ANS system and some other more or less trivial words. > > These changes should make life easier, feedback is > welcome! > > Matthias > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > > iD8DBQFGUDEI9bEHdGEMFjMRAr0jAJ9/GQOL7P8k8LEoxng6hZ7fJH8YWQCdEx2j > MeVL1UZI6P/iL7nCzqT1p3g= > =rLw7 > -----END PGP SIGNATURE----- > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Amforth-devel mailing list > Amf...@li... > https://lists.sourceforge.net/lists/listinfo/amforth-devel > |
|
From: <ha...@hu...> - 2007-05-20 13:57:48
|
Hi Matthias, I just tried checking out from trunk, and there is no appl or lib directory. Has the URL changed? I used 2007/5/20, Matthias Trute <mt...@we...>: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > Today I've changed the repository structure. There are two new > directories at the top level: appl and lib. The directories blocks and > target within trunk are gone together with the makefile there. > > Why these changes? amforth itself is basically useless. It needs > a few information about the environment it will run. I call this > an "appl(ication)". In this directory you can find a collection of > targets: AVR Butterfly, the Evaluation Boards and (new!) thanks to > Alexander Haucks impressive work an application to use a tv with > minimal hardware (2 resistors!). > > These applications have all that's needed to build and burn the hex > files: a makefile, speed definition files (the former target/xy.asm) > and some useful forthcode specific for this environment. The build > process includes the amforth source tree like a library. It is up > to the developer to decide which version is be used. trunk > is always the lastest and newest, maybe useless version. release/x.y > is stable in a sense that it is never changed. > > The lib directory contains forth code snippets that may be useful > across applications. Currently it contains some definitions for > an ANS system and some other more or less trivial words. > > These changes should make life easier, feedback is > welcome! > > Matthias > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > > iD8DBQFGUDEI9bEHdGEMFjMRAr0jAJ9/GQOL7P8k8LEoxng6hZ7fJH8YWQCdEx2j > MeVL1UZI6P/iL7nCzqT1p3g= > =rLw7 > -----END PGP SIGNATURE----- > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Amforth-devel mailing list > Amf...@li... > https://lists.sourceforge.net/lists/listinfo/amforth-devel > |
|
From: <ha...@hu...> - 2007-05-20 13:39:47
|
2007/5/20, Matthias Trute <mt...@we...>: > Today I've changed the repository structure. There are two new > directories at the top level: appl and lib. The directories blocks and > target within trunk are gone together with the makefile there. Totally cool! I have done something similar for my private needs, but it is way better to have amforth being prepared like this upfront. Thanks! Something else: How do you (as in everyone) handle bitwise I/O with amforth? The AVR has the very useful SBI/CBI instructions that can be used to set and clear individual bits without affecting the state of the other bits in a port. The bit number is coded into the instruction, so I am a bit at loss when it comes to defining a proper amforth word to do it. Obviously, having cbi and sbi words ( bit port -- ) would be just great. Any ideas? Thanks, Hans |
8 messages has been excluded from this view by a project administrator.
