When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
I'm very sorry, you're right. I had both connectors stored and took the wrong one. C4 on the PCM4 is in fact USB- .
I don't see any pin for "Amp on" on the PCM4.
I assume the "amp on" comes as a CAN signal to the amps (normally a Bose or Burmester with PCM4).
You might need to use a switched + as a workaround.
I used the power on pin on the MIB2 (PCM4) 'E5' and it now powers up the ASK amp. Contrary to the feedback in here it sounds just like it did before (958.2 Cayenne).
The next challenges are as follows:
1. the antenna amplifier power, there is an ANT pin on the PCM 3.1 but again it is not present or clear on the PCM4. It is working but the signal is not as strong as before, can I simply tap into the same pin "power on"?
2. the parking distance display is not working on PCM4. Maybe it requires a new module, it knows when I go into reverse as I receive a message on the PCM to tell me the display is not working.
3. the selector wheel on the steering wheel for scrolling menus on the cluster is controlling the volume of the pcm at the same time. Maybe that will fix when I update the cluster software.
Replying to myself 🤣 but hopefully it helps others. Challenge 1 is fixed I modified my adapter harness so that the antenna and amp receive power from E5 from PCM4.
Last step is the coding and hopefully that solves the remainder of the challenges and I've done it.
Do you only have the parking distance displayed or do you have a backup camera?
the Camera signal on the PCM4 is on a different pin than on the PCM3.1. I once retrofitted the camera on my Macan. if you need that pin nr I could look it up.
if you have no cam, you might look up PET and check if different PDC modules were used in the 991.1 vs 991.2.
Working through the challenges, there have been many but slowly getting there. Park assist is working but no display yet, will try some more coding and if that doesn't work I'll upgrade the park assist module.
Does anybody know how to code the steering wheel controls, I have the multifunction wheel and with pcm 3 volume wheel is on the left and control of the cluster menu wheel is on the right.
With the pcm4 installed the wheel on the right is controlling both the menu and the volume which is really annoying!
I noted above someone mentioned changing FML generation but I can't see that option. Any assistance appreciated.
Well, the LIN protocol has changed from old Multifunction Wheel to the 991.2 wheel. Folks who retrofit the new wheel therefore buy a module which translates to the older protocol.
Since you'll probably flash your dash cluster to a later firmware in order to work with the PCM4, the new wheel version might work for you?
I have not seen any adapter which goes the other way around, working with dash and PCM4 while using an old wheel and LIN version.
Thanks guys, I managed to solve the problem with the steering controls, the car is an early .2 958 so already had the newer style steering wheel but my steering module did not have the option to code to the newer communication style. I replaced the module with a used one from a slightly later 2015 car and tweaked two options in the coding and it started working.
I was able to retain the existing clockspring.
I am just about finished now. Park assist screen and a slight thump from the amp when turning it on. But I am working on solutions for both issues.
i worked on retrofit of PCM4 from 2017. Here are my notes about that
- unlock PCM4 ( remove component protection ) can be done by hacker, it cost like 250-350 euros, here in europe. I found some hackers in netherlands, poland, ukraine, italy...
- hacker also enable fec codes for you (bluetooth, navigation, carplay....)
- if you update your pcm in future for new firmware you will lost cp remove and fec codes since these features has been done by fw modification
--
unlock of PCM is least problem
--
- PCM4 has different wiring, but it is not hard to sort it out and produce own adapter from quadlock 40 to 52 for few bucks
- PCM4 is not working with instrument clusters fitted in PCM 3.1 cars, (maybe after software update like Chris wrote before), so you have no temperature, no time, no trip data (just "please turn on ignition" message. If you remove keys pcm will turn off and show you message "do not forget your cell phone) - that tells me that some can-bus messages are common and works - also dimming light of buttons works - also controlled by canbus
- you can buy new instruments and it works, i bought from salvage 991.2 GTS, but problem is that new engines has different RPM limit - just 8K, so you can do this on GT3/GT3RS and Turbo modes which has same range, but on Carrera/Targa you have different RPM dial, but instruments will show actual values and works fine
- PCM4 is bit longer than PCM 3.1 so you have to destroy edges on PCM 3.1 plastic cage in dashboard - not a problem and easy
---
My car is 2015 991.1 GTS, i fitted PCM4 in to my car, since my car has burmester audio system, sound is not working (you need new amplifier which supports most 150, old one is most 25) - i dont know if old amplifier car be flashed or reprogrammed to work with new PCM
- this means that if you have just basic sound system retrofit is possible because PCM4 has internal amplifier (also 3.1 has internal amplifier but they used ASK analog amplifies - i dont know why), but if you running on bose/burmester - retrofit is impossible for now, because you need to remove component protection from new amplifier, since new generation of amplifiers already use this anti-theft feature - and this is a problem.
You can root PCM4 since it has some operating systemm but not on amplifier, i think nobody has done it yet
Symptoms of active component protection on amplifier is that you have just 1-2 active speakers for music, for calls and navigation all channels works well, but no music...
thats my knowledge about that!
thank you for this topic! PCM4 is much more better than PCM 3.1
p.s. sorry for my english, i am still learning :-)
Ahy progress on bose?
Last edited by vartech; 10-24-2022 at 09:50 AM.
Reason: text
In case I missed the EDIT button on my last post, please merge both posts
So, I got a bit further and was able to connect via JTAG to the unit, however full connection couldn't be established.
Any ideas o how to fix this and get it working?
How I connected J-LINK with JTAG on MMX:
Spoiler
With this command I loaded uboot and BCT to the system:
Spoiler
Code:
sudo tegrarcm --bct original.bct --bootloader qboot.bin --loadaddr 0x84000000
bct file: original.bct
bootloader file: qboot.bin
load addr 0x84000000
entry addr 0x84000000
device id: 0x7030
uid: 0x015ced07b70ffe12
RCM version: 3.1
downloading miniloader to target at address 0x4000a000 (128916 bytes)...
miniloader downloaded successfully
Chip UID: 0x0000000000000000015ced07b70ffe12
Chip ID: 0x30
Chip ID Major Version: 0x1
Chip ID Minor Version: 0x3
Chip SKU: 0x90 (t30)
Boot ROM Version: 0x1
Boot Device: 0x6 (SNOR)
Operating Mode: 0x3 (developer mode)
Device Config Strap: 0x0
Device Config Fuse: 0x0
SDRAM Config Strap: 0x2
sending file: original.bct
- 6128/6128 bytes sent
original.bct sent successfully
sending file: qboot.bin
\ 68648/68648 bytes sent
qboot.bin sent successfully
This is the error I get while connectiong via JTAG to the system:
Spoiler
Code:
Connecting ...
- Connecting via USB to probe/ programmer device 0
- Probe/ Programmer firmware: J-Link V11 compiled Jul 17 2020 16:24:07
- Device "CORTEX-A9" selected.
- TotalIRLen = 8, IRPrint = 0x0011
- JTAG chain detection found 2 devices:
- #0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP
- #1 Id: 0x4F1F0F0F, IRLen: 04, ARM7TDMI-S Core
- Scanning AP map to find all available APs
- AP[3]: Stopped AP scan as end of AP map has been reached
- AP[0]: AHB-AP (IDR: 0x44770001)
- AP[1]: APB-AP (IDR: 0x24770002)
- AP[2]: JTAG-AP (IDR: 0x14760010)
- Iterating through AP map to find APB-AP to use
- AP[0]: Skipped. Not an APB-AP
- AP[1]: APB-AP found
- ROMTbl[0][0]: CompAddr: 80001000 CID: B105900D, PID:04-003BB907 ETB
- ROMTbl[0][1]: CompAddr: 80002000 CID: B105900D, PID:04-003BB906 CTI
- ROMTbl[0][2]: CompAddr: 80003000 CID: B105900D, PID:04-004BB912 TPIU
- ROMTbl[0][3]: CompAddr: 80004000 CID: B105900D, PID:04-001BB908 CSTF
- ROMTbl[0][4]: CompAddr: 80005000 CID: B105900D, PID:04-002BB913 ITM
- ROMTbl[0][5]: CompAddr: 80006000 CID: B105900D, PID:04-002BB914 SWO
- ROMTbl[0][6]: CompAddr: 80020000 CID: 20323232, PID:00-00000000 ???
- TotalIRLen = 8, IRPrint = 0x0011
- JTAG chain detection found 2 devices:
- #0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP
- #1 Id: 0x4F1F0F0F, IRLen: 04, ARM7TDMI-S Core
- ERROR: Cortex-A/R-JTAG (connect): Could not determine address of core debug registers. Incorrect CoreSight ROM table in device?
- Target interface speed: 1000 kHz (Auto)
- VTarget = 1.812V
- TotalIRLen = 8, IRPrint = 0x0011
J-Flash setting I used:
Spoiler
how to enable USB for sending files with tegrarcm, because in my case it detects as unknown device and disable it , remain for 3cesonds and disappears, but reapers after 10- seconds for second time but same, I cant install nay driver on it.
Is there a special procedure to enable, I can enter in IPL from RCC, in MMX Serial there is nothing so no communication via serial no MMX, also no comunication from RCC to MMX.
I need this to be able to flash NOR with JTAG.
07-29-2022, 12:50 PM
