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

[Dmitry Baryshkov]

Jim,

ср, 21 окт. 2020 г. в 00:37, Jim Unroe <rock.unroe at gmail.com>:
>
> Dmitri,
>
> Isn't this going to change these bytes for all models? For example, my
> regular RT22 which has "P32073" at 0x01b8 will be overwritten with
> "P3207!". I'm afraid to try this to see because I have already ruined
> 2 RT22 FRS models trying to add them to CHIRP.

This sounds interesting. I'll add this check and send v2 of this patch.
BTW: is there a way to check that developer options are enabled?
I would not dare to enable all-zero radio ID (since this well might be
some other random radio), but it would be required to restore broken
RT22 radios.

> Since it appears to me that this radio (and its RT22 FRS cousin) has
> "P3207!" stored at 0x0000 and 0x0200, there couldn't there be some
> kind of check that when 0x01b8-0x01bd is 0x00 * 6, then the value in
> 0x0000-0x0006 (or 0x0200-0x0206) could be sent at 0x01b8 during the
> upload?
>
> 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.


-- 
With best wishes
Dmitry R1BBD