[chirp_users] How to analyse the memory map for a new radio type?

Kalle Tuulos OH1HQZ oh1hqz at gmail.com
Mon Dec 31 00:09:35 PST 2018


Hi Dan

Please, first read this page:
https://chirp.danplanet.com/projects/chirp/wiki/DevelopersProcess

I'm currently reverse engineering Yaesu FT-8900's memory map using
following procedure:

  * I'm working this reverse engineering primarily in Ubuntu, as it is
    easiest for me to debug Python there, using the Pycharm IDE.
  * Check out Chirp's repository using Pycharm's own Mercurial support.
  * I have created two spreadsheets for helping this development:
      o First one, where I'm maintaining settings areas as horizontal
        rows and configurations (readouts from device) as vertical
        columns. Sample:
        https://tuulos.org/nxld/index.php/s/5ELcBBKPqFGfZk2 (link valid
        till 14-Jan-2019)
      o 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.
  * 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.
  * I'm converting the memory map dump to text file using standard Linux
    hexdump command. Each vertical column has its own text file.
  * 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.
  * After finding out, what was changed and how, I'm implementing
    support for those, by expanding the earlier implementation.

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,

  Kalle

Dan Clemmensen kirjoitti 30.12.2018 klo 20:26:
> 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.
>
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to Kalle Tuulos OH1HQZ at oh1hqz at gmail.com
> To unsubscribe, send an email to chirp_users-unsubscribe at intrepid.danplanet.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20181231/f7ab40a1/attachment-0002.html 


More information about the chirp_users mailing list