avr-chat
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [avr-chat] Mac OS X, mkII, avrdude, to program fuse bytes on mega128


From: Ned Konz
Subject: Re: [avr-chat] Mac OS X, mkII, avrdude, to program fuse bytes on mega128?
Date: Sat, 11 Feb 2006 19:09:26 -0800


On Feb 11, 2006, at 12:45 PM, Rick Mann wrote:

Is anyone successfully using Mac OS X, a JTAGICE mkII, and avrdude to program fuse bits on an (unprogrammed) ATmega128? I've successfully used the JTAGICE with an ATmega32 that had previously had its fuse bits set with AVRISP and uisp, but I seem to be having trouble with this.

In this case, I try this:

$ avrdude -P /dev/tty.KeySerial1 -c jtagmkII -p m128 -u -U hfuse:w: 0x81:m

But it just hangs there. I can't interrupt it with ctrl-C, but I can suspend it with ctrl-Z. I can't kill it; I have to unplug the KeySpan serial adapter.

Any suggestions would be most appreciated. Thanks!

Works for me in both avarice (v2.4, from CVS) and avrdude (v5.0):

neds_mini:~ ned$ avarice --mkII -r -j /dev/cu.usbserial-FTB5PNU8
AVaRICE version 2.4, Feb  3 2006 16:31:49

Defaulting JTAG bitrate to 1 MHz. Make sure that the target
frequency is at least 4 MHz or you will likely encounter failures
controlling the target.

JTAG config starting.
Found a device: JTAGICEmkII
Serial number:  00:a0:00:00:33:a6
Reported JTAG device ID: 0x9702
Configured for device ID: 0x9702 atmega128
JTAG config complete.

Reading Fuse Bytes:
  Extended Fuse byte -> 0xff
      High Fuse byte -> 0x19
       Low Fuse byte -> 0xcf


neds_mini:~ ned$ avarice --mkII -j /dev/cu.usbserial-FTB5PNU8 -W ff19cf
AVaRICE version 2.4, Feb  3 2006 16:31:49

Defaulting JTAG bitrate to 1 MHz. Make sure that the target
frequency is at least 4 MHz or you will likely encounter failures
controlling the target.

JTAG config starting.
Found a device: JTAGICEmkII
Serial number:  00:a0:00:00:33:a6
Reported JTAG device ID: 0x9702
Configured for device ID: 0x9702 atmega128
JTAG config complete.

Writing Fuse Bytes:
  Extended Fuse byte -> 0xff
      High Fuse byte -> 0x19
       Low Fuse byte -> 0xcf


neds_mini:~ ned$ avrdude -P /dev/cu.usbserial-FTB5PNU8 -c jtagmkII -p m128 -u -U hfuse:w:0x19:m

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.22s

avrdude: Device signature = 0x1e9702
avrdude: reading input file "0x19"
avrdude: writing hfuse (1 bytes):

Writing | ################################################## | 100% 0.18s

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

Reading | ################################################## | 100% 0.03s

avrdude: verifying ...
avrdude: 1 bytes of hfuse verified

avrdude done.  Thank you.


(and it reads back as 0x19 with avarice and avrdude).

$ avrdude -P /dev/cu.usbserial-FTB5PNU8 -c jtagmkII -p m128 -u -U hfuse:r:-:r | xxd

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.24s

avrdude: Device signature = 0x1e9702
avrdude: reading hfuse memory:

Reading | ################################################## | 100% 0.20s

avrdude: writing output file "<stdout>"

avrdude done.  Thank you.

0000000: 19                                       .

--
Ned Konz
address@hidden







reply via email to

[Prev in Thread] Current Thread [Next in Thread]