amforth-devel — Development discussion and user support

Re: [Amforth-devel] amforth-upload.py does not set serial interface parameters

[Matthias T. <mt...@we...>]

Hi Erich,

> I use amforth-upload.py as well. However, I have noticed that the
> script apparently does not know/check the settings of the serial
> port (speed, parity, etc). Thus I use minicom to connect to the
> controller first, then amforth-upload.py will work nicely.

Interesting thing. Do want to send me a patch? ;=) I put on
my todo list...

Matthias

Re: [Amforth-devel] Python scripts under WinXP - Python 3.1.2

[Matthias T. <mt...@we...>]

Hi pito,

> Hi, dear friends who knows python well,
> somebody has got an experience/fix with the python scripts running under
> e.g Python 3.1.2

they are still at python2 level. There is no serial support in python3
(at least not to my knowledge). The syntax errors are from the print
command which needs parenthesis in python3, but that minor comparing
with the serial module issue.

Matthias

[Amforth-devel] amforth-upload.py does not set serial interface parameters

[Erich W. <ew....@na...>]

Hi,

just for the records:


On 07/03/2010 10:23 AM, Matthias Trute wrote:
> I use the amforth-upload.py a lot. Just have a look at the howto
> section.


I use amforth-upload.py as well. However, I have noticed that the
script apparently does not know/check the settings of the serial
port (speed, parity, etc). Thus I use minicom to connect to the
controller first, then amforth-upload.py will work nicely.


Cheers,
Erich

[Amforth-devel] Python scripts under WinXP - Python 3.1.2

[pito <pi...@vo...>]

Hi, dear friends who knows python well,
somebody has got an experience/fix with the python scripts running under
e.g Python 3.1.2 (winXP)? I've tried to run the ready to use amforth
v4 .py scripts, however with no success (when run with IDLE - "pythons
IDE" - it shows syntax errors). Thanks, Pito.

Re: [Amforth-devel] Starting with amforth v4

[pito <pi...@vo...>]

Hi Matthias,
yes the work under XP with amforth v4 and AVR Studio is easy (begginers
luck..), no issue, I am not using any .py scripts yet. Except the device.asm
path issue it was quick to start. The Forfiter is a simple but useful
forth terminal where you can set the CR delay and it may wait on the
"ok" response as well so uploading works nice.
My previous Q to the interactivity - so my understanding is you may delete
words from flash w/o burning new image. However let us mind the atmel
flash and eeprom endurance..
Pito



> Hi pito,
> 
> > Dear friends,
> > I've just started with amforth and I would be happy
> > to ask expets following:
> > > In the version 4 there is a feature which stops me
> > to compile succesfuly
> > > in the template.asm:
> > ....These files include the *def.inc from atmel internally.
> > > .include "device.asm"......
> > 
> > I had to change to:
> > ...These files include the *def.inc from atmel internally.
> > > .include "devices/atmega32/device.asm".....
> > in order to compile.
> 
> I just wrote a little page at
> http://amforth.sourceforge.net/porting.html that may
> be useful. (and to
> answer Leons question as well). Feel free to comment
> or (if possible)
> send me a better one. I may edit it anyway later on...
> 
> > I am using AVR studio under XP. It works great.
> 
> Yeah, since I do not really use the studio, I cannot
> give any assistance. My world is Linux and Make/ant,
> 
> despite the fact that I use the Atmel assembler with
> 
> the wine tool ;=)
> 
> > I am using Forfiter for uploading the words.
> 
> Well, my czech is not that good to praise it ;=)
> 
> > 2. I am new with forth (I am learning it because
> > I want to design a FPGA
> > > based forth procesor) so I've tried to add new words
> > from examples -
> > > however, some examples require to have defined additional
> > words, which
> > > are not included in the fresh compilation from the
> > template. I've read
> > > the docs there but - pls be so kind and do advise
> > me in which dict_*.inc
> > > shall I include missing *.asm word definitions? Is
> > there any "full version"
> > > which compiles all the words from your distribution
> > - all those in \amforth-4.0\core\words?
> > > And how to delete a word from flash when interactivly
> > added? With forget
> > > (..not there) or marker?
> 
> I use the amforth-upload.py a lot. Just have a look
> at the howto
> section. With it I can keep the assembly code as little
> as possible
> (forth code is much better maintainable than assembly).
> 
> 
> For those who want to convert forth source code into
> assembler syntax
> Michael Kalus wrote a smart utility. With it you can
> include the
> generated files in your dict_appl.inc file. Michaels
> tool is called
> g4 and can be found at http://www.forth-ev.de/trac/browser/g4
> 
> And finally: the dict-files from the template/ directory
> contain most of
> the pre-defined words. Either directly or via the dict_xy
> files fromthe
> core directory. There are only a very few that are
> not included (you
> won't miss them initially).
> 
> And yes, marker is the word you need. Just upload the
> lib/ans/postpone.frt and lib/ans94/marker.frt in that
> order
> to your controller. I droped FORGET in order to get
> the
> word list feature simple.
> 
> 
> Matthias

Re: [Amforth-devel] Starting with amforth v4

[Matthias T. <mt...@we...>]

Hi pito,

> Dear friends,
> I've just started with amforth and I would be happy to ask expets following:
> In the version 4 there is a feature which stops me to compile succesfuly
> in the template.asm:
> ....These files include the *def.inc from atmel internally.
> .include "device.asm"......
> 
> I had to change to:
> ...These files include the *def.inc from atmel internally.
> .include "devices/atmega32/device.asm".....
> in order to compile.

I just wrote a little page at
http://amforth.sourceforge.net/porting.html that may be useful. (and to
answer Leons question as well). Feel free to comment or (if possible)
send me a better one. I may edit it anyway later on...

> I am using AVR studio under XP. It works great.

Yeah, since I do not really use the studio, I cannot
give any assistance. My world is Linux and Make/ant, 
despite the fact that I use the Atmel assembler with 
the wine tool ;=)

> I am using Forfiter for uploading the words.

Well, my czech is not that good to praise it ;=)

> 2. I am new with forth (I am learning it because I want to design a FPGA
> based forth procesor) so I've tried to add new words from examples -
> however, some examples require to have defined additional words, which
> are not included in the fresh compilation from the template. I've read
> the docs there but - pls be so kind and do advise me in which dict_*.inc
> shall I include missing *.asm word definitions? Is there any "full version"
> which compiles all the words from your distribution - all those in \amforth-4.0\core\words?
> And how to delete a word from flash when interactivly added? With forget
> (..not there) or marker?

I use the amforth-upload.py a lot. Just have a look at the howto
section. With it I can keep the assembly code as little as possible
(forth code is much better maintainable than assembly). 

For those who want to convert forth source code into assembler syntax
Michael Kalus wrote a smart utility. With it you can include the
generated files in your dict_appl.inc file. Michaels tool is called
g4 and can be found at http://www.forth-ev.de/trac/browser/g4

And finally: the dict-files from the template/ directory contain most of
the pre-defined words. Either directly or via the dict_xy files fromthe
core directory. There are only a very few that are not included (you
won't miss them initially).

And yes, marker is the word you need. Just upload the
lib/ans/postpone.frt and lib/ans94/marker.frt in that order
to your controller. I droped FORGET in order to get the
word list feature simple.


Matthias

[Amforth-devel] Starting with amforth v4

[pito <pi...@vo...>]

Dear friends,
I've just started with amforth and I would be happy to ask expets following:
In the version 4 there is a feature which stops me to compile succesfuly
in the template.asm:
....These files include the *def.inc from atmel internally.
.include "device.asm"......

I had to change to:
...These files include the *def.inc from atmel internally.
.include "devices/atmega32/device.asm".....
in order to compile. I am using AVR studio under XP. It works great.
I am using Forfiter for uploading the words.

2. I am new with forth (I am learning it because I want to design a FPGA
based forth procesor) so I've tried to add new words from examples -
however, some examples require to have defined additional words, which
are not included in the fresh compilation from the template. I've read
the docs there but - pls be so kind and do advise me in which dict_*.inc
shall I include missing *.asm word definitions? Is there any "full version"
which compiles all the words from your distribution - all those in \amforth-4.0\core\words?
And how to delete a word from flash when interactivly added? With forget
(..not there) or marker?

Thanks a lot.

Re: [Amforth-devel] Help getting started with a atmeg644PA

[Leon N M. <leo...@gm...>]

Awesome. That's just what I was looking for. I used the wrong uart_X.asm file 
and didn't modify USART_B_VALUE and USART_C_VALUE. Now everything works.

Is there a document that would have told me to do this?

Thanks for your help.
-Leon

>Friday 02 July 2010
>From: Matthias Trute <mt...@we...>
>Subject: Re: [Amforth-devel] Help getting started with a atmeg644PA
> Hi Leon,
> 
> > Could you be more specific about what worked for you?
> 
> What did I do? I took the amforth-4.0 files and added the Atmel files
> from the studio to them. Than I created the device tree for the
> atmega644pa with the pd2amforth utility and modified the template
> application to use it. Than I used the Atmel assembler to generate the
> hex files. All worked without any problem, even with my ubuntu linux
> wine setup. I did not check whether amforth actually works, I do not
> have the hardware...
> 
> I cannot reproduce your problem, that makes it really hard to solve
> it.
> 
> > I never doubted that
> > there are microcontollers that work. I get the same message from the
> > relevant device.asm file with the 644 and 644p, so whatever my problem
> > is, it's not limited to the 644pa.
> > 
> > devices/atmega644{,p,pa}/device.asm(13): error: Overlap in .cseg:
> > addr=0x1 conflicts with 0x0:0x2
> 
> This error message is of the not-so-useful type. I have no idea where it
> comes from. Sorry.
> 
> log from the terminal follows (excuse the German phrases, I forgot to
> set LANG properly..)
> 
> --------
> mt@ayla:~/2/amforth-4.0/tools$ ./pd2amforth
> ATmega644PA.xml
> 
> ... copy the file to core/devices, chdir to appl/template ...
> 
> mt@ayla:~/2/amforth-4.0/appl/template$ make
> wine ../../Atmel/avrasm2.exe -I ../../Atmel/Appnotes2 -I ../../core
> -I ../../core/devices/atmega644pa -fI -v0 -e template.eep.hex -l
> template.lst template.asm
> mt@ayla:~/2/amforth-4.0/appl/template$ svn diff
> Index: template.asm
> ===================================================================
> --- template.asm (Revision 899)
> +++ template.asm (Arbeitskopie)
> @@ -17,10 +17,10 @@
> .equ F_CPU = 8000000
> 
> ; initial baud rate of terminal
> -.include "drivers/usart.asm"
> +.include "drivers/usart_0.asm"
> .equ BAUD = 9600
> -.equ USART_B_VALUE = (1<<TXEN) | (1<<RXEN) | (1<<RXCIE)
> -.equ USART_C_VALUE = (3<<UCSZ0)
> +.equ USART_B_VALUE = (1<<TXEN0) | (1<<RXEN0) | (1<<RXCIE0)
> +.equ USART_C_VALUE = (3<<UCSZ00)
> 
> 
> .equ HLDSIZE  = $10    ; 16 bit cellsize with binary representation
> Index: makefile
> ===================================================================
> --- makefile (Revision 899)
> +++ makefile (Arbeitskopie)
> @@ -17,7 +17,7 @@
> 
> # the MCU should be identical to the device
> # setting in template.asm
> -MCU=atmega16
> +MCU=atmega644pa
> 
> # set the fuses according to your MCU
> LFUSE=0xnn
> mt@ayla:~/2/amforth-4.0/appl/template$
> ------------------
> 
> Matthias

Re: [Amforth-devel] Help getting started with a atmeg644PA

[Matthias T. <mt...@we...>]

Hi Leon,

> Could you be more specific about what worked for you?

What did I do? I took the amforth-4.0 files and added the Atmel files
from the studio to them. Than I created the device tree for the
atmega644pa with the pd2amforth utility and modified the template
application to use it. Than I used the Atmel assembler to generate the
hex files. All worked without any problem, even with my ubuntu linux
wine setup. I did not check whether amforth actually works, I do not
have the hardware...

I cannot reproduce your problem, that makes it really hard to solve
it.

> I never doubted that 
> there are microcontollers that work. I get the same message from the relevant 
> device.asm file with the 644 and 644p, so whatever my problem is, it's not 
> limited to the 644pa.
> 
> devices/atmega644{,p,pa}/device.asm(13): error: Overlap in .cseg: addr=0x1 
> conflicts with 0x0:0x2

This error message is of the not-so-useful type. I have no idea where it
comes from. Sorry.

log from the terminal follows (excuse the German phrases, I forgot to
set LANG properly..)

--------
mt@ayla:~/2/amforth-4.0/tools$ ./pd2amforth
ATmega644PA.xml

... copy the file to core/devices, chdir to appl/template ...

mt@ayla:~/2/amforth-4.0/appl/template$ make
wine ../../Atmel/avrasm2.exe -I ../../Atmel/Appnotes2 -I ../../core
-I ../../core/devices/atmega644pa -fI -v0 -e template.eep.hex -l
template.lst template.asm
mt@ayla:~/2/amforth-4.0/appl/template$ svn diff
Index: template.asm
===================================================================
--- template.asm (Revision 899)
+++ template.asm (Arbeitskopie)
@@ -17,10 +17,10 @@
.equ F_CPU = 8000000

; initial baud rate of terminal
-.include "drivers/usart.asm"
+.include "drivers/usart_0.asm"
.equ BAUD = 9600
-.equ USART_B_VALUE = (1<<TXEN) | (1<<RXEN) | (1<<RXCIE)
-.equ USART_C_VALUE = (3<<UCSZ0)
+.equ USART_B_VALUE = (1<<TXEN0) | (1<<RXEN0) | (1<<RXCIE0)
+.equ USART_C_VALUE = (3<<UCSZ00)


.equ HLDSIZE  = $10    ; 16 bit cellsize with binary representation
Index: makefile
===================================================================
--- makefile (Revision 899)
+++ makefile (Arbeitskopie)
@@ -17,7 +17,7 @@

# the MCU should be identical to the device
# setting in template.asm
-MCU=atmega16
+MCU=atmega644pa

# set the fuses according to your MCU
LFUSE=0xnn
mt@ayla:~/2/amforth-4.0/appl/template$ 
------------------

Matthias

Re: [Amforth-devel] Help getting started with a atmeg644PA

[Leon N. M. <leo...@gm...>]

Hello Matthias,

Could you be more specific about what worked for you? I never doubted that 
there are microcontollers that work. I get the same message from the relevant 
device.asm file with the 644 and 644p, so whatever my problem is, it's not 
limited to the 644pa.

devices/atmega644{,p,pa}/device.asm(13): error: Overlap in .cseg: addr=0x1 
conflicts with 0x0:0x2

Thanks.
-Leon

On Friday, July 02, 2010 11:48:11 am you wrote:
> I just compiled a file set, no problems. I'd really recoommend you
> another controller to begin with, even the avrdude does not (yet)
> this one.
> 
> Matthias

Re: [Amforth-devel] Help getting started with a atmeg644PA

[Matthias T. <mt...@we...>]

Hi Leon,

> I've used pd2amforth to generate the files, and I switched to a different usart 
> file. That got rid of one error, but I still have the other one:
> 
> devices/atmega644pa/device.asm(13): error: Overlap in .cseg: addr=0x1 conflicts 
> with 0x0:0x2

I just compiled a file set, no problems. I'd really recoommend you
another controller to begin with, even the avrdude does not (yet)
this one.

Matthias

Re: [Amforth-devel] Help getting started with a atmeg644PA

[Leon N M. <leo...@gm...>]

I've used pd2amforth to generate the files, and I switched to a different usart 
file. That got rid of one error, but I still have the other one:

devices/atmega644pa/device.asm(13): error: Overlap in .cseg: addr=0x1 conflicts 
with 0x0:0x2

Any other advice?

Thanks.
-Leon

>Friday 02 July 2010
>From: Matthias Trute <mt...@we...>
>Subject: Re: [Amforth-devel] Help getting started with a atmeg644PA
> Hi Leon,
> 
> > C:\Users\Leon\Desktop\amforth-4.0\core\drivers/usart.asm(2): warning:
> > Use of undefined or forward referenced symbol 'UBRRL' in .equ/.set
> 
> etc. That means that your controller uses a different naming scheme
> for the usart ports. Looking at the part description files: they are
> names UBBR0L, UBRR1L etc. You will have to use the drivers/usart_0.asm
> instead (or whatever your terminal is).
> 
> > After getting this to assemble, the next problem is getting it on a
> > device. As I said, I'd like to use a atmega644PA, but I only see
> > atmega644 and atmega644P in the devices directory. Can I use one of
> > them, and if so, which one?
> 
> None of them by default. You have to generate the proper files with
> the pd2amforth utility from the original Atmel Partdescription file.
> I've never tested it on windows however, it's a non-trivial perl
> script.
> 
> You may have success with the 644 hex files, I do not know whether
> the controllers are similiar enough..
> 
> Matthias

Re: [Amforth-devel] Help getting started with a atmeg644PA

[Leon N M. <leo...@gm...>]

Thanks for the information -- I'll give pd2amforth a try (in Linux).
-Leon 

>Friday 02 July 2010
>From: Matthias Trute <mt...@we...>
>Subject: Re: [Amforth-devel] Help getting started with a atmeg644PA
> Hi Leon,
> 
> > C:\Users\Leon\Desktop\amforth-4.0\core\drivers/usart.asm(2): warning:
> > Use of undefined or forward referenced symbol 'UBRRL' in .equ/.set
> 
> etc. That means that your controller uses a different naming scheme
> for the usart ports. Looking at the part description files: they are
> names UBBR0L, UBRR1L etc. You will have to use the drivers/usart_0.asm
> instead (or whatever your terminal is).
> 
> > After getting this to assemble, the next problem is getting it on a
> > device. As I said, I'd like to use a atmega644PA, but I only see
> > atmega644 and atmega644P in the devices directory. Can I use one of
> > them, and if so, which one?
> 
> None of them by default. You have to generate the proper files with
> the pd2amforth utility from the original Atmel Partdescription file.
> I've never tested it on windows however, it's a non-trivial perl
> script.
> 
> You may have success with the 644 hex files, I do not know whether
> the controllers are similiar enough..
> 
> Matthias

Re: [Amforth-devel] Help getting started with a atmeg644PA

[Leon N M. <leo...@gm...>]

Are you sure that 644PA means 644P Automotive?

The 644P is not recommended for new designs; they suggest the 644PA instead:

http://www.atmel.com/dyn/products/product_card.asp?part_id=3896

Furthermore, the 644PA and 644P Automotive have separate pages:

http://atmel.com/dyn/products/product_card.asp?part_id=4604
http://atmel.com/dyn/products/product_card.asp?PN=ATmega644P%20Automotive

Thanks.
-Leon

>Thursday 01 July 2010
>From: Andy Kirby <an...@ki...>
>Subject: Re: [Amforth-devel] Help getting started with a atmeg644PA
> Personaly i would go with the 644p (picopower 644) for the 644pa (644
> picopower, automotive grade)
> 
> grades for chips tend to be stuff like commercial, industrial, automotive,
> military. These normaly refer to how well the chip should survive lifes
> nastys like temperature ranges, radiation, vibration etc
> 
> so basicaly can be ignored by the average hobyist or commercial
> constructor. Go with the cheapest. (Military grade is normaly stupidly
> expensive).
> 
> Hope this helps.
> 
> Cheers
> 
> andy kirby

Re: [Amforth-devel] Help getting started with a atmeg644PA

[Matthias T. <mt...@we...>]

Hi Leon,


> C:\Users\Leon\Desktop\amforth-4.0\core\drivers/usart.asm(2): warning:
> Use of undefined or forward referenced symbol 'UBRRL' in .equ/.set

etc. That means that your controller uses a different naming scheme
for the usart ports. Looking at the part description files: they are
names UBBR0L, UBRR1L etc. You will have to use the drivers/usart_0.asm
instead (or whatever your terminal is).

> After getting this to assemble, the next problem is getting it on a
> device. As I said, I'd like to use a atmega644PA, but I only see
> atmega644 and atmega644P in the devices directory. Can I use one of
> them, and if so, which one?

None of them by default. You have to generate the proper files with
the pd2amforth utility from the original Atmel Partdescription file.
I've never tested it on windows however, it's a non-trivial perl
script.

You may have success with the 644 hex files, I do not know whether
the controllers are similiar enough..

Matthias

Re: [Amforth-devel] Help getting started with a atmeg644PA

[Andy K. <an...@ki...>]

Personaly i would go with the 644p (picopower 644) for the 644pa (644 picopower, automotive grade) 

grades for chips tend to be stuff like commercial, industrial, automotive, military. These normaly refer to how well the chip should survive lifes nastys like temperature ranges, radiation, vibration etc

so basicaly can be ignored by the average hobyist or commercial constructor. Go with the cheapest. (Military grade is normaly stupidly expensive).

Hope this helps.

Cheers

andy kirby 


-- 
Like a rolling stone
----- Original message -----
> Hello everyone,
> 
> I'm not sure if this it the right place to request help, but I don't
> see where else to do it, so I apologize if I'm asking in the wrong
> place.
> 
> As the subject suggests, I'm interested in getting amforth working on
> a atmega644PA chip. I've tried assembling amforth in Linux with avra,
> in Linux with wine/avrasm2, and in Windows with AVR Studio -- all
> without success.
> 
> Although the first two methods interest me more, perhaps we should
> start with the third, because there I was following instructions (from
> amforth-AVR-Studio.pdf -- are there instructions for the other two?) I
> get 10 errors and 2 warnings:
> 
> C:\Users\Leon\Desktop\amforth-4.0\core\drivers/usart.asm(2): warning:
> Use of undefined or forward referenced symbol 'UBRRL' in .equ/.set
> C:\Users\Leon\Desktop\amforth-4.0\core\drivers/usart.asm(3): warning:
> Use of undefined or forward referenced symbol 'UBRRH' in .equ/.set
> C:\Users\Leon\Desktop\amforth-4.0\core\drivers/usart.asm(4): warning:
> Use of undefined or forward referenced symbol 'UCSRC' in .equ/.set
> C:\Users\Leon\Desktop\amforth-4.0\core\drivers/usart.asm(5): warning:
> Use of undefined or forward referenced symbol 'UCSRB' in .equ/.set
> C:\Users\Leon\Desktop\amforth-4.0\core\drivers/usart.asm(6): warning:
> Use of undefined or forward referenced symbol 'UCSRA' in .equ/.set
> C:\Users\Leon\Desktop\amforth-4.0\core\drivers/usart.asm(7): warning:
> Use of undefined or forward referenced symbol 'UDR' in .equ/.set
> C:\Users\Leon\Desktop\amforth-4.0\core\drivers/usart.asm(8): warning:
> Use of undefined or forward referenced symbol 'RXC' in .equ/.set
> C:\Users\Leon\Desktop\amforth-4.0\core\drivers/usart.asm(9): warning:
> Use of undefined or forward referenced symbol 'UDRE' in .equ/.set
> C:\Users\Leon\Desktop\amforth-4.0\appl\HandHeldForth\template.asm(22):
> warning: Use of undefined or forward referenced symbol 'TXEN' in
> .equ/.set
> C:\Users\Leon\Desktop\amforth-4.0\appl\HandHeldForth\template.asm(23):
> warning: Use of undefined or forward referenced symbol 'UCSZ0' in
> .equ/.set
> C:\Users\Leon\Desktop\amforth-4.0\core\drivers/usart-isr-rx.asm(4):
> error: Use of undefined or forward referenced symbol 'URXCaddr' in
> .org
> C:\Users\Leon\Desktop\amforth-4.0\core\devices/atmega644p/device.asm(13):
> error: Overlap in .cseg: addr=0x1 conflicts with 0x0:0x2
> 
> Please let me know if I can provide any information that might help
> identify what I'm doing wrong.
> 
> After getting this to assemble, the next problem is getting it on a
> device. As I said, I'd like to use a atmega644PA, but I only see
> atmega644 and atmega644P in the devices directory. Can I use one of
> them, and if so, which one?
> 
> Thanks.
> -Leon
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Amforth-devel mailing list
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel

[Amforth-devel] Help getting started with a atmeg644PA

[Leon M. <leo...@gm...>]

Hello everyone,

I'm not sure if this it the right place to request help, but I don't
see where else to do it, so I apologize if I'm asking in the wrong
place.

As the subject suggests, I'm interested in getting amforth working on
a atmega644PA chip. I've tried assembling amforth in Linux with avra,
in Linux with wine/avrasm2, and in Windows with AVR Studio -- all
without success.

Although the first two methods interest me more, perhaps we should
start with the third, because there I was following instructions (from
amforth-AVR-Studio.pdf -- are there instructions for the other two?) I
get 10 errors and 2 warnings:

C:\Users\Leon\Desktop\amforth-4.0\core\drivers/usart.asm(2): warning:
Use of undefined or forward referenced symbol 'UBRRL' in .equ/.set
C:\Users\Leon\Desktop\amforth-4.0\core\drivers/usart.asm(3): warning:
Use of undefined or forward referenced symbol 'UBRRH' in .equ/.set
C:\Users\Leon\Desktop\amforth-4.0\core\drivers/usart.asm(4): warning:
Use of undefined or forward referenced symbol 'UCSRC' in .equ/.set
C:\Users\Leon\Desktop\amforth-4.0\core\drivers/usart.asm(5): warning:
Use of undefined or forward referenced symbol 'UCSRB' in .equ/.set
C:\Users\Leon\Desktop\amforth-4.0\core\drivers/usart.asm(6): warning:
Use of undefined or forward referenced symbol 'UCSRA' in .equ/.set
C:\Users\Leon\Desktop\amforth-4.0\core\drivers/usart.asm(7): warning:
Use of undefined or forward referenced symbol 'UDR' in .equ/.set
C:\Users\Leon\Desktop\amforth-4.0\core\drivers/usart.asm(8): warning:
Use of undefined or forward referenced symbol 'RXC' in .equ/.set
C:\Users\Leon\Desktop\amforth-4.0\core\drivers/usart.asm(9): warning:
Use of undefined or forward referenced symbol 'UDRE' in .equ/.set
C:\Users\Leon\Desktop\amforth-4.0\appl\HandHeldForth\template.asm(22):
warning: Use of undefined or forward referenced symbol 'TXEN' in
.equ/.set
C:\Users\Leon\Desktop\amforth-4.0\appl\HandHeldForth\template.asm(23):
warning: Use of undefined or forward referenced symbol 'UCSZ0' in
.equ/.set
C:\Users\Leon\Desktop\amforth-4.0\core\drivers/usart-isr-rx.asm(4):
error: Use of undefined or forward referenced symbol 'URXCaddr' in
.org
C:\Users\Leon\Desktop\amforth-4.0\core\devices/atmega644p/device.asm(13):
error: Overlap in .cseg: addr=0x1 conflicts with 0x0:0x2

Please let me know if I can provide any information that might help
identify what I'm doing wrong.

After getting this to assemble, the next problem is getting it on a
device. As I said, I'd like to use a atmega644PA, but I only see
atmega644 and atmega644P in the devices directory. Can I use one of
them, and if so, which one?

Thanks.
-Leon

Re: [Amforth-devel] Amforth on Arduino Nano V3.0, Notes, Hexfile

[<an...@ki...>]

If the files you are renaming are the ones I emailed over. I think it
may be problematic as they were for the 168 and you state below you have
a 328.

I will email over the 328 files named duemilanove.

Use the fuse settings for Duemilanove from the readme as well.

Cheers

Andy Kirby



On 01/07/10 20:51, avr feedback wrote:
> Thanks! Great, this is exiting!
> 
> What I have is a ATMega 328 and I'm using a ATAVR mkII in-system programmer.
> 
> To restore the bootloader I use these two lines(from Arduino IDE
> 0018.) It's not as easy as just renaming the hex file.
> That did not work. :) (I can se that i'm transmitting characters but
> nothing is coming back. Tried 9600,19200,38400 with screen and
> minicom.)
> 
> avrdude -c stk500v2 -p atmega328p -P usb -b 115200 -e -u -U
> lock:w:0x3f:m -U efuse:w:0x05:m -U hfuse:w:0xDA:m -U lfuse:w:0xFF:m
> avrdude -c stk500v2 -p atmega328p -P usb -b 115200 -U
> flash:w:ATmegaBOOT_168_atmega328.hex -U lock:w:0x0f:m
> 
> I can't figure out what to do with the eep-file. I feel lost. I guess
> I have to start from the beginning..
> 
> /mat
> 
> On Wed, Jun 30, 2010 at 11:19 PM, an...@ki...
> <an...@ki...> wrote:
>> It looks like a compressed Diecimila (atmega168) so the Diecimila build
>> should work OK.
>>
>>
>>
>>
>>
>> On 30/06/10 19:18, avr feedback wrote:
>>> Someone with a hexfile or installation notes for Arduino Nano V3.0?
>>> Will it work?
>>>
>>> http://www.arduino.cc/en/Main/ArduinoBoardNano
>>>
>>> ------------------------------------------------------------------------------
>>> This SF.net email is sponsored by Sprint
>>> What will you do first with EVO, the first 4G phone?
>>> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
>>> _______________________________________________
>>> Amforth-devel mailing list
>>> Amf...@li...
>>> https://lists.sourceforge.net/lists/listinfo/amforth-devel
>>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Sprint
>> What will you do first with EVO, the first 4G phone?
>> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
>> _______________________________________________
>> Amforth-devel mailing list
>> Amf...@li...
>> https://lists.sourceforge.net/lists/listinfo/amforth-devel
>>
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Amforth-devel mailing list
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel
> 

