Attachments (0)
Nordic Case Info
  • Case ID: 339861
Options

Getting error "ImportError: Module use of python312.dll conflicts with this version of Python." when flashing - can build perfectly fine

SoldOutYungLean

I get the error "ImportError: Module use of python312.dll conflicts with this version of Python." when I try to flash my device using any Python version below 3.12.x. I get no error when I try to build the project.

However, when I set the global Python version to 3.12.0 using pyenv, it first and foremost correctly doesn't recognize the nrfutil package until I install it into the new version, which is a sign that it has correctly changed the version, but I also get a new error related to not having the package "constants." When I pip install that I get a third error:

Fullscreen
1
2
3
versions\3.12.0\Lib\site-packages\nordicsemi\lister\windows\lister_win32.py", line 43, in <module>
from constants import DIGCF_PRESENT, DEVPKEY, DIGCF_DEVICEINTERFACE
ImportError: cannot import name 'DIGCF_PRESENT' from 'constants' (C:\Users\DripTooHard\.pyenv\pyenv-win\versions\3.12.0\Lib\site-packages\constants.py)
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX


Looking online, it seems like the fix to this issue is to downgrade to 3.8 or 3.9. But this just goes back to me having the original error.

I tried looking at the support information, and it seems like the toolchain is reffering to a Python 3.12.4 version?

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
// IMPORTANT: The following data can contain sensitive or confidential information about your environment.
// If you do not want others to see this information, make sure to remove it before sharing the data.
// For help and support, visit Nordic Semiconductor's DevZone at https://devzone.nordicsemi.com/.
{
"platform": {
"os": "win32",
"osVersion": "Windows 11 Home",
"osKernel": "10.0.26100",
"vscode": "1.96.4",
"electron": "32.2.6",
"node": "v20.18.1"
},
"system": {
"date": "2025-01-30T15:19:16.999Z",
"vscodeRoot": "d:\\DripTooHard\\Microsoft VS Code\\resources\\app",
"nrfConnectForDesktopInstalled": true,
"vscodeUptime": "00:12:00",
"osUptime": "00:36:06",
"cpu": "11th Gen Intel(R) Core(TM) i5-11400H @ 2.70GHz"
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX


I am wondering if the fix would be to somehow change the python version in the toolchain, but I would like to hear first if you have any other suggestions? I have gone through my path and replaced all occurances of Python with a refference to 3.8.6, but once again, it appears that pyenv is correctly setting the right python versions, so this is most likely not a path issue.

  • 0

    Same issue since 2 or 3 days, don’t know why, any partial build will fail, but a pristine will work…

    I don’t know why I can’t post my output in this editor, it says “An error has occured. Please try again or contact your administrator” so here it is on pastebin: https://pastebin.com/HzGZv3jd

  • 0

    Hi

    Are you using the VS Code extension for NCS here when seeing this issue? Have you tried removing the 3.12.x version(s) of Python from your computer altogether on your end so you only have versions 3.8 or 3.9 installed?

    Also, since this is related to flashing a device only, can you share some information on what device you're trying to flash here, is it an nRF54L15 DK or custom board. If it's a DK, what version of the board do you have?

    Best regards,

    Simon

  • 0 in reply to Simonr

    Hello Simon,

    Yes I have tried removing the 3.12.x version of Python. It didn't work. It is indeed the VS code extension.

    It is the nRF54L15DK, I am not quite sure how to read the information you're requesting from the board, but it has the following values on the sticker:

    PCA10156
    0.9.1
    2024.45
    1057733114

    With that said, I do believe the issue is related to nrfutil more than the boaard itself.

  • 0

    Hi

    Thanks, I have made an internal ticket with the VS Code extension developers now and I'm awaiting their feedback. Can you confirm you also see mentions of v3.12.x of Python after uninstalling all instances of this Python version as well?

    The HW information you provided is what I was after. I just wanted to confirm you were working on a DK that is expected to work in the first place.

    Suggestion from our devs: You should not use pyenv with NCS or the toolchains. Try removing the following on your end and see if that helps with this

    C:\\Users\\DripTooHard\\.pyenv\\pyenv-win\\shims\\nrfutil": null,

     

    Best regards,

    Simon

  • 0 in reply to Simonr

    Hey Sigmar,

    How do you mean "remove it"? Any file related to nrfutil from the shims folder? I tried that, but then it prompted me to install the library.

    I will investigate whether uninstalling pyenv will solve it. If so, I would reccommend looking into making pyenv compatible with your toolchain as it is quite commonly used.

1 2
Terms of service