er9x eeprom inconsistency

[GoogleCodeExporter]

What steps will reproduce the problem?
1. read TX eeprom using averdude avrdude.exe -B 1 -c usbtiny -p m64 -U 
eeprom:r:"eprom_rep_eepe.hex":i (or using eePe and save in HEX format)
2. open companion9x and read TX eeprom
3. save the document in HEX format
4. compare the two files

What is the expected output?

the both files should be identical (may be one have a CrLf at end but no other 
difference)

What do you see instead?

The files are different

What version of the product are you using? On what operating system?

Companion9x 1.02 (1443) in Windows 7 Professional 64 bits

Please provide any additional information below.

if you open both files in companion and compares models none difference between 
each. but the models are bigger and use more memory

Original issue reported on code.google.com by impe...@gmail.com on 18 Oct 2012 at 2:50

• Merged into: #96

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

C9x does not yet support all the latest changes er9x implemented in the past 
few weeks (safety switch "modes", all the voice-related stuff, custom telemetry 
screen etc...), so it would obviously not import/translate everything 
correctly, and might also lose some settings. At this point I wouldn't use C9X 
to manage the latest er9x eeproms.
Save eeprom to file should give the same file though, as no processing is done.

Original comment by bernet.a...@gmail.com on 23 Oct 2012 at 12:02

[GoogleCodeExporter]

Hi, ok, I understand, and know ER9x has make several changes in short time. 
this could be a time consuming process to keep update, i will wait.  softy for 
no be able to help but my C and QT knowledge is almost zero.

regards

Original comment by impe...@gmail.com on 23 Oct 2012 at 9:18

[GoogleCodeExporter]

ER9X compatibility issues should go in issue 96

Original comment by romolo.m...@gmail.com on 14 Apr 2013 at 11:08

• Changed state: Duplicate