I went through all the python/CW and the Matlab setups. The waveforms are visible in the capture GUI.
Also, the MATLAB has a valid Python environment. My working directory is also the location of the .m script files. However, cwconnect() throws some error:

Hi debayan,
I am taking a look into it now. There is a good chance that the updating of this documentation was overlooked during the transition to cw 4.0. If that is the case I will test working steps and update the wiki documentation.
Cheers,
Franz

Thanks for your response.
Running ‘pip install chipwhisperer’ from the WinPython Command Prompt installed the v3.5 CW capture.
So, it is the CW v3.5 running with Python 2.7.10.3.
Please let me know what I should do to resolve the issue.

I am not able to solve the problem.
Can you please tell me the versions of the Python and CW that worked for Windows 7/10 with Matlab R2015?
Both Win 7/10 gives the same error in Matlab (as in the last reply).
Am I missing anything?

I cannot replicate this error on my system, I have been trying numerous possibilities. Chipwhisperer works with the python interpreter without matlab, and “py.importlib.import_module(‘chipwhisperer’)” does not work which bypasses the MATLAB api and manually imports chipwhisperer, which means it is most likely a different problem.

The place I have seen the "Python Error: DLL load failed: The specified procedure could not be found. " is when there is 64-bit version vs. 32-bit version problems. You could try uninstalling chipwhisperer and MATLAB and the cw example api and then reinstall everything but keep it as isolated as possible, so do not add the python included in your installation to the system path and check if your system wide python is not interfering with MATLAB paths (if you have a different python installation installed)

Also make sure everything you have installed is 64 bit, because the DLL exception usually arises when there is problem related to this. It could also be a problem with MATLAB’s api to python, I experienced a few issues with how MATLAB caches calls to the python functions (restarting MATLAB after deleting the *.pyc files usually fixed this).

It could also have to do with and issue with 2015b version that was fixed in later versions (as I am testing with 2017b). If you can it might be good to upgrade your MATLAB installation to the latest one.

Other than that I am not sure what the issue could be. I hope one of these suggestions helps you find a way to fix the problem, or at least give you a starting point on what to look for.

If you choose the second method you have bypassed the api and need to use the chipwhisper package manually as you would a python package.

I just want to make sure it is not related to you not disconnecting from the scope. Easiest way to disconnect between uses is to unplug the chipwhisperer and plug it back into the computer. Normally you would run

scope.dis()

target.dis()

When running commands you just have to be careful not to try to connect to the scope when it is already in use. More information can be found on the wiki page MATLAB 4.0 api usage

Hope this helps. If you get another error just post that. Another quick question: you are still using cw 4.0?
Cheers,
Franz