I believe this is actually being caused by a bug in avrdude that I found a while ago, but never got around to submitting a patch for. The "buf[i] = 0;" at line 72 of http://svn.savannah.gnu.org/viewvc/trunk/avrdude/update.c?annotate=722&root=avrdude needs to be moved up to line 54. - Carl
On Mon, Apr 27, 2009 at 9:02 AM, Royce Pereira <royc...@gmail.com> wrote: > Hi, > Today I decided to try our Windows 7 (beta build 7077). This is the > build just before RC1. > I aso installed just today WinAVR 2090313. > > I'm not sure if either one could be at fault. > > When I try to use Avrdudein the DOS window, or thru a bat file,it > reads funny garbage at the end of the **filename**. Like so: > (This is the output of my editor ) > > > avrdude -c stk500v2 -p m8 -u -U benz-ppm3.hex -U lfuse:w:0x21:m -U > lock:w:0x3c:m > > > avrdude: AVR device initialized and ready to accept instructions > > Reading | ################################################## | 100% 0.08s > > avrdude: Device signature = 0x1e9307 > avrdude: NOTE: FLASH memory has been specified, an erase cycle will be > performed > To disable this feature, specify the -D option. > avrdude: erasing chip > avrdude: reading input file "benz-ppm3.hex#h" > avrdude: error opening benz-ppm3.hex#h: No such file or directory > avrdude: input file benz-ppm3.hex#h auto detected as invalid format > avrdude: can't open input file benz-ppm3.hex#h: No such file or directory > avrdude: write to file 'benz-ppm3.hex#h' failed > > Note the garbage after the hex-file name. This happens even if the > command line is typed at the prompt. > I tried with AVRstudio, and the chip gets programmed wth no problem. > > What could be wrong ? Thanks, > > --Royce. > > > _______________________________________________ > AVR-GCC-list mailing list > AVR-GCC-list@nongnu.org > http://lists.nongnu.org/mailman/listinfo/avr-gcc-list >
_______________________________________________ AVR-GCC-list mailing list AVR-GCC-list@nongnu.org http://lists.nongnu.org/mailman/listinfo/avr-gcc-list