Re: [Amforth-devel] Amforth on Arduino Nano V3.0, Notes, Hexfile

[Erich W. <ew....@na...>]

Hi,

> I can't figure out what to do with the eep-file. I feel lost. I guess
> I have to start from the beginning..
>

The .eep.hex file is the content of the eeprom. It is absolutely neccessary
for amforth to operate.

I use this command via a make file

TARGET = main
MCU=atmega32
SP12=-c sp12 -i 10 -P /dev/parport0
BURNER=$(SP12)
AVRDUDE=avrdude
AVRDUDE_FLAGS=-q $(BURNER) -p $(MCU)

install: $(TARGET).hex
         $(AVRDUDE) $(AVRDUDE_FLAGS)  -e -U flash:w:$(TARGET).hex:i -U eeprom:w:$(TARGET).eep.hex:i


please adjust to your settings.

Have fun,
Erich

Re: [Amforth-devel] Amforth on Arduino Nano V3.0, Notes, Hexfile

[avr f. <avr...@gm...>]

Thanks! Great, this is exiting!

What I have is a ATMega 328 and I'm using a ATAVR mkII in-system programmer.

To restore the bootloader I use these two lines(from Arduino IDE
0018.) It's not as easy as just renaming the hex file.
That did not work. :) (I can se that i'm transmitting characters but
nothing is coming back. Tried 9600,19200,38400 with screen and
minicom.)

avrdude -c stk500v2 -p atmega328p -P usb -b 115200 -e -u -U
lock:w:0x3f:m -U efuse:w:0x05:m -U hfuse:w:0xDA:m -U lfuse:w:0xFF:m
avrdude -c stk500v2 -p atmega328p -P usb -b 115200 -U
flash:w:ATmegaBOOT_168_atmega328.hex -U lock:w:0x0f:m

I can't figure out what to do with the eep-file. I feel lost. I guess
I have to start from the beginning..

/mat

On Wed, Jun 30, 2010 at 11:19 PM, an...@ki...
<an...@ki...> wrote:
> It looks like a compressed Diecimila (atmega168) so the Diecimila build
> should work OK.
>
>
>
>
>
> On 30/06/10 19:18, avr feedback wrote:
>> Someone with a hexfile or installation notes for Arduino Nano V3.0?
>> Will it work?
>>
>> http://www.arduino.cc/en/Main/ArduinoBoardNano
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Sprint
>> What will you do first with EVO, the first 4G phone?
>> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
>> _______________________________________________
>> Amforth-devel mailing list
>> Amf...@li...
>> https://lists.sourceforge.net/lists/listinfo/amforth-devel
>>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Amforth-devel mailing list
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel
>

Re: [Amforth-devel] Amforth on Arduino Nano V3.0, Notes, Hexfile

