[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [avrdude-dev] Parallel port doesn't keep programmed states
From: |
Rune Christensen |
Subject: |
RE: [avrdude-dev] Parallel port doesn't keep programmed states |
Date: |
Fri, 21 Nov 2003 08:44:53 +0100 |
Hi
I have had the same problem.
You need to disable Windows XP Plug'n'Play for the parallel port.
I solved the problem with the following file:
http://www.student.dtu.dk/~s991363/avr/avrdude/winxp1.reg
You need to save the file and the run it.
It will change a setting in the Windows registry.
The file content:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Parport\Parameters]
"DisableWarmPoll"=dword:00000001
I have only used this on Windows XP.
Rune
-----Original Message-----
From: address@hidden
[mailto:address@hidden
Behalf Of idefixx
Sent: Friday, November 21, 2003 6:32 AM
To: address@hidden
Subject: [avrdude-dev] Parallel port doesn't keep programmed states
Hi guys!
As I can see you are all a very fast and flexible group! congratulations!
But before you make your next release, I want to call your attention to
another problem that I have encountered.
Every time after rebooting my windows XP system (running on Intel Celeron
500MHz, 256MB RAM) I have got a problem programming my microcontroller with
AVRdude using the parallel port dongle. When I start the programming, the
first few seconds everything works fine. But after having written to the AVR
for some seconds, AVRdude reports a program fail for every single byte.
Also, if I repeat programming - again after a certain time (not the same
time) AVRdude reports " ***failed; ". As often I repeat, AVRdude never can
manage to program the AVR fully.
What I do then, to get it work, is to read out the AVR flash memory. After
this I again try to program the AVR and - oh wonder - then it works without
a problem. This problem just appears after rebooting my system.
I now did a little test using the ppiwin.c file only. I modified it by
inserting a main() function so that I can run it by itself in order to
control the parallel output pins. Here the same thing happens again. After
some seconds the parallel port pins automatically change their states. I
couldn't find out so far, why. This seems to me is the same problem that
appears when I use AVRdude, because here after performing an AVR read out
suddenly this automatic change of port pin states doesn't appear anymore
until the next reboot.
Does someone have a clue, what could be the problem?
Sorry for coming up with new problems all the time ;-)
/idefixx
_______________________________________________
avrdude-dev mailing list
address@hidden
http://mail.nongnu.org/mailman/listinfo/avrdude-dev
- [avrdude-dev] Parallel port doesn't keep programmed states, idefixx, 2003/11/21
- RE: [avrdude-dev] Parallel port doesn't keep programmed states,
Rune Christensen <=
- RE: [avrdude-dev] Parallel port doesn't keep programmed states, E. Weddington, 2003/11/21
- Re: [avrdude-dev] Parallel port doesn't keep programmed states, idefixx, 2003/11/23
- Re: [avrdude-dev] Parallel port doesn't keep programmed states, Jan-Hinnerk Reichert, 2003/11/24
- Re: [avrdude-dev] Parallel port doesn't keep programmed states, E. Weddington, 2003/11/24
- RE: [avrdude-dev] Parallel port doesn't keep programmed states, Marc Wetzel, 2003/11/24
- RE: [avrdude-dev] Parallel port doesn't keep programmed states, E. Weddington, 2003/11/24
- RE: [avrdude-dev] Parallel port doesn't keep programmed states, Rune Christensen, 2003/11/25
- Re: [avrdude-dev] Parallel port doesn't keep programmed states, Jan-Hinnerk Reichert, 2003/11/25
- RE: [avrdude-dev] Parallel port doesn't keep programmed states, Rune Christensen, 2003/11/26
- Re: [avrdude-dev] Parallel port doesn't keep programmed states, Jan-Hinnerk Reichert, 2003/11/26