amforth-devel — Development discussion and user support

Re: [Amforth-devel] floating-point

[Matthias T. <mt...@we...>]

Hi Leon,

> I've been working on a single precision floating point word set, and I
> recently got addition/subtraction working.

and a f* is already there :=))

Great work, Leon!! really!

Matthias

[Amforth-devel] floating-point

[Leon M. <leo...@gm...>]

On Sun, Jul 18, 2010 at 2:17 PM, Matthias Trute <mt...@we...> wrote:
>> PS: Any plans for amforth 32bit with float??
>
> Not currently. Maybe someone want to volonteer?

I've been working on a single precision floating point word set, and I
recently got addition/subtraction working. Everything is trivial after
that... right?  ;) I haven't done a lot of testing, and this is my
first real forth project, but you can see its current state at:

http://github.com/lnmaurer/amforth-float/blob/master/float.fth

It's written in forth and uses the data stack. I haven't made words
for turning strings in to floats and vice versa (that's probably the
last thing I'll take care of), so -- unless you want to enter numbers
by hand (builds character) -- it's limited to working with integers,
but that seems to work:

> 10 s>f 5 s>f f- f>s .
5  ok
> 10 s>f -5 s>f f+ f>s .
5  ok
> -10 s>f -5 s>f f+ f>s .
-15  ok
> -10 s>f -5 s>f f- f>s .
-5  ok

I may take a break from this for a while, but multiplication/division
is next on the todo list.

If you have suggestions/questions/patches/whatever feel free to email me.
-Leon

[Amforth-devel] Minimalist 644p and 1284p board.

[<an...@ki...>]

Guys

I have now completed and published the designs for a minimalist DIY 644p
and 1284p board. As well as building a couple, then tweaking the design
a little more.

There is an experimental clone facility as part of the design.
Completely untried, but as the board was being designed I thought to
have a first go at it. If the SPI peripheral does'nt work on as hoped on
the master board there is always the option of bit banging.

Next stop Amforth on the 1284p.

The DIY board can be found here:-

http://aka47.adsl24.co.uk/serendipity/index.php?/pages/min644p.html

Cheers

Andy Kirby

Re: [Amforth-devel] Atmega<any> support

[<an...@ki...>]

Yus

I agree the Arduino boot loader is irrelevant as it gets replaced. If
Amforth can be persuaded to run on the chip (no reason why not it works
fins on a 328) the other differences should be fairly trivial.

Only way to be sure is to try it. If the cost of the board is a touch
steep for a maybe, then either stripboard or breadboard up a minimalist
setup with a blank chip and take it from there. Once you have that
working to your satisfaction buy in a rugedised board.

Mathias's parts files seem to be pretty much there from the limited
experience I have of them.

Cheers

Andy Kirby

On 24/08/10 19:21, Marcin Cieslak wrote:
> On Tue, 24 Aug 2010, Kalus Michael wrote:
> 
>> Hi Andy.
>>
>> Am 23.08.2010 um 13:40 schrieb an...@ki...:
>> ..
>>> http://www.ruggedcircuits.com/html/mb324p.html
>>
>> Very interesting board. But there is no information on how they
>> solved the USB-serial to ATmega324P connection. They call it Arduino
>> compatible, so i guess they usa a the bootloader as in Arduinos, and
>> since amforth needs the bootloader section on its own, this board is
>> not good for amforth?
> 
> Here is the patch for the arduino software:
> 
> http://ruggedcircuits.com/Arduino/arduino-0018-patch.txt
> 
> - a bit different serial port (but this is chip-related, not board-related)
> - the board does not probably use auto-reset, an annoying Arduino feature :)
> - I/O pin layout is different
> 
> I don't see any reason why amforth couldn't run on the board
> (as long as we don't have any issues with the chip itself).
> 
> --Marcin
> 
> 
> ------------------------------------------------------------------------------
> Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
> Be part of this innovative community and reach millions of netbook users 
> worldwide. Take advantage of special opportunities to increase revenue and 
> speed time-to-market. Join now, and jumpstart your future.
> http://p.sf.net/sfu/intel-atom-d2d
> _______________________________________________
> Amforth-devel mailing list
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel
> 

Re: [Amforth-devel] Atmega<any> support

[Marcin C. <sa...@sa...>]

On Tue, 24 Aug 2010, Kalus Michael wrote:

> Hi Andy.
>
> Am 23.08.2010 um 13:40 schrieb an...@ki...:
> ..
>> http://www.ruggedcircuits.com/html/mb324p.html
>
> Very interesting board. But there is no information on how they
> solved the USB-serial to ATmega324P connection. They call it Arduino
> compatible, so i guess they usa a the bootloader as in Arduinos, and
> since amforth needs the bootloader section on its own, this board is
> not good for amforth?

Here is the patch for the arduino software:

http://ruggedcircuits.com/Arduino/arduino-0018-patch.txt

- a bit different serial port (but this is chip-related, not board-related)
- the board does not probably use auto-reset, an annoying Arduino feature :)
- I/O pin layout is different

I don't see any reason why amforth couldn't run on the board
(as long as we don't have any issues with the chip itself).

--Marcin

Re: [Amforth-devel] Atmega<any> support

[Kalus M. <mic...@on...>]

Hi Andy.

Am 23.08.2010 um 13:40 schrieb an...@ki...:
..
> http://www.ruggedcircuits.com/html/mb324p.html

Very interesting board. But there is no information on how they  
solved the USB-serial to ATmega324P connection. They call it Arduino  
compatible, so i guess they usa a the bootloader as in Arduinos, and  
since amforth needs the bootloader section on its own, this board is  
not good for amforth?

I realy would like to have a board exactly like this, but amforth  
compatible . :-)

Michael

Re: [Amforth-devel] Atmega<any> support

[<an...@ki...>]

I guess it would be possible. I am not aware of a currently available
"Drop in" solution though.

For hostile environments I would be more inclined to take an off the
shelf or DIY board that already existed and put it into a Potting box
(or Mould) with connectors on the ends. Then fill the potting box with a
clear resin or epoxy. (Maybe fibre glassing resin) so I could still see
the LED's. Put fixed links on the board instead of plug on jumpers.

If you DIY your own PCB you don't need to put pins in the connector
holes. You can leave these out and wire the board direct to the
connectors of your choice using short lengths of wire.

Given that DB25's have only 25 pins though if using a 644 or 1284 you
will have to choose which IO you want on them. Using a smaller device
like the 328 you would put them all on.

Once potted your board becomes impervious to moisture, vibration etc
etc. But impossible to modify, repair or get at. So test it thoroughly
first.

All in all how much effort you go to will be governed by your need or
application.

For a class room environment something along these lines may be more
appropriate as it provides some degree of electrical protection as well..

http://www.ruggedcircuits.com/html/mb324p.html

Cheers

Andy Kirby





