MCP Fails after install on new PC

[Simon Third]

Hi all,

I've been trying to get a new Win 7 (x64) PC setup with with the Nordic dev tools. Studio, MCP, SDK etc. I've installed Studio (1.17.1) and MCP (3.7.1). This also installed toolkit 6.2.2 (J-Link 4.92) But I get this failure.

MCP_Fails.jpg

Have tried going back to toolkit 6.2.1 with the same issue. The interesting thing is that I have another machine that has be running Nordic tools for a while now which is up to date with these versions also and it works fine.

I tested both dongle versions 0.10 and 0.9 with the same result.

I'm thinking there is something missing from this new PC?

Simon

[Asbjørn]

Did you get a request to update the Segger drivers? J-link 4.92 are a bit old and I would recommend you to upgrade to the latest Segger drivers (4.96).

[Simon Third]

Hi Ashjorn, OK tried that still no joy. It asked me to load the DLL's into the Keil directory, but not a Nordic related directory. Do I have to do a manual copy to somewhere? Maybe this new machine is missing some system level SW that your tools are historically relying on? S3

[Asbjørn]

The dll should only be needed at one place, but I would recommend you to delete studio and MCP, then try to install nRFtools first. After you have installed nRFtools, then try to install studio and MCP again. It shouldn't be a problem, but also make sure you install them with administrator rights.

[Simon Third]

Still no luck. It gets a bit further but still crashes after "SERVER: Server has started." When following your sequence I noted that Toolbox 6.2.1 is installed, but when MCP installs it installs 6.2.2.
I feel something is still missing from this machine as the same installation works fine on my current PC. Is there any debug or logging info I can get for you guys?

[Asbjørn]

I've asked one of the MCP developers to have a look at this one and he would be interested in seeing the log file from MCP from when you start up MCP, program the dongle with the MEFW and then when it crashes. If you could upload it here or send it to us through the MyPage system on Nordics website.

It could be related to the various Segger drivers used and removal of old registries when new versions are installed. So if you haven't tried to remove/erase Segger drivers and then re-installing them yet, that would be the recommendation.