[chirp_devel] Extending the UV-5R Structure Definition
Hi all,
Over the last few weekends I have been mapping the various features and functions of the Baofeng UV-5R to CHIRP image files that were created by different firmware versions. After a short email exchange with Dan and after examining a some files that he suggested I look at, I think I might be able to assist with extending the UV-5R structure definition.
Does anyone have any advice for me on how to get started?
Thanks, Jim KC9HI
Over the last few weekends I have been mapping the various features and functions of the Baofeng UV-5R to CHIRP image files that were created by different firmware versions. After a short email exchange with Dan and after examining a some files that he suggested I look at, I think I might be able to assist with extending the UV-5R structure definition.
If there are any developers with environments already set up who have an interest in the UV5R driver, this would be an easy way to contribute. Jim has already done a bunch of the work.
Does anyone have any advice for me on how to get started?
Jim, what platform are you on? Any chance you have a Linux box you could use?
I think that we need a way to dump the raw bitwise data of the settings structure similar to what we do for "show raw memory". This would let Jim modify the mem_format and see that the values are landing in the right buckets, which would then make it easy for a developer to plumb those to UI elements.
Anyone interested?
participants (2)
-
Dan Smith
-
Jim Unroe