Power Profiler Kit is not detected

[vit bernatik]

Hello I have this error:

Checking installed packages
pyside:          1.2.4
pyqtgraph:       0.10.0
numpy:           1.12.1
pynrfjprog:      9.0.0
Warning: The software is tested with PyQtGraph 0.9.10, and may not work with your version (0.10.0)
Warning: The software is tested with np 1.9.2, and may not work with your version (1.12.1)
Power Profiler Kit started, initializing...
Unable to connect to the PPK, check debugger connection and make sure pynrfjprog is up to date.

I did try to run on other PC and it works. So I'm sure HW switches and FW and everything shall be OK.

I read other threads other threads

And I have everything:

Python 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:42:59) [MSC v.1500 32 bit (Intel)] on win32

I did install MSVC 9.0 (2008) redistributable (vcredist_x86.exe)

I did run python_packages.bat.

I even try to reinstall python 2.7 freshly...

Any other hint???

Also can be the PPK code improved in error reporting? If there is more details what is wrong we could solve it faster...

[vit bernatik]

So I did found the issue. My stupid company rules is that we need to install our development tools to special directory.

Stupid Nordic code expects that everybody installs Segger into: C:\Program Files (x86)\SEGGER\JLink_V*

If only at least the error reporting would do Nordic properly it would save me one step. If you go to ppk.py and change line 1002 from:

    except:
        print("Unable to connect to the PPK, check debugger connection and make sure pynrfjprog is up to date.")

into:

    except Exception as exc:
        print(str(exc))

Then you would get much more useful error info from true exceptions. In my case:

Power Profiler Kit started, initializing...
Could not locate a JLinkARM.dll in the default SEGGER installation path.

Then if you install dll into:

C:\Program Files (x86)\SEGGER\JLink_V612h\JLinkARM.dll

it starts work...

I'm crying that so great Power Profiling Kit is so killed by such a stupid python code. And on top of that written in archaic python 2.7 :(

[wlgrd]

Sorry for writing this stupid code, and thank you very much for the feedback! The reason for hiding the raw exceptions in general was that often times they just cause more confusion. Will make sure to add in the helpful exceptions for the next release. Also yes, it should be python 3, but not all packages was supported before just recently