Hi,
> Questions: The file “core/devices/atmega128/device.asm” says-
> "generated do not edit" Can these changes be added to the regular
> code base?
The MCUSR stuff should be possible. I'll have to rewrite the
tool that generates these files anyway.
>
> “core/drivers/usart_0.asm” - Can the chan
Hi David
Just found your response and time, so I tried it on amforth 4.8
Works great!
I had to use AVR Simulator 2 to get ATmega128 (instead of 128A and 128P on AVR
simulator1)
Some of the instructions in the 4.2 User guide are out of sync with 4.8; but
since the software was known to be goo
Hi D Williams -
I managed to get Amforth running on a Mega128. There are three
undocumented file changes you need to make:
“core/devices/atmega128/device.asm”: add these lines (I put them after
'ifndef EEPME' etc…)
.ifndef MCUSR
.equ MCUSR = MCUCSR
.endif
For some reason the Mega128 doesn't ha
Hello,
On 09/15/2011 05:22 PM, D Williams wrote:
>
> FWIW - The last version that worked for me on the amtega128 was amforth 3.1
> After that, I could not sort out the interrupts.
There was a Problem with interrupt addresses being off by a factor of 2. But
I don't recall, which version it was. A
FWIW - The last version that worked for me on the amtega128 was amforth 3.1
After that, I could not sort out the interrupts.
>Hello guys,
>I'm trying to build amforth for an ATmega128.
>It won't compile, searching for a definition of MCUSR.
>Attached you'll find the folder content I'm using (a st
Hello FORTH folk -
I have got amforth running on an ATMega128, using AVRStudio 4.18 and
Hapsim, a peripheral emulator that supports serial communications. It
displays the welcome message and you can run amforth on it, but real
slow! Its main utility is confirming that the build functions corre
