Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#106 readmem under Windows produces incorrect sized file

0.x
closed-fixed
UrJTAG (102)
5
2013-07-20
2009-10-08
Daryl Tester
No

Hi there

Using UrJTAG 0.10 under Windows, the readmem command produced an incorrect sized file. On further investigation, it appears that size difference (of what was expected to what was produced) matches the number of linefeeds (character 0x0a) that was in the flash file, and that a carriage return (0x0d) character was inserted before the 0x0a. I suspect that the readmem() command needs to open the output file in binary mode before calling the readmem() function. Sorry, I don't have a cygwin environment set up to confirm this.

Under Linux, UrJTAG produced the correct sized file.

Discussion

  • Mike Frysinger
    Mike Frysinger
    2010-07-14

    • assigned_to: nobody --> vapier
     
  • Mike Frysinger
    Mike Frysinger
    2010-07-18

    all the fopen() locations in trunk now include "b"

     
  • Mike Frysinger
    Mike Frysinger
    2010-07-18

    • status: open --> closed-fixed
     
  • DanMan32
    DanMan32
    2013-07-20

    Problem may be fixed in the sourcecode, but the precompiled windows executable downloadable from Sourceforge still has this problem.
    Can you recompile the windows version and publish the update on sourceforge, perhaps as version .10.1? I like the standalone in that it doesn't rely on cygwin, and the Data folder is in the same folder that jtag executible is at.

    Is this problem only with Readmem? If so, I can work around the issue by using hex editor to replace 0D0A with 0A. This issue drove me nuts!