HI ,
Looking at upgrading MCU My unit is GS so I was going to flash this..
FOR GS
GS v.2.55 with sleep and redesigned sound processor from darkleo - MCU_GS_2.55_Sleep_Musik.rar
Im just a little confused about the following instructions as they talk about resolution, does this apply only when flashing the rom and not the MCU?
BEFORE UPGRADING YOUR UNIT YOU MUST KNOW
MCU your unit, there are many (KGL, KGL1, KGL2, KGL3, KGL4, KGL5, KLD, KLD1, KLD2, JY, GS, KYD, MD, BN, HA, MX), If you install the wrong MCU, you will brick your unit.
To know which one you have. Go to Settings -->About
If still not clear, see: here or here.
If you cannot find it here, it probably means that you are in the wrong thread.
Resolution of your unit. 800x480 or 1024x600. If you install the wrong ROM, you will brick your unit.
Chip of your unit RK3066 or RK3188. It does not really matter, ROMs and MCU are compatible between chips.
Thanks
Does not matter for mcu. Just make sure you use the correct mcu (same letter combo) and you may need to change settings in your factory settings menu for radio. Make note of your old mcu so that you can go back if required
Thanks, I'll try it tomorrow. There is only one available mcu on here for the GS model.
I'll go with that.
I have an Eonon GA2114 - rk3188, 800*480, KLD2 2.77 MCU, BC6B BT board
With the original Eonon ROM bluetooth is unusable. There is no default device name or PIN. If I type in these, they disappear after reboot. It does not detect either phones or OBD, nor is it detected by phones.
With other KLD ROMs bluetooth is active, can be paired to both phones and OBD but all sound is muted during calls (both ways)
With Joying ROMs, including Malaysk, BT works as it should.
This is clearly a software issue, anyone has any clues about where should I start looking? Are these manufacturers using different BT stack implementations maybe?
Anybody can provide a working rk3188 800*480 Eonon ROM? Not the October 19 ROM also available on this forum, that one has the issue described above.
Hi,
I'm facing the same issue, I have an GA5153V device and contacted Eonon about that but hey keep sending me wrong MCU version and ROM. Can You please tell me which MCU version do You have?
It would be great if someone posts working version of Eonon ROM.
Sn00k said:
Hi,
I'm facing the same issue, I have an GA5153V device and contacted Eonon about that but hey keep sending me wrong MCU version and ROM. Can You please tell me which MCU version do You have?
It would be great if someone posts working version of Eonon ROM.
Click to expand...
Click to collapse
My MCU is a KLD2.
I have requested Eonon to send a compatible ROM, even older, but they say it's the only one available. The ROM they are sending id the one available on this forum in the Factory ROM thread. Eonon appear to just brand generic units and have no technical personnel. I gave up getting a competent answer from them. For now I am on Booroondook's ROM, waiting for Joying to release a Lollipop version.
m00n61 said:
waiting for Joying to release a Lollipop version.
Click to expand...
Click to collapse
At present there is no need to have a bugged (and unfixed by Google) Lollipop 5.0.x on these units, Kitkat 4.4.4 is still the best IMHO.
We'll see in the future what will happen with Marshmellow...
m00n61 said:
My MCU is a KLD2.
I have requested Eonon to send a compatible ROM, even older, but they say it's the only one available. The ROM they are sending id the one available on this forum in the Factory ROM thread. Eonon appear to just brand generic units and have no technical personnel. I gave up getting a competent answer from them. For now I am on Booroondook's ROM, waiting for Joying to release a Lollipop version.
Click to expand...
Click to collapse
Since Eonon is keep sending me KLD2 based mcu even I have KLD(MTCB-KLD-v2.78) by default I cannot use this version because FM radio is not working. I said that to them but again they sent me KLD2, the I gave up on them and now trying to fing some solution to make bluetooth to work.
Can You please tell me where did You download current ROM that You are using?
thx!
Sn00k said:
Since Eonon is keep sending me KLD2 based mcu even I have KLD(MTCB-KLD-v2.78) by default I cannot use this version because FM radio is not working. I said that to them but again they sent me KLD2, the I gave up on them and now trying to fing some solution to make bluetooth to work.
Can You please tell me where did You download current ROM that You are using?
thx!
Click to expand...
Click to collapse
MCU and OS ROM image are independent, even if the Chinese keep sending both you can burn only the Android ROM and leave the MCU untouched.
Anyway, I am currently using this ROM. A more detailed installation procedure is in the first post of the thread.
Go to factory settings and adjust the bt module there. Code is 126.
I was seeing the same thing when I found that option and began playing around.
Hi
Someone have at eonon GA5165F for BMW E9X?
I need to know the original configuration for this unit.
Rui tomas said:
Hi
Someone have at eonon GA5165F for BMW E9X?
I need to know the original configuration for this unit.
Click to expand...
Click to collapse
What do you mean by "original configuration" ?
Which head unit manufacturer is it ?
GA5165F BMW 323i E90 2011
typos1 said:
What do you mean by "original configuration" ?
Which head unit manufacturer is it ?
Click to expand...
Click to collapse
I may not be of any help now because I have flashed Malaysk May rom a few days after I received my unit.
I hope we can help each other in the future.
I'm, also, trying to findout WHAT and WHO is MTCB-ZD9-V2.72 ??? Was expecting KGL-790 for a BMW E90.
Here was my Malaysk install comments: http://forum.xda-developers.com/showpost.php?p=67143277&postcount=4486
Thank you all
noise672 said:
I may not be of any help now because I have flashed Malaysk May rom a few days after I received my unit.
I hope we can help each other in the future.
I'm, also, trying to findout WHAT and WHO is MTCB-ZD9-V2.72 ??? Was expecting KGL-790 for a BMW E90.
Here was my Malaysk install comments: http://forum.xda-developers.com/showpost.php?p=67143277&postcount=4486
Thank you all
Click to expand...
Click to collapse
It doesnt matter that you have flashed Malaysk's ROM - I think hes talking about the buttons when he says "configuration" which is MCU controlled not Android. But you still cant help as its not possible to get a copy of the MCU software from a unit.
"ZD9" units have been appearing recently, we dont know the name of the company yet (we may never), but its not that important as long as copies of MCU updates become available, check Malaysk's MCU thread. None there yet.
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:
Oberbergler said:
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
Click to expand...
Click to collapse
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:
Bose321 said:
Here it is: https://gerbenbol.com/android/dmcu.cfg.
Click to expand...
Click to collapse
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.
Hi! Confirmed, I've upgraded to PX5 (JY UL135). Flashed KD2.40 over JY 2.06_2 then flashed HA 2.52 and everything is working as it should be. Thanks for your work.
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.
To make it easier to re-apply the settings, you can use the mcu.cfg function and flash it with the MCU, just in case anyone didnt know.
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.
f1x said:
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.
Click to expand...
Click to collapse
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.
Does this also apply to LM_ (Erisin) MCUs?
I have a Erisin 5048 HU with MCU 2.41_1. Does anyone have any experience in flashing a different MCU to a LM_ type MCU? I´m worried to brick my HU if a flash a higher HA_ version.
Any info would be highly appreciated.
Greetings
Speedycarv
SpeedyCarv said:
I have a Erisin 5048 HU with MCU 2.41_1. Does anyone have any experience in flashing a different MCU to a LM_ type MCU? I´m worried to brick my HU if a flash a higher HA_ version.
Any info would be highly appreciated.
Greetings
Speedycarv
Click to expand...
Click to collapse
There are no "Erisin" MCUs - Erisin are a seller only, they sell units made by several manufacturers. You have an "LM" unit.
I would stick to what @marchnz has tested already, although having said that, on the MTCB/C units if you flash the wrong MCU you can simply flash the correct MCU to correct it, cant say if its the same for MTCD units, up to you if you want to risk it.
typos1 said:
There are no "Erisin" MCUs - Erisin are a seller only, they sell units made by several manufacturers. You have an "LM" unit.
I would stick to what @marchnz has tested already, although having said that, on the MTCB/C units if you flash the wrong MCU you can simply flash the correct MCU to correct it, cant say if its the same for MTCD units, up to you if you want to risk it.
Click to expand...
Click to collapse
My level of knowledge has not grown in any way after reading your post.
Thank you anyway..
SpeedyCarv said:
My level of knowledge has not grown in any way after reading your post.
Thank you anyway..
Click to expand...
Click to collapse
Maybe read it again ?
Basically, you could risk trying it - MTCB/C units can be restored if the wrong MCU is flashed, maybe MTCD units could be restored if the wrong MCU is flashed also ? But maybe not, so that is your decision whether to try or not.
Otherwise stick to what @marchnz has said and do not try it.
And your unit is NOT an "Erisin" unit, they are sellers and sell units from many manufacturers, you have an LM MTCD unit.
Cant make it any clearer than that.
typos1 said:
Maybe read it again ?
And your unit is NOT an "Erisin" unit, they are sellers and sell units from many manufacturers, you have an LM MTCD unit.
Click to expand...
Click to collapse
Not necessary to read again. I already knew that. That's what i tried to express in typing "my level of knowledge has not grown" Sorry if i write misunderstandable, i'm not a native speaker (German).
Thank you again for your time and patience
typos1 said:
To make it easier to re-apply the settings, you can use the mcu.cfg function and flash it with the MCU, just in case anyone didnt know.
Click to expand...
Click to collapse
Can you explain me how ? Do I put the mcu.cfg file with the new mcu in the root of gps SD ?
In factory settings I see only the option to export, not to import. Or did I miss something ?
Wout2426 said:
Can you explain me how ? Do I put the mcu.cfg file with the new mcu in the root of gps SD ?
In factory settings I see only the option to export, not to import. Or did I miss something ?
Click to expand...
Click to collapse
Thats correct, just put the mcu.cfg file on the SD card with the mcu.img.
typos1 said:
Thats correct, just put the mcu.cfg file on the SD card with the mcu.img.
Click to expand...
Click to collapse
Or, once mcu has been upgraded, you can remove the mcu update (.img) from the root of the gps card and apply the config (.cfg) on the root of the gps card separately - by running the 'upgrade MCU', it will see .cfg file and apply it.
Update for 800x480 users who update to the latest MCU - you must also apply a dmcu.ext
DMCU.EXT details
DMCU.EXT & screen resolution setting/howto/details
dmcu.ext details for PX5 800x480
That said - why is anyone purchasing a PX5 unit with 800x480?!?!
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).
So I tried HA 2.52 on Xtrons TB706APL
I get the following error on reboot.
After I update from dmcu.cfg it goes away but if you go into factory settings and change anything it comes back.
I also didnt see the option for the shutdown that this mcu is supposed to have.
typos1 said:
Thats correct, just put the mcu.cfg file on the SD card with the mcu.img.
Click to expand...
Click to collapse
I assume you mean "dmcu.img" and "dmcu.cfg"? That's how my downloaded img and backup cfg are called.
Bose321 said:
I assume you mean "dmcu.img" and "dmcu.cfg"? That's how my downloaded img and backup cfg are called.
Click to expand...
Click to collapse
Yeah, thats right - the "d" is just there to show its an MTCD MCU not an MTCB or MTCC one.
1-2-Hak said:
So I tried HA 2.52 on Xtrons TB706APL
I get the following error on reboot.
After I update from dmcu.cfg it goes away but if you go into factory settings and change anything it comes back.
I also didnt see the option for the shutdown that this mcu is supposed to have.
Click to expand...
Click to collapse
The shutdown option is under System Settings --> extra settings. You wont find it in the factory settings. Just FYI.
Which dmcu.cfg did you use? I might be wrong, but it seems to me it might be dangerous to use different dmcu.cfg files with different versions of the MCU Code.