Retrofitting PCM4 in a 991.1
#151
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:
With this command I loaded uboot and BCT to the system:
This is the error I get while connectiong via JTAG to the system:
J-Flash setting I used:
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
Last edited by CaneTLOTW; 09-07-2020 at 05:07 PM.
#153
Hello Chris,
after you flashed unit your trip computer started to work also temperature display started to work - perfect
but how about coding of instrument cluster? did you lost all your settings and adaptations? dials calibration...
how about map in cluster? is working? can you see the map?
what about parking pilot in pcm? Working?
thank you
after you flashed unit your trip computer started to work also temperature display started to work - perfect
but how about coding of instrument cluster? did you lost all your settings and adaptations? dials calibration...
how about map in cluster? is working? can you see the map?
what about parking pilot in pcm? Working?
thank you
Map in cluster does not work. I think there must be a hardware difference, or some component in the cluster is not accepting a firmware update. My PIWIS does throw an error after programming the cluster, so it might just be a software issue. I don't have a spare cluster, so I do not want to experiment with it further.
Parking, not sure, it should work fine. I just don't have that feature enabled, as my car doesn't have a rear cam or any parking sensors.
----
I actually just had my PCM4 fail, so that's why I'm checking back in on this thread. It's been a while so I'm behind on some questions.
Anyway my tegra (MMX) board failed with the 3.3v rail shorted directly to ground. I removed the associated inductor and hooked it up to my bench PSU with 3.3v @ 30A (essentially assuring constant voltage) and the short quickly blew out. I'm not sure what component was the problem, but it's back in my car and working again.
Last edited by chris2; 09-18-2020 at 11:39 PM.
#154
As far as I recall, the coding wasn't changed significantly but since the software was much newer, there were some coding issues I had to fix. I think most of the coding I performed was to set the cluster to recognize PCM4 since it was set for PCM3.1 from the factory. None of the calibration for dials or mileage was changed.
Map in cluster does not work. I think there must be a hardware difference, or some component in the cluster is not accepting a firmware update. My PIWIS does throw an error after programming the cluster, so it might just be a software issue. I don't have a spare cluster, so I do not want to experiment with it further.
Parking, not sure, it should work fine. I just don't have that feature enabled, as my car doesn't have a rear cam or any parking sensors.
----
I actually just had my PCM4 fail, so that's why I'm checking back in on this thread. It's been a while so I'm behind on some questions.
Anyway my tegra (MMX) board failed with the 3.3v rail shorted directly to ground. I removed the associated inductor and hooked it up to my bench PSU with 3.3v @ 30A (essentially assuring constant voltage) and the short quickly blew out. I'm not sure what component was the problem, but it's back in my car and working again.
Map in cluster does not work. I think there must be a hardware difference, or some component in the cluster is not accepting a firmware update. My PIWIS does throw an error after programming the cluster, so it might just be a software issue. I don't have a spare cluster, so I do not want to experiment with it further.
Parking, not sure, it should work fine. I just don't have that feature enabled, as my car doesn't have a rear cam or any parking sensors.
----
I actually just had my PCM4 fail, so that's why I'm checking back in on this thread. It's been a while so I'm behind on some questions.
Anyway my tegra (MMX) board failed with the 3.3v rail shorted directly to ground. I removed the associated inductor and hooked it up to my bench PSU with 3.3v @ 30A (essentially assuring constant voltage) and the short quickly blew out. I'm not sure what component was the problem, but it's back in my car and working again.
Hello Chris, thank your for reply. I already programmed my cluster and everything in pcm and cluster works just fine. Except map in cluster - i found some parameters about lvds in pcm4 coding but did not succeed yes. I will play with it next weekend.
about parking sensors and rear cam - they has to be replaces - cam and parking sensors module (not sensors) - all works after replace with new parts
#155
This might also be interesting for retrofit:
M.I.B. - More Incredible Bash
https://bit.ly/3nPIHl8
Contains a few Porsche Patches
Other patches can be build on request - FW files or RCC dump required.
MIB2 MHI2/MH2P/MHS2/MST2/RMC FW and Solutions Collection
https://bit.ly/3nunsEj
Contains a few Porsche FW Updates
MHI2 Root Password List
https://bit.ly/37LHHc1
Missing password can be found - requires FW updates files, RCC/MMX dump or HASH
If you can provide additional FW files or other useful information, feel free to get in contact
https://t.me/joinchat/EHt4RRksHcMQk6Xi6tFaBw
M.I.B. - More Incredible Bash
https://bit.ly/3nPIHl8
Contains a few Porsche Patches
Other patches can be build on request - FW files or RCC dump required.
MIB2 MHI2/MH2P/MHS2/MST2/RMC FW and Solutions Collection
https://bit.ly/3nunsEj
Contains a few Porsche FW Updates
MHI2 Root Password List
https://bit.ly/37LHHc1
Missing password can be found - requires FW updates files, RCC/MMX dump or HASH
If you can provide additional FW files or other useful information, feel free to get in contact
https://t.me/joinchat/EHt4RRksHcMQk6Xi6tFaBw
Last edited by CaneTLOTW; 01-10-2021 at 09:19 AM.
The following users liked this post:
rainer (12-20-2020)
#157
I'm sure someone will take your money to do it for you, but expect to pay a ludicrous sum.
The following users liked this post:
Lee1 (02-01-2021)
#159
Thanks chris2 for this fantastic list! Do you have an updated version?
I have a 718 Boxster with PCM 4.0 and the standard Sound Package Plus (internal amp, 6 speakers). The equivalent Cayman or 911 has 8 speakers. The PCM part numbers are identical between the Cayman, 911, and Boxster. I have installed the 2 missing speakers in my Boxster however there seems to be a software issue that is preventing the PCM from sending the sound to the 2 new rear speakers. Using your list i have suceeded in getting my PCM to display the Fader selection (front/rear sound split which is missing in the standard Boxster setup) by chanigng Bytes 0-2 to those for the Cayman. As I still dont get any sound out of the rear speakers it seems like some other parameters need to be changed too. I am therefore wondering if you have an updated version of the above list where you have identified more of the parameters?
Thanks in advance!
PS . Do you have to happen to have the Euro Map Database for the Navigation? I am trying to activate the Nav as well?
I have a 718 Boxster with PCM 4.0 and the standard Sound Package Plus (internal amp, 6 speakers). The equivalent Cayman or 911 has 8 speakers. The PCM part numbers are identical between the Cayman, 911, and Boxster. I have installed the 2 missing speakers in my Boxster however there seems to be a software issue that is preventing the PCM from sending the sound to the 2 new rear speakers. Using your list i have suceeded in getting my PCM to display the Fader selection (front/rear sound split which is missing in the standard Boxster setup) by chanigng Bytes 0-2 to those for the Cayman. As I still dont get any sound out of the rear speakers it seems like some other parameters need to be changed too. I am therefore wondering if you have an updated version of the above list where you have identified more of the parameters?
Thanks in advance!
PS . Do you have to happen to have the Euro Map Database for the Navigation? I am trying to activate the Nav as well?
#160
Some more coding stuff, based on my notes at this point, this might change since some bytes are unknown and some are probably wrong
Byte 0-2 - Car Type
Byte 7 - Sound System ID - Unused: 00
Byte 8 - Aux Settings
Byte 11 - Sound Package
Byte 14 - Unused 00
Byte 15 - Porsche Connect
Byte 18 - Startup Animation
Byte 21 - ??? value = 70
Byte 22 - Instrument Cluster?
Still need a coding dump from a 911 so I can get the proper coding for bytes 0-2
Byte 0-2 - Car Type
- 07 44 06 = Macan
- 07 44 05 = Boxster
- 07 44 04 = Cayman
- Need 911 values
- 01 = Europe
- 02 = North American Region
- 03 = Centra / South America
- 06 = Japan
- 09 = South Africa
- BE = Basic Sound System (basic sound pkg)
- 00 = Sound System Installed (ex: bose / burmeister)
- 0A = Basic Sound System (basic sound pkg)
- 00 = Sound System Installed
Byte 7 - Sound System ID - Unused: 00
Byte 8 - Aux Settings
- 03 = Microphone Installed
- 13 = Microphone Installed, Aux In Active (Aux retrofit is possible by installing port and changing coding byte)
- 22 = North American Region
Byte 11 - Sound Package
- 01 = Base Sound System, Internal Amplifier
- 02 = Bose Sound System, External Amplifier
- 03 = Burmeister Sound System, External Amplifier
- ??? 06 for PCM with Sirius + FM installed
Byte 14 - Unused 00
Byte 15 - Porsche Connect
- 10 = Porsche Connect Module Installed
- 03 = No Porsche Connect, Telephone Baseplate Installed
- 2F = Telephone Available, Bluetooth Multimedia Installed
Byte 18 - Startup Animation
- Possible values in post above, convert to hex before programming
- C4 = LHD, Rear View Camera, USB + iPhone, Internal Amplifier (disable MOST bus)
- E4 = LHD, Rear View Camera, USB + iPhone, External Amplifier (uses MOST bus)
Byte 21 - ??? value = 70
Byte 22 - Instrument Cluster?
- Value = 41 ????
- 06 = Legal Disclaimer Active, Speller Function Inactive
- DC = Media Import, Navigation, WIFI Functionality, Predictive Route Display
Still need a coding dump from a 911 so I can get the proper coding for bytes 0-2
I have a 718 Boxster with PCM 4.0 and the standard Sound Package Plus (internal amp, 6 speakers). The equivalent Cayman or 911 has 8 speakers. The PCM part numbers are identical between the Cayman, 911, and Boxster. I have installed the 2 missing speakers in my Boxster however there seems to be a software issue that is preventing the PCM from sending the sound to the 2 new rear speakers. Using your list i have suceeded in getting my PCM to display the Fader selection (front/rear sound split which is missing in the standard Boxster setup) by chanigng Bytes 0-2 to those for the Cayman. As I still dont get any sound out of the rear speakers it seems like some other parameters need to be changed too. I am therefore wondering if you have an updated version of the above list where you have identified more of the parameters?
Thanks in advance!
PS . Do you have to happen to have the Euro Map Database for the Navigation? I am trying to activate the Nav as well?
The following users liked this post:
Vinh Nguyen (06-05-2021)
#162
Hi, can anyone help me, I have about 75% of the way through doing this and it's looking good but have no sound, I know my ask amp won't work properly and will need to bypass it but I would like to test it anyway, but I am getting no sound though to it at all. The pcm 3.1 harness has an 'amp on' terminal but which is the corresponding terminal on the MIB2 52 quadlock connector? Anyone know?
#163
PCM4 pin C4 is what you're looking for.
Hi, can anyone help me, I have about 75% of the way through doing this and it's looking good but have no sound, I know my ask amp won't work properly and will need to bypass it but I would like to test it anyway, but I am getting no sound though to it at all. The pcm 3.1 harness has an 'amp on' terminal but which is the corresponding terminal on the MIB2 52 quadlock connector? Anyone know?
The following users liked this post:
TDS (07-29-2022)
#165
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 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.
Last edited by rainer; 07-29-2022 at 10:25 AM.