nRFgo Studio hangs when having two j-link kits connected at the same time.

[andlier]

When I'm trying to connect to the new nrf51 dk kit with nrfgo studio, and at the same time have another j-link based dev-kit connected to the PC, the studio hangs while trying to access the wrong kit. I have to close it using task manager.

See attached image of j-link trying to connect to the EFM32 j-link enabled kit, instead of the nordic kit, even though the serial number in the studio is the correct one. But the J-link-driver is trying to connect to a different serial number. This issue does not happen when using the older j-link Lite that was supplied with the old nrf51 dev kit. It only happens with the new nrf51 dk kits. And when I disconnect the EFM32 kit, everything works as normal again. Tried with both 4.96 and 4.98 j-link version, and 1.17 and 1.19 version of nrfgo studio

[Øyvind Karlsen]

Hi,

I will try to replicate the error, which EFM32 kit are you using?

[andlier]

The EFM32GG giant gecko kit, latest firmware. Also latest j-link-firmware on the nordic kits (4 May 2015 firmware). It's not a big issue, just a nuisance. Using nrfjprog mostly, which works fine with the --snr option. But its nice to be able to have nrfgo studio open when I measure power consumption with the efm32-kit, without having to plug it out and in again every time I need do something in nrfgo studio.

[Øyvind Karlsen]

Hi again,

I have attempted to recreate the error with the EFM32GG-STK3700, however I am not getting the consistent results that you are. However inconsistencies do occur when using several development kits at once, but so far nothing that has been possible to recreate. From the information you have given it seems that this might be a SEGGER error, I would suggest asking on their forums.

[andlier]

ok, thanks for trying to reproduce. I did a bit more digging and found out it only hangs if I have the EFM32 kit and the nordic kit connected to the PC through the same usb-hub. If I have the nordic kit through the hub and the efm32-kit directly to the PC, it works. I still think it is related to nrfgo studio, because addressing the kits by serial number even if they are on the same hub, works fine from both Keil and with nrfjprog cmd-line-tool. All of which uses the same Segger driver.

[andlier]

Maybe, if you have access to the source-code, have a look at how the nrfjprog translate serial-number to which kit it connects to, vs. how the same process is done in nrfgo Studio.