New MD-UV380 or RT3S

1DangerMouse
Posts: 20
Joined: Sun May 03, 2020 12:31 am

Re: IMPORTANT. New MD-UV380 or RT3S are not compatible

Post by 1DangerMouse » Tue Feb 14, 2023 9:02 am

EA5JAQ wrote:
Mon Feb 13, 2023 10:05 am
I'm gonna buy another of this radios in case the newer ones never get supported. Does anyone know if this problem is present too with the MD-UV390 (not 380) GPS version? I suppose it is, as internally they are the same radio, but I hope they are using older stock for the 390. I just asked the seller for the serial number and production date before buying it.

I'm gonna try to get a working one, but if I get a radio with the clone chip and I can't return it, I'll just attach my JLink and help out solving the issue, hoping it's an easy one. For me it's useless anyway without the custom firmware.
Hi, I got two ST Linker if it’s easy etc I’d be keen on help etc. But will need the information etc to do it.

VK3KYY
Posts: 7478
Joined: Sat Nov 16, 2019 3:25 am
Location: Melbourne, Australia

Re: IMPORTANT. New MD-UV380 or RT3S are not compatible

Post by VK3KYY » Tue Feb 14, 2023 9:39 am

1DangerMouse wrote:
Tue Feb 14, 2023 9:02 am
Hi, I got two ST Linker if it’s easy etc I’d be keen on help etc. But will need the information etc to do it.
Its not easy unless you have experience in programming and using an in circuit debugger
It also involves opening the radio and soldering debugging wires to pads on the PCB.

EU1AEQ
Posts: 141
Joined: Sat Jan 30, 2021 7:25 pm

Re: IMPORTANT. New MD-UV380 or RT3S are not compatible

Post by EU1AEQ » Tue Feb 14, 2023 10:55 am

And where to get the settings data that are available in the engineering menu on the original firmware? After replacing the processor and programming it, will this information be lost?

G4EML
Posts: 919
Joined: Sat Nov 16, 2019 10:01 am

Re: IMPORTANT. New MD-UV380 or RT3S are not compatible

Post by G4EML » Tue Feb 14, 2023 11:53 am

On the STM32 based radios the calibration information is saved in the secure area of the Flash memory chip. So changing the processor won't affect this.

EA5JAQ
Posts: 86
Joined: Thu Jul 16, 2020 6:08 am

Re: IMPORTANT. New MD-UV380 or RT3S are not compatible

Post by EA5JAQ » Tue Feb 14, 2023 1:22 pm

EU1AEQ wrote:
Mon Feb 13, 2023 1:16 pm
Yes, a colleague got such an instance of UV390. Released in December 2022.
Hope that doesn't happen to me :( I contacted the seller and the serial number starts with 2203, so I hope it's old stock and it's compatible. We'll see when I get it :cry:

PU2PWR
Posts: 17
Joined: Mon Feb 14, 2022 5:55 pm

Re: IMPORTANT. New MD-UV380 or RT3S are not compatible

Post by PU2PWR » Tue Feb 14, 2023 8:49 pm

unfortunately we can't count on the serial number... photo sent by a friend yesterday 02/13/2023

PU2PWR
Posts: 17
Joined: Mon Feb 14, 2022 5:55 pm

Re: IMPORTANT. New MD-UV380 or RT3S are not compatible

Post by PU2PWR » Tue Feb 14, 2023 8:51 pm

PU2PWR wrote:
Tue Feb 14, 2023 8:49 pm
unfortunately we can't count on the serial number... photo sent by a friend yesterday 02/13/2023
I can't post image

N6IJK
Posts: 3
Joined: Tue Dec 20, 2022 4:03 pm

Re: IMPORTANT. New MD-UV380 or RT3S are not compatible

Post by N6IJK » Wed Feb 15, 2023 4:27 am

Today I received two new MD-UV380s from Amazon stock. Both radios took the firmware with no issues. Not sure how many more they have. I'm happy they had enough as this makes three, I've bought in the last month.

EU1AEQ
Posts: 141
Joined: Sat Jan 30, 2021 7:25 pm

Re: IMPORTANT. New MD-UV380 or RT3S are not compatible

Post by EU1AEQ » Thu Feb 16, 2023 8:14 am

G7JIQ wrote:
Thu Feb 16, 2023 6:46 am

Has anyone any ideas.
1. It is necessary to write down the codeplag for the factory firmware.
2.Try to turn on the radio station with the button pressed on the left under PTT.

VK3KYY
Posts: 7478
Joined: Sat Nov 16, 2019 3:25 am
Location: Melbourne, Australia

Re: IMPORTANT. New MD-UV380 or RT3S are not compatible

Post by VK3KYY » Thu Feb 16, 2023 9:03 am

Anyone with one of these new UV380 / RT3S radios, who has programming experiece, and would like to try to debug the problem themselves

See viewtopic.php?f=19&t=2662

Post Reply