Adafruit-PlatformDetect version 3.60.0 was unable to identify the board about adafruit_blinka HOT 13 CLOSED

@makermelissa This appears to be failing with Python 3.12 on Windows and macOS, even with the MCP2221 env var set?

from adafruit_blinka.

@mrdrdemmy Note that the Terminal window in VSCode is PowerShell, by default, so you need to use $env:BLINKA_MCP2221=1, not set BLINKA_MCP2221=1. I have added a note to the Guide about this.

from adafruit_blinka.

Same deal here (yes, latest package is reported to have been installed). At the Python prompt:

>>> import board Traceback (most recent call last): File "<stdin>", line 1, in <module> File "C:\Users\xyz\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.11_qbz5n2kfra8p0\LocalCache\local-packages\Python311\site-packages\board.py", line 387, in <module> raise NotImplementedError( NotImplementedError: Adafruit-PlatformDetect version 3.60.0 was unable to identify the board and/or microcontroller running the Windows platform. Please be sure you have the latest packages by running: 'pip3 install --upgrade adafruit-blinka adafruit-platformdetect'

I am not sure what is being looked for here. The desktop machine is a year-old Dell Vostro, running an up-to-date Windows 11. A mcp2221a breakout is connected, and looks fine in device manager. What's up?

EDIT (per dhalbert, below): I am using the latest VS Code and build tools, and followed the instructions at https://learn.adafruit.com/circuitpython-libraries-on-any-computer-with-mcp2221.

from adafruit_blinka.

I had the same problem, but changing the Python version from 3.10 to 3.9 fixed it.

from adafruit_blinka.

I have version 3.11.6 installed, and bristle at being compelled to roll back just to address an otherwise obscure issue. I will give it a shot, though, and see whether it was worth the effort. Thanks for the tip!

from adafruit_blinka.

Well, that was easy. On a whim, I moved up to 3.12.2, instead of down to 3.9, and the blinka install worked after that. Thanks again for the versioning tip!

from adafruit_blinka.

Whoops. Upgrading to 3,12,2 DID NOT fix the problem; import board continues to yield the same error as above. Python.org no longer offers an installer for version 3.9, so I will be putting this little project aside pending more ideas. Too bad, since the mcp2221 breakout would have been pretty handy.

Apologies, if I led anyone astray with my previous comment!

from adafruit_blinka.

@mrdrdemmy and @raku9cam Please edit your posts above to make clear exactly what platform you are running on, if you've set any environment variables for an MCP2221, etc., and how you're setting them. Someone was trying to set the variable in a VScode terminal window, for instance, and that did not seem to work.

from adafruit_blinka.

I did set BLINKA_MCP2221=1 in the VS Code terminal. It's interesting to learn about the potential VS Code issue, though I haven't noticed trouble setting environment variables there before (e.g., when wrestling with the pico pi sdk install). I'll try setting it outside of VS Code when I get a chance. Thank you.

from adafruit_blinka.

per dhalbert, above: "Someone was trying to set the variable in a VScode terminal window, for instance, and that did not seem to work."

YES! Adding BLINKA_MCP2221 to my local environment outside of VS Code worked. I guess that'll have to go in my start-up script now.

Thank you for your help.

from adafruit_blinka.

@caternuson of interest to you

from adafruit_blinka.

@mrdrdemmy Note that the Terminal window in VSCode is PowerShell, by default, so you need to use $env:BLINKA_MCP2221=1, not set BLINKA_MCP2221=1. I have added a note to the Guide about this.

Ah. Good catch! Thank you very much.

from adafruit_blinka.