SEAT Ateca, MHI2_ER_SEG11_P4709 / MU1447: read-only compatibility report and stock map-plane geometry

[bartberden]

Area

New platform / vehicle

Topic

Read-only compatibility data from a SEAT target, offered as input for a SEG11 / MU1447 profile.

Vehicle: SEAT Ateca, 2016 / MHI2
Firmware: MHI2_ER_SEG11_P4709 / MU1447
Cluster: SEAT Digital Cockpit, believed to be a "...920 790 A" part (prefix and HW/SW version not yet read out; to be confirmed)
SSH access: WLAN

Nothing was installed and no target filesystem was modified. No gate, DIRECT or GEN2 test has been run, and CarPlay was not exercised. I can run further bounded, stock-safe tests on this unit if that helps.

Context / evidence

compatibility-report.sh (commit aa19750) finished with MIBR_COMPAT=PASS_READ_ONLY.

Component hashes vs the MU1440 stock reference

Component	Size	SHA-256	vs MU1440
libairplay.so	703688	193a4fd9101ec2aa05e7159cfa307b96500810d379ca74a194f172adc13a46b5	identical
libdsicarplayproxy.so	73384	9ccb46c1c185f9be507d74d1e46433cabde2833fc77ac478744ea95629f9be96	identical
mm-ipod	40297	de99a7f4dd941589c6d5173b7601856275c4ea615229058ec84b8e3efa748d27	identical
libiap2client.so.1	18613	c33021b21c5656886e64964efcf806fddb4259027c3c1ed396522e7a44adfdea	identical
smartphone_integrator	806516	fe82427e27e33238185ab3fdd159fa2752a78adfca7f4e0d64af38d0d4c54243	differs (ref 806539 B)
dio_manager	686481	18c29fb6d65a07df409b1f1334a35b642551be075ddd7159d22ed43922228d25	differs (ref 686552 B)
displaymanager	586381	8c052e8bee0e8325e469bf25503910e36506fe7bd212cffa3e004b4db5ec8495	differs, same size
smartphone_integrator.json	7360	20bb3291f0e1176a261111e22fbabee3bdcd225bc84d3ce9a2579e54915ee98c	differs, same size
dio_manager.json	13142	7e21c2c5dd816927a01272e66230d052cc6df383f1bd6b30a8643c224716d541	differs
displaymanager.json	5979	61b6b83b839cc57a1fa22d7661d9433b1ec10a004c6fe5638144dc919ddc0d88	not in reference table
/ifs/lsd.jxe	55712574	945586fbede2fe53b5b41d7c10490641ff71fcc9581fb237cf40328f450cb22e	differs
lsd.sh	16155	77eacf3b768122e20a9322774ff0d1690d3cc47729f5d780571e8063bf8f669f	not in reference table

Java state is stock: no custom bootclasspath entries in lsd.sh; the jars directory holds only GEM.jar and nullservice.jar.

Stock DisplayManager state (dmdt, read-only getters)

dmdt gd:

displaymanager knows 5 displayables:
16  window    800  x 480 2   DISPLAYABLE_HMI
19  window    800  x 480 2   DISPLAYABLE_MAPVIEWER
33  window    1010 x 376 2   DISPLAYABLE_KOMBI_MAP_VIEW
22  window    285  x 276 2   DISPLAYABLE_MAP_3D_INTERSECTION_VIEW
23  window    285  x 276 2   DISPLAYABLE_MAP_JUNCTION_VIEW

dmdt gs:

display 0: name display0, terminal main, size 800 x 480, context id 0 -> 16 (DISPLAYABLE_HMI)
display 1: name <error>, terminal <error>, size 0 x 0, context id 70 -> 33 (DISPLAYABLE_KOMBI_MAP_VIEW)

dmdt gc reports 30 contexts, including:

70 | 1 | NONE -> 33 (DISPLAYABLE_KOMBI_MAP_VIEW)
71 | 2 | NONE -> 16 (DISPLAYABLE_HMI), 59 (DISPLAYABLE_EXTERNAL_SMARTPHONE)

pidin -p displaymanager fds | grep isoTX:

58  1028168 -w        0 /dev/mlb/isoTX2

displaymanager.json: most_encoder.device is /dev/mlb/isoTX2, nv_encoder_data_rate 9600000, force_kombi_type "none".

So the stock map plane on this SEAT target is 1010x376 on context 70 / displayable 33, and DisplayManager holds /dev/mlb/isoTX2 open for writing. Whether data was flowing at that moment was not measured.

Cluster views

The cluster has three views. The native SEAT map is visible in all of them:

View	Native map in cluster	dmdt gs / gc
Gauges	small, centred	context 70 / displayable 33
Large map	large	identical
Side widgets	small, centred between the widgets	identical

dmdt gs, dmdt gc and the isoTX2 fd were identical in all three views. The view change is not visible in the unit-side DisplayManager state.

Collector findings on this target

1. SD path check. On this unit pwd resolves the SD root to /net/mmx.mibhigh.net/fs/sda0. The case "$P" in /net/mmx/fs/*) branch in mibr_media_rw does not match, so the medium is never remounted writable and the collector stops with cannot_create_sd_session rc=4. A manual mount -uw /net/mmx/fs/sda0 beforehand works around it.
2. displaymanager path. The process runs as /eso/bin/apps/displaymanager; /mnt/app/eso/bin/apps/displaymanager does not exist, so the collector reports it as missing. The hash in the table above was taken manually from /eso/bin/apps/displaymanager.
3. dmdt output redirected to a file is unreliable here. Using the run_dmdt invocation from common.sh with > file 2>&1, gs and gd produced empty files and gc was truncated mid-output, in four out of four runs. The same commands printed to the terminal return complete output with rc=0. This may affect direct_snapshot.
4. lsd.sh exists. The profile map notes that the selected SEG11 app tree did not contain lsd.sh. On the unit it is present at /mnt/app/eso/hmi/lsd/lsd.sh (size and hash above).

Attached

The three stock config snapshots are available on request.

component-hashes.txt
runtime-observation.txt
session.log
vehicle-summary.txt

Before posting

• I removed credentials, VINs, addresses and other private information.

[andreic933]

@bartberden How did you initially obtain SSH access on your SEAT Ateca? Was SSH already enabled, or did you use a specific procedure compatible with the MHI2 firmware?

[bartberden]

With MIB toolbox enabled ssh.