You can subscribe to this list here.
2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
(5) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2007 |
Jan
|
Feb
(6) |
Mar
(41) |
Apr
(23) |
May
(11) |
Jun
(2) |
Jul
|
Aug
|
Sep
(9) |
Oct
(2) |
Nov
(1) |
Dec
(1) |
2008 |
Jan
(6) |
Feb
(1) |
Mar
(23) |
Apr
(18) |
May
(21) |
Jun
(13) |
Jul
(34) |
Aug
(5) |
Sep
(1) |
Oct
(4) |
Nov
|
Dec
(4) |
2009 |
Jan
|
Feb
(5) |
Mar
(5) |
Apr
(10) |
May
(1) |
Jun
(11) |
Jul
(1) |
Aug
|
Sep
|
Oct
(2) |
Nov
(3) |
Dec
(13) |
2010 |
Jan
(10) |
Feb
(4) |
Mar
(28) |
Apr
(3) |
May
(38) |
Jun
(22) |
Jul
(92) |
Aug
(154) |
Sep
(218) |
Oct
(45) |
Nov
(20) |
Dec
(1) |
2011 |
Jan
(33) |
Feb
(15) |
Mar
(32) |
Apr
(33) |
May
(48) |
Jun
(35) |
Jul
(7) |
Aug
|
Sep
(11) |
Oct
(5) |
Nov
|
Dec
(7) |
2012 |
Jan
(56) |
Feb
(11) |
Mar
(6) |
Apr
|
May
(128) |
Jun
(59) |
Jul
(21) |
Aug
(16) |
Sep
(24) |
Oct
(39) |
Nov
(12) |
Dec
(12) |
2013 |
Jan
(14) |
Feb
(61) |
Mar
(97) |
Apr
(46) |
May
(13) |
Jun
(23) |
Jul
(12) |
Aug
(25) |
Sep
(9) |
Oct
(81) |
Nov
(73) |
Dec
(45) |
2014 |
Jan
(36) |
Feb
(57) |
Mar
(20) |
Apr
(41) |
May
(43) |
Jun
(11) |
Jul
(14) |
Aug
(32) |
Sep
(9) |
Oct
(27) |
Nov
(21) |
Dec
(6) |
2015 |
Jan
(14) |
Feb
(23) |
Mar
(1) |
Apr
(19) |
May
(40) |
Jun
(11) |
Jul
(1) |
Aug
(2) |
Sep
(14) |
Oct
(10) |
Nov
(9) |
Dec
(13) |
2016 |
Jan
(4) |
Feb
(3) |
Mar
(7) |
Apr
|
May
(4) |
Jun
(13) |
Jul
(8) |
Aug
(3) |
Sep
(4) |
Oct
(1) |
Nov
|
Dec
|
2017 |
Jan
(6) |
Feb
(1) |
Mar
(1) |
Apr
(7) |
May
(10) |
Jun
(5) |
Jul
(7) |
Aug
(9) |
Sep
|
Oct
(1) |
Nov
(5) |
Dec
|
2018 |
Jan
|
Feb
|
Mar
(5) |
Apr
|
May
|
Jun
(3) |
Jul
(6) |
Aug
|
Sep
(2) |
Oct
(54) |
Nov
(47) |
Dec
(53) |
2019 |
Jan
(23) |
Feb
(24) |
Mar
(19) |
Apr
(15) |
May
(5) |
Jun
(34) |
Jul
(9) |
Aug
(9) |
Sep
(3) |
Oct
(2) |
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
(7) |
Apr
(7) |
May
(5) |
Jun
(15) |
Jul
(22) |
Aug
(28) |
Sep
(13) |
Oct
(9) |
Nov
(17) |
Dec
(13) |
2021 |
Jan
(5) |
Feb
(1) |
Mar
(1) |
Apr
(9) |
May
(21) |
Jun
(9) |
Jul
|
Aug
(6) |
Sep
(16) |
Oct
|
Nov
(1) |
Dec
(6) |
2022 |
Jan
|
Feb
|
Mar
|
Apr
(7) |
May
(6) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(11) |
Sep
(21) |
Oct
(5) |
Nov
(1) |
Dec
(1) |
2024 |
Jan
(1) |
Feb
(4) |
Mar
|
Apr
(7) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
From: Matthias T. <mt...@we...> - 2019-06-04 19:11:41
|
Am Dienstag, den 04.06.2019, 18:39 +0000 schrieb Jan Kromhout: > Hello, > > Ho do I set the parameters for the speed if the I2C to 400 > kHz? Thanks for any help. > > : init_i2c ( --- ) > \ init at 100 kHz > i2c.prescaler/1 #72 i2c.init > ; > Did you check http://amforth.sourceforge.net/TG/recipes/TWI.html#twi ? (Javascript required) Matthias |
From: Jan K. <kro...@ho...> - 2019-06-04 18:39:26
|
Hello, Ho do I set the parameters for the speed if the I2C to 400 kHz? Thanks for any help. : init_i2c ( --- ) \ init at 100 kHz i2c.prescaler/1 #72 i2c.init ; Thanks for any help. Cheers, Jan |
From: Peter C. H. <pet...@un...> - 2019-06-04 15:41:31
|
amforth/avr8/lib/hardware/spi.frt Peter > On 4 Jun 2019, at 17:29, Jan Kromhout via Amforth-devel <amf...@li...> wrote: > > Hello, > > I need to read and write to the SPI interface (bus) on the arduino. (pin 10,11,12,13) > Wich words are the best to use? > > Thanks for any help. > Cheers, > > Jan > > _______________________________________________ > Amforth-devel mailing list for http://amforth.sf.net/ > Amf...@li... > https://lists.sourceforge.net/lists/listinfo/amforth-devel |
From: Matthias T. <mt...@we...> - 2019-06-04 15:39:26
|
Hi, > I need to read and write to the SPI interface (bus) on the arduino. > (pin 10,11,12,13) > Wich words are the best to use? The ones desccribed in the SPI recipe are the best current practice. http://amforth.sourceforge.net/TG/recipes/SPI.html The arduino hello world recipe shall give some hints and further links for working with this platform http://amforth.sourceforge.net/TG/recipes/Arduino-HelloWorld.html HTH+BR Matthias |
From: Jan K. <jan...@ic...> - 2019-06-04 15:29:13
|
Hello, I need to read and write to the SPI interface (bus) on the arduino. (pin 10,11,12,13) Wich words are the best to use? Thanks for any help. Cheers, Jan |
From: Matthias T. <mt...@we...> - 2019-06-02 08:41:43
|
Hi, Thanks for your analysis. > This suggests that both the MCUSR and the WDTSR should be cleared on > reset. > > I've added a line: > out_ WDTCSR, zerol > to COLD which covers it. adding it to COLD in a central location is troublesome. Not all AVR8 have a watchdog at all and those who have one, have at least two different ways to handle it. Rather difficult to implement centrally. > > The minimum requirement is to clear both MCUSR.WDRF and WDTCSR.WDE. AFAIK, the minimum reset intervall is 15ms, what makes it possible to add the reset code to the application turnkey word. For debugging purposes, the reset recipe may be helpful http://amforth.sourceforge.net/TG/recipes/Reset.html Matthias |
From: Martin N. <amf...@mg...> - 2019-06-01 14:28:09
|
This snippet is a bit more like it (I think): lds temp0, WDTCSR ori temp0, (1<<WDCE) | (1<<WDE) out_ WDTCSR, temp0 out_ WDTCSR, zerol -- Regards, Martin Nicholas. E-mail: rep...@mg... (Address will be valid throughout 2019). |
From: Martin N. <amf...@mg...> - 2019-06-01 12:28:33
|
Looking into a crashing ATmega2560, I found this clause in the docs: "If the Watchdog is accidentally enabled, for example by a runaway pointer or brown-out condition, the device will be reset and the Watchdog Timer will stay enabled. If the code is not set up to handle the Watchdog, this might lead to an eternal loop of time-out resets. To avoid this situation, the application software should always clear the Watchdog System Reset Flag (WDRF) and the WDE control bit in the initialisation routine, even if the Watchdog is not in use." This suggests that both the MCUSR and the WDTSR should be cleared on reset. I've added a line: out_ WDTCSR, zerol to COLD which covers it. The minimum requirement is to clear both MCUSR.WDRF and WDTCSR.WDE. Cheers! -- Regards, Martin Nicholas. E-mail: rep...@mg... (Address will be valid throughout 2019). |
From: Matthias T. <mt...@we...> - 2019-05-31 17:59:08
|
Am Donnerstag, den 30.05.2019, 09:56 +0100 schrieb Martin Nicholas via Amforth-devel: > Taken me months to notice, but 6.8 still reports a "ver" of 6.7 from > env-forthversion.asm Thank you. In fact, for the AVR8 and MSP430 variants, version 6.8 is in fact 6.7 since no changes were made for them. Fixed for 6.9 :) Matthias |
From: Martin N. <amf...@mg...> - 2019-05-30 08:56:32
|
Taken me months to notice, but 6.8 still reports a "ver" of 6.7 from env-forthversion.asm -- Regards, Martin Nicholas. E-mail: rep...@mg... (Address will be valid throughout 2019). |
From: Matthias T. <mt...@we...> - 2019-05-20 17:20:07
|
Hi Claus, > I saw an amForth for the HiFive1 board. Is there a relese for the > HiFive1 Rev. B board available? Sorry, there is no immediate plan to implement amforth on the rev.B platform. Matthias |
From: Claus K. <in...@ck...> - 2019-05-19 12:19:32
|
Hi, I am going my first steps with HiFive1 Rev. B. To look inside this new system I think Forth could be helpful. I saw an amForth for the HiFive1 board. Is there a relese for the HiFive1 Rev. B board available? Regards, Claus Dr. Claus Kühnel - Talstr. 13b - CH-8852 Altendorf Mobile +41-76-3960801 |
From: Terry B. <tr...@gm...> - 2019-05-09 18:52:04
|
Just a quick update and a note about a problem I encountered (which might help someone else facing the same issue): I was able to build using the instructions given in the Linux User's Guide. But I was unable to run, at any baud rate, the amforth-shell.py. This turned out to be an issue with the COM port drivers when using VirtualBox to emulate linux on a Windows 10 host. Once I was running real linux (dual boot on my laptop) this issue went away and the amforth-shell.py works great. |
From: Terry B. <tr...@gm...> - 2019-04-30 18:23:33
|
Tristan, Thank you for the prompt reply! Please see my comments below On Tue, Apr 30, 2019 at 12:01 PM Tristan Williams <ho...@tj...> wrote: > > I am interested to know what eval hardware you are using. > I am using an Olimex AVR-CAN: https://www.olimex.com/Products/AVR/Development/AVR-CAN/ > > I have not used this device, but I think > amforth-6.8/avr8/devices/at90can128/at90can128.frt has the constants > and these can be sent to the mcu with various tools, including > amforth-shell.py which can do many other things too. > > http://amforth.sourceforge.net/TG/recipes/Upload.html?highlight=upload > > > A lot more words are available as forth code, rather than built-in. > To use them send the forth code to the mcu as above. From amforth-6.8 > directory > > find . -name *.frt > > will show where the files are. amforth-shell.py helps a lot with > including files. > > I also found the technical guide and cookbook really helpful. > > http://amforth.sourceforge.net/TG/TG.html > http://amforth.sourceforge.net/TG/Cookbook.html > > Kind regards, > Tristan > I will try that. Thank you for pointing me in the right direction. Terry |
From: Tristan W. <ho...@tj...> - 2019-04-30 17:01:13
|
Hello Terry, > I moved my builds to Linux and I can now build a working set of .hex files > that run on my eval hardware without errors or warnings. I am interested to know what eval hardware you are using. > Though there are some parts that appear to be missing, in particular > the various PORTX constants I have not used this device, but I think amforth-6.8/avr8/devices/at90can128/at90can128.frt has the constants and these can be sent to the mcu with various tools, including amforth-shell.py which can do many other things too. http://amforth.sourceforge.net/TG/recipes/Upload.html?highlight=upload > and the words that operate on them (like pinport). A lot more words are available as forth code, rather than built-in. To use them send the forth code to the mcu as above. From amforth-6.8 directory find . -name *.frt will show where the files are. amforth-shell.py helps a lot with including files. I also found the technical guide and cookbook really helpful. http://amforth.sourceforge.net/TG/TG.html http://amforth.sourceforge.net/TG/Cookbook.html Kind regards, Tristan |
From: Terry B. <tr...@gm...> - 2019-04-30 15:37:32
|
I moved my builds to Linux and I can now build a working set of .hex files that run on my eval hardware without errors or warnings. Though there are some parts that appear to be missing, in particular the various PORTX constants and the words that operate on them (like pinport). When looking at the .lst file generated as part of the build process I see that last .set for each port is: .set WANT_PORTA = 1 >From my understanding this is all that should be needed to get the constants included. My Makefile defines the MCU as: MCU=at90can128 Any idea what I am missing? Thanks Terry |
From: Terry B. <tr...@gm...> - 2019-04-29 13:03:38
|
Good morning, This is my first mailing to the list, and very much a newbie to forth. I am trying to build for the AT90CAN128 mcu, following the directions given the "User Manual for Windows". I am using AVRStudio 4.18 (build 716). The first issue I ran across was adding the additional path to the assembly options as stated in section "1.2.5 Setting up AVRStudio" of the documentation. I could not locate the "core" directory, but realizing these directions are out of date, I did add the full path to the "avr8" directory which contains, among other things, preamble.asm, device.asm, and macros.asm. This did help the assembler locate the correct files. So I attempted to run a build. The second issue I ran into is during the compile of "device.asm", I get the following error: "...\device.asm(54): error: Undefined symbol: isr". I think that this means that I am missing the definition of "isr". I've looked in the various include (*.inc) files, and assembly (*.asm) files and can't find this anywhere. Any clue where I have gone astray? Thanks Terry |
From: Michael P. <mp...@pl...> - 2019-04-20 23:05:50
|
Hello Tristan and Jan, Thank you! To quote that famous line from the movie "Young Frankenstein" ... "It's ALIVE!!!" :-) I did have to move from my Windoze box to a Linux box to get it programmed! Linux identified the USB port easily ... Wondoze ... not so! Now to work through the manual a bit ... printed out Release 6.7. Then I might have more questions! I hope this old guy (me!) can re-learn enough to be able to make it interesting to a 17-year old that I'm trying to get interested in programming on the Arduino! Kind regards, Michael K6MLE On 4/20/2019 12:34 PM, Tristan Williams wrote: > Hello Michael, > > It is also worth checking your communication settings are 38000 8N1 > and that flow control is not set to hardware (RTS/CTS), unless your > serial connection is wired that way. > > kind regards, > > Tristan > > On 20Apr19 11:47, Jan Kromhout via Amforth-devel wrote: >> Hello, >> >> I use these with a pololu programmer v2.1 >> >> Laad de nieuwe versie: >> avrdude -p m328p -c avrispv2 -P /dev/tty.usbmodem00230362 -U efuse:w:0xFF:m -U hfuse:w:0xD9:m -U lfuse:w:0xFF:m -U flash:w:amforth.hex:i -U eeprom:w:amforth.eep.hex:i >> >> And it works great, no problems at all. >> >> >> Cheers, >> >> Jan >> >> >> >>> Op 20 apr. 2019, om 00:12 heeft Michael Picco <mp...@pl...> het volgende geschreven: >>> >>> Hello, >>> >>> I've bought some extra atmega328P-U parts and attempted to install the Amforth files using the AVR Pocket Programmer from Sparkfun. The first couple of attempts ended in failure and I got nothing back from the Arduino Uno when hooking it up using Putty on my Linux box. I was able to use the programmer to reinstall the optiboot and was successful, so it appears that the programmer is doing as intended. >>> >>> Does the Amforth loading procedure involve setting the fuses? >>> >>> The command line being used is: avrdude -p m328p -c usbtiny -U flash:w:uno.hex -U eeprom:w:uno.eep.hex -v >>> >>> Any help is greatly appreciated! >>> >>> Kind regards, >>> >>> Michael >>> >>> K6MLE >>> >>> >>> >>> >>> _______________________________________________ >>> Amforth-devel mailing list for http://amforth.sf.net/ >>> Amf...@li... >>> https://lists.sourceforge.net/lists/listinfo/amforth-devel >> >> >> _______________________________________________ >> Amforth-devel mailing list for http://amforth.sf.net/ >> Amf...@li... >> https://lists.sourceforge.net/lists/listinfo/amforth-devel >> > > _______________________________________________ > Amforth-devel mailing list for http://amforth.sf.net/ > Amf...@li... > https://lists.sourceforge.net/lists/listinfo/amforth-devel > |
From: Tristan W. <ho...@tj...> - 2019-04-20 19:35:07
|
Hello Michael, It is also worth checking your communication settings are 38000 8N1 and that flow control is not set to hardware (RTS/CTS), unless your serial connection is wired that way. kind regards, Tristan On 20Apr19 11:47, Jan Kromhout via Amforth-devel wrote: > Hello, > > I use these with a pololu programmer v2.1 > > Laad de nieuwe versie: > avrdude -p m328p -c avrispv2 -P /dev/tty.usbmodem00230362 -U efuse:w:0xFF:m -U hfuse:w:0xD9:m -U lfuse:w:0xFF:m -U flash:w:amforth.hex:i -U eeprom:w:amforth.eep.hex:i > > And it works great, no problems at all. > > > Cheers, > > Jan > > > > > Op 20 apr. 2019, om 00:12 heeft Michael Picco <mp...@pl...> het volgende geschreven: > > > > Hello, > > > > I've bought some extra atmega328P-U parts and attempted to install the Amforth files using the AVR Pocket Programmer from Sparkfun. The first couple of attempts ended in failure and I got nothing back from the Arduino Uno when hooking it up using Putty on my Linux box. I was able to use the programmer to reinstall the optiboot and was successful, so it appears that the programmer is doing as intended. > > > > Does the Amforth loading procedure involve setting the fuses? > > > > The command line being used is: avrdude -p m328p -c usbtiny -U flash:w:uno.hex -U eeprom:w:uno.eep.hex -v > > > > Any help is greatly appreciated! > > > > Kind regards, > > > > Michael > > > > K6MLE > > > > > > > > > > _______________________________________________ > > Amforth-devel mailing list for http://amforth.sf.net/ > > Amf...@li... > > https://lists.sourceforge.net/lists/listinfo/amforth-devel > > > > _______________________________________________ > Amforth-devel mailing list for http://amforth.sf.net/ > Amf...@li... > https://lists.sourceforge.net/lists/listinfo/amforth-devel > |
From: Michael P. <mp...@pl...> - 2019-04-20 18:20:01
|
Thank you Jan! I have a Pololu programmer arriving on Monday. I will give this a try with the Pocket Programmer as well. Kind regards, Michael K6MLE On 4/20/2019 2:47 AM, Jan Kromhout via Amforth-devel wrote: > Hello, > > I use these with a pololu programmer v2.1 > > Laad de nieuwe versie: > avrdude -p m328p -c avrispv2 -P /dev/tty.usbmodem00230362 -U efuse:w:0xFF:m -U hfuse:w:0xD9:m -U lfuse:w:0xFF:m -U flash:w:amforth.hex:i -U eeprom:w:amforth.eep.hex:i > > And it works great, no problems at all. > > > Cheers, > > Jan > > > >> Op 20 apr. 2019, om 00:12 heeft Michael Picco <mp...@pl...> het volgende geschreven: >> >> Hello, >> >> I've bought some extra atmega328P-U parts and attempted to install the Amforth files using the AVR Pocket Programmer from Sparkfun. The first couple of attempts ended in failure and I got nothing back from the Arduino Uno when hooking it up using Putty on my Linux box. I was able to use the programmer to reinstall the optiboot and was successful, so it appears that the programmer is doing as intended. >> >> Does the Amforth loading procedure involve setting the fuses? >> >> The command line being used is: avrdude -p m328p -c usbtiny -U flash:w:uno.hex -U eeprom:w:uno.eep.hex -v >> >> Any help is greatly appreciated! >> >> Kind regards, >> >> Michael >> >> K6MLE >> >> >> >> >> _______________________________________________ >> Amforth-devel mailing list for http://amforth.sf.net/ >> Amf...@li... >> https://lists.sourceforge.net/lists/listinfo/amforth-devel > > > _______________________________________________ > Amforth-devel mailing list for http://amforth.sf.net/ > Amf...@li... > https://lists.sourceforge.net/lists/listinfo/amforth-devel > |
From: Jan K. <jan...@ic...> - 2019-04-20 09:47:35
|
Hello, I use these with a pololu programmer v2.1 Laad de nieuwe versie: avrdude -p m328p -c avrispv2 -P /dev/tty.usbmodem00230362 -U efuse:w:0xFF:m -U hfuse:w:0xD9:m -U lfuse:w:0xFF:m -U flash:w:amforth.hex:i -U eeprom:w:amforth.eep.hex:i And it works great, no problems at all. Cheers, Jan > Op 20 apr. 2019, om 00:12 heeft Michael Picco <mp...@pl...> het volgende geschreven: > > Hello, > > I've bought some extra atmega328P-U parts and attempted to install the Amforth files using the AVR Pocket Programmer from Sparkfun. The first couple of attempts ended in failure and I got nothing back from the Arduino Uno when hooking it up using Putty on my Linux box. I was able to use the programmer to reinstall the optiboot and was successful, so it appears that the programmer is doing as intended. > > Does the Amforth loading procedure involve setting the fuses? > > The command line being used is: avrdude -p m328p -c usbtiny -U flash:w:uno.hex -U eeprom:w:uno.eep.hex -v > > Any help is greatly appreciated! > > Kind regards, > > Michael > > K6MLE > > > > > _______________________________________________ > Amforth-devel mailing list for http://amforth.sf.net/ > Amf...@li... > https://lists.sourceforge.net/lists/listinfo/amforth-devel |
From: Michael P. <mp...@pl...> - 2019-04-19 22:12:48
|
Hello, I've bought some extra atmega328P-U parts and attempted to install the Amforth files using the AVR Pocket Programmer from Sparkfun. The first couple of attempts ended in failure and I got nothing back from the Arduino Uno when hooking it up using Putty on my Linux box. I was able to use the programmer to reinstall the optiboot and was successful, so it appears that the programmer is doing as intended. Does the Amforth loading procedure involve setting the fuses? The command line being used is: avrdude -p m328p -c usbtiny -U flash:w:uno.hex -U eeprom:w:uno.eep.hex -v Any help is greatly appreciated! Kind regards, Michael K6MLE |
From: Matthias T. <mt...@we...> - 2019-04-08 14:16:17
|
Hi, It's a little late to respond.. I'm impressed. Good work. May I put a link to your pages via the amforth cookbook? Matthias |
From: Tristan W. <ho...@tj...> - 2019-04-07 08:30:37
|
Hello Michael, Something I only discovered recently (when my AVRIPSmkII clone started misbehaving) is that avrdude has various bitbang drivers, including one for my usb-serial adaptor (5V FT232R based). I used the avrdude ft232r programmer type, though a search through the output of avrdude -c ? shows drivers for a number of different usb-serial adaptors. Connection details are in avrdude.conf (excerpt below) programmer id = "ft232r"; desc = "FT232R Synchronous BitBang"; type = "ftdi_syncbb"; connection_type = usb; miso = 1; # RxD sck = 0; # TxD mosi = 2; # RTS reset = 4; # DTR ; Tristan On 07Apr19 08:48, Jan Kromhout via Amforth-devel wrote: > Hello Michael > > I use the Pololu avr programmer v2.1 on my macbook, this works great! > > Cheers, > > Jan > > > Op 7 apr. 2019, om 05:31 heeft Michael Picco <mp...@pl...> het volgende geschreven: > > > > Hello Jan, > > Thank you for that! I've located the hex files. > > What I can't seem to locate is my old AVRIPSmkII programmer. I notice that it's been obsoleted by Atmel! Can you suggest a more current model? > > Thanks again! > > Michael > > K6MLE > > > > > > > > On 4/6/2019 11:35 AM, Jan Kromhout via Amforth-devel wrote: > >> Hello Michael, > >> > >> amForth has in the download the complete hex files! > >> > >> Cheers, > >> > >> Jan > >> > >>> Op 6 apr. 2019, om 20:20 heeft Michael Picco <mp...@pl...> het volgende geschreven: > >>> > >>> Hello, > >>> > >>> I am trying to get back to amForth after a hiatus (last used 5.2). > >>> > >>> Is there a set of compiling instructions suited for version 6.7 using Atmel Studio 7? > >>> > >>> Thank you in advance! > >>> > >>> Michael > >>> > >>> > >>> > >>> > >>> _______________________________________________ > >>> Amforth-devel mailing list for http://amforth.sf.net/ > >>> Amf...@li... > >>> https://lists.sourceforge.net/lists/listinfo/amforth-devel > >> > >> > >> _______________________________________________ > >> Amforth-devel mailing list for http://amforth.sf.net/ > >> Amf...@li... > >> https://lists.sourceforge.net/lists/listinfo/amforth-devel > >> > > > > > > > > _______________________________________________ > > Amforth-devel mailing list for http://amforth.sf.net/ > > Amf...@li... > > https://lists.sourceforge.net/lists/listinfo/amforth-devel > > > > _______________________________________________ > Amforth-devel mailing list for http://amforth.sf.net/ > Amf...@li... > https://lists.sourceforge.net/lists/listinfo/amforth-devel > |
From: Jan K. <jan...@ic...> - 2019-04-07 06:49:04
|
Hello Michael I use the Pololu avr programmer v2.1 on my macbook, this works great! Cheers, Jan > Op 7 apr. 2019, om 05:31 heeft Michael Picco <mp...@pl...> het volgende geschreven: > > Hello Jan, > Thank you for that! I've located the hex files. > What I can't seem to locate is my old AVRIPSmkII programmer. I notice that it's been obsoleted by Atmel! Can you suggest a more current model? > Thanks again! > Michael > K6MLE > > > > On 4/6/2019 11:35 AM, Jan Kromhout via Amforth-devel wrote: >> Hello Michael, >> >> amForth has in the download the complete hex files! >> >> Cheers, >> >> Jan >> >>> Op 6 apr. 2019, om 20:20 heeft Michael Picco <mp...@pl...> het volgende geschreven: >>> >>> Hello, >>> >>> I am trying to get back to amForth after a hiatus (last used 5.2). >>> >>> Is there a set of compiling instructions suited for version 6.7 using Atmel Studio 7? >>> >>> Thank you in advance! >>> >>> Michael >>> >>> >>> >>> >>> _______________________________________________ >>> Amforth-devel mailing list for http://amforth.sf.net/ >>> Amf...@li... >>> https://lists.sourceforge.net/lists/listinfo/amforth-devel >> >> >> _______________________________________________ >> Amforth-devel mailing list for http://amforth.sf.net/ >> Amf...@li... >> https://lists.sourceforge.net/lists/listinfo/amforth-devel >> > > > > _______________________________________________ > Amforth-devel mailing list for http://amforth.sf.net/ > Amf...@li... > https://lists.sourceforge.net/lists/listinfo/amforth-devel |