New MD-UV380 or RT3S
New MD-UV380 or RT3S
Edit. We now have experimental firmware which we think fixes this problem
-------------------- Orginal post ---------------------------------
VE2NCK is currently unable to install the firmware onto some brand new non-GPS RT3S radios.
VK2NCK kindly opened his radio and took a photo of the CPU chip
And its clear that TYT are no longer fitting the same CPU chip, because the new chip has no markings
VK2NCK has assured me that there are no markings on the CPU chip at all, and its not just that the markings do not appear in the photo
I have been able to send a debug application to VK2NCK which was able to display the CPU Device ID and Revision ID onto the screen, and the CPU reports the correct Device ID of 0x0413 (1043 decimal), but the Revision ID of 9 is not a valid STM revision ID
My radio has revision ID 0x1007 (Decimal 4103) which is listed as "Revision 1" on some websites
The chip is likely to be a non-identical clone of the STM32F405 CPU which is normally fitted in this radio, and its not 100% compatible with the official STM development enviroment and low level code libraries which we use for the OpenMDUV380 firmware
The problem appears to be that the RealTime Operating System, RTOS (FreeRTOS), crashes and hangs when its started.
But the only way to debug these sorts of problems, is to use a hardware debugger dongle directly soldered to the debug points on the PCB.
And as I don't have one of these new radios, and also don't have the time or money to buy and then debug the problem.
Currently this new version can not be supported
-------------------- Orginal post ---------------------------------
VE2NCK is currently unable to install the firmware onto some brand new non-GPS RT3S radios.
VK2NCK kindly opened his radio and took a photo of the CPU chip
And its clear that TYT are no longer fitting the same CPU chip, because the new chip has no markings
VK2NCK has assured me that there are no markings on the CPU chip at all, and its not just that the markings do not appear in the photo
I have been able to send a debug application to VK2NCK which was able to display the CPU Device ID and Revision ID onto the screen, and the CPU reports the correct Device ID of 0x0413 (1043 decimal), but the Revision ID of 9 is not a valid STM revision ID
My radio has revision ID 0x1007 (Decimal 4103) which is listed as "Revision 1" on some websites
The chip is likely to be a non-identical clone of the STM32F405 CPU which is normally fitted in this radio, and its not 100% compatible with the official STM development enviroment and low level code libraries which we use for the OpenMDUV380 firmware
The problem appears to be that the RealTime Operating System, RTOS (FreeRTOS), crashes and hangs when its started.
But the only way to debug these sorts of problems, is to use a hardware debugger dongle directly soldered to the debug points on the PCB.
And as I don't have one of these new radios, and also don't have the time or money to buy and then debug the problem.
Currently this new version can not be supported
Re: Possibly not compatible with new Non-GPS MD-UV380 or RT3S
I confirm that retevis rt 3s no gps does not install the firmware.After downloading the firmware, the screen turns black and does not respond to any actions. Only the installation of the official firmware helps.
Re: Possibly not compatible with new Non-GPS MD-UV380 or RT3S
Please can you post the first part of the serial number of the radio that would not work.
The firmware certainly works on my RT3S Non-GPS radio with a serial number starting 2201.
Colin G4EML
The firmware certainly works on my RT3S Non-GPS radio with a serial number starting 2201.
Colin G4EML
Re: Possibly not compatible with new Non-GPS MD-UV380 or RT3S
The walkie-talkie is no longer on hand. It was purchased in the second half of December 2022. TYT md uv 380gps was purchased.
Re: Possibly not compatible with new Non-GPS MD-UV380 or RT3S
I have a non GPS rt3s arriving shortly, dunno the serial yet but I will notify here.
Re: Possibly not compatible with new Non-GPS MD-UV380 or RT3S
Strange,
I've purchased mine on Dec 22th from Retevis official store on aliexpress.
This is nonGPS model.
Opengd77 works well on this rig,
EDIT:
S/N 2105R03S*******
I've purchased mine on Dec 22th from Retevis official store on aliexpress.
This is nonGPS model.
Opengd77 works well on this rig,
EDIT:
S/N 2105R03S*******
Last edited by SP5PRZ on Fri Jan 27, 2023 8:46 am, edited 1 time in total.
-
- Posts: 17
- Joined: Sun May 03, 2020 12:31 am
Re: Possibly not compatible with new Non-GPS MD-UV380 or RT3S
I have a RT3S GPS Version and Serial with 22112xxxxxxxxx Its Seemed to Enter DFU Mode All Good and Allow me to upload the Latest Firmware. Then its Just a Blank Black Screen, no sound or anything and Computer Doesn't See it as any Com Port. All I Can do is revert to Official FW or Enter DFU Only.
Any Suggestions?
Any Suggestions?
Re: Possibly not compatible with new Non-GPS MD-UV380 or RT3S
See my updated first post.1DangerMouse wrote: ↑Thu Jan 26, 2023 11:38 pmI have a RT3S GPS Version and Serial with 22112xxxxxxxxx Its Seemed to Enter DFU Mode All Good and Allow me to upload the Latest Firmware. Then its Just a Blank Black Screen, no sound or anything and Computer Doesn't See it as any Com Port. All I Can do is revert to Official FW or Enter DFU Only.
Any Suggestions?
The photo from VK2NCK and also a debug test application I wrote, confirms that TYT have replaced the CPU in the MD-UV380 / RT-3S with an unknow clone, which is not compatible with the official STM code libraries which the firmware uses.
Currently I do not see a way that uknown CPU's can be supported
Re: IMPORTANT. New Non-GPS MD-UV380 or RT3S are not compatible
Just to add to the available data, I received a new Retevis RT3S GPS Serial 2208R03S1100777 with a date label of 08/2022. It was ordered on Amazon and shipped from Retevis Direct. This radio installed the firmware and operates fine. -Rick
Re: IMPORTANT. New Non-GPS MD-UV380 or RT3S are not compatible
I suppose anyone buying a RT3S or UV380 from now on, needs to check with the vendor first and confirm that its old version with the STM32F407 and not a unknown / clone CPU in it
I doubt the vendor would know what CPU / MCU is in the radio, but at least if it does have the clone chip in it, you have more grounds to return it and get a refund.