Ford Peprah

This is a known bug. I just merged in a PR #25, which should remedy this issue for you if you upgrade to `0.1.3` of the package.

You can suppress that pop-up (only shows up on Windows actually) by calling `disable_dialog_boxes()` before calling `open()`. I believe the DLL has some logic around unlocking as well. I would...

It should happen automatically if you've specified the device correctly. There are unlock methods, but I've only implemented the unlock sequence for the Kinetis chip family.

Whoops, you are correct, we by default specify `NO` to unlock automatically.

Which exception is thrown? If you run with logging enabled, you should see more helpful messages: ``` import logging logging.basicConfig(level=logging.DEBUG) ```

This is definitely an issue. Unfortunately, I think renaming the module would have wide reaching consequences for downstream consumers. If you're not already using it, would maybe a [virtual environment](https://docs.python.org/3/tutorial/venv.html)...

Hello, Do you mean changing the last few bytes of the image you're flashing? There are two flashing apis: [`flash`](https://pylink.readthedocs.io/en/latest/pylink.html#pylink.jlink.JLink.flash) and [`flash_file`](https://pylink.readthedocs.io/en/latest/pylink.html#pylink.jlink.JLink.flash_file). I'm going to assume you're using the latter....

We currently provide both Python2 and Python3 support; the provided wheels and tarballs on PyPi are both PY2 and PY3 compatible: https://pypi.org/project/pylink-square/#files

This doesn't seem to be a secured issue. `WindowsError` generally indicates a Windows system call error. This could be related to what is being fixed by PR #25, so I'd...

We currently have not implemented an `unlock` method for the STM32 in PyLink FWIW.