This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF Connect Programmer hangs on start

Configuration:

  • nRF Connect for Desktop v3.7.0
  • Programmer v1.4.11
  • PCA10040 v2.0.0 EVK (date code 2020.39)
  • When Programmer app does start Log says: "Using nrfjprog library 10.12.1, pc-nrfjprog-js 1.7.6". 
  • OS: Windows 10.

I can program debug with this EVK using SES.

When I start the Programmer app with the EVK plugged in, Programmer app hangs with blank screen.

I have tried upgrading/downloading EVK J-Link to v6.92 and 6.44e.  With 6.44e, sometimes Programmer will start, then hang when I attempt to select this J-Link.

CTRL+R while Programmer is stuck will re-start it (spinning wheel), then it goes blank again. 

I can get no log output to debug the issue from Programmer, since it just hangs with blank screen.

Any suggestions?

Parents
  • Hi,

    Could you try updating to jlink v6.88a? 

    regards

    Jared 

  • Still fails with v6.88a or v7.50a.   Yesterday it worked for a while with v7.50a, now it hangs with either driver.

    Pressing CTRL+R repeatedly eventually gets Programmer screen to come up, but selecting EVK causes blank screen/hang again. 

    Very erratic behavior -- occasionally Programmer can recognize EVK and function, but it usually takes multiple CTRL+R to get this to happen.  This seems to be the case with J-Link v6.88a and v7.50a.

    Once EVK is recognized, Programmer seems to work correctly.  

  • Ok, We've started an internal investigation into this issue. I'll update you when we have more information.

    Please expect some delay as many of us are out of office due to the summer vacation.

    regards

    Jared

  • Have you seen this behavior at your end? 

    Is it possible to revert to earlier version of Programmer app to test if it happens with various versions?

    Below is the system configuration (NOTE: the "System Report" function identifies the PCA10040 EVK, but Programmer may still hang when attempting to "Select Device"):

    # nRFConnect System Report - 2021-07-15T13-30-47.129Z

    - System: HP HP ProBook 470 G5
    - BIOS: HP HPQOEM - 0
    - CPU: 1 x Intel® CoreTm i7-8550U 1.8 GHz 8 cores (4 physical)
    - Memory: 18.1 GB free of 31.9 GB total
    - Filesystem: C: (NTFS) 1.8 TB 20.1% used

    - OS: Microsoft Windows 10 Pro (10.0.18363) win32 ia32

    - Versions
    - kernel: 10.0.18363
    - git: 2.22.0.windows.1
    - node: 12.13.0
    - python: 3.9.0
    - python3:

    - Connected devices:
    - COM3: 000682229075 PCA10040

  • Hi,

    I haven't, I tried reproducing it by wasn't able to. It worked fine on my end. 

     

    Jackson Wilson said:

    Is it possible to revert to earlier version of Programmer app to test if it happens with various versions?

     See this answer on how to downgrade nRF Connect apps to an earlier version.

    regards

    Jared 

  • Additional debugging:

    I tested a second computer with the same EVK and nRF Connect/Programmer versions and everything worked.

    Then I went back to the initial machine (System Report above) and removed all other USB hubs and devices.  In that configuration Programmer functions correctly.

    By process of elimination I found that a Brother ADS-1200 scanner causes the failure of Programmer to start and/or detect attached J-Link.  Or, powering off the scanner fixes Programmer (not enumerated in Device Manager).

    There is some USB conflict with the scanner.  

    I can work around this issue, but it should be investigated and addressed by Nordic to ensure that the Programmer functions regardless of other USB devices connected to the computer. 

Reply
  • Additional debugging:

    I tested a second computer with the same EVK and nRF Connect/Programmer versions and everything worked.

    Then I went back to the initial machine (System Report above) and removed all other USB hubs and devices.  In that configuration Programmer functions correctly.

    By process of elimination I found that a Brother ADS-1200 scanner causes the failure of Programmer to start and/or detect attached J-Link.  Or, powering off the scanner fixes Programmer (not enumerated in Device Manager).

    There is some USB conflict with the scanner.  

    I can work around this issue, but it should be investigated and addressed by Nordic to ensure that the Programmer functions regardless of other USB devices connected to the computer. 

Children
Related