Posts by rui.saraiva

The UpdateID 001315031613548831 (that you used in the previous URL to download the license) is for firmware version 21.08.87.32_NAC-r1. That license obviously doesn't work with the latest firmware version for the NAC Wave 2, 21.08.90.52_NAC-r0 (UpdateID 001315031666020829).

But if you use the Toolbox to prepare the USB flash drive, everything should be fine.

The UpdateID you posted (3C0023...) is invalid, but any UpdateID that starts with "0023" is a map update and those doesn't have any license to download.

With this information (1st post)

HMI version: rcc2019.82.19.16.2.1.00
iMX version: x0401065_190620_19.1E027.2
V850 Version: RCC19_19.1S18.5

It's clearly a RCC Wave 3 (RCC_EU_W3_ECO) with the 1st 084 system version installed (UpdateID 005315191561110251).

It doesn't make any difference - any software that uses the Majestic API, using that VIN will download the updates for the NAC Wave 4 system.

It isn't the first time the information stored in the Peugeot/Stellantis servers is wrong.

As I wrote, he needs the original VIN from where that RCC came from (probably impossible to know), or the UIN that he could find in the head unit's label. Because it's a RCC system, without using a diagnostic software, it's is impossible to know the UIN. In a NAC system, you could use the "export config" option and find the UIN in the created files. Or find it in the spylogs. No sush options on a RCC system.

By the way, the UIN from that NAC Wave 4 was validated in January 2020:

[
  {
    "uin": "0D01152109D4F220799A",
    "creationDate": "2020/01/19 05:15:12",
    "updateDate": "2020/01/20 16:15:06",
    "type": "create",
    "status": {
      "code": "VAL",
      "label": "Request validated"
    }
  }
]

murpi89 To download the correct license, you need either the VIN of the car from where that head unit came, or the labels in that head unit:

Thread

Here's how to find out the RCC Serial Number (UIN) for the License Key

I changed my RCC A1 for an RCC A2, however, I didn't know the VIN number of the donor, I don't have an Arduino or Diagbox, so I couldn't know what the serial number of the RCC A2 was, to generate the license key for that I could update my RCC A2.

When preparing the update pendrive with my car's VIN, for the RCC A1 (using Citroen Update), I noticed that part of the UIN number that appears is on the RCC label. The only part that is not on the label are the first three characters (2D0). Look at the…

marbroalves

Feb 28th 2024

murpi89 You have a Bosch RCC Wave 3 head unit and you're trying to install a Continental NAC Wave 4 firmware...

Yesterday was released another RCC Wave 3 firmware, 6_0431_23.2I41.1, maybe it can help with your problem.

If you install this new firmware, please post here the HMI. iMX and V850 versions.

That is already the latest firmware version for the RCC Wave 3.

And in RCC systems, you cannot reinstall the same version, only upgrade.

It is also impossible to install any map update for the NAC Wave 3, they all have, you guessed it, expired signing certificates. Right now, you could only install:

It seems the 44.07.33.32_NAC-r0 firmware version is available again in PUB status.
It should be possible to upgrade using the Peugeot Update software or with an online installation (without the license key on the USB flash drive):

{
  "updateType": "ovip-int-firmware-version",
  "updateVersion": "44.07.33.32_NAC-r0",
  "updateProvider": "CONTINENTAL",
  "updateId": "001315031692686757",
  "updateDate": "2025/01/28 12:39:24",
  "fileName": "PSA_ovip-int-firmware-version_44-07-33-32_NAC-r0_NAC_EUR_WAVE4.tar",
  "updateStatus": {
    "code": "PUB",
    "label": "Publié"
  }
}

The .tar update file is exactly the same, there's no need to download it again if you already have an older version (it hasn't had any problem in the first place anyway...).

The previous 44.07.05.22_NAC-r0 version is still in AVP status and probably died right here...

No, you can't install a Chinese firmware for the NAC CN Wave 4 on a NAC EUR Wave 4 hardware.

Also, the Chinese versions use a cartography/map sold by AutoNavi that isn't compatible with the EURopean versions (P6CNS format) and the TomTom doesn't have a cartography for the Chinese territory (although they have the name "map-cm" reserved and the respective 00231565... UpdateID/MediaVersion).

Those 2 firmware versions, 44.07.xx.xx, that still are signed with a valid certificate, are no longer in PUB status. So MyPeugeot/Peugeot Update/Mittns Toolbox will offer the latest version that is in PUB status, the 44.06.44.22_NAC-r0, that hasn't a valid certificate and it is impossible to install.

Because those 2 firmware versions 44.07.xx.xx are no longer in PUB status, you also need to prepare the USB flash drive manually, copy the license file to it and the car must be offline.

They're f*cking consistent, now it is impossible to install any NAC firmware.

Those connection errors are probably because there's corrosion (caused by the AdBlue itself) in the ECU module PCB or electric cables/connectors inside the AdBlue tank.

I had that P20E8 DTC and the (supposedly hermetic) box above the tank had AdBlue inside.

Because the latest NAC Wave 2 firmware version (21.08.90.52_NAC-r0, that is) is not in PUB status, you probably need the digital license/key in the USB flash drive. The generic "Version not compatible with hardware" error message now might be because the license cannot be verified online and not the expired certificate.

kenan1206 : Only the certificate for the last NAC Wave 2 firmware version (21.08.90.52_NAC-r0) was updated. The last 2 firmware versions for the NAC Wave 4 (44.07.*.*_NAC-r0) still have valid certificates.

File downloaded from https://ds4emloty3shq.cloudfro…_NAC-r0_NAC_EUR_WAVE2.tar (2 729 062 912 bytes, old file was 2 728 908 800 bytes):

> openssl smime -in SWL/001315031666020829/MediaHeader/MediaVersion.ini -pk7out | openssl pkcs7 -print_certs -text | head
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            7e:3e:30:93:b5:e0:50:3a:43:c3:02:68:b1:06:c4:1d:fb:35:db:b7
        Signature Algorithm: sha256WithRSAEncryption
        Issuer: C=FR, L=Paris, O=PSA Peugeot Citroen, OU=Certificate Authorities, OU=(c) PSA Peugeot Citroen - For authorized use only, OU=0002 319187308, CN=PSA - OVIP - Code signing - G1
        validity
            Not Before: Nov 8 18:27:06 2023 GMT
            Not After : Nov 8 18:27:06 2026 GMT
        Subject: C=FR, L=Paris, O=PSA Peugeot Citroen, OU=Open Vehicle Infotainment Platform, OU=(c) PSA Peugeot Citroen - For authorized use only, CN=Continental \/ NAC \/ 1

SHA256 sums of PSA_ovip-int-firmware-version_21-08-90-52_NAC-r0_NAC_EUR_WAVE2.tar:

885fa4ea3ee469d867c74a1f3cdde2c960b250582abf07f3ebcf932b0e15555c Original file, certificate expired on 8 Nov 2024
0b9dcb42e6d5d1d11d97230f49f818ed68373a93659965cb3bd9bf3bb4b62d39 File from 3 Dec 2024, new PSA-OVIP-CS-G1.crl
a7ebd29a468f23779994fae4df426354d6dbc6516b28e43a56bc09678a6934dd File from 9 Jan 2025, signed MediaVersion.ini

DerDieDasWerWieWas

> curl --head https://ds4emloty3shq.cloudfront.net/CONTINENTAL/NAC_EU/ovip-int-firmware-version/PSA_ovip-int-firmware-version_21-08-90-52_NAC-r0_NAC_EUR_WAVE2.tar
HTTP/1.1 200 OK
Content-Type: application/octet-stream
Content-Length: 2729062912
Connection: keep-alive
Date: Thu, 09 Jan 2025 15:57:00 GMT
Last-Modified: Thu, 09 Jan 2025 08:40:10 GMT

This is the new file, uploaded today. The Majestic API was returning a "PSA_ovip-nt-firmware...", missing an "ï".

Quote from Arminius

Quote from rui.saraiva

It seems they finally fixed it - And it just took 2 months for them to figure it out!

A new update was reuploaded today, and the code is finally signed with a valid certificate (until 8 Nov 2026).

For the Wave 2, or in general?

Wave 2 only. Don't ask too much, it only took 2 months to sign a file with a certificate they already had!...

It seems they finally fixed it - And it just took 2 months for them to figure it out!

A new update was reuploaded today, and the code is finally signed with a valid certificate (until 8 Nov 2026).

Quote from Arminius

Quote from rui.saraiva

For instance, the signing certificate of the map-eur_28.0.0-r0 (for NAC_EUR_WAVE2):

Besteht eigentlich die Möglichkeit in einem Zertifikat (mit passender Software) die Ablaufzeit einfach zu ändern, um so die Gültigkeit zu verlängern?

This is the base of all cryptography, so no...

Quote from Herbert

rui.saraiva

Gibt es inzwischen schon neuere Informationen zu den nicht funktionierenden SW-Updates?

No. The history goes something like:

3 Nov 2024: Certificate expired, updates are now "impossible" with the generic "Version not compatible with hardware" error;

3 Dec 2024: New .tar file was uploaded with a new certificate, but the code wasn't signed using it;

13 Dec 2024: They removed the "PUB" (Published) status from the 21.08.90.52_NAC-r0 version (now in "AVC" status - Waiting for supplier validation), the previous 21.08.87.32_NAC-r1 is now the latest version with "PUB" status - everything that uses the Majestic API (Peugeot Update, MyPeugeot, Mittns toolbox, etc) now offers that version, but is also signed with the certificate that expired in 3 Nov 2024...

So it seems that they are aware of the problem, but don't know how to fix it!