<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-gb">
	<link rel="self" type="application/atom+xml" href="https://forums.obdev.at/app.php/feed/topic/742" />

	<title>Objective Development Forums</title>
	
	<link href="https://forums.obdev.at/index.php" />
	<updated>2007-09-17T18:22:39+02:00</updated>

	<author><name><![CDATA[Objective Development Forums]]></name></author>
	<id>https://forums.obdev.at/app.php/feed/topic/742</id>

		<entry>
		<author><name><![CDATA[christian]]></name></author>
		<updated>2007-09-17T18:22:39+02:00</updated>

		<published>2007-09-17T18:22:39+02:00</published>
		<id>https://forums.obdev.at/viewtopic.php?t=742&amp;p=2422#p2422</id>
		<link href="https://forums.obdev.at/viewtopic.php?t=742&amp;p=2422#p2422"/>
		<title type="html"><![CDATA[AVR-Dopper in HVSP propably cannot work  for t11/t12/13!]]></title>

		
		<content type="html" xml:base="https://forums.obdev.at/viewtopic.php?t=742&amp;p=2422#p2422"><![CDATA[
I have heard reports that some of the 8 pin devices don't work in HVSP mode, maybe due to the difference you found! I have not gone through all the tedious diagrams in all data sheets when writing the original firmware.<br /><br />I'm quite confident that the Tiny11/12, 13 and 45 can be programmed in the same way, the STK500 would have to know the device type otherwise. If you make a firmware change, I can easily test it with a Tiny45 and an old AT90Sxxx here. I don't have a Tiny11 or 12, though.<br /><br />The code is prepared to support HVPP mode, but the Mega8 does not have enough pins. An ATMega16 should be sufficient for that. I don't have plans to support this mode myself because I never found ISP a limiting factor with the bigger devices. But if you want to start this project, I can give you hints.<p>Statistics: Posted by <a href="https://forums.obdev.at/memberlist.php?mode=viewprofile&amp;u=8">christian</a> — Mon Sep 17, 2007 6:22 pm</p><hr />
]]></content>
	</entry>
		<entry>
		<author><name><![CDATA[butrus.butrus]]></name></author>
		<updated>2007-09-12T20:12:40+02:00</updated>

		<published>2007-09-12T20:12:40+02:00</published>
		<id>https://forums.obdev.at/viewtopic.php?t=742&amp;p=2342#p2342</id>
		<link href="https://forums.obdev.at/viewtopic.php?t=742&amp;p=2342#p2342"/>
		<title type="html"><![CDATA[AVR-Dopper in HVSP propably cannot work  for t11/t12/13!]]></title>

		
		<content type="html" xml:base="https://forums.obdev.at/viewtopic.php?t=742&amp;p=2342#p2342"><![CDATA[
Hi!<br /><br />I tried to look and compare the datasheets for HVSP and I found, that the HVSP algorithm <strong class="text-strong">differs</strong> for ATtiny45(etc) and ATtiny11/12 <strong class="text-strong">and</strong> for ATtiny13! It seems, that in order to get the device's singature into the latch one must pulse at least 6x (t13) or 4x (t11/t12) the SCI clock  <strong class="text-strong">before</strong> bringing the RESET into 12V (see the datasheets for more details).<br /><br />I would be glad to help with debugging any new firmware, but ATM I only have tiny11 and tiny12 to try.<br /><br />(BTW, maybe it wouldn't be bad idea to add the possibility to &quot;debug&quot; the 12V wiritng by extending the firmware to listen for a specific vendor command that would put the HVSP reset line into 0V/5V/12V on user request. It would be easier to see whether something with the analog circuit is wrong or there is another - software - problem..)<br /><br />And Yes, Christian, do You have plans to support PP in some future version? I have seen some code in the hvprog.c. Do you think ATmega16 (or compatible) would be enough for a complete ICP/HVPP/HVSP programmer?<br /><br />(And Yet another note, I have look at the specification of HVPP initialization for M8 and M16 and seems really strange: one has to &quot;clear&quot; some fuses if for example the RESET bin is disabled BEFORE starting HV programming :-((((( )<p>Statistics: Posted by <a href="https://forums.obdev.at/memberlist.php?mode=viewprofile&amp;u=443">butrus.butrus</a> — Wed Sep 12, 2007 8:12 pm</p><hr />
]]></content>
	</entry>
	</feed>
