[chirp_devel] [PATCH] [rt22] patch radio ID for RT-622

[Jim Unroe]

Dmitry,

On Sat, Nov 28, 2020 at 8:15 PM Jim Unroe <rock.unroe at gmail.com> wrote:
>
> Dmitry,
>
> On Tue, Oct 20, 2020 at 6:36 PM Dmitry Baryshkov <dbaryshkov at gmail.com> wrote:
> > > I am really glad that you have discovered this because, as I mentioned
> > > above, I have already made 2 RT22 FRS radios unusable. The factory
> > > software asks for a password now (for download and upload) and so far
> > > I have not been able to discover what it is.
> >
> > Could you please check if writing the proper string at 0x1b8 would fix
> > your radios? It does for my RT622.
> > However my radios still worked even when radio ID was a series of 0.
>
> What I finally ended up doing was to perform a serial port capture
> while using the factory software to remove the password of one of my
> working radios. Armed with this information I created a driver just
> for the purpose of removing the password. Worked like a charm. Now
> both radios are functioning as they should.
>
> Jim KC9HI

Here is version 2 of my proposal. This one reads the image being
uploaded to determine if 0x1b8 needs patched or not. It acquires the
"patch_id" and uses it to build the appropriate "patch" based on the
radio that the image is being uploaded to.

I have tested this with all 3 versions of my Retevis radios (RT22
(original), RT22 (FRS) and RT622). I have "images" from other similar
models (WLN KD0C1 and Zastone ZT-X6) but I don't have the physical
radios for testing.

Take a look at the attached driver module. Let me know your thoughts
as to how we should proceed.

Jim KC9HI
-------------- next part --------------
A non-text attachment was scrubbed...
Name: retevis_rt22(rt622&rt22frs v2).py
Type: application/octet-stream
Size: 21604 bytes
Desc: not available
Url : http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20201204/ccbf4caf/attachment-0001.obj