On 22/08/10 23:02, Kalus Michael wrote:
> Hi Andy.
> 
> I see.
> Do you think there could be an 'drop in' solution for an 1284 in a  
> jumper box?
> http://parts.digikey.com/1/parts/290826-jumper-box-db25-male-db25- 
> female-ab973-r.html
> Will it fit into the holes of the borad that is in there already?
> 
> In such a box it would be a nice 'of the shelf' micro for rough  
> environment. Femal side has the ports, male connects to terminal and  
> programmer.
> 
> Michael
> 
> 
> Am 22.08.2010 um 22:27 schrieb an...@ki...:
> 
>> Michael
>>
>> I have yet to document and put up the board design I am using as it  
>> is a
>> work in progress.
>>
>> The techniques I use to make PCB's at home I have already  
>> documented here:-
>>
>> http://aka47.adsl24.co.uk/serendipity/index.php?/pages/sspcb.html
>>
>> This is where I will also document the minimalist microcontroler board
>> design I am using. It is a single sided PCB easy to make at home.
>>
>> Most design work is sort of iterative in that I do a design and  
>> then try
>> out making it to discover where I did something wrong. Followed by
>> modifying the design and then trying it again until I am happy with  
>> the
>> end result.
>>
>> The design itself is OK I am just iterating on the PCB layout to  
>> get to
>> something that is easy for other folk to work with. It is nearly  
>> there.
>> I am just making some of the pads a little larger to make it easier  
>> for
>> learner solderers. Then I can Document it and put all the files on  
>> line.
>>
>> The need to enlarge the pads was something I found when building up a
>> pair of 644p boards to take the 1284p devices. These will be set up at
>> the full device clock of 20Mhz.
>>
>> The version of the PCB when I put the details up should be 1.2  
>> (1.0, 1.1
>> are the previous iterations).
>>
>> For etching I use the Copper Chloride method documented here :-
>>
>> http://www.instructables.com/id/Stop-using-Ferric-Chloride- 
>> etchant!--A-better-etc/
>>
>> Sorry I am not big on video.
>>
>> But hope these help
>>
>>
>> Cheers
>>
>> Andy Kirby
>>
>>
>>
>>
>> On 22/08/10 18:51, Kalus Michael wrote:
>>> Hi Andy.
>>>
>>> I'd realy like to take a look over your sholder when you do "built a
>>> couple of boards up" - video? How do you do it?
>>> Michael
>>>
>>>
>>> Am 22.08.2010 um 19:02 schrieb an...@ki...:
>>>
>>>> Thanks mathias
>>>>
>>>> I have just received a couple of 1284's and built a couple of
>>>> boards up
>>>> with them so should be able to try it out over the next week.
>>>>
>>>> Cheers
>>>>
>>>> Andy Kirby
>>>
>>>
>>> --------------------------------------------------------------------- 
>>> ---------
>>> This SF.net email is sponsored by
>>>
>>> Make an app they can't live without
>>> Enter the BlackBerry Developer Challenge
>>> http://p.sf.net/sfu/RIM-dev2dev
>>> _______________________________________________
>>> Amforth-devel mailing list
>>> Amf...@li...
>>> https://lists.sourceforge.net/lists/listinfo/amforth-devel
>>>
>>
>> ---------------------------------------------------------------------- 
>> --------
>> This SF.net email is sponsored by
>>
>> Make an app they can't live without
>> Enter the BlackBerry Developer Challenge
>> http://p.sf.net/sfu/RIM-dev2dev
>> _______________________________________________
>> Amforth-devel mailing list
>> Amf...@li...
>> https://lists.sourceforge.net/lists/listinfo/amforth-devel
> 
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by 
> 
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev 
> _______________________________________________
> Amforth-devel mailing list
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel
> 

Re: [Amforth-devel] Atmega<any> support

[Kalus M. <mic...@on...>]

Hi Andy.

I see.
Do you think there could be an 'drop in' solution for an 1284 in a  
jumper box?
http://parts.digikey.com/1/parts/290826-jumper-box-db25-male-db25- 
female-ab973-r.html
Will it fit into the holes of the borad that is in there already?

In such a box it would be a nice 'of the shelf' micro for rough  
environment. Femal side has the ports, male connects to terminal and  
programmer.

Michael


Am 22.08.2010 um 22:27 schrieb an...@ki...:

> Michael
>
> I have yet to document and put up the board design I am using as it  
> is a
> work in progress.
>
> The techniques I use to make PCB's at home I have already  
> documented here:-
>
> http://aka47.adsl24.co.uk/serendipity/index.php?/pages/sspcb.html
>
> This is where I will also document the minimalist microcontroler board
> design I am using. It is a single sided PCB easy to make at home.
>
> Most design work is sort of iterative in that I do a design and  
> then try
> out making it to discover where I did something wrong. Followed by
> modifying the design and then trying it again until I am happy with  
> the
> end result.
>
> The design itself is OK I am just iterating on the PCB layout to  
> get to
> something that is easy for other folk to work with. It is nearly  
> there.
> I am just making some of the pads a little larger to make it easier  
> for
> learner solderers. Then I can Document it and put all the files on  
> line.
>
> The need to enlarge the pads was something I found when building up a
> pair of 644p boards to take the 1284p devices. These will be set up at
> the full device clock of 20Mhz.
>
> The version of the PCB when I put the details up should be 1.2  
> (1.0, 1.1
> are the previous iterations).
>
> For etching I use the Copper Chloride method documented here :-
>
> http://www.instructables.com/id/Stop-using-Ferric-Chloride- 
> etchant!--A-better-etc/
>
> Sorry I am not big on video.
>
> But hope these help
>
>
> Cheers
>
> Andy Kirby
>
>
>
>
> On 22/08/10 18:51, Kalus Michael wrote:
>> Hi Andy.
>>
>> I'd realy like to take a look over your sholder when you do "built a
>> couple of boards up" - video? How do you do it?
>> Michael
>>
>>
>> Am 22.08.2010 um 19:02 schrieb an...@ki...:
>>
>>> Thanks mathias
>>>
>>> I have just received a couple of 1284's and built a couple of
>>> boards up
>>> with them so should be able to try it out over the next week.
>>>
>>> Cheers
>>>
>>> Andy Kirby
>>
>>
>> --------------------------------------------------------------------- 
>> ---------
>> This SF.net email is sponsored by
>>
>> Make an app they can't live without
>> Enter the BlackBerry Developer Challenge
>> http://p.sf.net/sfu/RIM-dev2dev
>> _______________________________________________
>> Amforth-devel mailing list
>> Amf...@li...
>> https://lists.sourceforge.net/lists/listinfo/amforth-devel
>>
>
> ---------------------------------------------------------------------- 
> --------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> Amforth-devel mailing list
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel

Re: [Amforth-devel] Atmega<any> support

[<an...@ki...>]

Michael

I have yet to document and put up the board design I am using as it is a
work in progress.

The techniques I use to make PCB's at home I have already documented here:-

http://aka47.adsl24.co.uk/serendipity/index.php?/pages/sspcb.html

This is where I will also document the minimalist microcontroler board
design I am using. It is a single sided PCB easy to make at home.

Most design work is sort of iterative in that I do a design and then try
out making it to discover where I did something wrong. Followed by
modifying the design and then trying it again until I am happy with the
end result.

The design itself is OK I am just iterating on the PCB layout to get to
something that is easy for other folk to work with. It is nearly there.
I am just making some of the pads a little larger to make it easier for
learner solderers. Then I can Document it and put all the files on line.

The need to enlarge the pads was something I found when building up a
pair of 644p boards to take the 1284p devices. These will be set up at
the full device clock of 20Mhz.

The version of the PCB when I put the details up should be 1.2 (1.0, 1.1
are the previous iterations).

For etching I use the Copper Chloride method documented here :-

http://www.instructables.com/id/Stop-using-Ferric-Chloride-etchant!--A-better-etc/

Sorry I am not big on video.

But hope these help


Cheers

Andy Kirby




On 22/08/10 18:51, Kalus Michael wrote:
> Hi Andy.
> 
> I'd realy like to take a look over your sholder when you do "built a  
> couple of boards up" - video? How do you do it?
> Michael
> 
> 
> Am 22.08.2010 um 19:02 schrieb an...@ki...:
> 
>> Thanks mathias
>>
>> I have just received a couple of 1284's and built a couple of  
>> boards up
>> with them so should be able to try it out over the next week.
>>
>> Cheers
>>
>> Andy Kirby
> 
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by 
> 
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev 
> _______________________________________________
> Amforth-devel mailing list
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel
> 

Re: [Amforth-devel] Atmega<any> support

[Kalus M. <mic...@on...>]

Hi Andy.

I'd realy like to take a look over your sholder when you do "built a  
couple of boards up" - video? How do you do it?
Michael


Am 22.08.2010 um 19:02 schrieb an...@ki...:

> Thanks mathias
>
> I have just received a couple of 1284's and built a couple of  
> boards up
> with them so should be able to try it out over the next week.
>
> Cheers
>
> Andy Kirby

Re: [Amforth-devel] Atmega<any> support

[<an...@ki...>]

Thanks mathias

I have just received a couple of 1284's and built a couple of boards up
with them so should be able to try it out over the next week.

Cheers

Andy Kirby



On 22/08/10 17:10, Matthias Trute wrote:
> Hi,
> 
> I've understood that not everyone wants to use the full toolchain
> him/herself. So i changed my policy slightly from "publish only
> tested" to "publish that may work" ;=) 
> 
>> Hi, There is the atmega1284p available (128k flash, 16k ram, dil40)
>> - drop in replacement of 32, 64 - so quite sexy chip. Do you plan to
>> support it? P.
> 
> The trunk just got nearly 100 new devices. Please report any success
> and failure here on this list, I want to create a
> works/works_with_mods/does_not_work table on the project website but
> cannot check all types myself.
> 
> The files are generated with the pd2amforth utility with the most
> recent part definition XML files from Atmel Studio 4.18SP2
> 
> feedback very welcome
> 
> Matthias
> 
> 
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by 
> 
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev 
> _______________________________________________
> Amforth-devel mailing list
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel
> 

