<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Currently, none of the settings load in under the UV3-R radio since these settings fail.<BR> <BR>They do look resolvable, however without a radio I cannot test. It appears that the memory block at the location which chirp is reading these settings from has the memory bits all set (0xFF) where it expects to find a valid frequency. I compared this to the free UV3-R tool (old) and it appears to set the bits correctly, wears the image in the tests does not. It may be a possible that the image is a diff. model or variant of the previous uv3r.<BR> <BR>I will put a patch together with only the test code if you would like to try resolving it as I believe the settings test still remains useful.<BR> <BR> <BR><div>Date: Wed, 28 Jan 2015 17:37:32 -0800<br>From: dsmith@danplanet.com<br>To: chirp_devel@intrepid.danplanet.com<br>Subject: Re: [chirp_devel] [PATCH] Add Support for Settings UnitTest<br><br><pre>> [PATCH] Add Support for Settings UnitTest<br>> Add a basic unit test coverage of the radio Settings API.<br>> Currently, all but one image passes the test (UV3R).<br>> Commented out offending code in uv3r module.<br> <br>This is great, thanks! I'd rather not just disable the settings in the<br>UV3R driver to add this. Do the failures look resolvable?<br> <br>Also, the commit message says "commented out" but actually remove the code.<br> <br>If you want to send just a patch with the test bit, I'll see if I can<br>fix the UV3 driver and then apply it.<br> <br>--Dan<br> <br></pre><br>_______________________________________________
chirp_devel mailing list
chirp_devel@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers</div> </div></body>
</html>