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
|
Dec
|
|
From: Bernard M. <bme...@gm...> - 2008-04-29 23:00:59
|
Ok, so the existing assembler should work fine. On first glance I do see some differences, the main one is that the interrupt vectors are 4 bytes apart not two bytes apart as in the other devices. Also, the names in ATxmega128A1.inc a quite a bit different so names in the .asm files will have to change accordingly .. On Tue, Apr 29, 2008 at 6:20 PM, Matthias Trute <mt...@we...> wrote: > > > Quick question: Does amforth support the XMEGA with just the addition of > > the > > .asm in the /devices folder and the appropriate .inc file from ATMEL > > Studio? > > I hope so, but do not know it. The assembler code works with > very little modifications (mostly regarding the serial interface). > > > Or is a bit harder than that? > > maybe, but Atmel mentioned that existing atmega code works for atxmega > without modifications. > > bye > Matthias > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _______________________________________________ > Amforth-devel mailing list > Amf...@li... > https://lists.sourceforge.net/lists/listinfo/amforth-devel > |
|
From: Matthias T. <mt...@we...> - 2008-04-29 13:19:11
|
Bernard, debugging hardware remotly is difficult. Did you check google, there was a short discussion around this with some possible reasons that cause a serial line to not work, the most stupid one is probably keeping the programmer connected (that may keep the reset line). > I have a 16mhz crystal connected to an external oscillator which feeds the > chip via XTAL1. Using the link you mentioned I get LFUSE = 0xC0 HFUSE= > 0xD9 > nad EFUSE= 0xff, is this correct? Cannot check, but the calculator works fine, usually. > Not sure what to debug next. just join on #forth-ev this evening Bye Matthias |
|
From: Bernard M. <bme...@gm...> - 2008-04-29 08:33:01
|
Thanks Mathias, I have a 16mhz crystal connected to an external oscillator which feeds the chip via XTAL1. Using the link you mentioned I get LFUSE = 0xC0 HFUSE= 0xD9 nad EFUSE= 0xff, is this correct? I then added these values to the sample makefile and did a "make write-fuse" and then reset the device. I also have frequency=16000000 in the bf.asm file. I still have no activity out the serial port. I am using miniterm and a loopback on the cable works fine at 9600 baud (what I have in bf.asm). Not sure what to debug next. Thanks again, Bernard On Tue, Apr 29, 2008 at 8:06 PM, Matthias Trute <mt...@we...> wrote: > > > 1. the line ".equ cpu_frequency = 8000000" in the bf.asm file, is that > the > > crystal frequency of the crystal frequency devided by two? > > That is the frequency, the controller runs with in Hz. which > clock source is used and the possible clock modification depend > on the fuse settings. http://palmavr.sf.net/cgi-bin/fc.cgi > may be useful here. > > Keep in mind, that the usart interface has a 2x setting that doubles > the baudrate, but this is unused in the default sources. > > btw: The template directory is a much better starting point since the > relevant files are better documented. > > > 2. Which serial port of the mega128 device will I expect the forth to > use? > > If you use the default sources, connect with usart0. > > Bye > Matthias > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _______________________________________________ > Amforth-devel mailing list > Amf...@li... > https://lists.sourceforge.net/lists/listinfo/amforth-devel > |
|
From: Matthias T. <mt...@we...> - 2008-04-29 08:06:10
|
> 1. the line ".equ cpu_frequency = 8000000" in the bf.asm file, is that the > crystal frequency of the crystal frequency devided by two? That is the frequency, the controller runs with in Hz. which clock source is used and the possible clock modification depend on the fuse settings. http://palmavr.sf.net/cgi-bin/fc.cgi may be useful here. Keep in mind, that the usart interface has a 2x setting that doubles the baudrate, but this is unused in the default sources. btw: The template directory is a much better starting point since the relevant files are better documented. > 2. Which serial port of the mega128 device will I expect the forth to use? If you use the default sources, connect with usart0. Bye Matthias |
|
From: Bernard M. <bme...@gm...> - 2008-04-29 07:04:16
|
Hi Mathias, Thanks but I found that setting the device flag to "-c stk200" solved the issue and downloading and verification finished fine. I am now trying to get a prompt out of the Forth via the serial port. I have a couple of questions: 1. the line ".equ cpu_frequency = 8000000" in the bf.asm file, is that the crystal frequency of the crystal frequency devided by two? 2. Which serial port of the mega128 device will I expect the forth to use? Thanks, Bernard On Tue, Apr 29, 2008 at 6:18 PM, Matthias Trute <mt...@we...> wrote: > > > Hi All, > > > > I have an STK500/STK501 and am trying to load a forth image to the > > atmega128 > > that is on the STK501. > > I have modified the bf.asm file etc for this micro and everything > > assembles > > ok on a Linux host. > > > > The problem is communication to the parallel port doesn't seem to work, > > anyone have any suggestions? > > Looks like a permission problem on the parport device. You may try > running avrdude as root (sudo recommended). Otherwise you may need > to contact the avrdude folks. > > Bye > Matthias > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _______________________________________________ > Amforth-devel mailing list > Amf...@li... > https://lists.sourceforge.net/lists/listinfo/amforth-devel > |
|
From: Matthias T. <mt...@we...> - 2008-04-29 06:26:51
|
> Matthias, > > Thanks for the personal reply. > >> emit/key and friends are deferred since they should easily >> re-targettable from the serial to say can or I2C. For number >> there was so such scenario. Why do you want to behave number >> differently? A solution could be to CATCH conversion errors, >> since number THROWs on them > >... or to allow entering double precision numbers. That may be added into the main-stream code base sometimes. Feel free to send a patch ;=) But note, that the number conversion in amforth is only good enough and not fully standard compatible... > Of course I am only playing, but when I used Forth as a sort of > super-monitor on an embedded system controlling a lathe I did this to > allow me to enter hex as $abcd whilst keeping BASE set to 10. Ahh. There are ongoing standardization tasks running with the forth2000x folks on this topic, and I remender a (short) discussion in the usenet (clf) this year around this topic too. We'll see, what will happen. bye Matthias |
|
From: Matthias T. <mt...@we...> - 2008-04-29 06:26:11
|
> Quick question: Does amforth support the XMEGA with just the addition of > the > .asm in the /devices folder and the appropriate .inc file from ATMEL > Studio? I hope so, but do not know it. The assembler code works with very little modifications (mostly regarding the serial interface). > Or is a bit harder than that? maybe, but Atmel mentioned that existing atmega code works for atxmega without modifications. bye Matthias |
|
From: Matthias T. <mt...@we...> - 2008-04-29 06:18:03
|
> Hi All, > > I have an STK500/STK501 and am trying to load a forth image to the > atmega128 > that is on the STK501. > I have modified the bf.asm file etc for this micro and everything > assembles > ok on a Linux host. > > The problem is communication to the parallel port doesn't seem to work, > anyone have any suggestions? Looks like a permission problem on the parport device. You may try running avrdude as root (sudo recommended). Otherwise you may need to contact the avrdude folks. Bye Matthias |
|
From: Bernard M. <bme...@gm...> - 2008-04-29 04:25:01
|
Hi All, I have an STK500/STK501 and am trying to load a forth image to the atmega128 that is on the STK501. I have modified the bf.asm file etc for this micro and everything assembles ok on a Linux host. The problem is communication to the parallel port doesn't seem to work, anyone have any suggestions? The error is: ------------------------------------------------------------------- make: *** [bf] Error 1 bmentink@laptop:~/amForth/amforth-2.7/appl/avr-STK500$ make bf avrdude -c stk500 -P /dev/parport0 -p atmega128 -e -U flash:w:bf.hex:i -U eeprom:w:bf.eep.hex:i avrdude: ser_open(): can't set attributes for device "/dev/parport0": Inappropriate ioctl for device make: *** [bf] Error 1 Thanks, Bernard. |
|
From: Tom H. <cel...@gm...> - 2008-04-29 00:51:32
|
Matthias, Thanks for the personal reply. > emit/key and friends are deferred since they should easily > re-targettable from the serial to say can or I2C. For number > there was so such scenario. Why do you want to behave number > differently? A solution could be to CATCH conversion errors, > since number THROWs on them One reason would be to allow the entering of different number bases whatever BASE is set to, or to allow entering double precision numbers. Of course I am only playing, but when I used Forth as a sort of super-monitor on an embedded system controlling a lathe I did this to allow me to enter hex as $abcd whilst keeping BASE set to 10. Regards Tom Harris <cel...@gm...> |
|
From: Bernard M. <bme...@gm...> - 2008-04-28 20:56:44
|
Quick question: Does amforth support the XMEGA with just the addition of the .asm in the /devices folder and the appropriate .inc file from ATMEL Studio? Or is a bit harder than that? Regards, Bernard |
|
From: Bernard M. <bme...@gm...> - 2008-04-28 06:53:37
|
Thanks Mathias, I may just do that. In the same vein, is there a mega128.asm around somewhere? If not I may create one using the at90can128.asm as a guide (I know there is the associated m128def.inc file supplied by the atmel studio install). Cheers, Bernard. On Mon, Apr 28, 2008 at 4:48 PM, Matthias Trute <mt...@we...> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Bernard Mentink wrote: > > Hi All, > > > > Has anyone written and Forth code to support the CAN perpheral on this > > device? > > The mcu core is supported, the perpheral to my knowledge not (yet). > > You are welcome to contribute it ;=) > > Matthias > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > > iD8DBQFIFVcl9bEHdGEMFjMRAoWLAJoDw8ARTXxPA2QhqT3HOIFDXDh5rwCfRLcq > 5nePEafyN1h6Q+VYtRKCb9w= > =nQ3+ > -----END PGP SIGNATURE----- > > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _______________________________________________ > Amforth-devel mailing list > Amf...@li... > https://lists.sourceforge.net/lists/listinfo/amforth-devel > |
|
From: Matthias T. <mt...@we...> - 2008-04-28 04:51:46
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tom Harris wrote: > Greetings, > > I am still trying to find my way around amforth, after a 20 year gap > since I last used Forth. I have what I suspect is a stupid question. > > On the Forth I last used I remember that the number word was vectored > via a variable 'number, so that you could replace the number parser. > Amforth does not use a deferred word for number, so it is not possible > to replace number, is this correct? I can redefine number, but any > previous usages of number, like the all-important quit word will still > use the old definition. Is there a reason why number was not deferred > like emit, key, pause, etc.? emit/key and friends are deferred since they should easily re-targettable from the serial to say can or I2C. For number there was so such scenario. Why do you want to behave number differently? A solution could be to CATCH conversion errors, since number THROWs on them Matthias -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIFVfh9bEHdGEMFjMRAjClAKCJqDErXIVFGpUqXJf8f2OLfYy1mgCgpSQL SZ+Rb2gJc+9XJiXPjG1gPB8= =Xizt -----END PGP SIGNATURE----- |
|
From: Matthias T. <mt...@we...> - 2008-04-28 04:48:39
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Bernard Mentink wrote: > Hi All, > > Has anyone written and Forth code to support the CAN perpheral on this > device? The mcu core is supported, the perpheral to my knowledge not (yet). You are welcome to contribute it ;=) Matthias -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIFVcl9bEHdGEMFjMRAoWLAJoDw8ARTXxPA2QhqT3HOIFDXDh5rwCfRLcq 5nePEafyN1h6Q+VYtRKCb9w= =nQ3+ -----END PGP SIGNATURE----- |
|
From: Tom H. <cel...@gm...> - 2008-04-28 03:19:19
|
Greetings, I am still trying to find my way around amforth, after a 20 year gap since I last used Forth. I have what I suspect is a stupid question. On the Forth I last used I remember that the number word was vectored via a variable 'number, so that you could replace the number parser. Amforth does not use a deferred word for number, so it is not possible to replace number, is this correct? I can redefine number, but any previous usages of number, like the all-important quit word will still use the old definition. Is there a reason why number was not deferred like emit, key, pause, etc.? On the bright side, what other language allows you to have enough knowledge to poke around in the internals after a few days spent learning it? TomH |
|
From: Bernard M. <bme...@gm...> - 2008-04-28 01:49:35
|
Hi All, Has anyone written and Forth code to support the CAN perpheral on this device? Thanks, Bernard Mentink |
|
From: Matthias T. <mt...@we...> - 2008-04-05 18:51:55
|
Hi, I just made a new release of amforth. The most notable changes are a better ans94 conformance (stack order of double cell values) and the assembler from Lubos Pekny (www.forth.cz). The assembler may emit a warning like Appnotes\m169def.inc(1199): warning: Register r31 (and r30) already defined by the .DEF directive this is harmless and can be ignored. The downloadable package contains now every file to make it easier to use. Have fun with it Matthias |
|
From: Matthias T. <mt...@we...> - 2008-03-24 15:25:34
|
Klaus Zerbe wrote: > @Matt: If possible, try also another controller since Atmega8 ist a > little bit small for amforth anyway. For the records: I just put an amforth from repository trunk on an atmega8 with an external 12MHz quartz and everything worked as expected. amforth 2.7 ATmega8 > unused cells decimal u. 2298 ok > The fuses are as follows MCU=atmega168 LFUSE=0xee HFUSE=0xdf EFUSE=0xf9 MCU=atmega8 LFUSE=0xee HFUSE=0xd9 Bye Matthias |
|
From: Matthias T. <mt...@we...> - 2008-03-23 09:09:14
|
Hi, > are there yet any ideas on how the Block commands will be done? I guess > the > biggest problem is memory as the normal 1024 byte block size would be far > to big. I've implemented some words for the I2C EEPROM with the native block sizes of the chips (around 32 or 64 bytes per block). One approach to implement full block buffers could be a virtualization. But this will be difficult since the normal memory access words have to be used to access the block buffer. A word set like b@/b! to access (virtual) block memory would certainly work, but does not help porting code from other forth's . In older forth version a word b/blk was defined to give the size of a block buffer in bytes. The value can be different for each block device (EEPROM, SD-Card etc). A total different solution would be: full block buffer sizes but only on systems that have enough memory (internal or external). All solution should provide some kind of an abstraction layer, since there are far too many different block devices available. That layer can work with native block sizes. Bye Matthias |
|
From: Christian B. <cas...@ca...> - 2008-03-22 18:26:10
|
Servus, (=bavarian for hello and goodbye) are there yet any ideas on how the Block commands will be done? I guess the biggest problem is memory as the normal 1024 byte block size would be far to big. Servus Casandro |
|
From: Matthias T. <mt...@we...> - 2008-03-13 20:24:29
|
Christian Berger wrote: > Ohh I was able to get it from therw. It seems like you did preety much what I > did. I think from what I have seen the only point where I could claim my code > to be better is in the vsync area, but that's largely irrelevant. Ohh and my > clock doesn't need an additional quartz. > > Anyhow, are you interrested in getting some FM-Synthesis sound routines for > your application? I'm collecting everything and publish all I'm allowed to do. But the TV application is not mine. Bye Matthias |
|
From: Christian B. <cas...@ca...> - 2008-03-13 20:11:43
|
Am Donnerstag 13 März 2008 20:57:57 schrieb Matthias Trute: > Erich Waelde wrote: > > Hello, > > > > Christian Berger wrote: > >> Am Mittwoch 12 März 2008 20:43:16 schrieb Erich Waelde: > >>> not sure whether this helps: You did look at the application > >>> in amforth/appl/tv, did you? > >> > >> No, but that sounds interresting. What is it and where do I find it? I > >> don't have an appl directory. > > > > You need to look at the svn sources directly: > > http://amforth.svn.sourceforge.net/viewvc/amforth/appl/tv/ > > I'm sorry to tell, that the link does not work any more... Ohh I was able to get it from therw. It seems like you did preety much what I did. I think from what I have seen the only point where I could claim my code to be better is in the vsync area, but that's largely irrelevant. Ohh and my clock doesn't need an additional quartz. Anyhow, are you interrested in getting some FM-Synthesis sound routines for your application? Servus Casandro |
|
From: Matthias T. <mt...@we...> - 2008-03-13 19:57:55
|
Erich Waelde wrote: > Hello, > > Christian Berger wrote: >> Am Mittwoch 12 März 2008 20:43:16 schrieb Erich Waelde: >>> not sure whether this helps: You did look at the application >>> in amforth/appl/tv, did you? >> No, but that sounds interresting. What is it and where do I find it? I don't >> have an appl directory. > > You need to look at the svn sources directly: > http://amforth.svn.sourceforge.net/viewvc/amforth/appl/tv/ I'm sorry to tell, that the link does not work any more... The reason is simple: a reorganization of the repository structure. It is not yet fully finished but I think it won't change a lot again, since I use the new structure internally for quite some time. The only thing thats left is around applications that I cannot work with, like the tv application. The actual link for them is http://amforth.svn.sourceforge.net/viewvc/amforth/applications/ All new code is now in trunk, regardless of core or library or (my) applications. Matthias |
|
From: Erich W. <ew....@on...> - 2008-03-13 19:14:10
|
Hello, Christian Berger wrote: > Am Mittwoch 12 März 2008 20:43:16 schrieb Erich Waelde: > > not sure whether this helps: You did look at the application > > in amforth/appl/tv, did you? > > No, but that sounds interresting. What is it and where do I find it? I don't > have an appl directory. You need to look at the svn sources directly: http://amforth.svn.sourceforge.net/viewvc/amforth/appl/tv/ Cheers, Erich |
|
From: Christian B. <cas...@ca...> - 2008-03-13 08:05:36
|
Servus, I just made the first release of the Forth-Computer, a modified version of amforth with video output and keyboard input. Here's the release note: http://www.mikrocontroller.net/topic/94193 Servus Casandro |