[Amforth-devel] Atmega<any> support

[Matthias T. <mt...@we...>]

Hi,

I've understood that not everyone wants to use the full toolchain
him/herself. So i changed my policy slightly from "publish only
tested" to "publish that may work" ;=) 

> Hi, There is the atmega1284p available (128k flash, 16k ram, dil40)
> - drop in replacement of 32, 64 - so quite sexy chip. Do you plan to
> support it? P.

The trunk just got nearly 100 new devices. Please report any success
and failure here on this list, I want to create a
works/works_with_mods/does_not_work table on the project website but
cannot check all types myself.

The files are generated with the pd2amforth utility with the most
recent part definition XML files from Atmel Studio 4.18SP2

feedback very welcome

Matthias

Re: [Amforth-devel] SET-CURRENT (and MARKER)

[Matthias T. <mt...@we...>]

Hi,

in addition to Erichs notes

> I wanted to install MARKER on my device, but the definition in lib/ans94 use 
> SET-CURRENT, which mysteriously seems to not be in my dictionary but is in 
> core/words. (Other words are missing too, like SET-ORDER).
> 
> How can I correct this?

I try to get amforth as small as possible. The bare minimum of words
are collected in the dict_core and dict_minimum files. If you look at
the directory you will find a number of additional dict_ files, that
include some other files: dict_wl is for word lists, dict_vm
has definitions for the A/B registers (a VM extension), dict_mcu
has microcontroller specific words like sleep or -jtag that are
basically wrappers for specific machine instructions.

I did not yet found the gold way to make amforth both beginner
friendly and powerful and flexible and space optimal at once. 
The dict_* files are a vehicle but not the final solution. Sorry


Matthias

PS: and the wishes to make all this platform neutral make life
much harder... With linux only I could... ;=)

Re: [Amforth-devel] SET-CURRENT (and MARKER)

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

On 08/19/2010 08:46 PM, Leon Nathaniel Maurer wrote:
> I wanted to install MARKER on my device, but the definition in lib/ans94 use
> SET-CURRENT, which mysteriously seems to not be in my dictionary but is in
> core/words. (Other words are missing too, like SET-ORDER).
>
> How can I correct this?

in dict_appl.inc you add a few lines like
.include "words/set-current.asm"
.include "words/set-order.asm"

reassemble forth an burn it to your device again.
They are missing probably because they are not absolutely neccessary to run
amforth, however, using marker runs up against this.

Cheers,
Erich

[Amforth-devel] SET-CURRENT (and MARKER)

[Leon N. M. <leo...@gm...>]

I wanted to install MARKER on my device, but the definition in lib/ans94 use 
SET-CURRENT, which mysteriously seems to not be in my dictionary but is in 
core/words. (Other words are missing too, like SET-ORDER).

How can I correct this?

Thanks.
-Leon

PS For what it's worth, here's what I get when I run WORDS:

