Posts by rui.saraiva

The "ovip-patch-usb-*" patches are referred to in some TSB, so they are theoretically installed in an official garage (probably never happened before, but that's beside the point).

And yes, both the "ovip-patch-usb-*" and "ovip-patch-ota-*" are shown in the "packageslist_<UIN>.txt" file and in the boot log of the RCC/NAC:

Post

RE: NAC/RCC/SMEG Updates Datenbank

Guten Abend,
ich bekomme es auch einfach nicht hin, mein Infotainment System zu Updaten. Jedes mal kommt die nachricht "Version nicht Kompatibel mit der Hardware". Ich habe schon viele verschiedene tar-Datei-Versionen heruntergeladen und alle mit der Mittns Toolbox auf USB-Sticks geladen. Die Verifizierung sagt auch immer, dass alles OK ist. Am Anfang hatte ich es mit Opel Update probiert, damit hat es nicht funktioniert. Desshalb bin ich zu Mittns Toolbox umgestiegen, mit der hoffnung, dass es…

Ichkanna

May 11th 2026

https://www.forum-peugeot.com/Forum/threads/nac-wave-4-maj-firmware-44-07-33-32_nac-r0.135811/page-2#post-2756185

swl-manager[2923]: Update from path /SWL/001328051681720865/Packages: Hw found, Proj found => OK !
swl-manager[2923]: pExt:CN (expected: Continental / NAC /) validation status=1
swl-manager[2923]: pExt:MediaHeader verification status=1
swl-manager[2923]: pExt:hash validation=1
swl-manager[2923]: pExt:localLicense (folder:/mnt/mmc_ovip_rw/media/datastore_rw/swl/ota/Security/license) found=0
swl-manager[2923]: pExt:localLicense (file:/mnt/mmc_ovip_rw/media/datastore_rw/swl/ota/Security/license/license_0D010F0761D4D1E2992A_001328051681720865.key) found=0
swl-manager[2923]: pExt:licenseServer=https://majestic.p3cs.com/mjf00-web/rest/LicenseDownload?mediaVersion=001328051681720865&uin=0D010F0761D4D1E2992A
swl-manager[2923]: pExt:license validation=1
swl-manager[2923]: pExt:MediaHeader processing status=1
swl-manager[2923]: Cycling:DISABLED
swl-manager[2923]: User Input:ENABLED
swl-manager[2923]: Downgrade:DISABLED
swl-manager[2923]: Samegrade:ENABLED
swl-manager[2923]: Downloading file:///tmp/multiarchive/SWL/Packages/packages/Packages.gz.
swl-manager[2923]: Inflating file:///tmp/multiarchive/SWL/Packages/packages/Packages.gz.
swl-manager[2923]: Updated list of available packages in /Data/mnt-wt/opkg/opkg/lists/local.
swl-manager[2923]: Installing ovip-patch-ota-nac-17825 (3.0.0-r0) on root.
swl-manager[2923]: Downloading file:///tmp/multiarchive/SWL/Packages/packages/ovip-patch-ota-nac-17825_3.0.0-r0_armv7a.ipk.
swl-manager[2923]: Enabled security update from path:/mnt/mmc_ovip_rw/media/datastore_rw/swl/ota/Security

I've only found those patches for the NAC_EUR_WAVEx, RCC_AIO_LATAM_WAVEx and NAC_AIO_LATAM_WAVEx systems (only the RCC AIO has one patch currently in PUBlic state).

There are OTA updates for NAC systems, but they aren't very common...

NAC & RCC Updates - patches

sites.google.com

Double-click the "updateType" and there are a bunch of "ovip-patch-ota-nac-*" files.

@someone: And what makes you think they were updates for the NAC_EUR_WAVE1? Firmware versions 6.x.x or 7.x.x? Maps in the P1CNS format? If you input your VIN on my page, what is the infotainment system identified?

In an older post you wrote:

In fact, a NAC -WAVE2 system is displayed in the toolbox, even though only NAC1 software was offered and installed previously.

Software version: 21.08.90.52_NAC-r0
Installed version: 21.08.87.32_NAC-r1

Any of those 2 firmware versions are for NAC_EUR_WAVE2. If you're referring to the "-r1", that's just the revision number. There was an -r0:

21.08.87.32_NAC-r0 04 Feb 2021 001315031612436595 2 730 649 600
21.08.87.32_NAC-r1 17 Feb 2021 001315031613548831 2 730 657 792

Or even:

21.07.13.42_NAC-r0 04 Apr 2018 001315031522833814
21.07.13.42_NAC-r1 09 Apr 2018 001315031523275454
21.07.13.42_NAC-r2 10 Apr 2018 001315031523342146

All of them are still for NAC_EUR_WAVE2.

And why do you think you've a NAC_EUR_WAVE1 system?

No, for the NAC_EUR_WAVE1, there's this testing version:

{
  "updateType": "map-eur",
  "updateVersion": "32.0.0",
  "updateProvider": "TOMTOM",
  "updateId": "002315011776062834",
  "updateDate": "2026/05/29 11:16:50",
  "updateStatus": {
    "code": "AVC",
    "label": "En attente de validation supplier"
  }
}

And there are no such WAVE1 updated to WAVE2 devices.

You only need to delete any file that isn't a *.ttpkg (TomTom Package) in the "SWL/*/Data/data-pkg/NAV/MAP/" folder:

find /Volumes/*/SWL/002*/Data/data-pkg/NAV/MAP/ -type f ! -name "*.ttpkg" -delete

The installation process will verify the SHA256 digest of every update file, but also that full folder (see the last 2 lines of the "SWL/00231*/HashList.ini" file). Any extra files in that folder, the SHA256 hash will be different and the update fails.

Accordingly with historic data (time since a version has been in the testing stage and then released to the public), and if they won't withdraw these testing versions, new European map versions should be released next month.

Quote from CitronenFahrer

Where can I download it?

Sorry, no download links for testing versions. Hopefully, this should be released to the public in a couple of weeks.

This 31.0.0-r0 version was compiled on 13 Apr 2026 (based on TomTom MapVersion Europe 1170.13188) and has been "available" since 29 May 2026. If this version (UpdateID/MediaVersion 002315011776064069) is published, it will be called "31.0.0-r0". They usually release map updates to the public after 1-2 months in testing state.

{
  "updateType": "map-eur",
  "updateVersion": "31.0.0-r0",
  "updateProvider": "TOMTOM",
  "updateId": "002315011776064069",
  "updateDate": "2026/05/29 07:54:40",
  "updateStatus": {
    "code": "AVC",
    "label": "En attente de validation supplier"
  }
}

So probably in July.

EDIT:

BTW, for the NAC_EUR_WAVE1:

{
  "updateType": "map-eur",
  "updateVersion": "32.0.0",
  "updateProvider": "TOMTOM",
  "updateId": "002315011776062834",
  "updateDate": "2026/05/29 11:16:50",
  "updateStatus": {
    "code": "AVC",
    "label": "En attente de validation supplier"
  }
}

I've installed the testing version of the map-eur_31.0.0-r0 for the NAC_EUR_WAVE2 and it's been working fine in the last couple of weeks.

There's also a new testing version for the NAC_EUR_WAVE1 (32.0.0). For the NAC_EUR_WAVE4 I didn't find any testing version, but that's probably because the Majestic API doesn't really support Wave levels. For the NAC_EUR_WAVE3 you're expected to install a 4x.xx.xx.xx firmware and convert it to a NAC_EUR_WAVE4.

That license, "license_0D01230961D4D9656BCB_001315031650642080.key " is for the 44.02.16.52_NAC-r0 firmware version .

The firmware version actually offered by the Majestic API, 44.06.44.22_NAC_r0 (UpdateID 001315031671116172), hasn't been changed since 6 Apr:

> curl --head https://ds4emloty3shq.cloudfront.net/CONTINENTAL/NAC_EU/ovip-int-firmware-version/PSA_ovip-int-firmware-version_44-06-44-22_NAC-r0_NAC_EUR_WAVE4.tar
HTTP/2 200
content-type: application/octet-stream
content-length: 6285709824
last modified: Mon, 06 Apr 2026 08:19:09 GMT

I find it odd that file magically works again...

The 22.07.88.52_RCC-r0 firmware version is, in fact, a Continental RCC system (RCC_CN_WAVE2.20) - https://sites.google.com/view/…c/system/rcc/cn/wave-2-20

But because that firmware version has almost 7 years old, its signing certificates are already expired and the update is impossible to install.

Your current firmware versions, 22.06.25.52_RCC-r0, is used in another system, RCC_CN_WAVE2 - https://sites.google.com/view/nac-rcc/system/rcc/cn/wave-2 but to be sure, input your VIN in my page and you should be able to identify it. If this is the case, you already have the latest version for that system.

{
  "updateType": "ovip-int-firmware-rcc-dpca",
  "updateVersion": "22.06.25.52_RCC-r0",
  "updateProvider": "CONTINENTAL",
  "updateId": "001315211498481011",
  "updateDate": "2017/06/27 09:24:00",
  "updateStatus": {
    "code": "AVC",
    "label": "En attente de validation supplier"
  }
}

AFAIK the DPCA (Dongfeng Peugeot-Citroën Automobiles) and CAPSA (Changan PSA DS Automobiles), respectively VINs that start with "LDC" and "LPA", can use the same firmware update files in RCC_CN_WAVE* systems, although it exists different files for each marque (the difference is just the certificate). This is not true in the NAC_CN_WAVE* systems.

The Magneti Marelli In-Vehicle Infotainment (IVI) R1 system is used in many Stellantis products, but it is unsupported on my site because it has only OTA updates. You can't download any updates for that system.

The Citroën/DS/Opel/Peugeot/Vauxhall Update software and the Mittns Toolbox can only be used for systems that you use a USB flash drive to update.

Is that VIN correctly identified on my page - https://sites.google.com/view/nac-rcc/ ?

The USB port must be the same one used for upgrading.

Vehicles from that era usually had 2 USB ports, a type-A used for sharing data with the infotainment system (that you can use with a USB flash drive with .MP3 audio files or upgrading the firmware/maps AND for Apple CarPlay or Google Android Auto). The adapter/dongle must be connected here.

The type-C is only used for charging and it isn't connected to the infotainment system. This one usually has a battery symbol.

If that's a NAC_EUR_WAVE4, you cannot use the Peugeot Update or the Mittns tool - both give you the wrong update file, you must prepare the USB flash drive manually. See my recent posts.

The Peugeot Update and the Mittn's Toolbox use the same API, so they both offer the same update files. Sometimes that API is misconfigured and offers the wrong files.

For instance, right now, the last firmware version for the NAC Wave 4 is the 44.07.33.32_NAC-r0 (that you can't install, BTW) and the file offered by those software is https://ds4emloty3shq.cloudfro…_NAC-r0_NAC_EUR_WAVE4.tar with 6 312 210 432 bytes. You can't install this update, it also gives you the "Version not compatible with hardware" error.

But there's also the https://majestic-web.mpsa.com/…_NAC-r0_NAC_EUR_WAVE4.tar file with 6 312 212 480 bytes that will install fine. Sometimes you have to do things manually...

The file https://ds4emloty3shq.cloudfro…_NAC-r0_NAC_EUR_WAVE3.tar (6 158 254 080 bytes) that they used to update the firmware was uploaded on 29 Oct 2025, but the older https://download-cde.tomtom.co…_NAC-r0_NAC_EUR_WAVE3.tar (with 24 874 301 440 bytes, because it also includes the map_eur-10.0.0-r0) is still available and was offered by those tools long after 29 Oct 2025. You can't install that file.

And you can't update your firmware until Stellantis acknowledges you already have a NAC_EUR_WAVE4 system, because you can't generate a license key for any version of the system. You can confirm your system is still identified as a NAC_EUR_WAVE3 on my page, despite already having a NAC Wave 4 system and map installed.

The Opel Update software should automatically download the appropriate firmware license key.

If you prepare the USB flash drive manually, you only need the license key if your car is not connected to the internet - either directly to a WiFi AP, a valid and active connection service subscription or the Bluetooth-connected phone is sharing mobile data (tethering). If your car is connected to the internet, the installation process should automatically verify the key online.

Stellantis recently changed the last firmware version for the NAC Wave 4, to update the internal signing certificate, so there's a higher probability they messed up. There are 2 versions of that file:

https://majestic-web.mpsa.com/…_NAC-r0_NAC_EUR_WAVE4.tar 21 Jan 2026, 6 312 212 480 bytes

https://ds4emloty3shq.cloudfro…_NAC-r0_NAC_EUR_WAVE4.tar -4 Feb 2026, 6 312 210 432 bytes

That key is for the 42.03.33.42_NAC-r0 firmware version for the NAC Wave 3. If you're using the "Opel Update" software you don't need to manually download the key.

In the NAC_EUR_WAVE3 and NAC_EUR_WAVE4 systems you can select individual countries, in the previous hardware versions (NAC Wave 1 and 2) you didn't had such option.

In any case, all installed maps are deleted before installing new ones, so if you want to keep those old maps, you have to select them again in the installation process.

Another problem is the official update software (Peugeot Update in this case) won't offer you that 17.0.0-r0 version again, because you already have that version installed. So you have to manually prepare the USB flash drive, downloading that version and extract it to a FAT32-formatted USB flash drive.