[<an...@ki...>]

It looks like a compressed Diecimila (atmega168) so the Diecimila build
should work OK.





On 30/06/10 19:18, avr feedback wrote:
> Someone with a hexfile or installation notes for Arduino Nano V3.0?
> Will it work?
> 
> http://www.arduino.cc/en/Main/ArduinoBoardNano
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Amforth-devel mailing list
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel
> 

[Amforth-devel] Amforth on Arduino Nano V3.0, Notes, Hexfile

[avr f. <avr...@gm...>]

Someone with a hexfile or installation notes for Arduino Nano V3.0?
Will it work?

http://www.arduino.cc/en/Main/ArduinoBoardNano

Re: [Amforth-devel] Clone Word

[Matthias T. <mt...@we...>]

Hi Andy,

> Logicaly then I thought the easiest way to do cloning should be to use 
> the ISP peripheral to handle the serialization and low level protocols 
> rather then bit banging a port. But use a port to drive the target 
> devices reset line (like the debug LED port.)

I'm afraid that you cannot avoid doing the bit-banging youself.

The following projects that may serve
as an inspiration for you (atmega programs 
another atmega):

http://www.fourwalledcubicle.com/ButtLoad.php
http://www.arduino.cc/playground/Code/Programmer2

wrt to the schematics, sourceforge seem to drop your attachment,
I could place it on the web space and post a link to it. I'm still
not sure whether I should collect hardware descriptions like yours
for amforth. My current understanding is that amforth is pure
software on a very hardware centric level and I'm not a hardware guy at
all. ok, I find the hot end of a soldering iron, by pain ;=) 

