-
Hi Thank you for the usefull mod! Unfortunately - I made the same mistake as mentioned in: #363
This worked, I played around with the radio tested all functions. Everything worked fine. Installed chirp with the egzumer driver not realizing there is a different driver for the F4HNW firmware to programm the channels.
Now the radio behaves strangely and often freezes. I guess some part of the ezgumer config causes this issue with the F4HNW Firmware. Is there a way to wipe the custom config and start over with a clean config? 73 Benoit / -HB9EUE- |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
Hello Benoit, Reading the documentation is a step that should never be skipped. If you did, just reflash your EEPROM backup, reinstall the F4HWN firmware, and use the dedicated driver as explained. Otherwise, you can access the hidden menus and perform a full RESET via menu 72/72, using the ALL option. I’m moving this issue to Discussions — this is not a firmware problem, but a user-related one. — Armel, F4HWN |
Beta Was this translation helpful? Give feedback.
-
Thank you. Indeed, I made a backup with k5prog before flashing which created k5_eeprom.raw file. I attempted to flash this back with the web-flasher, which did not work - file not supported. Then I read the help for k5prog and learned that there is a difference between the 'firmware' and the 'eeprom' file. I concluded the eeprom only contains the settings so there is no way to flash back the factory firmware and settings as I had only dumped the settings eeprom which I assumed not being compatible with your F4HWN firmware. |
Beta Was this translation helpful? Give feedback.
-
Ok. You really should read or re-read the documentation, watch my videos, etc. The EEPROM only contains settings, calibration data, and saved memory channels. The firmware, on the other hand, is stored in the internal flash memory of the microcontroller. In short, two types of memory for two different purposes. |
Beta Was this translation helpful? Give feedback.
Hello Benoit,
Reading the documentation is a step that should never be skipped.
I’m guessing you didn’t make a backup of the EEPROM before flashing a new firmware on your device either?
If you did, just reflash your EEPROM backup, reinstall the F4HWN firmware, and use the dedicated driver as explained.
Otherwise, you can access the hidden menus and perform a full RESET via menu 72/72, using the ALL option.
That, too, is documented… but unfortunately, I can’t read the manual for you ;)
I’m moving this issue to Discussions — this is not a firmware problem, but a user-related one.
— Armel, F4HWN