MTCD - Verified Cross compatible MCUs

Search This thread

csitkiri

Member
Oct 14, 2017
29
5
Hy!
Which one would go up in this direction?

A media auto 1024X600
Android: 6.0.1
2016.06.01
SF3GR_M-26-3_cpeg_rk-r2p_bc2-20160629_111639
Kernel:3.14.0+
[email protected]#15
Build:sofia3gr_car_64-userdebug 6.0.1 MMB29M eng.hct.20170705.123915 release key
MCU:
MTCD_LM_V2.55_1
Jun 23 2017 13:42:21
HCT2000022096
Thank you!
 

bettuccio

Senior Member
Apr 13, 2010
606
94
Italy
The new mtce mcus are from the new Rockchip PX3 Cortex A9, 4-core 1.6GHz updated boards running android 7.1.
One of the manufactures using it is WITSON .
Here is an example of my unit : mcu MTCE_MX_V2.65.1 (Please note that THE ABOVE also shows up as an MTCD_MX mcu depending on android version.

The same unit with the old board (Rockchip 64bit RK3368 Octa-core ARM Cortex-A53) Would have have an mcu version : MTCD_MX_V.x.x.x

Very interesting. I would try the MCU MTCE MX 2.65.1 that you have. I have a PX5 with MCU MX MTCD native. Where can I find it? Currently I am with a MTCE HA 2.65.
 

typos1

Senior Member
Apr 3, 2007
9,381
1,680
UK
The new mtce mcus are from the new Rockchip PX3 Cortex A9, 4-core 1.6GHz updated boards running android 7.1.
One of the manufactures using it is WITSON .
Here is an example of my unit : mcu MTCE_MX_V2.65.1 (Please note that THE ABOVE also shows up as an MTCD_MX mcu depending on android version.

The same unit with the old board (Rockchip 64bit RK3368 Octa-core ARM Cortex-A53) Would have have an mcu version : MTCD_MX_V.x.x.x

No, the MCU has nothing to do with the processor board - the Intel Sofia units use the same MCUs, the MCU and processor are entirely separate - I have a 2Gb ERAM Nougat RK3188/PX3 unit with an MTCD MCU, indeed most of the units with these boards started out with MTCD MCUs.

ALL MTCD units, using ANY processor can be upgraded to MTCE MCUs.

Witson ARE NOT manufactures, they are sellers.
 
Last edited:

arti777

Member
Sep 18, 2017
17
2
Mtcd_kld_v2.57

I confirm my MTCD_kld V2.57 to (MTCE mcu kld 2.65d)
PX5 rk3066 octa core [email protected] 2GB Honda Accord dual air, Steering wheel working super, nothing changed about my doors still I not see on my android screen just the small screen left for me under the counters (cloks)
I just reset the steering wheel and everything works fine. There is only a problem with Poweramp graphic equalizer - if I do turn it on instead of giving it a louder, on the radio playing normally.
 

Oberbergler

Senior Member
May 26, 2015
207
47
After some time with the HA MTCE MCU on my GS unit I recommend to any GS user to NOT install any HA MCU. My unit started yesterday to have some trouble with the HA MCU. First it didn`t boot anymore, it took about 10 secs to switch to the reversing camera, there was no more boot logo and all MCU settings were gone. The screen was reversed by the x-axis. When I tried to install the GS MCU and restore the GS cfg the unit hang up and didn`t do anything anymore. The screen was on from midday until I came back at the evening and my cars battery was totally empty. I had to unplug the unit and reinstall the GS MCU. Now everything is working but I am not able anymore to let disappear the MCU version unmatch error, even with the original MCU.
 

faria

Inactive Recognized Developer / Retired Senior Mod
Feb 24, 2006
2,915
770
45
Jersey
Very interesting. I would try the MCU MTCE MX 2.65.1 that you have. I have a PX5 with MCU MX MTCD native. Where can I find it? Currently I am with a MTCE HA 2.65.
I dont have to share, its in the unit, i'm waiting for the seller to send the Rom/mcu.
No playing with it until i have a backup rom:D
 

bettuccio

Senior Member
Apr 13, 2010
606
94
Italy
I dont have to share, its in the unit, i'm waiting for the seller to send the Rom/mcu.
No playing with it until i have a backup rom:D

When you're in possession, please post it. Thank you.
you can back up the MCU configurations. As Typos1 has said, there are many firmware and MCUs to be able to restore.
 
Last edited:

MrWaloo

Member
Oct 23, 2017
6
1
Altkirch
No, the MCU has nothing to do with the processor board - the Intel Sofia units use the same MCUs, the MCU and processor are entirely separate - I have a 2Gb ERAM Nougat RK3188/PX3 unit with an MTCD MCU, indeed most of the units with these boards started out with MTCD MCUs.

ALL MTCD units, using ANY processor can be upgraded to MTCE MCUs.

Witson ARE NOT manufactures, they are sellers.

Since I have sound problem with my (Erisin ES3715V) PX3 MTCD_LM_V2.55_1 with the radio, does this mean that I can update to any MTCE_????
 

typos1

Senior Member
Apr 3, 2007
9,381
1,680
UK
Since I have sound problem with my (Erisin ES3715V) PX3 MTCD_LM_V2.55_1 with the radio, does this mean that I can update to any MTCE_????

You can update to an MTCE MCU from your manufacturer, if you cant find any then check the "Cross Compatible MUCs" thread. It may fix your sound problem, it may not.
 
  • Like
Reactions: MrWaloo

xxfOxx

Member
Dec 16, 2012
39
3
Version Unmatch

Who know how to fix "Version Unmatch" error :( ?
From start I have unit with KLD 2.59_1 and I update it with Android HA (20170901 as I remember) + HA MCU ( so now I get error Version Unmatch at any firmware + KLD mcu. Error gone away when I update unit with HA mcu but in this case I get non-working FM radio
Can anybody help me ?
 

Attachments

  • Screenshot_20171030-122647.jpg
    Screenshot_20171030-122647.jpg
    123 KB · Views: 364

Kayhan 17#

Senior Member
Oct 14, 2008
60
12
Ulm
I have a 7.1.2 Nougat Radio from Erisin ES4798V, it has a PX3 chip and 2GB Ram according to what i could see in the System Information.
I had previously the MTCD_KGL_V2.60_4 file installed and did an Update to the MTCD_HA_V2.65f_1, then tried installing GS version and back again to the HA version(my android version is now the recent from malaysk).
I have the problem with the "Version Unmatch" message appearing, i must admit that i didnt do any backups of my previous settings but could access a second head unit after i know the factory settings =).
Anyway, does anyone also have an idea where i could find the Stock 7.1.2 Rom which was installed previously or how i could dump it, so in case i want to revert?
Kind Regards
 
Last edited:

typos1

Senior Member
Apr 3, 2007
9,381
1,680
UK
I have a 7.1.2 Nougat Radio from Erisin ES4798V, it has a PX3 chip and 2GB Ram according to what i could see in the System Information.
I had previously the MTCD_KGL_V2.60_4 file installed and did an Update to the MTCE_HA_V2.65f_1, then tried installing GS version and back again to the HA version(my android version is now the recent from malaysk).
I have the problem with the "Version Unmatch" message appearing, i must admit that i didnt do any backups of my previous settings but could access a second head unit after i know the factory settings =).
Anyway, does anyone also have an idea where i could find the Stock 7.1.2 Rom which was installed previously or how i could dump it, so in case i want to revert?
Kind Regards

The ROM has nothing to do with the MCU, they are entirely separate so it wont make any difference to your MCU problem. Have you read the entire thread and tried all the methods to remove the version unmatch error ? Have you tried other MTCE MCUs ?
 

Kayhan 17#

Senior Member
Oct 14, 2008
60
12
Ulm
The ROM has nothing to do with the MCU, they are entirely separate so it wont make any difference to your MCU problem. Have you read the entire thread and tried all the methods to remove the version unmatch error ? Have you tried other MTCE MCUs ?

i know that the MCU and ROM are different, altough i still would want to know how to revert as the style/Theme of malaysk is not that of my taste

i also read a lot of threads and lost the overview =)
 

marchnz

Senior Member
Nov 26, 2012
3,181
639
wombleton
Who know how to fix "Version Unmatch" error :( ?
From start I have unit with KLD 2.59_1 and I update it with Android HA (20170901 as I remember) + HA MCU ( so now I get error Version Unmatch at any firmware + KLD mcu. Error gone away when I update unit with HA mcu but in this case I get non-working FM radio
Can anybody help me ?

Resolve is in this thread
Version unmatch see this post
 

marchnz

Senior Member
Nov 26, 2012
3,181
639
wombleton
I have a 7.1.2 Nougat Radio from Erisin ES4798V, it has a PX3 chip and 2GB Ram according to what i could see in the System Information.
I had previously the MTCD_KGL_V2.60_4 file installed and did an Update to the MTCD_HA_V2.65f_1, then tried installing GS version and back again to the HA version(my android version is now the recent from malaysk).
I have the problem with the "Version Unmatch" message appearing, i must admit that i didnt do any backups of my previous settings but could access a second head unit after i know the factory settings =).
Anyway, does anyone also have an idea where i could find the Stock 7.1.2 Rom which was installed previously or how i could dump it, so in case i want to revert?
Kind Regards

Version unmatch see this post
 

Oberbergler

Senior Member
May 26, 2015
207
47
No, it worked one week with this method.
Now I have the version unmatch error and the only solution to let it disappear is to install the HA MCU but with the HA MCU the head unit is hanging up once a week. So I have now the same problem how xxfOxx and I think that there is no solution as I´ve tried everything to reset, reininstall, different other MCU versions, older, newer.... There is no solution :/
 

Top Liked Posts

  • There are no posts matching your filters.
  • 7
    This thread is to document MCUs found to be cross-compatible between MTCD units, which includes PX3 and PX5 variants, which share identical mainboard hardware and MCU Chip STM32F091.

    The following MTCD & MTCE (as of v2.56) MCUs have been validated as cross compatible on 1024x600 units:
    - MLT - 01/07/17 - caution - has resulted in issues for some @leonkernan
    - JY
    - KBT - 08/12/2017 - thanks @abagos
    - KD (v2.40_2 - enables bluetooth hands free in both front speakers)
    - KGL
    - KSP thanks @Overmann
    - GS - Note "version unmatch" error and fix below No issue experienced on MTCE going from JY 2.80 to GS 2.78 and back to HA 2.80 - March 2018
    - GS compatible on MX (see post #513)
    - HA (v2.56 06/07/17 - note v2.52 on enables "shutdown delay when acc off" menu) HA MTCE (30/09/17) V2.65 https://www.sendspace.com/pro/dl/ufie8k
    See this thread for pics where MCU HA and KD has been applied on JY. https://forum.xda-developers.com/showpost.php?p=72737797&postcount=640

    I initially upgraded to KD 2.40, then HA v2.52 after first exporting the MCU settings.
    Note that I had to reapply MCU settings in [factory sertings] to configure radio, LED, bluetooth, hardware keys, volume levels between radio, bluetooth, system etc.

    MCUs were previously thought to be manufacturer specific - e.g. HA, JY, GS, KD, however I have found that they are compatible and of interest where there is either a specific issue with your MCU (e.g. bluetooth out of one speaker, to enable PX5 sleep mode control) or the vendor has long ceased to support & release updates - such as JY.

    MCU cross-compatibility became of interest to me when I upgraded my JY [MCU v2.06_2] PX3 with a HCT PX5 SOM and wanted to enable the MCU specific menu item [shutdown delay when ACC off] to control sleep as found on HA/Dasaita.

    I first noted that from an XDA post listing JY an KD v2.06_2 being identical and on that assumption, upgraded to KDv2.40_2, which successfully applied - but had to reconfigure factory settings.
    Following on, I found a post which has an image of a GS board & MCU chip - noted it was identical to the MTCD JY MCU chip [STM32F091] - then came across a post where a user had inadvertently applied a MTCD GS MCU to a MTCD JY without bricking it.

    I then started comparing same version number firmware files from various manufacturer MCUs with a text compare tool. From this work, I had enough info to compare the latest HA v2.52 and conclude it 'should' be compatible. Indeed it is.

    As always, check first (suggest confirming MTCD, MCU Chip part number, view/compare the fw files, ensure you have original MCU FW, backup MCU settings or document the settings to ensure your hardware controls, volume control, bluetooth, radio, canbus etc are setup correctly). Apply at your own risk.

    Please post your results and I will update this thread.
    Updates:
    UPDATE: 26/06/2017 Users of 800x480 Users must also apply file[dmcu.ext], a text file containing:
    For PX3 --> screen:3
    For PX5 --> screen:1


    01/07/17 - MLT
    06/07/17 - KGL confirmed and new HA v2.56
    30/09/17 - MTCE MCU confimed compatible
    08/03/18 - MTCE JY/GS/HA compatible - No issue experienced on MTCE going from JY 2.80 to GS 2.78 and back to HA 2.80

    GS Specific Notes:
    For all those with a GS: Our unit is compatible with the MTCE MCU but you have to restore your settings and maybe to manually reconfigure your touchscreen and buttons. There is a simple function to do this in the factory settings (126) which is called key study. My touchscreen was also swapped by the x axis. I had to go with the swapped touchscreen into the settings, configure it, reboot the unit and everything was fine. For the buttons you have also the possibility to use short press and long press buttons, which is great because our units (at least mine) has only five buttons and no return button. So I use now the power off button as return in short press mode and power off in long press :)

    Version unmatch see this post where user resolved by reapplying MCU AND Software APK Fix Here
    - Attached Version Unmatch APK fix to this post, thanks @Wadzio

    GS Configuration Settings file:

    Do not dilute this thread by posting "how-to" questions such as - how do I update the MCU, what unit do I have, can I do it, how do I find factory settings, etc. This thread is to document cross-compatible MCUs and the fixes they apply.
    3
    KD --> HA for 800x480 Screen

    I have had quite an experience over the weekend, but am able to report successfully updating a PX3 MTCD_KD unit to a PX5 with the HA2.52 MCU Code.

    For those of us with 800x480 screen sizes, as now noted in the main thread, we need to create the dmcu.ext file with the appropriate screen size to be flashed with the dmcu.img file.

    Just a note that if you run across the issue of not having the appropriate resolution; don't freak out.

    One interesting note I hadn't mentioned before is that after the PX5 started thinking it was 1024, I replaced it with the PX3. The PX3 booted thinking it was 1024 also. After reverting the PX3 to 800 (flashing with screen:3), I replaced the PX5. The PX5 however, did not revert back to 800, but remained at 1024. The PX5 did not revert back to 800 until after I reflashed the MCU, specifically stating it was to be 800 (screen:1).
    2
    I can confirm a cross compatibility as well.

    My Unit is a xtrons device with die MCU firmware GS 2.43 and yesterday i did flash the HA 2.52. But be sure to save your mcu config first. Otherwise the hardware buttons won't do what they were supposed to do. But after flashing the firmware and restoring the config, everything is back to normal.
    2
    Hi, thanks, I have added to post #1. Do you have a screen shot I can add?
    I only have after installing it. Its px3, I'm waiting to px5 board to update it.
    2
    Some time ago I tried to investigate what actually those abbrevations mean. In my understanding GS, JY, HA is related to the canbus profiles, not directly to the reseller. It seems to be reasonable because MCU has really tiny flash capacity and add all canbus configurations to one chip would be impossible.

    No, you are wrong there - the letters very definitely relate to the manufacturer, NOT the CAN Bus profiles KLD = "Klyde" KGL, = "Kai Ge Le", JY = "Joyous" etc, this has been established for years.

    The seller has NOTHING to do with the software at all.

    The CAN Bus profiles are named in factory settings

    On MTCB/C headunits there was a slight difference in the code between MCU types so they were not interchangeable (apart from BN and HA), it would seem that on MTCD units there is no such variation in the code.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone