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
|
| 2025 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(7) |
Sep
(9) |
Oct
|
Nov
(4) |
Dec
|
|
From: Kalus M. <mic...@on...> - 2010-08-24 18:13:43
|
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 |
|
From: <an...@ki...> - 2010-08-23 11:40:36
|
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 > |
|
From: Kalus M. <mic...@on...> - 2010-08-22 22:03:07
|
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 |
|
From: <an...@ki...> - 2010-08-22 20:28:01
|
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 > |
|
From: Kalus M. <mic...@on...> - 2010-08-22 17:51:31
|
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 |
|
From: <an...@ki...> - 2010-08-22 17:02:14
|
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 > |
|
From: Matthias T. <mt...@we...> - 2010-08-22 16:10:38
|
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 |
|
From: Matthias T. <mt...@we...> - 2010-08-20 17:55:00
|
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... ;=) |
|
From: Erich W. <ew....@na...> - 2010-08-19 19:50:30
|
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 |
|
From: Leon N. M. <leo...@gm...> - 2010-08-19 19:47:14
|
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 |
|
From: Matthias T. <mt...@we...> - 2010-08-19 19:26:43
|
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 |
|
From: Kalus M. <mic...@on...> - 2010-08-18 22:37:47
|
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. |
|
From: pito <pi...@vo...> - 2010-08-18 21:00:22
|
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 |
|
From: pito <pi...@vo...> - 2010-08-18 20:54:10
|
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 |
|
From: Marcin C. <sa...@sa...> - 2010-08-18 18:34:41
|
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 |
|
From: Matthias T. <mt...@we...> - 2010-08-18 18:29:08
|
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 |
|
From: Matthias T. <mt...@we...> - 2010-08-18 18:26:02
|
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 |
|
From: Marcin C. <sa...@sa...> - 2010-08-18 11:05:33
|
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 |
|
From: pito <pi...@vo...> - 2010-08-17 18:31:30
|
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 |
|
From: Kalus M. <mic...@on...> - 2010-08-17 16:51:48
|
Maybe this ist interersting for you then. |
|
From: pito <pi...@vo...> - 2010-08-17 08:50:28
|
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@ ff - flash external - ff!, ff@ e - eprom internal - e!, e@ ee - eprom external - ee!, ee@ i - index j - index c - char Pito. |
|
From: Marcin C. <sa...@sa...> - 2010-08-17 02:05:20
|
Below please find definitions of c?, i? and ? - I find
them useful while exploring amforth (and AVR) interactively.
--Marcin
; ( addr -- ) Numeric IO
; R( -- )
; output single character from the address
VE_CQUESTION:
.dw $ff02
.db "c?"
.dw VE_HEAD
.set VE_HEAD = VE_CQUESTION
XT_CQUESTION:
.dw DO_COLON
PFA_CQUESTION:
.dw XT_CFETCH
.dw XT_DOT
.dw XT_EXIT
; : c? ( addr -- ) c@ . ;
; ( addr -- ) Numeric IO
; R( -- )
; output single word from the address in flash
VE_IQUESTION:
.dw $ff02
.db "i?"
.dw VE_HEAD
.set VE_HEAD = VE_IQUESTION
XT_IQUESTION:
.dw DO_COLON
PFA_IQUESTION:
.dw XT_IFETCH
.dw XT_DOT
.dw XT_EXIT
; : i? ( addr -- ) i@ . ;
; ( addr -- ) Numeric IO
; R( -- )
; output single cell from the address
VE_QUESTION:
.dw $ff01
.db "?",0
.dw VE_HEAD
.set VE_HEAD = VE_QUESTION
XT_QUESTION:
.dw DO_COLON
PFA_QUESTION:
.dw XT_FETCH
.dw XT_DOT
.dw XT_EXIT
; : ? ( addr -- ) @ . ;
|
|
From: Marcin C. <sa...@sa...> - 2010-08-17 01:38:24
|
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
|
|
From: pito <pi...@vo...> - 2010-08-16 16:20:34
|
it was suuposed, but not available...p. ----- PŮVODNÍ ZPRÁVA ----- Od: an...@ki... Komu: amf...@li... Předmět: Re: [Amforth-devel] Atmega 1284p Datum: 16.8.2010 - 12:25:58 > Lol > > It was supposed to be mainstream about 2 years > ago. Check out the forums > on AVR Freaks. > > Got some on order, just waiting delivery, then we > can have a play. > > > > On 16/08/10 08:19, pito wrote: > > Matthias, > > mind an average windoze user cannot run the > > provided python files > > > (I've tried python 3.x and 2.7 as well). It > > would be great to find > > > an python expert who is able to port the stuff > > to windoze python.. > > > And yes, the 1284P is DIL40 and 44smd drop in > > replacement for 32 and > > > 644. My guess is it will be the mainstream for > > the next 2y. > > > Pito. > > > > ----- PŮVODNÍ ZPRÁVA ----- > > Od: "Matthias Trute" <mt...@we...> > > Komu: "Everything around amforth" > > <amf...@li...> > > Předmět: Re: [Amforth-devel] Atmega 1284p > > Datum: 15.8.2010 - 9:46:26 > > > >> Pito, > >> > >>> 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. > >> > >> amforth has a utility named pd2amforth that > >> creates the device > >> specific driver files. All of the currently > >> delivered controller > >> files (core/devices/*) are generated with that > >> tool. I excpect no > >> problems with that new controller, it should > >> work. > >> >> Formal support is > >> unlikly, I cannot buy each controller type and > >> test it myself, sorry. > >> > >> 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 > >> > > > > > > > ------------------------------------------------------------------------------ > > > > > 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 |
|
From: <an...@ki...> - 2010-08-16 10:26:06
|
Lol It was supposed to be mainstream about 2 years ago. Check out the forums on AVR Freaks. Got some on order, just waiting delivery, then we can have a play. On 16/08/10 08:19, pito wrote: > Matthias, > mind an average windoze user cannot run the provided python files > (I've tried python 3.x and 2.7 as well). It would be great to find > an python expert who is able to port the stuff to windoze python.. > And yes, the 1284P is DIL40 and 44smd drop in replacement for 32 and > 644. My guess is it will be the mainstream for the next 2y. > Pito. > > ----- PŮVODNÍ ZPRÁVA ----- > Od: "Matthias Trute" <mt...@we...> > Komu: "Everything around amforth" > <amf...@li...> > Předmět: Re: [Amforth-devel] Atmega 1284p > Datum: 15.8.2010 - 9:46:26 > >> Pito, >> >>> 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. >> >> amforth has a utility named pd2amforth that >> creates the device >> specific driver files. All of the currently >> delivered controller >> files (core/devices/*) are generated with that >> tool. I excpect no >> problems with that new controller, it should work. >> Formal support is >> unlikly, I cannot buy each controller type and >> test it myself, sorry. >> >> 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 > > > > ------------------------------------------------------------------------------ > 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 > |
8 messages has been excluded from this view by a project administrator.
