You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"I'm using AvrDude 4 as shipped with WinAVR, and I discovered a bug in the binary output format (as in "avrdude -c xx -p yy -f r -o file.bin"), since it seems to always open files in 'translated' mode, instead of using 'binary' mode.
This works well with Unix and alikes, since a '\n' has the same representation in the two modes, while on Windows it is translated in "\r\n", that has the nasty side effects of an additional 0x0D in the output -- fopen() needing a check for "wb" mode?"
Mon 21 Apr 2003 03:50:22 PM UTC
From Lou Cypher on AVR Freaks:
"I'm using AvrDude 4 as shipped with WinAVR, and I discovered a bug in the binary output format (as in "avrdude -c xx -p yy -f r -o file.bin"), since it seems to always open files in 'translated' mode, instead of using 'binary' mode.
This works well with Unix and alikes, since a '\n' has the same representation in the two modes, while on Windows it is translated in "\r\n", that has the nasty side effects of an additional 0x0D in the output -- fopen() needing a check for "wb" mode?"
This issue was migrated from https://savannah.nongnu.org/bugs/?3293
The text was updated successfully, but these errors were encountered: