Hello
After a interupted install of F10 maps that resulted in MEM_ERR01, the installation is finally fixed. Writing this as a possible help for others with same problem.
Started installation with first set of F10 map-files downloaded from FORD, with an autoinstall.lst like this
; SYNC3 Consumer Application Upgrade - Release 3.4.54 - Only for Nav/EU assemblies.
[SYNCGen3.0_3.4.21020_PRODUCT]
Item1 = HB5T-14G386-VCB
Open1 = SyncMyRide\HB5T-14G386-VCB.tar.gz
Item2 = HB5T-14G386-VHA
Open2 = SyncMyRide\HB5T-14G386-VHA.tar.gz
Item3 = 1U5T-14G424-BK
Open3 = SyncMyRide\1U5T-14G424-BK.tar.gz
Item4 = 1U5T-14G421-BAH
Open4 = SyncMyRide\1U5T-14G421-BAH.tar.gz
Item5 = 1U5T-14G421-BCH
Open5 = SyncMyRide\1U5T-14G421-BCH.tar.gz
Item6 = 1U5T-14G421-BDH
Open6 = SyncMyRide\1U5T-14G421-BDH.tar.gz
Item7 = 1U5T-14G421-BEH
Open7 = SyncMyRide\1U5T-14G421-BEH.tar.gz
Item8 = 1U5T-14G421-BFH
Open8 = SyncMyRide\1U5T-14G421-BFH.tar.gz
Item9 = 1U5T-14G421-BGH
Open9 = SyncMyRide\1U5T-14G421-BGH.tar.gz
Item10 = 1U5T-14G421-BHH
Open10 = SyncMyRide\1U5T-14G421-BHH.tar.gz
Options = AutoInstall
[SYNCGen3.0_ALL]
Item1 = GB5T-14G386-AD
Open1 = SyncMyRide\GB5T-14G386-AD.tar.gz
Item2 = LU5T-14G386-CA
Open2 = SyncMyRide\LU5T-14G386-CA.tar.gz
Options = Delay,Include,Transaction
Free memory was like this:
<d2p1:PartitionHealth available=β12Gβ total=β54Gβ type=β/fs/images/β/>
Installation failed after about one hour. When trying to restart installation, I got MEM_ERR01, in the interrogator file I had this memory setup.
<d2p1:PartitionHealth available=β676Kβ total=β1.1Gβ type=β/fs/sd/MAP/β/>
<d2p1:PartitionHealth available=β16Mβ total=β2.7Gβ type=β/fs/sd/MAP/β/>
<d2p1:PartitionHealth available=β14Mβ total=β2.3Gβ type=β/fs/sd/MAP/β/>
<d2p1:PartitionHealth available=β16Mβ total=β2.4Gβ type=β/fs/sd/MAP/β/>
<d2p1:PartitionHealth available=β7.9Mβ total=β1.5Gβ type=β/fs/sd/MAP/β/>
<d2p1:PartitionHealth available=β9.3Mβ total=β1.5Gβ type=β/fs/sd/MAP/β/>
<d2p1:PartitionHealth available=β17Mβ total=β2.2Gβ type=β/fs/sd/MAP/β/>
<d2p1:PartitionHealth available=β18Mβ total=β2.2Gβ type=β/fs/sd/MAP/β/>
<d2p1:PartitionHealth available=β24Mβ total=β3.7Gβ type=β/fs/sd/MAP/β/>
<d2p1:PartitionHealth available=β308Kβ total=β38Mβ type=β/fs/sd/MAP/β/>
<d2p1:PartitionHealth available=β5.7Mβ total=β3.2Gβ type=β/fs/sd/MAP/β/>
<d2p1:PartitionHealth available=β8.4Mβ total=β3.2Gβ type=β/fs/sd/MAP/β/>
<d2p1:PartitionHealth available=β24Mβ total=β3.1Gβ type=β/fs/sd/MAP/β/>
<d2p1:PartitionHealth available=β29Mβ total=β3.6Gβ type=β/fs/sd/MAP/β/>
<d2p1:PartitionHealth available=β26Mβ total=β4.4Gβ type=β/fs/Nuance/β/>
<d2p1:PartitionHealth available=β27Mβ total=β4.6Gβ type=β/fs/Nuance/β/>
<d2p1:PartitionHealth available=β8.4Mβ total=β1.9Gβ type=β/fs/Nuance/β/>
<d2p1:PartitionHealth available=β21Mβ total=β1003Mβ type=β/fs/Nuance/graceβ/>
<d2p1:PartitionHealth available=β947Mβ total=β1.2Gβ type=β/fs/rwdata/β/>
<d2p1:PartitionHealth available=β35Mβ total=β35Mβ type=β/fs/rwdata/quip/β/>
<d2p1:PartitionHealth available=β90Mβ total=β90Mβ type=β/fs/rwdata/quip/β/>
<d2p1:PartitionHealth available=β133Mβ total=β1.4Gβ type=β/fs/mp/β/>
<d2p1:PartitionHealth available=β432Kβ total=β73Mβ type=β/fs/mp/resourcesβ/>
<d2p1:PartitionHealth available=β4.8Gβ total=β54Gβ type=β/fs/images/β/>
14 map files instead of 9 and only 4.8 GB left. Also 2 voice files less.
Installed 14G386-VCB (min 50 GB check, and removes some failed files), got 6,8 GB free. Started to install map-files one or two files at a time to avoid MEM_ERR01. Finally βAbout Syncβ showed F10 maps but APIM diagnostics/software versions showed 1U5T-14G421-BAG (F9). All mem sizes looked good but the installation was not good.
I started to look deeper in the Interogator log xml-file and found some interesting rows, didvalue 8060 and 8061, looked a lot like ascii hex values, made a quick Excel-file to decode the rows and ended up with the names of what was installed. at this time the rows looked like this
-<d2p1:DID responseLength=β384β didValue=β8060β didType=βEmbedded Consumer Applications Part Numbers 1β didFormat=βPacketedβ>
d2p1:Response315535542d3134473432312d424147000000000000000000315535542d3134473432312d424248000000000000000000315535542d3134473432312d424347000000000000000000315535542d3134473432312d424447000000000000000000315535542d3134473432312d424547000000000000000000315535542d3134473432312d424647000000000000000000315535542d3134473432312d424748000000000000000000315535542d3134473432312d424848000000000000000000315535542d3134473432312d424a48000000000000000000315535542d3134473635382d414600000000000000000000315535542d3134473432342d424b00000000000000000000345535542d3134473432322d424146000000000000000000345535542d3134473432332d414300000000000000000000355535542d3134473339312d414e00000000000000000000345535542d3134473432322d424246000000000000000000345535542d3134473432322d424346000000000000000000</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
-<d2p1:DID responseLength=β384β didValue=β8061β didType=βEmbedded Consumer Applications Part Numbers 1β didFormat=βPacketedβ>
d2p1:Response345535542d3134473432322d424446000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
and decoded like this,
1U5T-14G421-BAG
1U5T-14G421-BBH
1U5T-14G421-BCG
1U5T-14G421-BDG
1U5T-14G421-BEG
1U5T-14G421-BFG
1U5T-14G421-BGH
1U5T-14G421-BHH
1U5T-14G421-BJH
1U5T-14G658-AF
1U5T-14G424-BK
4U5T-14G422-BAF
4U5T-14G423-AC
5U5T-14G391-AN
4U5T-14G422-BBF
4U5T-14G422-BCF
4U5T-14G422-BDF
Still 5 map files that was from F9. With this info I updated the 5 files one by one and finally I decoded the lines to only -B*H map files and APIM diagnostics/software versions also showed 1U5T-14G421-BAH
Maybe the decoding of the 8060 and 8061 lines are already known but it was not known to me and helped me alot. I hope this also can help others, Iβm not able to upload the Excel file, file type is not supported. Dropbox link below. File can be used to decode the didvalue lines 8060 and 8061 into file names that Sync have registered as installed files. Just paste the numbers that are embedded.