MD-2017 running latest OpenMDUV380(openGD77)

[SA0BUX]

I have a RT82 (GPS) which is the same radio as MD-2017 , I''m curious to test and load some OpenGD77 so I'm charging the radio now and installed the CPS X-version on my PC.

( Additionally I have the RT84 but I have lent it out for the moment, my OM friend would be very happy if it will be possibly to run OpenGD77 in the future )

[SA0BUX]

I have a RT82 (GPS) which is the same radio as MD-2017 , I''m curious to test and load some OpenGD77 so I'm charging the radio now and installed the CPS X-version on my PC.

( Additionally I have the RT84 but I have lent it out for the moment, my OM friend would be very happy if it will be possibly to run OpenGD77 in the future )

First test with the RT82:
+ Was possible to write flash with X CPS and Radio Type MD-2017 , I loaded 2023-02-27 OpenMDUV380.bin
+ Radio started up with the loaded software , No startup sounds , screen light is flashing randomly and radio seems to jump around in channel.
+ Writing a codeplug seems to work, I could write over the bad config data.

- Keyboard works randomly , not able to do any real control of the radio.
- No RX , was able to manipulate the squelch but no sound.
- It seems to go over in TX mode when I press PTT but no output.

Also tried with 2023-03-04 OpenDM1701.bin but that ones behaves similarly.

[VK3KYY]

I have a RT82 (GPS) which is the same radio as MD-2017 , I''m curious to test and load some OpenGD77 so I'm charging the radio now and installed the CPS X-version on my PC.

( Additionally I have the RT84 but I have lent it out for the moment, my OM friend would be very happy if it will be possibly to run OpenGD77 in the future )

First test with the RT82:
+ Was possible to write flash with X CPS and Radio Type MD-2017 , I loaded 2023-02-27 OpenMDUV380.bin
+ Radio started up with the loaded software , No startup sounds , screen light is flashing randomly and radio seems to jump around in channel.
+ Writing a codeplug seems to work, I could write over the bad config data.

- Keyboard works randomly , not able to do any real control of the radio.
- No RX , was able to manipulate the squelch but no sound.
- It seems to go over in TX mode when I press PTT but no output.

Also tried with 2023-03-04 OpenDM1701.bin but that ones behaves similarly.

OK.
CPS Radio Type MD2017 is the same as MD-380UV and RT-3S

Probably the MCU pin mapping for the keyboard and many other things is different.

Perhasp you can discuss with BD4VOW how to find the pin mapping on this radio, then will probably be able to support it.

BTW. Is this radio the Retevis branded version of the MD-2017, becuase BD4VOW says he will buy a MD-2017, and he can probably dissassemble the radio to try to find the pin mapping from the MCU / CPU
But the pin mapping differences are obviously not just the keypad

[SA0BUX]

OK.
CPS Radio Type MD2017 is the same as MD-380UV and RT-3S

Probably the MCU pin mapping for the keyboard and many other things is different.

Perhasp you can discuss with BD4VOW how to find the pin mapping on this radio, then will probably be able to support it.

BTW. Is this radio the Retevis branded version of the MD-2017, becuase BD4VOW says he will buy a MD-2017, and he can probably dissassemble the radio to try to find the pin mapping from the MCU / CPU
But the pin mapping differences are obviously not just the keypad

Yes , it seems to be mostly different pin mapping compared to RT84.

I found out that the flickering display light is related to the volume control setting.

I think I found out some keys that control options and squelch and power level, and I think that most of the number keys is correct.

But it's worse that both TX and RX control pins seems completely different.

[SA0BUX]

I would not advise at the moment that you install the UV380 or DM1701 firmware on the 2017 until we know which pins control the PA.
Because it may be possible to enable both Tx and Rx at the same time and damage the radio

Hopefully BD4VOW will be able to provide MCU pin mapping for this radio, becuase its not easy to reverse engineer the hardware, even if you open the radio and attempt to 'buzz' the connnections to the various chips, as it is difficult to know where the PA control transistors etc are located

We don't have a schematic for the UV380, we worked from the MD380 schematic and other information on the web about the UV380

Possibly TYT may give the pin mapping if they think it would sell more radios.

Yes, I understand that it may be very risky using wrong firmware on it.
Spent some time today flashing it back to Retevis version 4.15 and it is probably not working 100% anymore, DMR seems to behave strange in TX.
Doesn't matter so much as it's a radio I don't use, the little joystick is so annoying, I prefer the RT84 even if that one has cheaper built quality.

[VK3KYY]

OK.

I sure we will be able to support the MD-2017 when we know how the MCU pins are connected

[SA0BUX]

I would not advise at the moment that you install the UV380 or DM1701 firmware on the 2017 until we know which pins control the PA.
Because it may be possible to enable both Tx and Rx at the same time and damage the radio

Hopefully BD4VOW will be able to provide MCU pin mapping for this radio, becuase its not easy to reverse engineer the hardware, even if you open the radio and attempt to 'buzz' the connnections to the various chips, as it is difficult to know where the PA control transistors etc are located

We don't have a schematic for the UV380, we worked from the MD380 schematic and other information on the web about the UV380

Possibly TYT may give the pin mapping if they think it would sell more radios.

Yes, I understand that it may be very risky using wrong firmware on it.
Spent some time today flashing it back to Retevis version 4.15 and it is probably not working 100% anymore, DMR seems to behave strange in TX.
Doesn't matter so much as it's a radio I don't use, the little joystick is so annoying, I prefer the RT84 even if that one has cheaper built quality.

Seems to work better to my hotspot now after I calibrated the frequencies, I can't find that I ever saved the calibration for this RT82 but I had to lower the values around 10 steps as the radio frequency was a bit high.
But other calibration values looked decent , I guess that it would look more random if the calibration area had been corrupt.

[yo8sct]

I had the same problems when installing the firmware on RT82.

73 de YO8SCT