File wrong size

[sdavies]

Not sure whether this is an eepskye or ersky9x issue.

I have just downloaded r218 firmware to upgrade my ER9X Pro.

I started the process by using eepskye (v420) to save a copy of the current firmware (r217 11/4/15).
This worked as expected.
I then tried to backup my EEPROM settings.
The transfer started out OK but then came up with the "Error reading file. File wrong size" message.
I tried several times with the same result.

I also tried to Open the various saved EEPROM files (with eepskye) but the open menu was empty even though the files are there.

Does the "save to" file name have to have an extension? I see a file type selection box in the open menu but it seems to have no effect.

Cheers and thanks,
Stephen

[jhsa]

You say Er9x PRO.. Do you mean 9XR-PRO?
If so, are you sure you are using eepskye and not eepe?

João

[MikeB]

Please try with the most recent version of eepskye. This is found here: http://www.er9x.com/.
The most recent version IS r419 on there. I had a problem with the revision numbering when transferring the source files from googlecode to Github, so this version is more recent than the r420 you have.

Mike.

[sdavies]

Thanks Mike. That got me further.
I can now backup EEPROM to a file without getting the file size error.
The size of the backup file is now 524288 - the same size as the firmware backup.
It that right?

Is there any way to confirm that the backup is good apart from loading it back (and potentially zapping everything)?

I don't understand the contents of the eepskye download from www.er9x.com.
What are control.tar.gz, data.tar.gz and debian.binary? (I used to work for Control Data Corporation (CDC) so the names ring bells.)

I was able to run the usr/bin/eepskye from data.tar.gz on my Fedora 23 box so I didn't need to get the source code and rebuild.

Cheers,
Stephen

[MikeB]

Yes, the 9XR-PRO does have 512K of EEPROM (534288).
Open the backup file in eepskye. This should show it is OK.

I don't know about the files. If you are using the release for linux, what is in the .deb file is what gets put in there, I just run the build command to make it.

Mike.

[sdavies]

I tried to open the file with eepskye but the file selection menu is empty.
I tried changing the file type in the bottom right drop-down but the file list is always empty.
What is it looking for? (Yes. I am using the Linux release.)

Cheers,
Stephen

[MikeB]

What did you save the backup file as? For this, you would normally save the file a "something.bin".

Mike.

[sdavies]

I created dummy files with .hex and .bin endings and these appeared in the file selection window so I renamed my EEPROM backup file to backup.hex and it also appeared in the list but when I selected it for opening, nothing happened.
Obviously, eepskye is looking for particular endings. What is the expected ending for an EEPROM backup file?

[sdavies]

OOPS! Our emails crossed.I'll try .bin just now.

[sdavies]

OK. That does it.
I renamed the backup to backup.bin and now I can see it and open it.
Roll on r218;-)

(Relying on file name endings is a very windoze thing. The magic numbers in file headers are much more general and Open Source.
At least the expected file name formats should be better documented.)

Cheers and thanks,
Stephen