MTCD - Verified Cross compatible MCUs

Search This thread

typos1

Senior Member
Apr 3, 2007
9,492
1,740
UK
If no one has tried it in this thread then you ll have to try it yourself, but if you have no problem to solve or no function you want to obtain by changing the MCU to that of another manufacturer, then why bother ?
 
  • Like
Reactions: marchnz

jhony benitez

Senior Member
Mar 9, 2008
55
5
Is there a problem with the current MCU, I don't understand your other remark, you can assign dual actions to buttons, just not canbus buttons without mods.
There is any problem with it, and of course you can assign short and long press, but I've heard there are new MCU firmware that allow double action with short and long press like this
 

marchnz

Senior Member
Nov 26, 2012
4,577
897
NZ
There is any problem with it, and of course you can assign short and long press, but I've heard there are new MCU firmware that allow double action with short and long press like this

Thats not an MCU, it's mtcd-utils. So install mtcd-utils? Or install a ROM with the mod included?

Like I said, you can do just that today, with SWC non-canbus. For canbus, you need to install the rom or mod. You still haven't said if your unit is using canbus or not, but either way, an MCU won't help you.
 
Last edited:
  • Like
Reactions: jhony benitez

jhony benitez

Senior Member
Mar 9, 2008
55
5
Thats not an MCU, it's mtcd-utils. So install mtcd-utils? Or install a ROM with the mod included?

Like I said, you can do just that today, with SWC non-canbus. For canbus, you need to install the rom or mod. You still haven't said if your unit is using canbus or not, but either way, an MCU won't help you.
Understood and clear.... my unit isn't canbus I will try to do it with mtcd-utils
Thanks!!!
 

chnasir44

Member
Jul 28, 2021
5
0
Dear i need your help for upgrading relevant mcu and latest android
WhatsApp Image 2021-07-28 at 6.25.40 PM (1).jpeg
WhatsApp Image 2021-07-28 at 6.25.40 PM.jpeg
WhatsApp Image 2021-07-28 at 6.26.50 PM.jpeg

 

moreno_cos

Senior Member
Dec 17, 2011
67
3
How can I check if my px3 unit has a MCU Chip STM32F091 chip??

My auto radio version is:
px3-userdebug 7.1.2 NHG47L eng.hct20180
MTCE_XRC_V2.80_1
2Gb/ 16Gb

I would like update MCU to version MTCE_KGL_V_3.01_5. I have seen in a video that solve my problem.

Thank you very much
 

moreno_cos

Senior Member
Dec 17, 2011
67
3
How can I check if my px3 unit has a MCU Chip STM32F091 chip??

My auto radio version is:
px3-userdebug 7.1.2 NHG47L eng.hct20180
MTCE_XRC_V2.80_1
2Gb/ 16Gb

I would like update MCU to version MTCE_KGL_V_3.01_5. I have seen in a video that solve my problem.

Thank you very much

Can I test/upgrade to MCU KGL or do I run the risk of bricking my radio?

Thank you
 

typos1

Senior Member
Apr 3, 2007
9,492
1,740
UK
You have to read the thread, if you can find someone with an XRC MCU who has successfully changed to a KGL one then yes, if not, you will have to experiment yourself. Make sure you export your config before trying anything.
 

moreno_cos

Senior Member
Dec 17, 2011
67
3
You have to read the thread, if you can find someone with an XRC MCU who has successfully changed to a KGL one then yes, if not, you will have to experiment yourself. Make sure you export your config before trying anything.
Thx, I understand now.

My Original Mcu: MTCE_XRC_V2.80_1

I have installed all of the following MCUs ( 100% compatible) but it has not fixed the problem:
- MTCE_GS_V3.07
- MTCE_GS_V3.17
- MTCE_GS_V3.30
- MTCE_GS_V3.44
- MTCE_GS_V3.62
- MTCE_XRC_V2.84
- MTCE_XRC_V2.89
- MTCE_XRC_V2.94
- MTCE_XRC_V3.01

Hope this can help someone
 

marchnz

Senior Member
Nov 26, 2012
4,577
897
NZ
Thx, I understand now.

My Original Mcu: MTCE_XRC_V2.80_1

I have installed all of the following MCUs ( 100% compatible) but it has not fixed the problem:
- MTCE_GS_V3.07
- MTCE_GS_V3.17
- MTCE_GS_V3.30
- MTCE_GS_V3.44
- MTCE_GS_V3.62
- MTCE_XRC_V2.84
- MTCE_XRC_V2.89
- MTCE_XRC_V2.94
- MTCE_XRC_V3.01

Hope this can help someone
Could posting details of the problem help others to know what you are wanting to solve.
 

moreno_cos

Senior Member
Dec 17, 2011
67
3
Could posting details of the problem help others to know what you are wanting to solve.
My auto radio not working all SWC and not show temperature, doors, avg fuel,... in my alfa romeo 159 car. My version is:
Isudar
px3-userdebug 7.1.2 NHG47L eng.hct20180
MTCE_XRC_V2.80_1
2Gb/ 16Gb

I have seen similar radio working all functions in alfa romeo 159:
Member: warlock_srb
MTCE_KGL_V_3.01_5.

Perhaps, other motherboard, other MCU, other box canbus... I don´t know which is the problem.

thanks again
 

marchnz

Senior Member
Nov 26, 2012
4,577
897
NZ
My auto radio not working all SWC and not show temperature, doors, avg fuel,... in my alfa romeo 159 car. My version is:
Isudar
px3-userdebug 7.1.2 NHG47L eng.hct20180
MTCE_XRC_V2.80_1
2Gb/ 16Gb

I have seen similar radio working all functions in alfa romeo 159:
Member: warlock_srb
MTCE_KGL_V_3.01_5.

Perhaps, other motherboard, other MCU, other box canbus... I don´t know which is the problem.

thanks again
Canbus
 
  • Like
Reactions: moreno_cos

typos1

Senior Member
Apr 3, 2007
9,492
1,740
UK
The CAN Bus decoder is either wired incorrectly (you may need to change some wires or swap some of the plugs on the CAN Bus loom) or the incorrect CAN Bus version is set in factory settings.
 

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
    And did not show a mismatch message on screen?
    Yes but I used the McuUnmatchUnlock.apk
    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.