azzazello / mega-isp Goto Github PK

I thought I had a problem with avrdude.conf but it appears it might be trouble 
with the arduino code. Have a look at 
https://savannah.nongnu.org/bugs/index.php?30844

Thanks,

Mat

What steps will reproduce the problem?
1. Connect attiny45
2. Compile and burn test program using avrdude


What is the expected output? What do you see instead?
I expected the program to burn and verify successfully (as it does with
other chips like the attiny13 and attiny2313).

Instead avrdude complains that there is a verification error at offset 0x00.

When dumping the flash from avrdude, I notice that the only byte that is
incorrect is the first byte.

In the case of the attiny45, it seems like the correct byte (19 in this
case) is being bit-masked by 0x11

I am also having the same issue with atmega48s (except the bit-mask is 0x25).

I have tested my setup successfully with several attiny13 & 2313's.

I have also tried multiple attiny45's and atmega48's.

turning on -v -v -v -v on avrdude, i notice that avrdude is sending the
correct bytes

What version of the product are you using? On what operating system?


Please provide any additional information below.

I started a thread 
http://forum.arduino.cc/index.php?topic=174857.msg1297970#msg1297970 to see if 
others have the same problem.
Steps to reproduce the problem
1. build latest avrdude http://www.nongnu.org/avrdude/
2. install mega-isp onto a SainSmart MEGA 2560 board
3. test connection using Serial Monitor ("1 ") produces the expected result
4. attempt to sync with avrdude - avrdude -b 9600 -c arduino -p m644p -t -vvvv 
-P /dev/ttyACM0

Expected output?
I expect to see avrdude: ser_recv() with some content indicating that the 
sketch has responded to the "0 " message.

Actual output?
         Using Port                    : /dev/ttyACM0
         Using Programmer              : arduino
         Overriding Baud Rate          : 9600
avrdude: Send: 0 [30]   [20] 
avrdude: Send: 0 [30]   [20] 
avrdude: Send: 0 [30]   [20] 
avrdude: ser_recv(): programmer is not responding
avrdude: stk500_recv(): programmer is not responding

avrdude done.  Thank you.

avrdude Version 5.11svn-20111019
Running on Ubuntu 13.04
ArduinoISP-master downloaded from https://github.com/rsbohn/arduinoisp

What steps will reproduce the problem?
1. Install AvrISP on an Arduino Mega
2. Connect wires per the instructions
3. Attempt to program another Arduino

What is the expected output? What do you see instead?

expected: 
4. Programing using the Mega as an AVRISP works.

actual:
4. programming fails.

Problem is as described here:
http://www.arduino.cc/cgi-bin/yabb2/YaBB.pl?num=1287885315/8

--------------------
Steps to dupe:
--------------------
1. Using Arduino-0016, program Arduino Duemilanove (Duey) with mega-isp.

2. Hook Duey to Attiny85 (Tiny):
   Duey   Tiny
   13     pin7 (PB2 / SCK)
   12     pin6 (PB1 / MISO)
   11     pin5 (PB0 / MOSI)
   10     pin1 (PB5 / Reset)

3. Power Tiny with 5V (independent of Duey)
   0V     pin4
   5V     pin8

4. Compile and program Tiny:
avr-gcc -mmcu=attiny85 -Wall -I./ -o myblinky.out matt.c
avr-objcopy -j .text -O ihex myblinky.out myblinky.hex
avrdude -p t85 -c avrisp -b19200 -P /dev/ttyUSB0 

avrdude: please define PAGEL and BS2 signals in the configuration file for
part ATtiny85
avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.13s

avrdude: Device signature = 0x1e930b

avrdude: safemode: Fuses OK

avrdude done.  Thank you.

5. Disconnect Duey from Tiny.  Connect reset to VCC.

--------------------
Expected output
--------------------
I expect 5V on Tiny's PB4 (pin 3) or PB3 (pin 2).

--------------------
Actual output
--------------------
Tiny:
4.9V  pin1 PB5 (reset)
0.4V  pin2 PB3
0.3V  pin3 PB4
0.0V  pin4 GND
0.4V  pin5 PB0 (MOSI)
0.4V  pin6 PB1 (MISO)
0.4V  pin7 PB2 (SCK)
4.9V  pin8 VCC

Duey:
pin7 (heartbeat)   LED slowly pulsing
pin8 (error)       LED never comes on
pin9 (programming) LED on while programming, now off

--------------------
Other info
--------------------
Ubuntu 9.04

$ avrdude -v
avrdude: Version 5.5, compiled on Jan 28 2009 at 10:40:52

Here's the fuse data:
$ cat efuse.dat 
0b11111111
$ cat hfuse.dat 
0b11011111
$ cat lfuse.dat 
0b1100010

This is the first AVR I've ever tried to program.  I'm guessing I'm making
a newbie mistake.  And if I need to be directed to a different forum,
please tell me.

--------------------
matt.c
--------------------
/* Gets the avr library from /usr/lib/avr/include on my machine */
#include <avr/io.h>

int main (void) {
    /* PB4/PB3 are not used when programming */
    DDRB = _BV(PB4) | _BV(PB3);

    while (1) {
        /* PB4 = 1, PB3 = 0 */
        PORTB = _BV(PB4);
    }
}

I appreciate you to make this program 
but I have some problem in compile

When I compile avrisp in Arduino an error occurs like this
  In function 'int avrisp()':
  error: jump to case label

and the curser pointed this line
  case 0x61: //STK_PROG_DATA   

Is there any setting? 

I'm Arduino beginner and I don't know about C or JAVA, assembly

I using arduino on windowsXP and I want to burn arduino bootloader.

Can I burn arduino bootloader with this avrisp?

Simple fix, the pin numbers for the leds are hard-coded in setup(). They should 
be changed to 
used the pin definitions above so that it is possible to use different pin 
assignments.

Change:
void setup() {
  // 19200?
  Serial.begin(19200);
  pinMode(7, OUTPUT);
  pulse(7, 2);
  pinMode(8, OUTPUT);
  pulse(8, 2);
  pinMode(9, OUTPUT);
  pulse(9, 2);
}

To:
void setup() {
  // 19200?
  Serial.begin(19200);
  pinMode(LED_HB, OUTPUT);
  pulse(LED_HB, 2);
  pinMode(LED_ERR, OUTPUT);
  pulse(LED_ERR, 2);
  pinMode(LED_PMODE, OUTPUT);
  pulse(LED_PMODE, 2);
}

Would it be possible to add an explicit license file to the releases?

This project has some very useful tools and is being redistributed in 
Debian/Ubuntu. Those distributions would like to be clear with regards to 
copyright ownership and licensing.

The license appears to be:
http://www.opensource.org/licenses/bsd-license.php

What steps will reproduce the problem?
1. Load mega-isp from arduino 
2. Leave alone for hours/days
3. Come back an try to run

What is the expected output? What do you see instead?
Expect this:
justin@justin-laptop:~/avr/Bikelight$ make
/usr/bin/avrdude -p m168 -c avrisp -b 19200 -P /dev/ttyUSB0 -U
flash:w:Bikelight.hex -U lfuse:w:0xE2:m -U hfuse:w:0xDF:m

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.11s

avrdude: Device signature = 0x1e9406
avrdude: NOTE: FLASH memory has been specified, an erase cycle will be
performed
         To disable this feature, specify the -D option.
avrdude: erasing chip
avrdude: reading input file "Bikelight.hex"
avrdude: input file Bikelight.hex auto detected as Intel Hex
avrdude: writing flash (1076 bytes):

Writing | ################################################## | 100% 1.33s

avrdude: 1076 bytes of flash written
avrdude: verifying flash memory against Bikelight.hex:
avrdude: load data flash data from input file Bikelight.hex:
avrdude: input file Bikelight.hex auto detected as Intel Hex
avrdude: input file Bikelight.hex contains 1076 bytes
avrdude: reading on-chip flash data:

Reading | ################################################## | 100% 1.28s

avrdude: verifying ...
avrdude: 1076 bytes of flash verified
avrdude: reading input file "0xE2"
avrdude: writing lfuse (1 bytes):

Writing | ################################################## | 100% 0.05s

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

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

avrdude: verifying ...
avrdude: 1 bytes of lfuse verified
avrdude: reading input file "0xDF"
avrdude: writing hfuse (1 bytes):

Writing | ################################################## | 100% 0.05s

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

Reading | ################################################## | 100% 0.05s

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

avrdude: safemode: Fuses OK

avrdude done.  Thank you.


get this:
justin@justin-laptop:~/avr/Bikelight$ make
/usr/bin/avrdude -p m168 -c avrisp -b 19200 -P /dev/ttyUSB0 -U
flash:w:Bikelight.hex -U lfuse:w:0xE2:m -U hfuse:w:0xDF:m

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.05s

avrdude: Device signature = 0x000000
avrdude: Yikes!  Invalid device signature.
         Double check connections and try again, or use -F to override
         this check.


avrdude done.  Thank you.

make: *** [program] Error 1

The problem is fixed by a reload from arduino

What version of the product are you using? On what operating system?
arduino: 0010
mega-isp: 03
ubuntu linux: feisty-fawn

Please provide any additional information below.

What steps will reproduce the problem?
1. Flash with avrdude and the -D option to not erase before
2. during verify an error of compare appear

What is the expected output? What do you see instead?
Using -D option is not affecting the result

Just tried writing the EEPROM from the command line. Failed! Target is a
Tiny2313 chip.

What steps will reproduce the problem?
1. Create a .eep file using avrasm2.exe (just put some .db stuff in .eseg)
2. avrdude ... -U:eeprom:w:test.eep
3. Seems to write to eeprom but fails validation step.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

The AVR ISP documentation...
http://www.atmel.com/dyn/resources/prod_documents/doc0943.pdf

...states that... "SCK ... Immediately after the Reset goes active, this pin 
will be driven to zero by the programmer."

The opposite is performed in start_pmode...

  // RESET ---not--- active
  pinMode(RESET, OUTPUT);
  digitalWrite(RESET, HIGH);

  // SCK driven low
  pinMode(SCK, OUTPUT);
  digitalWrite(SCK, LOW);

  delay(50);

  // RESET active
  digitalWrite(RESET, LOW);

  delay(50);

If the target is driving SCK high when start_pmode is entered, this code 
creates a short-circuit for 50 ms.  More than enough time to damage both 
processors.

http://code.google.com/p/mega-isp/source/browse/trunk/avrisp/ArduinoISP.pde#241

What steps will reproduce the problem?
1. Write & read flash on a ATMega64 that have 2Kb of eeprom 

What is the expected output? What do you see instead?
Can you read& write all of the eeprom memory


Please provide any additional information below.

The bug is the start in the write_eeprom & read_eeprom subs
here was multiply for 2!!!

int start = here; // * 2; // BUG!!!

What steps will reproduce the problem?
1. connect atmega168 to arduino, noted that directions in comments at
beginning of avrisp.pde code seem to be incorrect (miso/mosi inverted). i
used the following instead:

arduino pin 7 - "communicating" led
arduino pin 8 - "error" led
arduino pin 9 - "heartbeat" led
arduino pin 10 - atmega pin 1 "reset"
arduino pin 11 - atmega pin 17 "mosi"
arduino pin 12 - atmega pin 18 "miso"
arduino pin 13 - atmega pin 19 "sck"


2. upload avrisp.pde into arduino diecimila, i can see heartbeat led fading
on/off. quit arduino environment.
3. enter command from within hardware/tools/avr/bin directory of
arduino-011 directory: ./avrdude -C ../etc/avrdude.conf -p m168 -c avrisp
-b 19200 -P /dev/tty.usbserial-A4001lXM -U flash:w:Blink.hex -U
lfuse:w:0xE2:m -U hfuse:w:0xDF:m 

What is the expected output? What do you see instead?
expected to burn "blink" program to atmega168.
instead:
- heartbeat went off 
- "communicating" led did not light up.
- after a while, "error" led started flashing.
- avrdude gives error messages, see below. program is not uploaded.

What version of the product are you using? On what operating system?
Mac OS X 10.4.11, Arduino Diecimila, Arduino environment v.11

Please provide any additional information below.

Although avrdude appeared to upload and verify the program hex file, it is
not so, since the same output happens whether or not the target atmega is
even connected to the programming lines.

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.11s

avrdude: Device signature = 0x1e9406
avrdude: NOTE: FLASH memory has been specified, an erase cycle will be
performed
         To disable this feature, specify the -D option.
avrdude: erasing chip
avrdude: reading input file "Blink.hex"
avrdude: input file Blink.hex auto detected as Intel Hex
avrdude: writing flash (1094 bytes):

Writing | ################################################## | 100% 1.00s

avrdude: 1094 bytes of flash written
avrdude: verifying flash memory against Blink.hex:
avrdude: load data flash data from input file Blink.hex:
avrdude: input file Blink.hex auto detected as Intel Hex
avrdude: input file Blink.hex contains 1094 bytes
avrdude: reading on-chip flash data:

Reading | ################################################## | 100% 0.85s

avrdude: verifying ...
avrdude: 1094 bytes of flash verified
avrdude: reading input file "0xE2"
avrdude: writing lfuse (1 bytes):

Writing |                                                    | 0% 0.00s
***failed;  
Writing | ################################################## | 100% 0.26s

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

Reading | ################################################## | 100% 0.01s

avrdude: verifying ...
avrdude: verification error, first mismatch at byte 0x0000
         0xe2 != 0x00
avrdude: verification error; content mismatch

avrdude: safemode: lfuse changed! Was e2, and is now 0
Would you like this fuse to be changed back? [y/n] 
avrdude: safemode: Fuses OK
avrdude: stk500_recv(): programmer is not responding 

What steps will reproduce the problem?
1. Rebuild mega-isp shield on breadboard
2. Connect this shield to Arduino Duemilanove and ATtiny2313
3. Connect to Linux-PC (Ubuntu 11.04)
4. Flash hex using avrdude

What is the expected output? What do you see instead?

Heartbeat blinks.
avrdude -c avrisp -P /dev/ttyUSB0  -p t2313 -b 57600 -U flash:w:myprog.hex:i

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.01s

avrdude: Device signature = 0x1e950f
avrdude: Expected signature for ATtiny2313 is 1E 91 0A
         Double check chip, or use -F to override this check.

avrdude done.  Thank you.


What version of the product are you using? On what operating system?
ArduinoISP.04.zip
Ubuntu 11.04 64bit


Please provide any additional information below.
Same result, even if no Target-Microcontroller is connected (still ATMega328p 
is detected).

I am trying to write the Arduino bootloader to a new Atmega328 chip and avrdude 
can't identify the chip.


1. setup programmer with a breadboard like described in 
http://arduino.cc/en/Tutorial/ArduinoISP
2. replace SCK by SCK1, MISO by MISO1, MOSI by MOSI1 and RESET by RESET1 in the 
program because Arduino 1.0 uses tihs names and upload the program to an 
Arduino Decimilia (atmega168)
3. Execute avrdude -C/usr/lib/arduino/hardware/tools/avrdude.conf  -patmega328p 
-cavrisp -P/dev/ttyUSB0 -b19200 
-Uflash:w:/usr/lib/arduino/hardware/arduino/bootloaders/atmega/ATmegaBOOT_168_at
mega328.hex:i -Ulock:w:0x0F:m

The command result in this: 


avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.12s

avrdude: Device signature = 0x000000
avrdude: Yikes!  Invalid device signature.
         Double check connections and try again, or use -F to override
         this check.


avrdude done.  Thank you.


Any help please?

What steps will reproduce the problem?
1. Attempt to use avrdude with this program

What is the expected output? What do you see instead?
     Expected output:
           Reading/Writing to the connected AVR
     Received output:
           Reading/Writing to the Diecimila's ATMega 168 chip.

What version of the product are you using? On what operating system?
 Arduino diecimila, writing to it with version 0012 alpha on XP

Please provide any additional information below.

What steps will reproduce the problem?
1. connect an ATtin2313 to arduino
2. press reset button
3. enter avrdude -c avrisp -P com4 -p t2313

What is the expected output? What do you see instead?
The programmer seems not to recognize the signature of the t2312.

I get the following.

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\UserName>avrdude -c avrisp -P com4 -p t2313 -F
avrdude: stk500_getsync(): not in sync: resp=0x00
avrdude: stk500_disable(): protocol error, expect=0x14, resp=0x51

avrdude done.  Thank you.

