Thank you for opening an issue on an Adafruit Python library repository. To
improve the speed of resolution please review the following guidelines and
common troubleshooting steps below before creating the issue:
Do not use GitHub issues for troubleshooting projects and issues. Instead use
the forums at http://forums.adafruit.com to ask questions and troubleshoot why
something isn't working as expected. In many cases the problem is a common issue
that you will more quickly receive help from the forum community. GitHub issues
are meant for known defects in the code. If you don't know if there is a defect
in the code then start with troubleshooting on the forum first.
If following a tutorial or guide be sure you didn't miss a step. Carefully
check all of the steps and commands to run have been followed. Consult the
forum if you're unsure or have questions about steps in a guide/tutorial.
For Python/Raspberry Pi projects check these very common issues to ensure they don't apply:
If you are receiving an ImportError: No module named... error then a
library the code depends on is not installed. Check the tutorial/guide or
README to ensure you have installed the necessary libraries. Usually the
missing library can be installed with the pip tool, but check the tutorial/guide
for the exact command.
Be sure you are supplying adequate power to the board. Check the specs of
your board and power in an external power supply. In many cases just
plugging a board into your computer is not enough to power it and other
peripherals.
Double check all soldering joints and connections. Flakey connections
cause many mysterious problems. See the guide to excellent soldering for examples of good solder joints.
If you're sure this issue is a defect in the code and checked the steps above
please fill in the following fields to provide enough troubleshooting information.
You may delete the guideline and text above to just leave the following details:
Platform/operating system (i.e. Raspberry Pi with Raspbian operating system,
Windows 32-bit, Windows 64-bit, Mac OSX 64-bit, etc.): Raspberry Pi Zero with RPi OS (32-bit)
Python version (run python -version or python3 -version): Python 3.7.3
Error message you are receiving, including any Python exception traces: Basically I can't get Adalink to detect OpenOCD 0.11.0 which is installed correctly on the system path and works with my ST Link v2, detecting an ATSAMD21G18. I installed Adalink using the Python command from : https://github.com/google/myelin-acorn-electron-hardware/tree/main/a3000_rom_emulator/bootloader ,it's version 2.5.0 also I cloned the Adafruit_Adalink repo and used the OpenOCD install script with the version of OpenOCD changed to 0.11.0, which downloaded and compiled correctly on my up-to-date RPi OS on a Pi Zero with a Waveshare USB and LAN hub (Plug'n'play). The openocd.cfg file uses 'stlink.cfg', swd transport is selected and I used the at91samdXX.cfg in Tcl/Target to detect the ATSAMD21G18 id code in the Arcflash board correctly. The ST Link v2 has the most recent firmware and STLink rules package installed (using the firmware updater and Rules for Linux utils from ST.com). If I try to modify the stlink.py in the installed Adalink with the path to openocd, which is in /usr/local/bin/, OpenOCD isn't detected like with no modification of the stlink.py, with the error: cannot use a string pattern on a bytes-like object. The traceback says of the _test_openocd (line 77 in stlink.py) that the error is re:IGNORECASE | re:MULTILINE and more string/bytes like object in the re.py file, line 183.
I don't think that the code can be correct for the recent version of OpenOCD because the error is a generic type that doesn't have logical basis.
List the steps to reproduce the problem below (if possible attach code or commands
to run): adalink atsamd21g18 --programmer stlink --info
Thank you for opening an issue on an Adafruit Python library repository. To improve the speed of resolution please review the following guidelines and common troubleshooting steps below before creating the issue:
Do not use GitHub issues for troubleshooting projects and issues. Instead use the forums at http://forums.adafruit.com to ask questions and troubleshoot why something isn't working as expected. In many cases the problem is a common issue that you will more quickly receive help from the forum community. GitHub issues are meant for known defects in the code. If you don't know if there is a defect in the code then start with troubleshooting on the forum first.
If following a tutorial or guide be sure you didn't miss a step. Carefully check all of the steps and commands to run have been followed. Consult the forum if you're unsure or have questions about steps in a guide/tutorial.
For Python/Raspberry Pi projects check these very common issues to ensure they don't apply:
If you are receiving an ImportError: No module named... error then a library the code depends on is not installed. Check the tutorial/guide or README to ensure you have installed the necessary libraries. Usually the missing library can be installed with the
piptool, but check the tutorial/guide for the exact command.Be sure you are supplying adequate power to the board. Check the specs of your board and power in an external power supply. In many cases just plugging a board into your computer is not enough to power it and other peripherals.
Double check all soldering joints and connections. Flakey connections cause many mysterious problems. See the guide to excellent soldering for examples of good solder joints.
If you're sure this issue is a defect in the code and checked the steps above please fill in the following fields to provide enough troubleshooting information. You may delete the guideline and text above to just leave the following details:
Platform/operating system (i.e. Raspberry Pi with Raspbian operating system, Windows 32-bit, Windows 64-bit, Mac OSX 64-bit, etc.): Raspberry Pi Zero with RPi OS (32-bit)
Python version (run
python -versionorpython3 -version): Python 3.7.3Error message you are receiving, including any Python exception traces: Basically I can't get Adalink to detect OpenOCD 0.11.0 which is installed correctly on the system path and works with my ST Link v2, detecting an ATSAMD21G18. I installed Adalink using the Python command from : https://github.com/google/myelin-acorn-electron-hardware/tree/main/a3000_rom_emulator/bootloader ,it's version 2.5.0 also I cloned the Adafruit_Adalink repo and used the OpenOCD install script with the version of OpenOCD changed to 0.11.0, which downloaded and compiled correctly on my up-to-date RPi OS on a Pi Zero with a Waveshare USB and LAN hub (Plug'n'play). The openocd.cfg file uses 'stlink.cfg', swd transport is selected and I used the at91samdXX.cfg in Tcl/Target to detect the ATSAMD21G18 id code in the Arcflash board correctly. The ST Link v2 has the most recent firmware and STLink rules package installed (using the firmware updater and Rules for Linux utils from ST.com). If I try to modify the stlink.py in the installed Adalink with the path to openocd, which is in /usr/local/bin/, OpenOCD isn't detected like with no modification of the stlink.py, with the error: cannot use a string pattern on a bytes-like object. The traceback says of the _test_openocd (line 77 in stlink.py) that the error is re:IGNORECASE | re:MULTILINE and more string/bytes like object in the re.py file, line 183.
I don't think that the code can be correct for the recent version of OpenOCD because the error is a generic type that doesn't have logical basis.
List the steps to reproduce the problem below (if possible attach code or commands to run): adalink atsamd21g18 --programmer stlink --info