-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Python3 interface for library #4
Comments
I'm going to be reorganizing the python module - I decided in the end it might be easier keeping the python side in a separate project (which could work with other backends later). Could still easily add the "core" part to this project - I'm open. For now I'll keep all my Python stuff separate to avoid problems! |
I read your article on Circuit Cellar and share your interest in this codebase as an extensible library of JTAG boundary scan algorithms. Take a look at my pull request. Does this offer a simpler way to build your Python3 interface? |
Short comment first - thanks so much for this library, I spent a while playing with various JTAG boundary scan options and it's frustrating how hard it is to toggle some IO pins for testing with other tools. I came close to buying some of the very expensive tools even but they wouldn't provide enough up-front information.
I'm adding a Python interface to this library, so far it seems to work OK (tested on Windows 10 w/ JLINK). See https://github.com/colinoflynn/jtag-boundary-scanner/tree/python-interface/pylibjtag
You use it something like this:
I've included my library build in that repo to make it easier for other people to use. I had a few issues I ran into - I can open separate issues for them or just paste as comments here, roughly around:
script_printf
was set to null and isn't checked (I routed it to just not print)drv_LPT_libGetDrv
so I commented them out (I'm nowhere near LPTs these days)Finally - do you want to have the Python interface as part of the repo (i.e. - I can open a PR once it's cleaner)? If you're not using Python you might be hesitant too for future support. I can start it as a separate project if you prefer, but it makes more sense to have it here to me (especially to keep any changes in the library & Python API in sync).
The text was updated successfully, but these errors were encountered: