[avr-gcc-list] uisp Communication Problem

[Kevin Neff]

On Tue, 18 Jan 2005, [gb2312] ÀîÆæÔ½ wrote:

>I checked the wiring on my board and there is no problem.

You read page 303?  I only ask because I had this same problem...


>In the datasheet,the default clock source is Calibrated Internal RC 
>Oscillator,so I think this is the reason of the error message.

The internal oscillator is fine.  It won't cause the error you posted.
Wiring, SCK frequency, reset level, and power are the most common problems
that I've had.

>Actually, i did use --wr_fuse_l=0xff, --wr_fuse_h=0x99, and
>--wr_fuse_e=0xff to set the fuse,and the error message appears.

OK.  Sounds like you're on the right track as with respect to fuse
programming.  But if uisp can't read the signature byte, you have other
troubles.  

> >On Tue, 18 Jan 2005, [gb2312] ÀîÆæÔ½ wrote:
> >
> >>when I use uisp to program my atmega128,there is the error message as
> >>below,and the oscillator on board doesn't surge at all.
> > 
> >Are you using the STK500 board to program your MCU?  My firmware (1.18)
> >doesn't play well with uisp.  I develop on a linux box and am using
> >AVR Studio on a window$ machine to program the MCU... I think I've put
> >100,000 miles on my mouse and monitor plugs so far for this project :)
> >
> >> An error has occurred during the AVR initialization.
> >>  * Target status:
> >>    Vendor Code = 0xff, Part Family = 0xff, Part Number = 0xff
> >> 
> >> Probably the wiring is incorrect or target might be `damaged'.
> >
> >This is not a very descriptive error.  Many, many things cause it.
> >Some of the causes that come to mind include (for the 128) wrong
> >programming pins.  Check the datasheet--I think the UART pins are used
> >for MISO and MOSI.  It's different from most of the other microprocessors.
> >
> >>But i found out that the default jtag_en fuse bit is unprogrammed,so
> >>the jtag ice is no use and i cann't change the clock source.
> >
> >Use --wr_fuse_l=0x??, --wr_fuse_h=0x??, and --wr_fuse_e=0x?? to set
> >the fuses.  The datasheet for the ATMEGA128 will have the specific bit
> >definitions.  You should probably disable the ATMEGA103 compatibility
> >mode while you're at it.
> 
> 
>