i@ (i!) i! e@ e! not s>d up! up@ >< cmove> unloop i sp! sp@ rp! rp@ +! rshift 
lshift 1- 1+ xor or and 2* 2/ invert um* um/mod m* + - log2 d< d> 0> u> u< 
true 0 0< > < 0= = <> r@ >r r> rot drop over swap ?dup dup c@ c! ! @ execute 
exit -int +int show-wordlist +usart baud tx? tx rx? rx order get-order get-
current environment? environment end-code code abort abort" [char] immediate 
recurse user constant variable [ ] ; :noname : does> create ?do leave +loop 
loop do again until repeat while begin then else if literal int! applturnkey 
is Rdefer Edefer words s" ." .s u. dinvert d- d+ d2* init-user ee>ram ee-user 
tib d2/ cmove dnegate dabs d>s j * defer@ defer! icompare find search-wordlist 
to value unused noop ver ?stack interpret depth rp0 sp sp0 cold pause quit 
place word /string source cscan parse 2swap >number number char refill accept 
cskip throw catch handler ' type count spaces space cr icount itype s, digit? 
ud/mod ud.r ud. . d. .r d.r sign #> #s # <# hold hld within max min abs mod / 
negate u/mod */ /mod */mod turnkey bl hex decimal bin ['] , compile ( \ allot 
here edp dp /key key? key emit? emit pad #tib >in cell+ cells base state f_cpu

Re: [Amforth-devel] 2constant, 2variable, 2!, 2@, 2drop, 2dup and (2variable) words

[Matthias T. <mt...@we...>]

Hi,


> what about to somehow consolidate
> everything available into a "the best of.." library in asm..?


The idea is great. The big drawback is, that the assembly
files are much harder to maintain. I prefer forth source
whenever possible. With the help of Michaels tool it should
be possible to generate asm files on the fly, if desired.

Doing that portably across the various OS'ses is nearly
impossible however. IMHO.

Matthias

Re: [Amforth-devel] 2constant, 2variable, 2!, 2@, 2drop, 2dup and (2variable) words

[Kalus M. <mic...@on...>]

Hi.

You are right - its in gforth. g4 was fun to do, used it for some  
privat purpose with amforth. Its free, use it as you like. There is  
no manual.

Michael



Am 18.08.2010 um 23:00 schrieb pito:

> g4 tool - interesting! On the first glance I tought I can run it in
> amforth, then I saw UPPERCASE, so it is now clear for me I have to
> use gforth..(:-).P.

Re: [Amforth-devel] 2constant, 2variable, 2!, 2@, 2drop, 2dup and (2variable) words

[pito <pi...@vo...>]

g4 tool - interesting! On the first glance I tought I can run it in
amforth, then I saw UPPERCASE, so it is now clear for me I have to
use gforth..(:-).P.

----- PŮVODNÍ ZPRÁVA -----
Od: "Matthias Trute" <mt...@we...>
Komu: "Everything around amforth"
<amf...@li...>
Předmět: Re: [Amforth-devel] 2constant, 2variable, 2!, 2@, 2drop,
2dup
Datum: 18.8.2010 - 20:25:51

> hi,
> 
> > Yes, those are written in assembler - ready to
> > be compiled into
> > > the image during the assembly stage (so I don't
> > need to upload them).
> > 
> Michael Kalus has written a smart tool that is
> able to convert any forth
> code to the special assembly notation. With that
> help you can
> use (almost) any forth code to include it at
> compile time.
> http://www.forth-ev.de/repos/g4/
> 
> > I don't see 2x.frt in the current repository -
> > but I have found
> > > it in the Lubos' 30mFC12 library.
> 
> Well, look at lib/ans94 there is a file named
> 2x.frt
> 
> 
> Matthias
> 
> 
> 
> ------------------------------------------------------------------------------
> > This SF.net email is sponsored by 
> 
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev 
> _______________________________________________
> Amforth-devel mailing list
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel

Re: [Amforth-devel] i! vs. f!

[pito <pi...@vo...>]

ok. f is clear, I've forgotten float does even exist.. i- what to
say..
why to diferentiate between storage technology? for readabilty and
the avoidance of errors..P.

----- PŮVODNÍ ZPRÁVA -----
Od: "Matthias Trute" <mt...@we...>
Komu: "Everything around amforth"
<amf...@li...>
Předmět: Re: [Amforth-devel] i! vs. f!
Datum: 18.8.2010 - 20:28:58

> hi,
> 
> > Hi, let me ask following - why the write to avr
> > flash in amforth
> > > uses i when i is used in other context as well.
> > Why not agree e.g.:
> > > 
> > f - flash internal - f!, f@
> 
> everything starting with f is already claimed by
> floating point words.
> 
> The i@/i! is based upon an recommendation by
> Elizabeth
> Rather. The i stands for instruction.
> 
> 
> 
> > ff - flash external - ff!, ff@
> 
> > ee - eprom external - ee!, ee@
> 
> feel free to use it. But wy differentiate
> between the storage technologies?
> 
> Matthias
> 
> 
> 
> ------------------------------------------------------------------------------
> > This SF.net email is sponsored by 
> 
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev 
> _______________________________________________
> Amforth-devel mailing list
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel

Re: [Amforth-devel] 2constant, 2variable, 2!, 2@, 2drop, 2dup and (2variable) words

[Marcin C. <sa...@sa...>]

On Wed, 18 Aug 2010, Matthias Trute wrote:

> hi,
>
>> Yes, those are written in assembler - ready to be compiled into
>> the image during the assembly stage (so I don't need to upload them).
>
> Michael Kalus has written a smart tool that is able to convert any forth
> code to the special assembly notation. With that help you can
> use (almost) any forth code to include it at compile time.
> http://www.forth-ev.de/repos/g4/

That's very useful, thank you.

>> I don't see 2x.frt in the current repository - but I have found
>> it in the Lubos' 30mFC12 library.
>
> Well, look at lib/ans94 there is a file named 2x.frt

Somehow my find(1) command misled me, sorry :)

--Marcin

Re: [Amforth-devel] i! vs. f!

[Matthias T. <mt...@we...>]

hi,

> Hi, let me ask following - why the write to avr flash in amforth
> uses i when i is used in other context as well. Why not agree e.g.:
> 
> f - flash internal - f!, f@

everything starting with f is already claimed by
floating point words.

The i@/i! is based upon an recommendation by Elizabeth
Rather. The i stands for instruction.



> ff - flash external - ff!, ff@

> ee - eprom external - ee!, ee@

feel free to use it. But wy differentiate
between the storage technologies?

Matthias

Re: [Amforth-devel] 2constant, 2variable, 2!, 2@, 2drop, 2dup and (2variable) words

[Matthias T. <mt...@we...>]

hi,

> Yes, those are written in assembler - ready to be compiled into
> the image during the assembly stage (so I don't need to upload them).

Michael Kalus has written a smart tool that is able to convert any forth
code to the special assembly notation. With that help you can
use (almost) any forth code to include it at compile time.
http://www.forth-ev.de/repos/g4/

> I don't see 2x.frt in the current repository - but I have found
> it in the Lubos' 30mFC12 library.

Well, look at lib/ans94 there is a file named 2x.frt


Matthias

Re: [Amforth-devel] 2constant, 2variable, 2!, 2@, 2drop, 2dup and (2variable) words

[Marcin C. <sa...@sa...>]

On Tue, 17 Aug 2010, pito wrote:

> Hi Marcin,
> let me ask you kindly following - there is an original 2x.frt
> library in amforth 4.0 with similar words - your lib is written in
> assembler - is this the same as the original (just rewritten to asm)
> or a new one?

Yes, those are written in assembler - ready to be compiled into
the image during the assembly stage (so I don't need to upload them).
I don't see 2x.frt in the current repository - but I have found
it in the Lubos' 30mFC12 library.

> So when I rename the file to 2x.asm can I include it into
> dictionaries when compile the amforth?

Yes, I am using a set of separate files called 2constant.asm,
2drop.asm etc.

> PS: there is a lot of other optimised words (in assembler ones) in
> Lubos Pekny's 30mFC12 library - what about to somehow consolidate
> everything available into a "the best of.." library in asm..? Pito

I didn't know that. I'm having a look at it, that seems useful, thank
you. Fortunately I think I can read some Czech :)

--Marcin

Re: [Amforth-devel] 2constant, 2variable, 2!, 2@, 2drop, 2dup and (2variable) words

[pito <pi...@vo...>]

Hi Marcin,
let me ask you kindly following - there is an original 2x.frt
library in amforth 4.0 with similar words - your lib is written in
assembler - is this the same as the original (just rewritten to asm)
or a new one? 
So when I rename the file to 2x.asm can I include it into
dictionaries when compile the amforth?
PS: there is a lot of other optimised words (in assembler ones) in
Lubos Pekny's 30mFC12 library - what about to somehow consolidate
everything available into a "the best of.." library in asm..? Pito

----- PŮVODNÍ ZPRÁVA -----
Od: "Marcin Cieslak" <sa...@sa...>
Komu: "Everything around amforth"
<amf...@li...>
Předmět: [Amforth-devel] 2constant, 2variable, 2!, 2@, 2drop, 2dup
and
Datum: 17.8.2010 - 3:37:26

> 
> Hello,
> 
> I have prepared some double-length words for your
> convenience:
> 
> Probably some could be more optimized.
> 
> --Marcin
> 
> ; ( d -- ) Compiler
> ; R( -- )
> ; create a named constant
> VE_2CONSTANT:
> .dw $ff09
> .db "2constant",0
> .dw VE_HEAD
> .set VE_HEAD = VE_2CONSTANT
> XT_2CONSTANT:
> .dw DO_COLON
> PFA_2CONSTANT:
> .dw XT_DOCREATE
> .dw XT_COMPILE
> .dw PFA_DO2VARIABLE
> .dw XT_SWAP
> .dw XT_COMMA
> .dw XT_COMMA
> .dw XT_EXIT
> 
> ; ( d -- ) Stack
> ; R( -- )
> ; drop TOS
> VE_2DROP:
> .dw $ff05
> .db "2drop",0
> .dw VE_HEAD
> .set VE_HEAD = VE_2DROP
> XT_2DROP:
> .dw PFA_2DROP
> PFA_2DROP:
> loadtos
> loadtos
> jmp DO_NEXT
> ; ( d1 -- d1 d1 ) Stack
> ; R( -- )
> ; stack manipulation
> VE_2DUP:
> .dw $ff04
> .db "2dup"
> .dw VE_HEAD
> .set VE_HEAD = VE_2DUP
> XT_2DUP:
> .dw PFA_2DUP
> PFA_2DUP:
> savetos
> ldd tosl, Y+2
> ldd tosh, Y+3
> savetos
> ldd tosl, Y+2
> ldd tosh, Y+3
> jmp DO_NEXT
> ; ( addr -- d ) Memory
> ; R( -- )
> ; read 2 cells from RAM (or IO or CPU register)
> ; byte order is little-endian 44 33 22 11 ->
> 11223344.
> VE_2FETCH:
> .dw $ff02
> .db "2@"
> .dw VE_HEAD
> .set VE_HEAD = VE_2FETCH
> XT_2FETCH:
> .dw PFA_2FETCH
> PFA_2FETCH:
> movw zl, tosl
> ld tosl, z+
> ld tosh, z+
> savetos
> ld tosl, z+
> ld tosh, z+
> jmp DO_NEXT
> ; ( d addr -- ) Memory
> ; R( -- )
> ; write 32bit to RAM memory (or IO or CPU
> registers)
> ; words are stored little-endian, so 12345678.
> becomes
> ; 78 56 34 12
> VE_2STORE:
> .dw $ff02
> .db "2!"
> .dw VE_HEAD
> .set VE_HEAD = VE_2STORE
> XT_2STORE:
> .dw PFA_2STORE
> PFA_2STORE:
> movw zl, tosl
> loadtos
> std Z+2, tosl
> std Z+3, tosh
> loadtos
> std Z+0, tosl
> std Z+1, tosh
> loadtos
> jmp DO_NEXT
> ; ( -- ) Compiler
> ; R( -- )
> ; create a variable entry and allocate RAM space
> for it
> VE_2VARIABLE:
> .dw $ff09
> .db "2variable",0
> .dw VE_HEAD
> .set VE_HEAD = VE_2VARIABLE
> XT_2VARIABLE:
> .dw DO_COLON
> PFA_2VARIABLE:
> .dw XT_HERE
> .dw XT_CONSTANT
> .dw XT_DOLITERAL
> .dw 4
> .dw XT_ALLOT
> .dw XT_EXIT
> ; ( -- addr )
> ; R( -- )
> ; puts content of parameter field (2 cells) to TOS
> ;VE_DO2VARIABLE:
> ;    .dw $ff0b
> ;    .db "(2variable)",0
> ;    .dw VE_HEAD
> ;    .set VE_HEAD = VE_DO2VARIABLE
> XT_DO2VARIABLE:
> .dw PFA_DO2VARIABLE
> PFA_DO2VARIABLE:
> savetos
> movw zl, wl
> adiw zl,1
> readflashcell tosl,tosh
> savetos
> movw zl, wl
> adiw zl,2
> readflashcell tosl,tosh
> jmp DO_NEXT
> 
> 
> ------------------------------------------------------------------------------
> > This SF.net email is sponsored by 
> 
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev 
> _______________________________________________
> Amforth-devel mailing list
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel

Re: [Amforth-devel] ?, c?, i? convenience words

[Kalus M. <mic...@on...>]

Maybe this ist interersting for you then.