#4 Incorrect file conversion.

[Anonymous]

Hi,

I was using hex2bin to convert hex files into code that is subsequently executed. I find in this file that it converts the whole file, but amits the final 2 bytes. I downloaded the latest 1.0.4 version to check, used in win XP.

Many thanks for your work,

Robbie.

[Nobody/Anonymous]

hex file that is not correctly converted.

[Jacques Pelletier]

Logged In: YES
user_id=615018
Originator: NO

I took note of it and will check this out in the following weeks.

[Jacques Pelletier]

Logged In: YES
user_id=615018
Originator: NO

:10044800E47889F6E47B7F7A017984A5587889E68F
:100458007B7F7A017983A558A5220000000000005F
:10046000000000000000000000000000000000008C
:10047000000000000000000000000000000000007C

The line :10045800... is too long and overlaps the following line.
It decodes addresses as 0458-0467 and the following line as 0460-046F,
so bytes at 0460 (A5 22) disappear. So the problem is not hex2bin itself,
but the program generating the hex file. I hope you already found out :)

[Jacques Pelletier]

Logged In: YES
user_id=615018
Originator: NO

The problem was due to overlapping records. Trying to correct this may lead to a major code rewrite.
I'm putting this as closed for now. Assuming that hex files are mostly generated, this shouldn't be a major problem.

[Jacques Pelletier]

Checking for overlapping record will be simpler than expected. This will be corrected in the next release due soon. Meanwhile I submitted a quick fix: see Tracker/Patches.