Bug #4885

FDC460A EEPROM mismatch

Added by Geraint Stimson over 5 years ago. Updated over 5 years ago.

Status:Closed Start date:06/06/2017
Priority:Normal Due date:
Assignee:Pavel Milanes % Done:

100%

Category:-
Target version:-
Chirp Version:daily Platform:All
Model affected:FD-460A

Description

Connecting to my rather old, and therefore I assume quite early (serial number less than 001750) model Feidaxin FDC460A results in the error: 'EEPROM fingerprint don't match, check if you selected the right radio model'

fd460a.txt - Serial log from original Feidaxin software (405 kB) Geraint Stimson, 06/06/2017 12:18 am

fd-460A.img - Assembled chirp img from the serial log, it don't work (id issues & issues with the no tone in used channels) (2 kB) Pavel Milanes, 06/06/2017 02:55 pm

debug.log (21.4 kB) Geraint Stimson, 06/06/2017 03:04 pm

fd460a_test.sin (2 kB) Geraint Stimson, 06/07/2017 01:51 am

Captura de pantalla de 2017-06-08 15-22-30.png - Screen shoot with the .sin file loaded, identifying it as FD-450A, not FD-460A (414.7 kB) Pavel Milanes, 06/08/2017 12:33 pm

History

Updated by Pavel Milanes over 5 years ago

  • Status changed from New to In Progress
  • Assignee set to Pavel Milanes
  • Model affected changed from FDC460A to FD-460A

Hi Geraint,

As I see on the log (thanks for the Serial Log!) your radio has not been reset by hardware (the FDC firmware has the bad procedure of cleaning the ENTIRE eeprom with 0xFF on hardware resets, wipping a bunch of usefull info in the process)

Can you please provide a debug.log from Chirp? (attach it to this post)

This debug.log has usefull info for the developers like me, you can know how to get the debug in this link: http://chirp.danplanet.com/projects/chirp/wiki/How_To_Report_Issues#Getting-your-debug-log

Hi have no free time right now, in the night I will inspect your serial log and will try to find the problem, a debug.log will speed up that process.; a file saved with the OEM software is usefull to, as it's exact copy of the eeprom with cosmetics changes.

I will remain online for an hour or so afther pushing this on the web, I will check if you has uploaded some files before going offline.

73 de Pavel CO7WT.

Updated by Pavel Milanes over 5 years ago

  • File fd-460A.img added
  • % Done changed from 0 to 50
  • Platform changed from Windows to All

Ok, I got some free time.

Geraint: I definitively need a file from the OEM software...

Please run the OEM Software, read the radio, program a few channels without tones, some of them with classic tones and other with digital tones, then write that to the radio; Read the radio again and export a file with that info, upload the file to this issue.

I was able to re-create a eeprom from your Serial Log and there are some issues with the identification and handling of the "no tone" on the channels, everything else looks fine.

It can be that your radio is a very early model and it's handled different in some aspects from the standard/late model.

With that info I will be able to patch the actual driver to support your specific radio (you will get a development version to test before the official release).

73 de Pavel CO7WT.

Updated by Geraint Stimson over 5 years ago

Hi Pavel,

Sterling work already!
Here's the debug.log
I'll get programming, but you may have to wait until morning (UTC+1 here) for the file.

Updated by Pavel Milanes over 5 years ago

Roger, no problem, I will check tomorrow.

73 de Pavel CO7WT

Updated by Geraint Stimson over 5 years ago

Here's the .sin from the OEM software.

Updated by Pavel Milanes over 5 years ago

Hi Geraint,

If I load the file you uploaded to my copy of the "FDX Communication Software-5.2" it get identified as a FD-450A not a FD-460A, Tweaking the .sin file and loading it in Chirp it get successfully loaded as a FD-450A.

Checking the guts of the file it match all fingerprints for a FD-450A.

As this radios allows to overwrite the programming with a different model, it can be possible that your radio was smashed with a FD-450A firmware; then you get all sort of problems.

The solution: If you radio states in the chassis that it's a FD-460A, please create a new (blank) profile of a FD-460A with the OEM software and then upload it to your radio.

Do as I suggested, then try to download it in Chirp, I bet you a beer that it will work as a FD-460A :)

73 de Pavel CO7WT.

Updated by Geraint Stimson over 5 years ago

Bang on Pavel, thanks for your work.
How much do I owe you for a beer?

Updated by Pavel Milanes over 5 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 50 to 100

Hi Geraint, drink your self that beer in the name of free/open source software and the Chirp Community.

I like beers because I'm on the Caribbean summer, depending on where you are you may like to change it for a Wisky shoot or a cup o wine ;-)

This issue is now solved.

Updated by Pavel Milanes over 5 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF