8000 J-Link .dll placement & use unclear. Test driving JTAG-Boundary Scan tools. · Issue #7 · colinoflynn/pyjtagbs · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
J-Link .dll placement & use unclear. Test driving JTAG-Boundary Scan tools. #7
Open
@floriangmeiner

Description

@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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0