MTCD - Verified Cross compatible MCUs

Search This thread

TOMMYX2

Senior Member
Oct 17, 2010
83
15
near Munich

typos1

Senior Member
Apr 3, 2007
9,381
1,680
UK
looking for my Original MTCD KLD V2.59 Mcu Image,because with other Mcus i get always Version Unmatch Error.
And with my Mcu Config File from 2.59 its all working ok,but after a full Reset its the Unmatch Error back and all my Mcu Settings are lost:confused:.

My Radio is Pumpkin:
http://www.autopumpkin.de/pumpkin-7-zoll-double-din-android-6-0-universal-autoradio-multimedia-player-mit-gps-navigation-unsterstutzt-bluetooth-octa-core-ram-2gb-rom-32gb.html

Pumpkin are sellers only, your radio is a Klyde unit, hence the "KLD" in the MCU, have you read the whole thread ?
 

TOMMYX2

Senior Member
Oct 17, 2010
83
15
near Munich
Pumpkin are sellers only, your radio is a Klyde unit, hence the "KLD" in the MCU, have you read the whole thread ?
yes and have you read my post?I get Unmatched Error.
I have found now KLD V2.50 here in the Forum,and all working again.
i Have test it with HA MCUS,LM and othe Mcus for MTCD Unit and i get always a Unmatched Error,thats not cross Compatible:crying:
 
Last edited:

chris4507

Senior Member
May 4, 2013
78
14
yes and have you read my post?I get Unmatched Error.
I have found now KLD V2.50 here in the Forum,and all working again.
i Have test it with HA MCUS,LM and othe Mcus for MTCD Unit and i get always a Unmatched Error,thats not cross Compatible:crying:
Please can you point me in the direction of the kld mcu as i screwed up i flashed ha mtce and says virsion unmatch in red on screen so i flashed ha mtcd still the same so i need kld to go back normal
 

excessdivide

Member
Mar 7, 2007
24
4
Per @marchnz suggestion I am moving this discussion here from its original posting (https://forum.xda-developers.com/showpost.php?p=74187608&postcount=2125)

Hello everyone,

Big thanks to the heavy hitters here that are making these units actually usable!

I received my Dasaita HA5217-V600 two weeks ago and thanks to having previously scoured these forums, I was able to install it, in my 2016 Toyota Corolla, with relative ease. Everything worked better than expected, and I had great bluetooth sound, strong WiFi connections, my door and A/C controls appeared on screen, my SWC all matched and decent FM reception. My bluetooth OBDII adapter is arriving this week so I'll have to report back on that.

I have been perplexed by my inability to use my A2DP stream anywhere other than the very generic A2DP widget included in the ROM. After a week of toying with it I became bold enough to attempt Makaysk's ROM and the install went beautifully. (Thanks Malaysk!) I was still limited to that widget however. So I when I saw the new MCTE 2.65f MCU update I gave that a try also. Except I goofed up. I somehow, (really not sure how I did this) downloaded and installed a GS MCU update instead of the HA update. As has been previously documented the update worked, but I lost the use of my capactive panel buttons. They no longer react to touch though the option to control their lighting still appeared in the settings menu and they did still light up on headlight activation which proves that the unit could still control them. The panel button reset screen in factory settings is now blank and does not list any keys at all. Once I caught my mistake I quickly updated to the correct HA MCTE 2.65f MCU update. However my panel buttons are still dead to the touch, and now they don't even light up or have the option to change their LED control mapping in the setting menu and the panel reset screen in the factory settings is still blank.

I actually tried to go back to HA MCU 2.60 which what shipped on my unit. The same issue persists. Upgraded back to MCTE HA MCU 2.65f and nothing has changed.

It's so frustrating that one MCU so easily changed the setting and now the original can't seem to restore it.

I have attached pics of the original software and the updated software, as well as the blank panel reset screen.

Any help in getting my panel buttons back would be much appreciated!

Thanks gang!

Updated MCU:
https://1drv.ms/i/s!AsfQ9pSp8e6FrUtCFUB80zQpFXJa

Original MCU:
https://1drv.ms/i/s!AsfQ9pSp8e6FrUrVnLzROkXFqMUv

Blank Panel Reset screen:
https://1drv.ms/i/s!AsfQ9pSp8e6FrUx08tiRzB_CBZJR
 
Last edited:
Oct 8, 2017
12
8
Per @marchnz suggestion I am moving this discussion here from its original posting (https://forum.xda-developers.com/showpost.php?p=74187608&postcount=2125)

Hello everyone,

Big thanks to the heavy hitters here that are making these units actually usable!

I received my Dasaita HA5217-V600 two weeks ago and thanks to having previously scoured these forums, I was able to install it, in my 2016 Toyota Corolla, with relative ease. Everything worked better than expected, and I had great bluetooth sound, strong WiFi connections, my door and A/C controls appeared on screen, my SWC all matched and decent FM reception. My bluetooth OBDII adapter is arriving this week so I'll have to report back on that.

I have been perplexed by my inability to use my A2DP stream anywhere other than the very generic A2DP widget included in the ROM. After a week of toying with it I became bold enough to attempt Makaysk's ROM and the install went beautifully. (Thanks Malaysk!) I was still limited to that widget however. So I when I saw the new MCTE 2.65f MCU update I gave that a try also. Except I goofed up. I somehow, (really not sure how I did this) downloaded and installed a GS MCU update instead of the HA update. As has been previously documented the update worked, but I lost the use of my capactive panel buttons. They no longer react to touch though the option to control their lighting still appeared in the settings menu and they did still light up on headlight activation which proves that the unit could still control them. The panel button reset screen in factory settings is now blank and does not list any keys at all. Once I caught my mistake I quickly updated to the correct HA MCTE 2.65f MCU update. However my panel buttons are still dead to the touch, and now they don't even light up or have the option to change their LED control mapping in the setting menu and the panel reset screen in the factory settings is still blank.

I actually tried to go back to HA MCU 2.60 which what shipped on my unit. The same issue persists. Upgraded back to MCTE HA MCU 2.65f and nothing has changed.

It's so frustrating that one MCU so easily changed the setting and now the original can't seem to restore it.

I have attached pics of the original software and the updated software, as well as the blank panel reset screen.

Any help in getting my panel buttons back would be much appreciated!

Thanks gang!

Updated MCU:
https://1drv.ms/i/s!AsfQ9pSp8e6FrUtCFUB80zQpFXJa

Original MCU:
https://1drv.ms/i/s!AsfQ9pSp8e6FrUrVnLzROkXFqMUv

Blank Panel Reset screen:
https://1drv.ms/i/s!AsfQ9pSp8e6FrUx08tiRzB_CBZJR

Hi, marchnz.

The painel buttons configuration screen is like the steering wheel screen. There, press any button of painel to configurate its function.
 
Oct 8, 2017
12
8
Except the screen does not list Any buttons. That is why I am asking for advice. See the last picture included in OP.

That's normal. I saw the picture.
That's already happen to me and I also didn't know how to solve because the list didn't appear.
Only press the physical or capacitive buttons, then will appear the list of commands to choose.
Only after buttons configured they will appear in the list of your last image.
I hope you understood. If not you can call me here again.
 

excessdivide

Member
Mar 7, 2007
24
4
That's normal. I saw the picture.
That's already happen to me and I also didn't know how to solve because the list didn't appear.
Only press the physical or capacitive buttons, then will appear the list of commands to choose.
Only after buttons configured they will appear in the list of your last image.
I hope you understood. If not you can call me here again.

Thank you. I appreciate you trying to help. Even if I touch the physical capacitive buttons in the Panel button reset screen under factory settings nothing happens. The buttons no longer light up either and the option to control their Led color, or when they light up is also missing which makes me believe that the firmware isn't configured to see them.
 
Oct 8, 2017
12
8
Thank you. I appreciate you trying to help. Even if I touch the physical capacitive buttons in the Panel button reset screen under factory settings nothing happens. The buttons no longer light up either and the option to control their Led color, or when they light up is also missing which makes me believe that the firmware isn't configured to see them.

I see. That's very strange. When I tryed to chance my MCU to a HA version on my GS head unit I also had problems, including the panel lights were off. I didn't remember if I tryed other things, but I remeber that I turned back to GS MCU and changed the light options on factory settings, but it's not works at the first time. Only after I rebooted the HU it works again. Try this or install the stock MCU again. Try to install the stock rom too.

---------- Post added at 05:00 PM ---------- Previous post was at 04:31 PM ----------

Thank you. I appreciate you trying to help. Even if I touch the physical capacitive buttons in the Panel button reset screen under factory settings nothing happens. The buttons no longer light up either and the option to control their Led color, or when they light up is also missing which makes me believe that the firmware isn't configured to see them.

excessdivide,

my bad. Sorry. I tryed right now to simulate the configuration on my HU and remembered why I had problems. Instead to press in touch key study instead in pannel key study. Will ask to press on the corners to configurate the screen, then will ask to press the capacitive buttons and to choose each function.
 

excessdivide

Member
Mar 7, 2007
24
4
I see. That's very strange. When I tryed to chance my MCU to a HA version on my GS head unit I also had problems, including the panel lights were off. I didn't remember if I tryed other things, but I remeber that I turned back to GS MCU and changed the light options on factory settings, but it's not works at the first time. Only after I rebooted the HU it works again. Try this or install the stock MCU again. Try to install the stock rom too.

---------- Post added at 05:00 PM ---------- Previous post was at 04:31 PM ----------



excessdivide,

my bad. Sorry. I tryed right now to simulate the configuration on my HU and remembered why I had problems. Instead to press in touch key study instead in pannel key study. Will ask to press on the corners to configurate the screen, then will ask to press the capacitive buttons and to choose each function.

Wow! That's was beyond what I expected anyone else to do! Thank you so much!

Sadly, after I configured the touch screen. It simple took me back to the key study main screen.

But really, thank you for your efforts!
 

excessdivide

Member
Mar 7, 2007
24
4
I got it to work! I started incrementally installing Stock ROMS in descending order until I found one that worked.
I had to go back to this MCU/ROM:
-V2.56 --> https://www.sendspace.com/pro/dl/tjnkwj

Then after resetting the touch panel it did take me to the option to remap the panel buttons, and now their LED controls also appear again!

Thanks you soooooo much! that was driving me crazy!!

These units have their quirks but if you can work through them, it is well worth it!
 
  • Like
Reactions: marchnz

ZeroZorro

Senior Member
Nov 24, 2008
645
121
Here it is: https://gerbenbol.com/android/dmcu.cfg

For others, this is my GS config. Use at own risk.
Thanks, wil try this and hope it will solve some issues I have like device leds on when lights off and visa versa. Also canbus signals are not all read (reverse camera works when shifted into reverse but no alarm sounds when reversing).
Fingers crossed!

Sent from my Z1 PRO using Tapatalk
 
  • Like
Reactions: marchnz

marchnz

Senior Member
Nov 26, 2012
3,181
639
wombleton
I got it to work! I started incrementally installing Stock ROMS in descending order until I found one that worked.
I had to go back to this MCU/ROM:
-V2.56 --> https://www.sendspace.com/pro/dl/tjnkwj

Then after resetting the touch panel it did take me to the option to remap the panel buttons, and now their LED controls also appear again!

Thanks you soooooo much! that was driving me crazy!!

These units have their quirks but if you can work through them, it is well worth it!

Great to hear. Can you clarify, was Touch panel [RESET] tested in each MCU test, or only when v2.56 was applied? Also which manufacturer MCU v2.56 was applied?
 

excessdivide

Member
Mar 7, 2007
24
4
Great to hear. Can you clarify, was Touch panel [RESET] tested in each MCU test, or only when v2.56 was applied? Also which manufacturer MCU v2.56 was applied?


I was incrementally working my way through the HA MCU's. I did test the panel reset buttons after each MCU update. Interestingly enough, after I had reprogrammed them, it took 2 reboots to get the Element light option to appear in the factory settings. But everything seems to be working fine now.

I am still annoyed by how restricted the a2dp stream is. I had expected to be able to see and control a2dp stream from anywhere in the system. Alas, I am limited to that a2dp widget which is really bare.

Thanks again gang!
 

typos1

Senior Member
Apr 3, 2007
9,381
1,680
UK
Interestingly enough, after I had reprogrammed them, it took 2 reboots to get the Element light option to appear in the factory settings. But everything seems to be working fine now.

Yes the same applies to MTCB/C units when switching to RGB LEDs in factory settings they need several reboots for Element to show up.
 

faria

Inactive Recognized Developer / Retired Senior Mod
Feb 24, 2006
2,915
770
45
Jersey
some info about MTCE MCU

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
 
Last edited:

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