[Top][All Lists]

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

RE: [avr-gcc-list] uisp Communication Problem

From: Craig Schlenter
Subject: RE: [avr-gcc-list] uisp Communication Problem
Date: Tue, 18 Jan 2005 07:14:40 +0200


[ I haven't been following this thread so comments below may have
been mentioned by someone else already btw. ]

> 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.

At least one of the atmel data sheets muttered something about some
chips having signature 0xff and then you'd have to manually tell the
programmer what chip it was ... I've only used uisp once but did run
into a chip that it couldn't program through the stk500 but using
avr-studio to drive the stk500 and program the same chip was fine.
And uisp had moaned about the signature bytes like the stuff below.
Try avr-studio instead and see if it's better.

> > >>  * Target status:
> > >>    Vendor Code = 0xff, Part Family = 0xff, Part Number = 0xff
> > >> 
> > >> Probably the wiring is incorrect or target might be `damaged'.

Possible. Or see above.

Also you should be rather careful choosing fuse setttings. If you
mess it up, you may have to use an external clock on the chip to
chat to it again or the reset might be disabled in which case you
won't get it into serial programming mode again etc.



This email and any accompanying attachments may contain confidential and 
proprietary information. This information is private and protected by law and, 
accordingly, if you are not the intended recipient, you are requested to delete 
this entire communication immediately and are notified that any disclosure, 
copying or distribution of or taking any action based on this information is 
Emails cannot be guaranteed to be secure or free of errors or viruses. The 
sender does not accept any liability or responsibility for any interception, 
corruption, destruction, loss, late arrival or incompleteness of or tampering 
or interference with any of the information contained in this email or for its 
incorrect delivery or non-delivery for whatsoever reason or for its effect on 
any electronic device of the recipient.
If verification of this email or any attachment is required, please request a 
hard-copy version.

reply via email to

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