search

phdlee / uvk5cec

Adds various experimental features to the uvk5 radio
Apache License 2.0
257 stars 20 forks source link

0x00 values only, while reading EEPROM memory #55

Open klaute opened 2 months ago

klaute commented 2 months ago

Hello,

I have recently started to write a CHIRP module: https://git.okoyono.de/klaute/uvk5-cec-chirp-driver

I read through your code to figure out the EEPROM structure.

At first I tried to read the EEPROM back to my computer using the k5prog_win.exe to verify my CHIRP structure. But the problem is that I receive only 0x00 values for the whole EEPROM content.

Next I have modified the CHIRP module to write down the read EEPROM content to a file, which also gives 0x00 values only.

For now I don't have a solution.

Currently I'm investigate to understood what happens in the firmware, what leads to that behaviour.

If you have any suggestions please feel free to contact me.

Thank you!

alboc2k commented 2 months ago

I think (but CEC is the man) it's firmware that sends eeprom data to PC and writes data from PC into EEPROM. So if actual firmware does not provide that function you can't access EEPROM at all. Try change FW and read out should succeeed. So should writing. Anyway R/W data on EEPROM via CHIRP module is a priority (IMHO).