HTH
Matthias

Re: [Amforth-devel] Enough for today

[Andy K. <an...@ki...>]

There are a lot of changes being done on trunk between releases. What you get at the point you down load may not be functional. Mathias tests before making releases though so these should be good.

Amforth is very dynamic at the moment.

-- 
Like a rolling stone
----- Original message -----
> Hi Andy,
> 
> I just upgraded to trunk and the duemilanove target fails to upload
> because the address range is too big:
> 
> [exec] avrdude: ERROR: address 0x8010 out of range at line 300 of
> duemilanove.hex
> 
> This happens with revision 883.
> 
> I also experienced hangs when I try to define colon words, once I
> reset the controller it seems hosed, i.e. numbers arent put on the
> stack but crash the atmega (or make it loop indefinitely)
> 
> What's your workflow when developing forth for these embedded
> devices?
> 
> HTH,
> 
> Christian

Re: [Amforth-devel] Enough for today

[Matthias T. <mt...@we...>]

Christian, 
> Hi Andy,
> 
> I just upgraded to trunk and the duemilanove target fails to upload
> because the address range is too big:
> 
> [exec] avrdude: ERROR: address 0x8010 out of range at line 300 of duemilanove.hex

This kind of error usually happens, when the dict_appl_core.inc contains
too much entries and goes beyond the flash limits. You will have to
place a few words into the dict_appl.inc file until it works. Note
however, that not all words can be moved around, esp not the one that
are included via dict_core.inc (without the appl suffix) and the istore
words.


> What's your workflow when developing forth for these embedded
> devices?

Trial and error until it works ;=) There are not that much
things that may cause the troubles: fuses, addresses and 
frequencies. If the hardware is ok....

Matthias