New MD-UV380 or RT3S
Posted: Wed Jan 25, 2023 10:03 pm
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