After interrupting the map update MEM_ERR01

Ford SYNC 3 Support
,
13

As stated by CyanLabs: You can’t upgrade non nav to nav the garage is wrong!

That said, what you did may not be recoverable since you have a 2020 vehicle. The reformatter will not work properly with it and will end up in a black screen due to incompatible drivers. I doubt that you have enough storage left on the APIM to load a downgrade. You can run the APIM Utility to see what the storage you have left. Look at previous post in this thread. Otherwise, talk to your dealer to get the unit repaired or replaced.

And go find another garage…

14

I need to clarify something, you can upgrade non nav to nav, all the parts are the same, both non nav and nav APIMS have GPS etc, however they do not have enough storage space for maps, you can technically if you are ROW install a very very small part of the maps and get NAV on a Non NAV unit but this is the only real case where it will work.

15

I agree with that. When you do the ROW maps, you end up with about 54 Mb of storage left.

1 Like
16

Let it run through again.
I should have removed the stick before the second reboot.

Can you add something when the procedure is finished and the stick doesn’t boot anymore?

17

If i could do that i would have, it’s not possible, if you follow the instructions correctly then you would know not to re-insert the stick

18

logGeneratedDateTime=“2020-10-21T07:39:38+00:00”>

<d2p1:PartitionHealth available=“36K” total=“1.4G” type=“/fs/sd/MAP/”/>

<d2p1:PartitionHealth available=“148K” total=“1.4G” type=“/fs/sd/MAP/”/>

<d2p1:PartitionHealth available=“12M” total=“1.3G” type=“/fs/sd/MAP/”/>

<d2p1:PartitionHealth available=“16M” total=“1.7G” type=“/fs/sd/MAP/”/>

<d2p1:PartitionHealth available=“16M” total=“1.7G” type=“/fs/sd/MAP/”/>

<d2p1:PartitionHealth available=“13M” total=“2.0G” type=“/fs/sd/MAP/”/>

<d2p1:PartitionHealth available=“329M” total=“1.2G” type=“/fs/rwdata/”/>

<d2p1:PartitionHealth available=“23M” total=“35M” type=“/fs/rwdata/quip/”/>

<d2p1:PartitionHealth available=“87M” total=“90M” type=“/fs/rwdata/quip/”/>

<d2p1:PartitionHealth available=“143M” total=“1.4G” type=“/fs/mp/”/>

<d2p1:PartitionHealth available=“238M” total=“10G” type=“/fs/images/”/>

d2p1:InstallationLog/

1 Like
19

This is the amount of storage free: 238MB. If there was a way to delete all the map data you could rescue the unit and reprogram it for the latest software, with NO MAPS. I am not aware of a solution to your problem.

20

Hi,

I’m new here. I have a Focus with Sync 3.4.20196 (it works fine). The car is a connected car wit own built-in Sim module.

I’ve tried to install the F9 maps with voices together (~22Gb package). After ~2.5 hours I stopped the installation (it looked like it stopped the install, but didn’t got the OK message).

Naturally today it didn’t want to start again, I always get this MEM_ERR01.

The XML looks like Laurent’s XML, I have twice as much map file in the fs/sd/MAP folder as it was before the start.

It is impossible to delete this files like the Gracenote data?

Or I must to reformat the whole disk (or whatelse in it)?

How can I be sure that I have a 2020 version system or the older one?

Waiting for your answer.

Regards,

Tamas

21

MEM_ERR01 – Error is MEM_NOSPACE_TO_COPY

Could you please post the storage usage from the APIM Utility xml? It looks like the installation was not finished.

You have a 2019 Focus EU. You should have 64GB of storage. What is the part number listed in the xml file? Look for the part number entry in the F113 didType/didValue.

Probably the best thing to do is downgrade to 3.3.19052 and then run the reformat with the desired app version and maps. This will ensure a clean install and no errant files.

22

It is very similar to Laurents description, but I can copy it:

