Quote:
Originally Posted by Knuppel
Quote:
Originally Posted by Sensible_
Whatever you do don't flash the CCC with a DCAN cable. It will take hours and likely fail and brick the CCC. You'll need and ICOM A and B.
Also, from what you've said I interpret that as Denison saying update the denison firmware. Not your CCC.
Also also, the Denison won't emulate factory bluetooth. The CCC doesn't support bluetooth. I guess the Denison unit is installed on the MOST ring and the car codes for a 'cd change'.
|
I've researched this extensively. It's possible to update through DCAN, but you have to use a Bimmergeeks cable, or flash the Edibiaslib firmware to a Chinese clone. Also, it's important to not drop below 13v, which is achieved by connecting a power supply (not a battery charger). The car is 12 years old, and i'm not spending money on an ICOM if i don't have to.
The Dension firmware is fully updated and it is stated in the manuals that the car should be on latest firmware. This is also the advice that was given from the Dension helpdesk. Dension 500s BT emulates a cd-changer, options: IPOD and 644.
Now back to the question: if i brick my CCC, will the car still work without any bugs (except for the nav-screen ofcourse)?
And is there another module available that i can use to test the flashing procedure that has the ability to recover when things go wrong? |
Ok. Good luck
You could use the best DCAN cable in the world, but this won't help you flash on the MOST bus with Async. But if you've researched it then I'm sure if will be fine.
Make sure you flash in the correct order.
If you've not flashed anything before then I'd suggest update something like the Kombi (instrument cluster). You'll need to code it to default with NCS after flashing with winkfp.
If you brick the CCC you'll just lose the CCC. The car will still function correctly.