( I should mention I tried several avrdude options)

What version of the product are you using? On what operating system?
I am using avrisp.03. ( I tested all versions but seem to get the same
responses.

Please provide any additional information below.

When using the option -c avr910 the fllowing appears and keeps repeating.

C:\Users\UserName>avrdude -c avr910 -P com4 -p t2313 -F

Found programmer: Id = ""; type = ♦
    Software Version =  . ; Hardware Version =  .

Programmer supports the following devices:
    Device code: 0xffffffe3 = (unknown)
    Device code: 0xffffffe3 = (unknown)
    Device code: 0xffffffe3 = (unknown)
    Device code: 0xffffffe3 = (unknown)
^C
C:\Users\UserName>

I also used a 200 ohm resistor between reset and 5V on the Arduino as
describe in the Arduino forum but I still get the same result.
I appreciate your help.

What steps will reproduce the problem?
1. burn some data > 4 bytes to EEPROM using ArduinoISP v4 and e.g. avrdude
an example (intel hex formatted eep) file would contain
:080000008040201008040201F9
:00000001FF
when running some AVR code to read values from EEPROM one will observe that the 
data written to the EEPROM is organized incorrectly.

2. read the EEPROM with another programmer, e.g. myAVR

3. compare results

What is the expected output? What do you see instead?

The above example should put this sequence of bytes into the EEPROM
0b10000000
0b01000000
0b00100000
0b00010000
0b00001000
0b00000100
0b00000010
0b00000001

what the flash actually contains after the write:
0b10000000
0b01000000
0b00100000
0b00010000
0b11111111
0b11111111
0b11111111
0b11111111
0b00001000
0b00000100
0b00000010
0b00000001
0b11111111
0b11111111
0b11111111
0b11111111

The data is complete, but has a wrong organization


What version of the product are you using? On what operating system?
ArduinoISP v4, ATMega8, avrdude on Windows 7. But this is not of any concern

Please provide any additional information below.

The misconception here is that the EEPROM is organized word-wise.
but the ATMega8 datasheet clearly states on page 19 that the EEPROM is 
organized bytewise. Thus multiplying the global variable "here" with two in the 
EEPROM read and write routines causes this bug. I suggest to change these 
functions as follows:

uint8_t write_eeprom(int length) {
  // this writes byte-by-byte,
  // page writing may be faster (4 bytes at a time)
  for (int x = 0; x < length; x++) {
    spi_transaction(0xC0, 0x00, here, buff[x]);
    delay(45);
  } 
  return STK_OK;
}

char eeprom_read_page(int length) {
  for (int x = 0; x < length; x++) {
    uint8_t ee = spi_transaction(0xA0, 0x00, here+x, 0xFF);
    Serial.print((char) ee);
  }
  return STK_OK;
}

worked perfectly for me ;-))

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.

What steps will reproduce the problem?
1. compile it with a AT90 atmega (teensy++)
2.
3.

What is the expected output? What do you see instead?
ArduinoISP work with AT90 usb (pin B0 B1 B2 B3)

Rolling back old version of arduinoisp to:
#include "pins_arduino.h"  // defines SS,MOSI,MISO,SCK
#define RESET SS

work perfectly!

What steps will reproduce the problem?

If I try and write over about 255 bytes to EEPROM, the check fails.
Command Line:
c:/WinAVR-20100110/bin/avrdude.exe -Cc:/WinAVR-20100110/bin/avrdude.conf -v
-pm328p -cstk500v1 -P//./COM10 -b19200
-Ueeprom:w:c:/Users/rich/AppData/Local/Temp/./build1566342148913742156.tmp/HotWa
ter.cpp.eep:i

Fuse bits and program flash work fine. Also can write < 255 bytes to EEPROM
and that works fine. 

Target CPU - Atmega328P (8Mhz internal clock)

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?
OS - Win7 64 bit
IDE - Arduino 18
Using Cygwin for command line interface.
avrisp.pde - the version available in Arduino release 18 - almost identical
code. They added read signature command.
Avrdude - EEPROM write fails with either version 5.4 as supplied with
Arduino or 5.10 from WinAVR. Using appropriate conf files with each version.

Please provide any additional information below.

Output from Avrdude:

avrdude.exe: Version 5.10, compiled on Jan 19 2010 at 10:45:23
             Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
             Copyright (c) 2007-2009 Joerg Wunsch

             System wide configuration file is
"c:/WinAVR-20100110/bin/avrdude.conf"

             Using Port                    : //./COM10
             Using Programmer              : stk500v1
             Overriding Baud Rate          : 19200
             AVR Part                      : ATMEGA328P
             Chip Erase delay              : 9000 us
             PAGEL                         : PD7
             BS2                           : PC2
             RESET disposition             : dedicated
             RETRY pulse                   : SCK
             serial program mode           : yes
             parallel program mode         : yes
             Timeout                       : 200
             StabDelay                     : 100
             CmdexeDelay                   : 25
             SyncLoops                     : 32
             ByteDelay                     : 0
             PollIndex                     : 3
             PollValue                     : 0x53
             Memory Detail                 :

                                      Block Poll               Page
          Polled
               Memory Type Mode Delay Size  Indx Paged  Size   Size #Pages MinW
 MaxW   ReadBack
               ----------- ---- ----- ----- ---- ------ ------ ---- ------
-----
 ----- ---------
               eeprom        65     5     4    0 no       1024    4      0
 3600
  3600 0xff 0xff
               flash         65     6   128    0 yes     32768  128    256
 4500
  4500 0xff 0xff
               lfuse          0     0     0    0 no          1    0      0
 4500
  4500 0x00 0x00
               hfuse          0     0     0    0 no          1    0      0
 4500
  4500 0x00 0x00
               efuse          0     0     0    0 no          1    0      0
 4500
  4500 0x00 0x00
               lock           0     0     0    0 no          1    0      0
 4500
  4500 0x00 0x00
               calibration    0     0     0    0 no          1    0      0
    0
     0 0x00 0x00
               signature      0     0     0    0 no          3    0      0
    0
     0 0x00 0x00

             Programmer Type : STK500
             Description     : Atmel STK500 Version 1.x firmware
             Hardware Version: 2
             Firmware Version: 1.18
             Topcard         : Unknown
             Vtarget         : 0.0 V
             Varef           : 0.0 V
             Oscillator      : Off
             SCK period      : 0.1 us

avrdude.exe: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.14s

avrdude.exe: Device signature = 0x1e950f
avrdude.exe: safemode: lfuse reads as E2
avrdude.exe: safemode: hfuse reads as DF
avrdude.exe: safemode: efuse reads as 5
avrdude.exe: reading input file
"c:/Users/rich/AppData/Local/Temp/./build1566342
148913742156.tmp/HotWater.cpp.eep"
avrdude.exe: writing eeprom (618 bytes):

Writing | ################################################## | 100% 41.21s

avrdude.exe: 618 bytes of eeprom written
avrdude.exe: verifying eeprom memory against
c:/Users/rich/AppData/Local/Temp/./
build1566342148913742156.tmp/HotWater.cpp.eep:
avrdude.exe: load data eeprom data from input file
c:/Users/rich/AppData/Local/T
emp/./build1566342148913742156.tmp/HotWater.cpp.eep:
avrdude.exe: input file
c:/Users/rich/AppData/Local/Temp/./build1566342148913742
156.tmp/HotWater.cpp.eep contains 618 bytes
avrdude.exe: reading on-chip eeprom data:

Reading | ################################################## | 100% 13.21s

avrdude.exe: verifying ...
avrdude.exe: verification error, first mismatch at byte 0x0000
             0x57 != 0x53
avrdude.exe: verification error; content mismatch

avrdude.exe: safemode: lfuse reads as E2
avrdude.exe: safemode: hfuse reads as DF
avrdude.exe: safemode: efuse reads as 5
avrdude.exe: safemode: Fuses OK

avrdude.exe done.  Thank you.

$

What steps will reproduce the problem?
1. Virgin ATmega328P connected in arduino.cc breadboard with external xtal 
configuration. 
2. Latest avrisp.pde (from here) running - heartbeat OK
3. Change "Board" to attempt to use "ADABoot loader w/ATmega328p" then "Burn 
Bootloader with Arduino as ISP"

What is the expected output? What do you see instead?
Program LED lights constant, heartbeat continues until errors out with:
  avrdude: stk500_recv(): programmer is not responding
  avrdude: error reading signature data for part "ATMEGA328P", rc=-1
  avrdude: error reading signature data, rc=-1
Heartbeat continues with program LED now off

What version of the product are you using? On what operating system?
- avrisp03 from here (re-downloaded for this documentation run
- Linux Mint, for this document (but had same issue on Windows XP previously)
- Arduino Duemilanove (tried with / without RESET-EN connected, same result)
- Breadboard or hardwired home-made shield, same result
- ADABoot materials freshly re-downloaded today
- Fresh Arduino018 re-download and installation today

Please provide any additional information below.

I must be missing something!

What steps will reproduce the problem?
1. load arduinoISP sketch in arduino target (I use the duemilanove board)
2. connect arduino pins 10-13+gnd+vcc to target AVR board ISP connector (I use 
a atmega128; that one is not supported as arduino board, thats why I revert to 
AVR studio)
3. In AVR Studio 4 (I use v4.18) Select AVR programmer "AVRISP" or "STK500"


What is the expected output? What do you see instead?

It is expected that AVR Studio 4 can connect to AVRISP, since the arduinoISP 
sketch is supposedly AVRISP compatible. It apparently is not.

First issue: arduinoISP sketch (this mega-isp) uses 19200 baud serial 
connection, whereas AVR Studio uses a fixed 115200 baud baudrate.
Changing the sketch to setup the serial port to use 115200 fixes this ussue.

Second issue: After fixing the baudrate issue, the arduinoISP does not go out 
of sync, but is still not recognized. It says connect failed after a short 
communication. The arduinoISP error led is not active.


What version of the product are you using? On what operating system?
 arduinoISP.04
 AVR Studio 4.18
 Windows Vista
 WinAvr 20100110
 avrdude 5.10

Please provide any additional information below.

It works with avrdude, after specifying the baudrate -b 19200 explicitly.

At one time, it did connect, but it complained that the AVRISP firmware was too 
old and suggested me to upgrade the firmware. I could not reproduce this.

What steps will reproduce the problem?
1. avrdude -p m8 -b 19200 -P com8 -c avrisp -F -e -U
flash:w:"D:/desktop/atmega/SID/monijonsyn.hex":a

similar error with all other tries.

- What is the expected output? What do you see instead?

i want to download the .hex file to the atmega8 (16)

if i dont do the -F in avrdude the error message comes earlier.
it then does erase and write stuff on the chip, but a mismatch in the end


- What version of the product are you using? On what operating system?

i use ur avrisp on winxp. downloading the avrisp.pde to my arduino seems to
work ok, the heartbeat led shines and the serial led turns on during comm.
the error led is never on.


can you help on that?

dusjagr

What steps will reproduce the problem?
1. Wire Arduino NG to an Arduino 23v.3 r.2 (2008 design) with an virgin atmega8
2. Not wire the HB, ERR and PMODE leds
3. Try to upload the most recent bootloader (00018) to the virgin atmega
4. It does not matter whether i use 19200 or 57600 baudrate
5. avrdude command: avrdude -P /dev/ttyUSB0 -p m8 -c avrisp -b 19200 -U 
flash:w:ATmegaBOOT.hex:i -v



Alternative: wire everything to a breadboard gives the same result

What is the expected output? What do you see instead?
The expected output would be the one informing the success of the process but 
instead i get the following message:

[eduardo@moon arduino-atmega8]$ avrdude -P /dev/ttyUSB0 -p m8 -c avrisp -b 
57600 -U flash:w:ATmegaBOOT.hex:i -v

avrdude: Version 5.10, compiled on Apr  3 2010 at 18:48:10
         Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
         Copyright (c) 2007-2009 Joerg Wunsch

         System wide configuration file is "/etc/avrdude.conf"
         User configuration file is "/home/eduardo/.avrduderc"
         User configuration file does not exist or is not a regular file, skipping

         Using Port                    : /dev/ttyUSB0
         Using Programmer              : avrisp
         Overriding Baud Rate          : 57600
         AVR Part                      : ATMEGA8
         Chip Erase delay              : 10000 us
         PAGEL                         : PD7
         BS2                           : PC2
         RESET disposition             : dedicated
         RETRY pulse                   : SCK
         serial program mode           : yes
         parallel program mode         : yes
         Timeout                       : 200
         StabDelay                     : 100
         CmdexeDelay                   : 25
         SyncLoops                     : 32
         ByteDelay                     : 0
         PollIndex                     : 3
         PollValue                     : 0x53
         Memory Detail                 :

                                  Block Poll               Page                       Polled
           Memory Type Mode Delay Size  Indx Paged  Size   Size #Pages MinW  MaxW   ReadBack
           ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
           eeprom         4    20   128    0 no        512    4      0  9000  9000 0xff 0xff
           flash         33    10    64    0 yes      8192   64    128  4500  4500 0xff 0x00
           lfuse          0     0     0    0 no          1    0      0  2000  2000 0x00 0x00
           hfuse          0     0     0    0 no          1    0      0  2000  2000 0x00 0x00
           lock           0     0     0    0 no          1    0      0  2000  2000 0x00 0x00
           calibration    0     0     0    0 no          4    0      0     0     0 0x00 0x00
           signature      0     0     0    0 no          3    0      0     0     0 0x00 0x00

         Programmer Type : STK500
         Description     : Atmel AVR ISP
         Hardware Version: 2
         Firmware Version: 1.18
         Topcard         : Unknown
         Vtarget         : 0.0 V
         Varef           : 0.0 V
         Oscillator      : Off
         SCK period      : 0.1 us

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.12s

avrdude: Device signature = 0x1e9307
avrdude: safemode: lfuse reads as E1
avrdude: safemode: hfuse reads as D9
avrdude: NOTE: FLASH memory has been specified, an erase cycle will be performed
         To disable this feature, specify the -D option.
avrdude: erasing chip
avrdude: reading input file "ATmegaBOOT.hex"
avrdude: writing flash (8170 bytes):

Writing | ############################################       | 87% 0.00s
avrdude: stk500_paged_write(): (a) protocol error, expect=0x14, resp=0x11
avrdude: stk500_cmd(): programmer is out of sync




What version of the product are you using? On what operating system?
avrisp03, avrdude 5.10 on a Linux box (archlinux fully updated - kernel 2.6.34 )

Please provide any additional information below.

It successfully read all the content of the memory to a file and the sck led 
blinks all time long. When i try to write data into the memory, it does not 
blink.

Using the avrdude command line, i also cannot write anything to the atmega 
memory spiking the following message:
avrdude> write flash 5 5
>>> write flash 5 5 
avrdude (write): error writing 0x05 at 0x00005 cell=0xff

If i try to write to the EE instead:
avrdude> write ee 5 5
>>> write ee 5 5 

avrdude> read ee
>>> read ee 
0000  ff ff ff ff ff 05 ff ff  ff ff ff ff ff ff ff ff  |................|

What steps will reproduce the problem?
1. Burn a 256 byte firmware to a Mega8 chip
2. Dump memory with avrdude
3. 0x20 row is blank (all still 0xff)

What is the expected output? What do you see instead?
Should write the rows instead of leaving them blank.

:: Problem is page size, which is currently hard-coded to 32.
:: So you can write Tiny13 and Tiny2313 no problem, anything
:: larger is wrong.

What is the expected output? What do you see instead?

When powering up, ISP pins are tied to ground, this can be problematic when 
doing In Circuit programming.

What version of the product are you using? On what operating system?

October 2010 by Randall Bohn

Please provide any additional information below.

simple to fix, add these lines at the end of the setup() function:

  pinMode(MOSI,INPUT);
  pinMode(RESET,INPUT);
  pinMode(MISO,INPUT);
  pinMode(SCK,INPUT);
  digitalWrite(MOSI,LOW);
  digitalWrite(RESET,LOW);
  digitalWrite(MISO,LOW);
  digitalWrite(SCK,LOW);

[deleted issue]

I noticed that in the function "start_pmode()" MOSI and SCK are set to
output before RESET is active.
That would mean that if the program currently running on the target uC has
set the pins corresponding to MOSI and SCK to HIGH, then there would be a
very high current (from target AVR to programmer AVR) for a short time.

shouldn't reset go active (LOW) first?