<d2p1:ODLNetwork d2p1:NetworkDataRate="500" d2p1:NetworkName="HS-CAN" d2p1:NetworkProtocol="CAN" d2p1:DLCName="SAE J1962" d2p1:Pins="6,14"/>
<d2p1:AdditionalAttributes logGeneratedDateTime="2020-12-09T17:24:31+00:00" RAM="942362624" vmcuVersion="Vector_VMCU_02.02.20">
  <d2p1:PartitionHealth type="/fs/sd/MAP/" total="1.1G" available="20M"/>
  <d2p1:PartitionHealth type="/fs/sd/MAP/" total="2.7G" available="16M"/>
  <d2p1:PartitionHealth type="/fs/sd/MAP/" total="2.6G" available="26M"/>
  <d2p1:PartitionHealth type="/fs/sd/MAP/" total="2.4G" available="16M"/>
  <d2p1:PartitionHealth type="/fs/sd/MAP/" total="2.3G" available="11M"/>
  <d2p1:PartitionHealth type="/fs/sd/MAP/" total="1.5G" available="9.3M"/>
  <d2p1:PartitionHealth type="/fs/sd/MAP/" total="1.5G" available="5.1M"/>
  <d2p1:PartitionHealth type="/fs/sd/MAP/" total="2.2G" available="18M"/>
  <d2p1:PartitionHealth type="/fs/sd/MAP/" total="2.2G" available="17M"/>
  <d2p1:PartitionHealth type="/fs/sd/MAP/" total="3.4G" available="23M"/>
  <d2p1:PartitionHealth type="/fs/sd/MAP/" total="31M" available="708K"/>
  <d2p1:PartitionHealth type="/fs/sd/MAP/" total="3.2G" available="8.4M"/>
  <d2p1:PartitionHealth type="/fs/sd/MAP/" total="3.1G" available="30M"/>
  <d2p1:PartitionHealth type="/fs/sd/MAP/" total="3.6G" available="29M"/>
  <d2p1:PartitionHealth type="/fs/sd/MAP/" total="3.6G" available="15M"/>
  <d2p1:PartitionHealth type="/fs/Nuance/" total="1.9G" available="8.4M"/>
  <d2p1:PartitionHealth type="/fs/Nuance/grace" total="998M" available="21M"/>
  <d2p1:PartitionHealth type="/fs/rwdata/" total="1.2G" available="955M"/>
  <d2p1:PartitionHealth type="/fs/rwdata/quip/" total="35M" available="35M"/>
  <d2p1:PartitionHealth type="/fs/rwdata/quip/" total="90M" available="90M"/>
  <d2p1:PartitionHealth type="/fs/mp/" total="1.4G" available="128M"/>
  <d2p1:PartitionHealth type="/fs/mp/resources" total="73M" available="432K"/>
  <d2p1:PartitionHealth type="/fs/images/" total="54G" available="13G"/>

The part number is : “5U5T-14G371-GKC” and yes, I have 64Gb of storage.

Can I do the reformat then? I think I select the automated method for sure.

Thanks for the answer and for helping!

Regards

Tamas,
Budapest,
Hungary

23

This part number shows up for 2019 and 2020 Focus vehicles. 5U5T-14G371-GKC
Is this original to the vehicle?

Attach the xml file to the post.

24

Yes, this XML from my car. I created with the manual tool from Ford.

The car build on middle of December 2019.

Unfortunately I cannot upload file because I’m a new user…

25

I fixed your user status, you can upload the file.

@CyanLabs, maybe you know if this unit is really a 2020 or 2019, can the reformat tool be used?

26

Here is the latest file.

201209b_Sync_LYBV02RV.xml (11,3 kB)

27

Not sure, wouldn’t want to take the risk personally

1 Like
28

Okay, then I will wait for a solution.

It is impossible to delete these files from the folder. There is a couple of small .sh script here which can delete files from the device:

for example (found in HB5T-14G386-VHA):
find /fs/images/ivsu_* -name “.lst” -remove!|
find /fs/images/ivsu_* -name “*.tar.gz” -remove!|

maybe it can work with different folder and different filename…

29

There is a map delete script that exists, but it might be vin or an locked. I have one, I’ll post it later for you to play with.

30

Thanks for the script. I’ve read it over, it clenas up all map and all voice files from the internal storage.
How I see it didn’t touch the system files, so count brick the system.

Theoretically it creates a LOG file and writes it back to the usb drive, so you can see what does it do.

Well, there is no other way, in the next days I will try it… Will come back to report…

1 Like
31

Some good news.

  1. A created a package with these component:
  • 64 Gb tester
  • MY18.5 HW tester
  • 3.4.20282 APP
  • AD version of log creator

I updated the the Sync 3 and llooked into the created log file.

All the unfinalized map install files deleted from the device. So I have 29 Gb of free space.

I think I am able now to install my map files. Also to the Ford site uploaded XML file precessed successfully and able to download the map files.

I don’t know the reason of the solution but I’ m happy with this situation.

1 Like
32

Where did you find this?

Glad you got this sorted.