AVR Downloader/UploaDEr - Bugs: bug #52687, avrdude eeprom uploader always...
You are not allowed to post comments on this tracker with your current authentication level.
bug #52687: avrdude eeprom uploader always uploads 0xff if line terminator is LF not CRLF
Submitter: | None | ||
Submitted: | Mon 18 Dec 2017 10:22:42 AM UTC | ||
Category: | None | Severity: | 3 - Normal |
Priority: | 5 - Normal | Item Group: | None |
Status: | None | Privacy: | Public |
Assigned to: | None | Originator Name: | James Collier |
Originator Email: | -email is unavailable- | Open/Closed: | Open |
Release: | 6.0.1 | Programmer hardware: | USBTiny |
Device type: | atmaga328p |
Sat 30 Dec 2017 07:23:47 AM UTC, comment #3: |
Joerg Wunsch <joerg_wunsch>![]() |
Sat 30 Dec 2017 01:21:32 AM UTC, comment #2: Windows and line termination characters may or may not be the problem, but removal of white space from the end of a line is not likely to have any noticeable impact on performance. |
Ryniker <ryniker> |
Fri 29 Dec 2017 11:29:37 PM UTC, comment #1: I'd have replied that Intel Hex files are by definition to be
|
Joerg Wunsch <joerg_wunsch>![]() |
Mon 18 Dec 2017 10:22:42 AM UTC, original submission:
It is useful to create eeprom .hex files from a program rather than from avr-gcc, for instance in a production environment to set calibration constants or a unique ID.
works fine: Writing and Reading get the progress lines of # characters, then the message
|
Anonymous |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
The question is not about removing whitespace but reimplementing
fgets() rather than using the system/library version.