| ??? 07/05/07 20:51 Modified: 07/05/07 21:01 Read: times |
#141517 - it\'s not just Atmel Responding to: ???'s previous message |
Richard said:
Although I don't doubt this for a moment, I wonder how you know it's the ringing on clock, or similar signal quality issues that are of concern. Some of the parallel-port JTAG adapters I have used over the years have been very "marginal" in their construction, inviting such problems, yet I've seen little evidence of this under JTAG. And, if it would be the case, what evidence would you expect to see? With properly implemented software, it is relatively easy to discover the error and hide it within retries. I don't say this is impossible with the SPI-like protocol, just it's more likely the software won't account for this. Clock corruption is a typical issue with homebrew "cables", where the "manufacturer" is often a beginner and is not aware of potential problems when he uses improper cabling (length, arrangement). This is barely the case of your JTAG-cable, is it. Besides, I listed at least 3 other reasons why do these things fail. Mostly, the problem lies in the combination of unknown and unpredictible with the little competence of the users (often beginners). JW |
| Topic | Author | Date |
| AT89 ISP | 01/01/70 00:00 | |
| alternative | 01/01/70 00:00 | |
| I found this in this forum | 01/01/70 00:00 | |
your link was helpful! | 01/01/70 00:00 | |
| Why do so many people "search" rather than "use" | 01/01/70 00:00 | |
| why does it fail | 01/01/70 00:00 | |
| So it's ATMEL's fault? | 01/01/70 00:00 | |
| it\'s not just Atmel | 01/01/70 00:00 | |
| Thank you.. | 01/01/70 00:00 | |
| few details required | 01/01/70 00:00 | |
| Either build and use what they recommend, or quit! | 01/01/70 00:00 | |
| and .. | 01/01/70 00:00 | |
| There\'s been a lot of discussion about this ... | 01/01/70 00:00 | |
| also | 01/01/70 00:00 | |
| Ok. Thank you. | 01/01/70 00:00 |