Title: Again buspirate programming fails
Post by: arupbsk on October 09, 2011, 01:22:56 pm
Post by: arupbsk on October 09, 2011, 01:22:56 pm
My problem is exactly the same as viewtopic.php?f=41&t=1691#p25698 (http://dangerousprototypes.com/forum/viewtopic.php?f=41&t=1691#p25698)
I have connected a mega32 with prototyping board. I connected accordingly as guided.
If I supply 5V from BP 10pin connector, few miliseconds powerup to the AVR chip.
I have preprogrammed 100ms LED1 glowing program via TinyISP in the mega32 so whenever reset occurs the LED blinks once after it initializes.
When I power externally the mega32 by 5V (common GND with AVr and BP) at the last steps of AVRDUDE's failing try, a reset occurs and my LED1 blinks.
Nevermind, I was trying to see when reset occurs so I installed the program to mega32 before connecting to BP.
My diagnostics say reset occurs when avrdude says " initialization failed, rc=-2"
I am using Bootloader 4.4 and firmware 5.1[attachment=0]000_0011[1].JPG[/attachment]
I have connected a mega32 with prototyping board. I connected accordingly as guided.
If I supply 5V from BP 10pin connector, few miliseconds powerup to the AVR chip.
I have preprogrammed 100ms LED1 glowing program via TinyISP in the mega32 so whenever reset occurs the LED blinks once after it initializes.
When I power externally the mega32 by 5V (common GND with AVr and BP) at the last steps of AVRDUDE's failing try, a reset occurs and my LED1 blinks.
Nevermind, I was trying to see when reset occurs so I installed the program to mega32 before connecting to BP.
My diagnostics say reset occurs when avrdude says " initialization failed, rc=-2"
I am using Bootloader 4.4 and firmware 5.1[attachment=0]000_0011[1].JPG[/attachment]
Code: [Select]
C:UsersArup>avrdude -P COM2 -c buspirate -p m32 -v -F
avrdude: 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-20100110binavrdude.conf"
Using Port : COM2
Using Programmer : buspirate
AVR Part : ATMEGA32
Chip Erase delay : 9000 us
PAGEL : PD7
BS2 : PA0
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 Max
W ReadBack
----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ---
-- ---------
eeprom 4 10 64 0 no 1024 4 0 9000 90
00 0xff 0xff
flash 33 6 64 0 yes 32768 128 256 4500 45
00 0xff 0xff
lfuse 0 0 0 0 no 1 0 0 2000 20
00 0x00 0x00
hfuse 0 0 0 0 no 1 0 0 2000 20
00 0x00 0x00
lock 0 0 0 0 no 1 0 0 2000 20
00 0x00 0x00
signature 0 0 0 0 no 3 0 0 0
0 0x00 0x00
calibration 0 0 0 0 no 4 0 0 0
0 0x00 0x00
Programmer Type : BusPirate
Description : The Bus Pirate
Detecting BusPirate...
avrdude: buspirate_readline(): #
avrdude: buspirate_readline(): RESET
avrdude: buspirate_readline():
**
avrdude: buspirate_readline(): Bus Pirate v3b
** Bus Pirate v3b
avrdude: buspirate_readline(): Firmware v5.10 (r559) Bootloader v4.4
** Firmware v5.10 (r559) Bootloader v4.4
avrdude: buspirate_readline(): DEVID:0x0447 REVID:0x3046 (24FJ64GA002 B8)
** DEVID:0x0447 REVID:0x3046 (24FJ64GA002 B8)
avrdude: buspirate_readline(): http://dangerousprototypes.com
** http://dangerousprototypes.com
avrdude: buspirate_readline(): HiZ>
**
BusPirate: using BINARY mode
BusPirate binmode version: 1
BusPirate SPI version: 1
avrdude: initialization failed, rc=-2
avrdude: AVR device initialized and ready to accept instructions
avrdude: Device signature = 0x000000
avrdude: Yikes! Invalid device signature.
avrdude: Expected signature for ATMEGA32 is 1E 95 02
BusPirate is back in the text mode
avrdude done. Thank you.
Title: Re: Again buspirate programming fails
Post by: ian on October 09, 2011, 02:27:05 pm
Post by: ian on October 09, 2011, 02:27:05 pm
Avr dude uses standard spi binmode commands, there's no special support. There probably is not a bug in the firmware. Double check your.connections, target power supply/circuit, and avrdude settings
Be.sure.to use regular and not hiz pins.
Be.sure.to use regular and not hiz pins.