You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Keil pack list site shows the latest version as 8.24.1. The pindex section of keil.vidx has a link to the nRF DFP version 8.7.1. (There is no Nordic-hosted pidx.) But the NordicSemiconductor.nRF_DeviceFamilyPack.8.7.1.pdsc file shows the most recent version is 8.26.0.
I think I understand why the keil.vidx and PDSC differ. The link to the PDSC is owned by Keil, whereas the PDSC and pack are on Nordic's site. So instead of communicating with the Keil team, Nordic has just continued to add new versions in the same PDSC without renaming the file and pack. Of course, this breaks the CMSIS-Pack versioning scheme.
When I attempt to download the nRF DFP using CPM via pyOCD, it reports this error:
$ pyocd pack -i nrf91
Downloading packs (press Control-C to cancel):
NordicSemiconductor::nRF_DeviceFamilyPack::8.26.0
Oct 05 12:01:13.923 WARN No such file or directory (os error 2)
The version mismatch is undoubtedly the culprit here.
I'm not really sure what CPM should do to work around this, mostly because I'm not sure where the error is actually coming from.
The nRF DFP is all screwed up…
The Keil pack list site shows the latest version as 8.24.1. The
pindex
section ofkeil.vidx
has a link to the nRF DFP version 8.7.1. (There is no Nordic-hosted pidx.) But theNordicSemiconductor.nRF_DeviceFamilyPack.8.7.1.pdsc
file shows the most recent version is 8.26.0.I think I understand why the
keil.vidx
and PDSC differ. The link to the PDSC is owned by Keil, whereas the PDSC and pack are on Nordic's site. So instead of communicating with the Keil team, Nordic has just continued to add new versions in the same PDSC without renaming the file and pack. Of course, this breaks the CMSIS-Pack versioning scheme.When I attempt to download the nRF DFP using CPM via pyOCD, it reports this error:
The version mismatch is undoubtedly the culprit here.
I'm not really sure what CPM should do to work around this, mostly because I'm not sure where the error is actually coming from.
cc @jkrech
The text was updated successfully, but these errors were encountered: