J-link ARM V7 with nRFgo Studio

[Sam]

Has anyone had success with a J-link ARM v7 with the nRFgo studio (and nRF51822)? I've got one of the older nRFgo moterboard dev kits, and I've been doing well with the included debug probe, but when I switched back to my generic J-link V7 (it's a bit old) nRFgo studio will detect the chip only once (after resetting the board) and then fail to do anything else (verify, read, etc all fail with "Code length of region 0 could not be rerieved from device: Could not connect to the target device). Afterwards, refreshing always results in "No device detected."

Keil also fails to find a chip with the J-link debugger afterwards. However, if I never run the nRFgo studio, Keil will successfully debug and download to the chip multiple times with no problems (haven't tried it for very long yet). I managed to use the commander to download a SoftDevice as well without problems (though it was quite a hassle). Just a bit annoying as I can't actually use the nRFgo studio with our second programmer.

Again:

1. I'm using one of the older nRFgo-based motherboard kits with a nRF51822 daughterboard

2. Using nRFgo Studio 1.19.0.7 (latest, older one couldn't reflash the second nRFgo motherboard firmware)

3. Using J-link 4.98e (latest, older versions were giving me other problems)

4. J-link ARM V8-lite based probe included with kit has no such problems.

Any way I can get my V7 to work? Is it a nRFgo bug or does the V7 just not support some of the newer SWD devices (last few times I used it was with full JTAG ARMs)

[Susheel Nuguru]

Sam I tried with

J-Link ARM V7 and also V8
PCA10007, very old boards with the motherboard
nrfgo V1.17.3252 (older than yours)
Jlink V4.92 (older than yours)

And I see no problems and cannot reproduce anything which you mentioned.

[Sam]

Thanks, I'll try again. Maybe the older version have better support, or possibly something's wrong with my V7 debugger hardware (haven't used it in a few years, I end up using IC manufacturer debug probes most of the time). The included debug probe still worked flawlessly and I was able to reproduce the problem switching back and forth between the debuggers several times. I'm starting to think maybe I should double check the 20 pin to 10 pin JTAG adapter I have (from Olimex, IIRC)

[Susheel Nuguru]

We stopped using that old versions about 18 months ago. I had to dig it out to test this. Anyways do not spend too much time on trying to fix old configuration ;)