(called Launchpads) and played with one for a while, but
wanted to more than it was capable of at the time.
So many parts ... so little time ... !! :)
Kind regards,
Michael
k6MLE
On 6/17/2021 2:38 AM, Erich Wälde wrote:
Hello Michael,
Michael Picco writes:
Hello!
I finally have figured out
Hello!
I finally have figured out how to efficiently interact with Amforth on
my mega2560 and have installed much of the I2C stuff on it.
Question:
Has anyone worked out how to talk to the BME280 sensor using Amforth?
Wading through the spec sheet tells me it's going to be a challenge. It
Hello Martin,
Thank you for responding!
In my work directory, which is aptly named 'amforth-6.9', I don't see a
copy of the template.asm file with "amforth-low.asm" mentioned. The
amforth-low.asm file is referenced in the avr8 subdirectory. Is there
something I am missing?
Kind regards,
. Is there a setting required prior to
flashing that I'm failing to set properly?
Thanks in advance!
On 5/22/2021 9:51 PM, George Herzog wrote:
There are AmForth error codes. Read up on them.
On Sun, May 23, 2021, 12:42 Michael Picco wrote:
Hello!
I seem to have stumbled across an issue.
First
.
Best wishes,
Tristan
On 2021-05-21 05:25, Michael Picco wrote:
Hello,
As mentioned earlier, it's now working.
I do not see the word 'marker' defined. Should it have been part of
the basic system, or do I need to pull it from somewhere?
Then I'd like to see about doing something real simple, like
approach to 'Hello World!' :)
Kind regards,
Michael
K6MLE
On 5/20/2021 12:41 PM, Michael Picco wrote:
I should add the following changes to Craig Lindley's write-up:
Step 3:
Under Win10, the correct file location for avrasm2.exe will be:
c:\Program
Files(86)\Atmel\Studio\7.0\toolchain\avr8
r the 2560)
device.inc (for the 2560)
dict_appl.inc
dict_appl_core.inc
LICENSE.txt
m2560def.inc
make.bat
readme.txt
uno.asm
Hope this helps!
Kind regards,
Michael
K6MLE
On 5/20/2021 11:56 AM, Michael Picco wrote:
Hello All!
I have finally had success!
It turns out that the .eep and .hex files I wa
ss I'm mistaken, you need an MKII programmer, because you can only
inject a .HEX file through this device. This operation overwrites the
original bootloader.
BR
Le mar. 18 mai 2021 à 06:08, Michael Picco a
écrit :
Hello,
I am attempting to use the mega2560 as a nicely featured development
plat
Hello,
I am attempting to use the mega2560 as a nicely featured development
platform for AmForth-6.9. The machine I'm using is a Win10 box, with
Microchip Studio version 7 installed.
In the zip file, under appl/atmega2561, I notice atmega256.eep.hex and
atmega256.hex. The eep.hex file
,
Jan
Op 20 apr. 2019, om 00:12 heeft Michael Picco 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
:
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 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
:
Hello Michael,
amForth has in the download the complete hex files!
Cheers,
Jan
Op 6 apr. 2019, om 20:20 heeft Michael Picco 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
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
Thanks to Craig Lindley's write-up, I've now gotten 5.2 working on a Uno
without the hair-pulling of previous versions.
That said, I attempted to install MARKER, but was told 'set-current' was
missing ... how does one get that installed?
Thanks,
Michael
K6MLE
, as there are people here that are far more
adept with it than I), which is what I hope this forum will return to.
Kind regards to all.
Michael Picco
On 2/19/2014 3:30 AM, Paulo Ferreira wrote:
Not reading Legal mumbo jumbo and not having a bit of good sense is the
kind of thing that can
Having been through this exercise with I2C, let me confirm what Matthias
has stated.
The address sent to the device contains a 1 for WRITE; 0 for READ in the
least significant bit position.
Regards,
Michael
K6MLE
On 11/21/2013 10:49 PM, Matthias Trute wrote:
Hi Craig,
In the function i2c
Thank you, Matthias. I think this will be quite helpful!
Regards,
Michael
On 10/25/2013 11:11 AM, Matthias Trute wrote:
Hi Michael,
These are the *definitions* of the constants for later use. The
WANT_TWI option includes the file device.inc at compile time and
Where, exactly, is the
Hi Matthias,
Looking at the core/devices/atmega328p directory (for the Uno) I see
three 'device.*' files and the atmega328p.frt file, which all have the
notation generated automatically, do not edit. In each of those I
note references to the TW* declarations desired for my Uno. If I
shouldn't
On 10/24/2013 11:12 AM, Matthias Trute wrote:
Michael,
Looking at the core/devices/atmega328p directory (for the Uno) I
see three 'device.*' files and the atmega328p.frt file, which all
have the notation generated automatically, do not edit. In each
of those I note references to the
Hi Craig,
Just catching up after a few days away from the computer ... I trust
you've been able to get 5.1 working on your Uno?
The link you posted (by Neal Crook), is well-done ... it got me started
and finally working, but it's out of date and some of the
items have changed. At home, I have
Programmed the resulting hex/eep files into the Uno and version 5.1
comes up just fine.
Still not sure why the warning came up, but amForth appears to be
working as expected.
Michael
On 10/9/2013 3:01 PM, Michael Picco wrote:
Hello,
I keep getting the following warning when compiling
Now that I have a repeatable process worked out that will yield a
programmed part, I'd like to give the part more functionality.
For starters, I'd like to add 1-wire capability to the Uno.
It appears that I need to modify the 1wire.asm file prior to including
it. This seems to include the
Perhaps I've figured it out!
I inserted the two equates into the project master file and followed
that with the include for 1wire.asm. Now the new words 1w.reset and
1w.slot are appearing on my Uno!
Now for some 1-wire development!
Thanks again!
Michael
On 10/10/2013 11:00 AM, Michael
I noticed that the documentation regarding Un-Doing Definitions is in
error.
The two forth source files referred to have different paths:
The current paths appear to be:
lib/ans94/core/postpone.frt
and
lib/ans94/core-ext/marker.frt
Having said that, when trying to compile 'marker.frt', it
Thanks Erich!
That wasn't quite clear in the write-up. Having made that change, it's
now working.
Regards,
Michael
On 10/10/2013 1:02 PM, Erich Waelde wrote:
Hello,
On 10/10/2013 09:48 PM, Michael Picco wrote:
I noticed that the documentation regarding Un-Doing
Definitions
Hello,
I keep getting the following warning when compiling amforth for an
Arduino Uno:
Use of undefined or forward referenced symbol 'XT_NOOP' in .equ/.set
The warning points to line 28 in the file usart_common.asm.
I've gone through the compilation process, double-checking my work
several
I am using the avrispMK2 and Atmel Studio 5.0.
I don't find an ASM file specifically for the 2560 and wonder if the
2561 file is the one I should being using. The other
question I have is the where in the 'project' I should include the 1wire
file from the driver directory?
Any guidance is
28 matches
Mail list logo
