<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Dan</p>
<p>Please, first read this page:
<a class="moz-txt-link-freetext" href="https://chirp.danplanet.com/projects/chirp/wiki/DevelopersProcess">https://chirp.danplanet.com/projects/chirp/wiki/DevelopersProcess</a><br>
</p>
<p>I'm currently reverse engineering Yaesu FT-8900's memory map
using following procedure:</p>
<ul>
<li>I'm working this reverse engineering primarily in Ubuntu, as
it is easiest for me to debug Python there, using the Pycharm
IDE.</li>
<li>Check out Chirp's repository using Pycharm's own Mercurial
support.</li>
<li>I have created two spreadsheets for helping this development:</li>
<ul>
<li>First one, where I'm maintaining settings areas as
horizontal rows and configurations (readouts from device) as
vertical columns. Sample:
<a class="moz-txt-link-freetext" href="https://tuulos.org/nxld/index.php/s/5ELcBBKPqFGfZk2">https://tuulos.org/nxld/index.php/s/5ELcBBKPqFGfZk2</a> (link
valid till 14-Jan-2019)<br>
</li>
<li>Second one, where I'm writing out memory areas, which I have
reverse engineered, if I'm not writing them directly to Chirp
memory maps.<br>
</li>
</ul>
<li>I'm making small changes to device configuration and creating
a new vertical column, where I'm documenting the change. Then,
I'm reading out the memory map from device.</li>
<li>I'm converting the memory map dump to text file using standard
Linux hexdump command. Each vertical column has its own text
file.</li>
<li>Meld is practical tool to compare those hexdump files. Using
that, it should be possible to isolate, which memory areas were
affected by device configuration changes.</li>
<li>After finding out, what was changed and how, I'm implementing
support for those, by expanding the earlier implementation.</li>
</ul>
<p>This is a pretty time consuming process, but so far, I have been
able to isolate some new device settings/configurations and bring
them to Chirp. Most likely, this will take still at least couple
of weeks before I'm able to publish my changes.<br>
</p>
<p>BR,</p>
<p> Kalle<br>
</p>
<div class="moz-cite-prefix">Dan Clemmensen kirjoitti 30.12.2018 klo
20:26:<br>
</div>
<blockquote type="cite"
cite="mid:CALCgjGQGiTbQJrfaDiR-jdM0ZDaGQ4DFvq+6UQP2ZWO0g90RWA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">I am a new Ham, and I foolishly selected a radio
that is not supported by CHIRP. (Yaesu FT-4XR). I wish to add
support for it and its recent Yaesu siblings. I have
successfully analysed the serial protocol and I can read and
write the memory, but I don't know what to do next. Is there a
HOWTO somewhere? If not, I can attempt to create one, but some
guidance would be appreciated.<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
chirp_users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.danplanet.com</a>
<a class="moz-txt-link-freetext" href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a>
This message was sent to Kalle Tuulos OH1HQZ at <a class="moz-txt-link-abbreviated" href="mailto:oh1hqz@gmail.com">oh1hqz@gmail.com</a>
To unsubscribe, send an email to <a class="moz-txt-link-abbreviated" href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com">chirp_users-unsubscribe@intrepid.danplanet.com</a></pre>
</blockquote>
</body>
</html>