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.
Is the MMX running u-boot as boot loader? Or what boot loader is used exactly?
I'm asking because the hardware (tegra30) is very similar if not the same then other car brand which I'm trying to get u-boot loader running
I'm pretty sure they are using QNX IPL without any sort of monitor. I don't see any reason why you couldn't launch into uboot from IPL, provided you have some way of loading the application onto the system (IPL supports ZModem, if nothing else)
Ah ok, I was triggered by your post because you mentioned the md.b command, which is used in u-boot as well.
I already have a way to launch u-boot on this Tegra30 system, but in its current form it is very basic and it still lacks emmc functionality which I need to extract the required file for root access (without isp/desoldering the chip).
So I'm looking for other systems that have same pcb like Porsche PCM4 and Audi Virtual Cockpit.
I've had a bit more of a look around and found a sqlite database called persistence.sqlite. However, this appears to be a database for storing stuff like the last radio station the system was at before it was shutdown. The keys in this database however do not match with those in some the of the Dev .sh scripts (which I was hoping). Also, this sqlite database has a partition table that references data tables so to edit data you would need to use the -p to specify a partition. When looking at the dev scripts again, they don't reference any partitions so whatever DB that is being used, it must be a single partition with multiple keys as primary keys. ie
for carplay: /eso/bin/apps/pc b:0:3221356628:8.0 1
If you look at the two above, they both use the same "key" 3221356628 but with different byte offsets.
Has anyone found the database file where "pc" and "dump_persistence_writer" edit? Has anyone had a look at these with IDAPro to check to see if the DB is hard-coded to a specific database file?
I suppose its not a biggie aslong as you can read a value and then change it and read it again to make sure it has taken correctly... Would just be interesting to see what is being edited..
So guys, I can confirm that the dev scripts that call "pc" and "dumb_persistence_writer" actually just change adaption channels. This means the developers don't need to have an OBD2 connection to MIB2... If you look at the name of certain scripts they will align with adaption channel names...
Attached are the pinouts for PCM3.1 and PCM4, anybody who is attempting this should be able to repin the adapter cable with this. Pins E1, E2, E7 and E8 should be removed from the PCM3.1 side of your adapter harness, re-terminated with the appropriate multilock pins, then routed to the PCM4 LCD connector. You'll also need to splice into +12V and ground to power the LCD panel.
If you use the pre-made adapter harness from aliexpress, the PCM3.1 side of it will only have up to pin A14, while pin A15 (VBATT) is required, so either remove it and install the wire into the PCM4 end of your new harness (position D16), or try to source the correct quadlock receptacle. The MOST waveguide on your factory harness is in the adapter's position of 12v/GND, so you will need to remove the 2 pins and drill them out to accommodate the optical connectors.
Some signals have been renamed on the PCM4 side of things, for example the rear camera is now FBAS vs CVBS. Also, the MOST optical cables are only required for Bose / Burmeister cars, if you have the standard sound system, there's no optical cables to connect so you can leave those off of your BOM. If you have a MOST network in your car, you can purchase a housing that accepts the optical cables from your old quadlock connector so it can be directly installed into your new PCM4 (TE Part # 1-1355426-1)
PCM4 Connector (OEM signal names)
PCM3.1 Connector (Porsche signal names)
PCM4 Display Connector
Just found this, thanks great info, I was looking for rear camera inputs and CANbus.
I am not sure Canbus is responsible for Pcm data on cluster
It should be trough LVDS cable from PCM to cluster
At first I had problem for steering wheel buttons and it fixed by coding cluster and changing FML from gen2 to gen1
12 V power supply to run PCM 4 without connecting it to the car. Do you have a recommendation?
PIWIS II. Trying to figure out which one to buy. Should I get the Wifi version? Should I buy the SSD with software? Or the WinXP Image that I will download from their forum will have the software preinstalled
Just updated my instrument cluster with PIWIS II from Kombiinstrument_A2.9 0391 to Kombiinstrument_A3.5 1770, and am happy to report success. PCM4 is now communicating with the rest of my car's systems, one more thing to add to the to do list is: reactivate my audio menu in the cluster, and reactivate navigation in PCM since PIWIS decided it would be cool to delete those features. Also need to finish wiring the speakers directly to PCM4 after the ASK amplifier delete and reinstall the passenger seat.
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
Last edited by Jacobello87; 06-02-2020 at 04:08 AM.
Hi,
Chris posted the pinout of the PCM 3.1, PCM4 main harness connector in post #1, #18. In case of PCM4 the UART pins (Rx, Tx) are there but not on the PCM 3.1 connector. Does anybody know where to access these pin to be able to communicate with the pcm 3.1 head unit via serial link?
Hello. Have anybody success with JTAG connection to MMX NOR ?
Any success on connecting with JTAG?
Sitting at the same step now, with a broken MMX.
I could connect to the unit to upload a new bootloader, which hopefullly enables JTAG.
Struggling now on how to connect with J-Link.
Connection between JTAG points on the MMX and J-Link is established, but have too little experience in working with J-Flash.
Spansion S29GL512S is not in the list of supported devices...
09-18-2019, 04:48 PM
