MEM_ERR01 Solved, info from Interrogator file

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.

Sync 3 decoded files.zip

2 Likes

Nice one, i have just added this function to the latest alpha of Syn3 Updater

2 Likes

You may find that there will be discrepancies in the listing sometimes. Example: 5U5T-14G391-CP will indicate that 5U5T-14G391-CN is installed, despite showing the 5U5T-14G391-CP in the IVSU screen in Sync, if the unit is not completely rebooted (power cycled) after the upgrade before running the Interrogator Tool. But overall a useful tool.

Great, then it will be useful.

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.