J-link not find device(Info: Could not measure total IR len. TDO is constant high.)

RE: J-link not find device(Info: Could not measure total IR len. TDO is constant high.)

Lionel Sacks — Fri, 06 Jun 2014 14:09:34 GMT

Just to add to the noise ... I also had this for the first time just now, although this was not the first time I'd copied a project from one folder to another!

Not to mention that it's a 'shame' that Keil mVision can't use environment variables...

RE: J-link not find device(Info: Could not measure total IR len. TDO is constant high.)

Sébastien Despont — Fri, 21 Mar 2014 13:43:46 GMT

Great answer. Thanks

RE: J-link not find device(Info: Could not measure total IR len. TDO is constant high.)

Paul — Tue, 28 Jan 2014 16:04:37 GMT

Must be the Jlink driver somehow decided to reset/change its setting automatically. Could be a setting somewhere (regedit?) to "lock" the setting, or disable the "auto mode".

RE: J-link not find device(Info: Could not measure total IR len. TDO is constant high.)

Shane — Tue, 28 Jan 2014 15:56:02 GMT

Yup, verified it this morning. Running WinXP on Parallels (8.0.18615) on OSX and relinking the JLink to the WinXP VM USB ->sometimes<- causes the Port to flick back to JTag within the debug/use panel w/o me doing anything to the setting.

Not sure what Parallels is doing, but a little annoying.

RE: J-link not find device(Info: Could not measure total IR len. TDO is constant high.)

Shane — Mon, 27 Jan 2014 15:47:05 GMT

Thanks Paul! Your solution worked for me this morning. Not sure why this happens. Yesterday, everything was downloading fine but this morning I got the TDO error. I had not made any changes to the JLink settings.

It seems these settings somehow get switched around w/o the user doing it. I am running on a VM, though, so the JLink is being connected/reconnected through Parallels. Not sure why that would matter.

RE: J-link not find device(Info: Could not measure total IR len. TDO is constant high.)

Paul — Tue, 21 Jan 2014 17:15:22 GMT

This is what I did to solve the problem:

Go to Cortex Jlink/Jtrace target driver setup.

In Debug Tab: Make sure the Port is set to SW, NOT JTAG. (Sometime copy/paste project will get this setting switch to JTAG).

In Flash Download Tab: Make sure nRF51xxx is selected in the programming algorithm.

After these two step. the TDO high problem is gone.

RE: J-link not find device(Info: Could not measure total IR len. TDO is constant high.)

Paul — Tue, 21 Jan 2014 16:47:34 GMT

I got the same problem today. Luckly it didn't take me too long to find out this "copy/paste" issue. Working on it right now to see if any luck to "fix" the copied folder. Otherwise I will create a new project. :-D

RE: J-link not find device(Info: Could not measure total IR len. TDO is constant high.)

Shane — Wed, 06 Nov 2013 17:08:41 GMT

I had exactly the same problem this morning with a J-link lite.

I am working on a project that is based on the ble_app_hrs code. Copied it over and just renamed the file names to my project. Everything was working fine over the last 3 weeks until this morning when I got the "TDO constant high" error. Untouched sample projects compiled and downloaded fine, but mine would not. I moved the Parallels VM on which I had the Keil environment running, but have no idea why that would cause a problem.

I have been keeping all projects under SVN, and I saw only three modified project config files that could be the culprits:

XXX(256k).dep, XXX.uvgui.Administrator XXX.uvopt.

I reverted all of them to my last working revision and the J-link lite worked fine. I tried reverting them one at a time to see if the problem was isolated in a single file and never could get it working.

In the attachment, the "Work" directory are those which download fine while the "Do Not Work" are those that don't. Hopefully they may help someone and shorten what looks to be a painful process.

RSL-Keil project files..zip

RE: J-link not find device(Info: Could not measure total IR len. TDO is constant high.)

Jim — Fri, 20 Sep 2013 12:25:20 GMT

Ah, I didn't change those file names, so it looks like they got recreated automatically with default settings.

Next time I'll try to rename those files, too.

RE: J-link not find device(Info: Could not measure total IR len. TDO is constant high.)

Ole Morten — Fri, 20 Sep 2013 11:55:22 GMT

To answer the original question here, it seems that the J-Link Lite for some reason can't find the nRF51822. This can be caused by a number of things, for example:

The nRF51822 being in system off (in this case, you should still be able to make things work by doing a recover, so this is most likely not the case here.)
The connector being wrongly connected (i.e. turned 180 degrees or similar).
The VTG of the connector not being connected to the nRF51822's VCC.
The VCC of the nRF51822 being outside of what's supported by the J-Link Lite. The J-Link Lite can only program devices running on 3.3 V. The voltage of the nRFgo motherboard can be set in nRFgo Studio. 5a. If you use version 1.0 of the Evaluation Kit, the jumpers on P8 either not being mounted or turned 90 degrees. 5b. If you use version 2.0 of the Evaluation Kit, the J-Link OB switch being off.

Could any of these be the problem here?

RE: J-link not find device(Info: Could not measure total IR len. TDO is constant high.)

Ole Morten — Fri, 20 Sep 2013 11:50:26 GMT

The recover button did not work in nRFgo Studio version 1.15.0, but should be fixed in version 1.15.1. Do you have trouble with this as well?

RE: J-link not find device(Info: Could not measure total IR len. TDO is constant high.)

Ole Morten — Fri, 20 Sep 2013 11:48:00 GMT

I'm sorry to hear about your trouble, but most of the J-Link settings should be included in Keil's project files themselves, so as long as you start with the .uvproj and .uvopt files from a working project, you should be fine. You can change the name of these files without changing any of their content. If you want to change the name of the output file, this can be done from the target options in Keil.

RE: J-link not find device(Info: Could not measure total IR len. TDO is constant high.)

Jim — Tue, 17 Sep 2013 21:19:10 GMT

OK, It appears that the J-link settings aren't making it from one directory to another.

I (painfully) made sure every setting in the Jlink tab in my new project is the same as the sample I copied. Lots of window snips, switching projects, and side-by-side comparisons.

And at long last I'm able to run my exact copy of the original example with a new name. All in a days' work. I didn't want to really get that much done today...

If anyone knows how to encapsulate the JLink settings better so I don't have to this by hand, I'd love to hear it.

RE: J-link not find device(Info: Could not measure total IR len. TDO is constant high.)

Jim — Tue, 17 Sep 2013 21:01:49 GMT

I'm running into this, too. I have narrowed it down a bit. If I compile an example application (ble_app_proximity for the pca10001) unchanged, it works.

If I duplicate that directory, and change the project name, I'm dead.

Not sure how I'm supposed to create a new project (lots of settings to match).

Sometimes I can still see the devices with nRF Studio (no need to recover) but this still happens so I don't think it's related to the need to recover.

RE: J-link not find device(Info: Could not measure total IR len. TDO is constant high.)

steven — Tue, 17 Sep 2013 08:19:15 GMT

hi, if it can't found device Generally,press "recover" at nRFgo studio.to clear the firmware .

but, i match another computer ,the recover button is Invalid at nRFgo studio the least version . you have to use nRFgo 1.14.1 to recover.