J-Link .dll placement & use unclear. Test driving JTAG-Boundary Scan tools.

[floriangmeiner]

Hello @colinoflynn,

Thank you for making this publicly available.

I'm trying out a bunch of tools and as a part of this test drive I'm trying out the Viveris - JTAG Boundary Scanner application but I'm having difficulties detecting the J-Link I have.

Your comments:

WARNING: The .dll in the repo is only a 32-bit build, so this only works with 32-bit Python on Windows

and Viveris' comment:

JLINK JTAG probes support. Note : JLinkARM.dll need to be copied into the JTAGBoundaryScanner folder for the JLink probes support.

Are a bit unclear to me. For the Viveris comment, do I need to recompile with the DLL path properly referenced? I've tried placing it everywhere I could think of and it won't detect the J-Link. Viveris I think also have also recently released a 64-bit executable I'm using for this.

Any guidance would be greatly appreciated.

Florian

[wuwbobo2021]

The 32-bit JLinkARM.dll from Segger is placed in the examples folder, it should be placed in the path of the script file (according to README.md).

The 64-bit libjtagcore_x64.dll simply doesn't work with the current pyjtagbs. See __init__ in jtagcore.py. I tried to modify the code, forcing it to load the 64-bit DLL, but failed: #8. I have to use the 32-bit Python.