Re: [Amforth] Coolterm on the Mac

[Peter C. Hauser]

Jan,

By default CoolTerm starts up in the Raw mode, in which each character is sent 
as it is entered on the keyboard.   I presume when you hit the delete key it 
will be sent as a non-printable ASCII code. 

If you set CoolTerm to the Line mode (under Options / Terminal) you can then 
enter and edit individual lines before there are sent out.

Peter

> On 16 Oct 2018, at 20:21, Jan Kromhout  wrote:
> 
> Thanks Peter for the response.
> How do you have setup Coolterm?
> When I try to delete a character two dots are printed!
> 
> Thanks for any help.
> 
> Jan Kromhout
> Hellevoetsluis-NL
> 
> 
> ___
> Amforth-devel mailing list for http://amforth.sf.net/
> Amforth-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/amforth-devel



___
Amforth-devel mailing list for http://amforth.sf.net/
Amforth-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amforth-devel

Re: [Amforth] Setting of the fuses Arduino Ono

[Dimitri Georganas]

Default values I use are: lfuse = 0x62, hfuse = 0xDF, efuse = 0x01.
Highspeed mode: lfuse = 0xE2.

On Tue, Oct 16, 2018 at 10:01 PM John Verne  wrote:

> Oh, wait. My last response is just going to add to the confusion. Sorry
> about that.
>
> Are you sure you have the fuse settings right in your command line? Have
> you swapped efuse and lfuse by accident in that command line?
>
> I would expect efuse to be 0xFF, which is the default. 0x05 doesn't really
> make sense, but does set a brown-out detector level -- which is true for
> 0xFD as well.
>
> The hfuse at 0xD9 is the default, and can be the most dangerous to change.
> Consider this an expert setting.
>
> lfuse is the one we usually want to change (unless tweaking brownout
> detection or debugging). This is the one where we set clock speed and
> oscillator source and so on, and is the one I usually customize. This
> should not be 0xFF unless you want to run at 1MHz instead of 8MHz. This is
> the one that is usually at 0x05 or 0x62.
>
> Double check your Makefile or the command you are typing in, and make sure
> you have't swapped the efuse and lfuse values.
>
> On Tue, 16 Oct 2018 at 14:56, Jan Kromhout  wrote:
>
> > When loading AmForth into my Arduino Uno  I get an error on the end.
> > My question is what to do in that case?
> > Are my settings of the fuse one?
> >
> > Cheers,
> >
> > Jan
> >
> >
> > avrdude: verifying ...
> > avrdude: verification error, first mismatch at byte 0x
> >  0xfd != 0x05
> > avrdude: verification error; content mismatch
> >
> > avrdude: safemode: efuse changed! Was 5, and is now fd
> > Would you like this fuse to be changed back? [y/n] n
> > avrdude: safemode: Fuses OK (E:05, H:DE, L:FF)
> >
> > My question is what to do in that situation?
> >
> >
> >
> >
> >
> > MacBook-Pro-van-Jan-5:avrdude jankromhout$ avrdude -P
> > /dev/tty.usbmodem00230362 -c avrispv2 -b 19200 -p m328p -e -U
> > flash:w:uno.hex:i -U eeprom:w:uno.eep.hex:i -U efuse:w:0x05:m -U
> > hfuse:w:0xD9:m -U lfuse:w:0xFF:m
> >
> > avrdude: AVR device initialized and ready to accept instructions
> >
> > Reading | ## | 100% 0.00s
> >
> > avrdude: Device signature = 0x1e950f (probably m328p)
> > avrdude: erasing chip
> > avrdude: reading input file "uno.hex"
> > avrdude: writing flash (32638 bytes):
> >
> > Writing | ## | 100% 2.06s
> >
> > avrdude: 32638 bytes of flash written
> > avrdude: verifying flash memory against uno.hex:
> > avrdude: load data flash data from input file uno.hex:
> > avrdude: input file uno.hex contains 32638 bytes
> > avrdude: reading on-chip flash data:
> >
> > Reading | ## | 100% 1.86s
> >
> > avrdude: verifying ...
> > avrdude: 32638 bytes of flash verified
> > avrdude: reading input file "uno.eep.hex"
> > avrdude: writing eeprom (144 bytes):
> >
> > Writing | ## | 100% 0.06s
> >
> > avrdude: 144 bytes of eeprom written
> > avrdude: verifying eeprom memory against uno.eep.hex:
> > avrdude: load data eeprom data from input file uno.eep.hex:
> > avrdude: input file uno.eep.hex contains 144 bytes
> > avrdude: reading on-chip eeprom data:
> >
> > Reading | ## | 100% 0.02s
> >
> > avrdude: verifying ...
> > avrdude: 144 bytes of eeprom verified
> > avrdude: reading input file "0x05"
> > avrdude: writing efuse (1 bytes):
> >
> > Writing | ## | 100% 0.01s
> >
> > avrdude: 1 bytes of efuse written
> > avrdude: verifying efuse memory against 0x05:
> > avrdude: load data efuse data from input file 0x05:
> > avrdude: input file 0x05 contains 1 bytes
> > avrdude: reading on-chip efuse data:
> >
> > Reading | ## | 100% 0.00s
> >
> > avrdude: verifying ...
> > avrdude: verification error, first mismatch at byte 0x
> >  0xfd != 0x05
> > avrdude: verification error; content mismatch
> >
> > avrdude: safemode: efuse changed! Was 5, and is now fd
> > Would you like this fuse to be changed back? [y/n] n
> > avrdude: safemode: Fuses OK (E:05, H:DE, L:FF)
> >
> > avrdude done.  Thank you.
> >
> > MacBook-Pro-van-Jan-5:avrdude jankromhout$
> >
> > ___
> > Amforth-devel mailing list for http://amforth.sf.net/
> > Amforth-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/amforth-devel
> >
>
>
> --
>
>
> [image: --]
>
> John Verne
> [image: https://]about.me/jverne
> 
>
> ___
> Amforth-devel mailing list for http://amforth.sf.net/
> Amforth-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/amforth-devel
>

___
Amforth-devel mailing list for http://amforth.sf.net/

Re: [Amforth] Setting of the fuses Arduino Ono

[John Verne]

Oh, wait. My last response is just going to add to the confusion. Sorry
about that.

Are you sure you have the fuse settings right in your command line? Have
you swapped efuse and lfuse by accident in that command line?

I would expect efuse to be 0xFF, which is the default. 0x05 doesn't really
make sense, but does set a brown-out detector level -- which is true for
0xFD as well.

The hfuse at 0xD9 is the default, and can be the most dangerous to change.
Consider this an expert setting.

lfuse is the one we usually want to change (unless tweaking brownout
detection or debugging). This is the one where we set clock speed and
oscillator source and so on, and is the one I usually customize. This
should not be 0xFF unless you want to run at 1MHz instead of 8MHz. This is
the one that is usually at 0x05 or 0x62.

Double check your Makefile or the command you are typing in, and make sure
you have't swapped the efuse and lfuse values.

On Tue, 16 Oct 2018 at 14:56, Jan Kromhout  wrote:

> When loading AmForth into my Arduino Uno  I get an error on the end.
> My question is what to do in that case?
> Are my settings of the fuse one?
>
> Cheers,
>
> Jan
>
>
> avrdude: verifying ...
> avrdude: verification error, first mismatch at byte 0x
>  0xfd != 0x05
> avrdude: verification error; content mismatch
>
> avrdude: safemode: efuse changed! Was 5, and is now fd
> Would you like this fuse to be changed back? [y/n] n
> avrdude: safemode: Fuses OK (E:05, H:DE, L:FF)
>
> My question is what to do in that situation?
>
>
>
>
>
> MacBook-Pro-van-Jan-5:avrdude jankromhout$ avrdude -P
> /dev/tty.usbmodem00230362 -c avrispv2 -b 19200 -p m328p -e -U
> flash:w:uno.hex:i -U eeprom:w:uno.eep.hex:i -U efuse:w:0x05:m -U
> hfuse:w:0xD9:m -U lfuse:w:0xFF:m
>
> avrdude: AVR device initialized and ready to accept instructions
>
> Reading | ## | 100% 0.00s
>
> avrdude: Device signature = 0x1e950f (probably m328p)
> avrdude: erasing chip
> avrdude: reading input file "uno.hex"
> avrdude: writing flash (32638 bytes):
>
> Writing | ## | 100% 2.06s
>
> avrdude: 32638 bytes of flash written
> avrdude: verifying flash memory against uno.hex:
> avrdude: load data flash data from input file uno.hex:
> avrdude: input file uno.hex contains 32638 bytes
> avrdude: reading on-chip flash data:
>
> Reading | ## | 100% 1.86s
>
> avrdude: verifying ...
> avrdude: 32638 bytes of flash verified
> avrdude: reading input file "uno.eep.hex"
> avrdude: writing eeprom (144 bytes):
>
> Writing | ## | 100% 0.06s
>
> avrdude: 144 bytes of eeprom written
> avrdude: verifying eeprom memory against uno.eep.hex:
> avrdude: load data eeprom data from input file uno.eep.hex:
> avrdude: input file uno.eep.hex contains 144 bytes
> avrdude: reading on-chip eeprom data:
>
> Reading | ## | 100% 0.02s
>
> avrdude: verifying ...
> avrdude: 144 bytes of eeprom verified
> avrdude: reading input file "0x05"
> avrdude: writing efuse (1 bytes):
>
> Writing | ## | 100% 0.01s
>
> avrdude: 1 bytes of efuse written
> avrdude: verifying efuse memory against 0x05:
> avrdude: load data efuse data from input file 0x05:
> avrdude: input file 0x05 contains 1 bytes
> avrdude: reading on-chip efuse data:
>
> Reading | ## | 100% 0.00s
>
> avrdude: verifying ...
> avrdude: verification error, first mismatch at byte 0x
>  0xfd != 0x05
> avrdude: verification error; content mismatch
>
> avrdude: safemode: efuse changed! Was 5, and is now fd
> Would you like this fuse to be changed back? [y/n] n
> avrdude: safemode: Fuses OK (E:05, H:DE, L:FF)
>
> avrdude done.  Thank you.
>
> MacBook-Pro-van-Jan-5:avrdude jankromhout$
>
> ___
> Amforth-devel mailing list for http://amforth.sf.net/
> Amforth-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/amforth-devel
>


-- 


[image: --]

John Verne
[image: https://]about.me/jverne


___
Amforth-devel mailing list for http://amforth.sf.net/
Amforth-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amforth-devel

Re: [Amforth] Setting of the fuses Arduino Ono

[John Verne]

It is warning you that you are changing the low fuse settings. This is
because changing fuses can permanently damage the chip.

 In this case it looks like the existing fuse settings are CKSEL1 only, but
your AVRDude command wants to set 0x05, which enables a bunch of fuses.

You should be ok setting them to factory defaults. I don't have my Makefile
handy, but I think I use 0x62 or 0x05, which is suitable for any bootloader
(and thus suitable for AMForth.)

Here is a good reference:
https://www.instructables.com/id/How-to-change-fuse-bits-of-AVR-Atmega328p-8bit-mic/

There are online tools to generate fuse values:
http://www.engbedded.com/fusecalc

Every time I run into this I have to recheck my notes, which is why I save
the values in the Makefile. I've yet to blow up a 328P with fuses, but I
suppose it can be done. I'll respond with my Makefile snippet and rationale
later if it looks like it will help.

On Tue, Oct 16, 2018, 14:56 Jan Kromhout  wrote:

> When loading AmForth into my Arduino Uno  I get an error on the end.
> My question is what to do in that case?
> Are my settings of the fuse one?
>
> Cheers,
>
> Jan
>
>
> avrdude: verifying ...
> avrdude: verification error, first mismatch at byte 0x
>  0xfd != 0x05
> avrdude: verification error; content mismatch
>
> avrdude: safemode: efuse changed! Was 5, and is now fd
> Would you like this fuse to be changed back? [y/n] n
> avrdude: safemode: Fuses OK (E:05, H:DE, L:FF)
>
> My question is what to do in that situation?
>
>
>
>
>
> MacBook-Pro-van-Jan-5:avrdude jankromhout$ avrdude -P
> /dev/tty.usbmodem00230362 -c avrispv2 -b 19200 -p m328p -e -U
> flash:w:uno.hex:i -U eeprom:w:uno.eep.hex:i -U efuse:w:0x05:m -U
> hfuse:w:0xD9:m -U lfuse:w:0xFF:m
>
> avrdude: AVR device initialized and ready to accept instructions
>
> Reading | ## | 100% 0.00s
>
> avrdude: Device signature = 0x1e950f (probably m328p)
> avrdude: erasing chip
> avrdude: reading input file "uno.hex"
> avrdude: writing flash (32638 bytes):
>
> Writing | ## | 100% 2.06s
>
> avrdude: 32638 bytes of flash written
> avrdude: verifying flash memory against uno.hex:
> avrdude: load data flash data from input file uno.hex:
> avrdude: input file uno.hex contains 32638 bytes
> avrdude: reading on-chip flash data:
>
> Reading | ## | 100% 1.86s
>
> avrdude: verifying ...
> avrdude: 32638 bytes of flash verified
> avrdude: reading input file "uno.eep.hex"
> avrdude: writing eeprom (144 bytes):
>
> Writing | ## | 100% 0.06s
>
> avrdude: 144 bytes of eeprom written
> avrdude: verifying eeprom memory against uno.eep.hex:
> avrdude: load data eeprom data from input file uno.eep.hex:
> avrdude: input file uno.eep.hex contains 144 bytes
> avrdude: reading on-chip eeprom data:
>
> Reading | ## | 100% 0.02s
>
> avrdude: verifying ...
> avrdude: 144 bytes of eeprom verified
> avrdude: reading input file "0x05"
> avrdude: writing efuse (1 bytes):
>
> Writing | ## | 100% 0.01s
>
> avrdude: 1 bytes of efuse written
> avrdude: verifying efuse memory against 0x05:
> avrdude: load data efuse data from input file 0x05:
> avrdude: input file 0x05 contains 1 bytes
> avrdude: reading on-chip efuse data:
>
> Reading | ## | 100% 0.00s
>
> avrdude: verifying ...
> avrdude: verification error, first mismatch at byte 0x
>  0xfd != 0x05
> avrdude: verification error; content mismatch
>
> avrdude: safemode: efuse changed! Was 5, and is now fd
> Would you like this fuse to be changed back? [y/n] n
> avrdude: safemode: Fuses OK (E:05, H:DE, L:FF)
>
> avrdude done.  Thank you.
>
> MacBook-Pro-van-Jan-5:avrdude jankromhout$
>
> ___
> Amforth-devel mailing list for http://amforth.sf.net/
> Amforth-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/amforth-devel
>

___
Amforth-devel mailing list for http://amforth.sf.net/
Amforth-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amforth-devel

[Amforth] Setting of the fuses Arduino Ono

[Jan Kromhout]

When loading AmForth into my Arduino Uno  I get an error on the end.
My question is what to do in that case?
Are my settings of the fuse one?

Cheers,

Jan


avrdude: verifying ...
avrdude: verification error, first mismatch at byte 0x
 0xfd != 0x05
avrdude: verification error; content mismatch

avrdude: safemode: efuse changed! Was 5, and is now fd
Would you like this fuse to be changed back? [y/n] n
avrdude: safemode: Fuses OK (E:05, H:DE, L:FF)

My question is what to do in that situation?





MacBook-Pro-van-Jan-5:avrdude jankromhout$ avrdude -P /dev/tty.usbmodem00230362 
-c avrispv2 -b 19200 -p m328p -e -U flash:w:uno.hex:i -U eeprom:w:uno.eep.hex:i 
-U efuse:w:0x05:m -U hfuse:w:0xD9:m -U lfuse:w:0xFF:m

avrdude: AVR device initialized and ready to accept instructions

Reading | ## | 100% 0.00s

avrdude: Device signature = 0x1e950f (probably m328p)
avrdude: erasing chip
avrdude: reading input file "uno.hex"
avrdude: writing flash (32638 bytes):

Writing | ## | 100% 2.06s

avrdude: 32638 bytes of flash written
avrdude: verifying flash memory against uno.hex:
avrdude: load data flash data from input file uno.hex:
avrdude: input file uno.hex contains 32638 bytes
avrdude: reading on-chip flash data:

Reading | ## | 100% 1.86s

avrdude: verifying ...
avrdude: 32638 bytes of flash verified
avrdude: reading input file "uno.eep.hex"
avrdude: writing eeprom (144 bytes):

Writing | ## | 100% 0.06s

avrdude: 144 bytes of eeprom written
avrdude: verifying eeprom memory against uno.eep.hex:
avrdude: load data eeprom data from input file uno.eep.hex:
avrdude: input file uno.eep.hex contains 144 bytes
avrdude: reading on-chip eeprom data:

Reading | ## | 100% 0.02s

avrdude: verifying ...
avrdude: 144 bytes of eeprom verified
avrdude: reading input file "0x05"
avrdude: writing efuse (1 bytes):

Writing | ## | 100% 0.01s

avrdude: 1 bytes of efuse written
avrdude: verifying efuse memory against 0x05:
avrdude: load data efuse data from input file 0x05:
avrdude: input file 0x05 contains 1 bytes
avrdude: reading on-chip efuse data:

Reading | ## | 100% 0.00s

avrdude: verifying ...
avrdude: verification error, first mismatch at byte 0x
 0xfd != 0x05
avrdude: verification error; content mismatch

avrdude: safemode: efuse changed! Was 5, and is now fd
Would you like this fuse to be changed back? [y/n] n
avrdude: safemode: Fuses OK (E:05, H:DE, L:FF)

avrdude done.  Thank you.

MacBook-Pro-van-Jan-5:avrdude jankromhout$

___
Amforth-devel mailing list for http://amforth.sf.net/
Amforth-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amforth-devel

[Amforth] Coolterm on the Mac

[Jan Kromhout]

Thanks Peter for the response.
How do you have setup Coolterm?
When I try to delete a character two dots are printed!

Thanks for any help.

Jan Kromhout
Hellevoetsluis-NL


___
Amforth-devel mailing list for http://amforth.sf.net/
Amforth-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amforth-devel

Re: [Amforth] How to download complete set of data from source forge.net

[Tristan Williams]

Hello Jan,

If you are happy to have version 6.7 rather than most recent sources
(see http://amforth.sourceforge.net/ below Work In Progress for more
information ) then using this link is probably the easiest way.

https://sourceforge.net/projects/amforth/files/amforth/6.7/

Then click on an archive link. If you are using OS X then I would choose
amforth-6.7.tar.gz as OS X knows what to do with this file type. On my
system double-clicking on it will expand it to a folder - and the
AmForth directory tree will be below the amforth-6.7 folder.

Kind regards,

Tristan


On 16Oct18 10:03, Jan Kromhout via Amforth-devel wrote:
> Hello,
> 
> In https://sourceforge.net/p/amforth/code/HEAD/tree/releases/ 
>  I found the release 6.7.
> How can I complete download this in one to my computer?
> 
> Thanks for any help.
> 
> Jan Kromhout
> Hellevoetsluis-NL
> ___
> Amforth-devel mailing list for http://amforth.sf.net/
> Amforth-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/amforth-devel
> 


___
Amforth-devel mailing list for http://amforth.sf.net/
Amforth-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amforth-devel

[Amforth] How to download complete set of data from source forge.net

[Jan Kromhout via Amforth-devel]

Hello,

In https://sourceforge.net/p/amforth/code/HEAD/tree/releases/ 
 I found the release 6.7.
How can I complete download this in one to my computer?

Thanks for any help.

Jan Kromhout
Hellevoetsluis-NL
___
Amforth-devel mailing list for http://amforth.sf.net/
Amforth-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amforth-devel