nRF52840 Dongle windows 7

[dhla]

Hi 

We have some production equipment still running windows 7. We would like to update the nrf51 dongle to a nrf52 dongle.

But drivers for nrf52 dongle is not installed correct although I have installed the newest version of nrf connect? Isn't it possible to use a nrf52 dongle in windows 7?

In windows 10 its not a problem to find the dongle.

Br

Danny

[JONATHAN LL]

There is\was an issue on Windows 7 and the 52 dongle. The Serial drivers need to be installed manually, assuming you plan to use the connectivity FW. 

Try these: https://github.com/NordicSemiconductor/pc-nrfconnect-launcher/tree/v3.7.0/build/drivers/dfu_trigger_and_cdc_acm 

Regards,
Jonathan

[dhla]

Hi Jonathan

Thank you very much for your reply. Now something interesting happened

But still it cannot find the device in nrf connect

[JONATHAN LL]

Hi,

What application is running on the dongle? Does it show in the programmer app?

Regards,
Jonathan

[dhla]

Hi

The firmware on the dongle is what nrf connect (Blue Low Energy) loaded to the dongle first time it was connected to my own win10 PC.

I also tried to connect a new dongle with no firmware (so it started up in boot mode) to the windows 7 PC. It could also not detect that in nrf connect.

It can also not detect it with the programmer app  

[dhla]

Hi 

I also tried uninstalling nrf Connect and reinstalling it. It also did not help. 

Any ideas?

[JONATHAN LL]

Thanks for the details, 

Since i do not have a w7 device to debug on and that w7 is end of support, it is not something we support any more either. And the nRF connect for Desktop app does not really support w7. 



I do see that this is a big inconvenience. So will try to find a solution but i currently do not have a win7 computer to test on. 
Could a issue be that the win7 computer you have has many instances of devices, more then 200-250? If so then the amount of ports in use might be causing strange behaviour. Dont think this is the issue but can be good to check. 


You can try to downgrade the nRF connect for desktop version maybe and see if that solves the issue. 
You can find previous versions here Releases · NordicSemiconductor/pc-nrfconnect-launcher · GitHub 


Since the device showes up as a USB CDC and Nordic DFU device i do find it strange that it does not showe in the Desktop app. 

Regards,
Jonathan

[dhla]

Hi Jonathan

I also thought of that since the dongle gets COM30. But it is not changeable

if I take another device that have have changeable port then I see that up to 32 have been in use

If I try to install older version of nrfConnect i get this error message

Our test equipments have older versions of windows since our product lifetime is longer than the lifetime of windows versions. And we don't add new value to our products but only a lot of work by updating all instrument drivers and test sequeneces by updating windows version. Therefore we have some test equipment running windows 7.

Br

Danny

[dhla]

By the way here is a log file from "Restart with verbose logging"

Fullscreen 2022-04-20T13_43_50.220Z-log.txt Download

2022-04-20T13:43:51.016Z DEBUG Application data folder: C:\Users\tester\AppData\Roaming\nrfconnect\pc-nrfconnect-ble
2022-04-20T13:43:51.180Z INFO Using nrf-device-lib-js version: 0.4.5
2022-04-20T13:43:51.181Z INFO Using nrf-device-lib version: 0.11.0
2022-04-20T13:43:51.181Z INFO Using nrfjprog DLL version: 10.15.1
2022-04-20T13:43:51.181Z INFO Using JLink version: JLink_V7.58b
2022-04-20T13:43:51.191Z VERBOSE [nrfdl][trace](15:43:51.042) DeviceLister::enumerate: Checking future_status of enumerate_task_status
2022-04-20T13:43:51.195Z VERBOSE [nrfdl][trace](15:43:51.043) DeviceLister::enumerate: Waiting for enumerate task to complete
2022-04-20T13:43:51.218Z VERBOSE [nrfdl][trace](15:43:51.043) DeviceLister::enumerate::enumerate_task: Start
2022-04-20T13:43:51.219Z VERBOSE [nrfdl][trace](15:43:51.043) DeviceLister::enumerate::enumerate_task: Device_pool is empty
2022-04-20T13:43:51.220Z VERBOSE [nrfdl][trace](15:43:51.043) DeviceLister::enumerate::enumerate_task: Before async_lister->enumarate
2022-04-20T13:43:51.222Z DEBUG [nrfdl][debug](15:43:51.052) Container ID has no value for USB.
2022-04-20T13:43:51.223Z DEBUG [nrfdl][debug](15:43:51.052) Container ID has no value for USB.
2022-04-20T13:43:51.224Z DEBUG [nrfdl][debug](15:43:51.052) Container ID has no value for USB.
2022-04-20T13:43:51.225Z DEBUG [nrfdl][debug](15:43:51.052) Container ID has no value for USB.
2022-04-20T13:43:51.226Z DEBUG [nrfdl][debug](15:43:51.052) Container ID has no value for USB.
2022-04-20T13:43:51.227Z DEBUG [nrfdl][debug](15:43:51.052) Container ID has no value for USB.
2022-04-20T13:43:51.228Z DEBUG [nrfdl][debug](15:43:51.053) Container ID has no value for USB.
2022-04-20T13:43:51.229Z DEBUG [nrfdl][debug](15:43:51.053) Container ID has no value for USB.
2022-04-20T13:43:51.230Z DEBUG [nrfdl][debug](15:43:51.053) Container ID has no value for USB.
2022-04-20T13:43:51.231Z VERBOSE [nrfdl][trace](15:43:51.053) DeviceLister::enumerate::enumerate_task: After async_lister->enumarate
2022-04-20T13:43:51.231Z VERBOSE [nrfdl][trace](15:43:51.053) DeviceLister::enumerate: Enumerating with sync lister
2022-04-20T13:43:51.232Z VERBOSE [nrfdl][trace](15:43:51.053) SerialPortLister::enumerate
2022-04-20T13:43:51.233Z VERBOSE [nrfdl][trace](15:43:51.059) DeviceLister::enumerate: Enumerating with sync lister
2022-04-20T13:43:51.234Z VERBOSE [nrfdl][trace](15:43:51.059) JLinkLister::enumerate
2022-04-20T13:43:51.235Z DEBUG [nrfdl][debug](15:43:51.059) [->] NRFDL::UniversalPlatform::JLinkHW::enumerate
2022-04-20T13:43:51.236Z DEBUG [nrfdl][debug](15:43:51.059) [HighLevel][TID:4656] get_connected_probes
2022-04-20T13:43:51.237Z DEBUG [nrfdl][debug](15:43:51.066) nrfjprog_function return value: 0
2022-04-20T13:43:51.238Z DEBUG [nrfdl][debug](15:43:51.066) [<-] NRFDL::UniversalPlatform::JLinkHW::enumerate [took 7ms]
2022-04-20T13:43:51.239Z VERBOSE [nrfdl][trace](15:43:51.066) DeviceLister::enumerate: Enumerating with sync lister
2022-04-20T13:43:51.240Z VERBOSE [nrfdl][trace](15:43:51.066) BrokenLister::enumerate
2022-04-20T13:43:51.240Z VERBOSE [nrfdl][trace](15:43:51.066) DeviceLister::enumerate: Completed waiting for enumerate task
2022-04-20T13:43:51.241Z VERBOSE [nrfdl][trace](15:43:51.066) DeviceLister::enumerate: done
2022-04-20T13:43:51.267Z DEBUG App pc-nrfconnect-ble v3.0.1 official
2022-04-20T13:43:51.268Z DEBUG App path: C:\Users\tester\.nrfconnect-apps\node_modules\pc-nrfconnect-ble
2022-04-20T13:43:51.268Z DEBUG nRFConnect 3.11.0, required by the app is (^3.8.0)
2022-04-20T13:43:51.268Z DEBUG nRFConnect path: C:\Users\tester\AppData\Local\Programs\nrfconnect\resources\app.asar
2022-04-20T13:43:51.268Z DEBUG HomeDir: C:\Users\tester
2022-04-20T13:43:51.268Z DEBUG TmpDir: C:\Users\tester\AppData\Local\Temp
2022-04-20T13:43:55.036Z ERROR TypeError: Failed to fetch. Falling back to stored data

[Sigurd]

nRF Connect for Desktop is supported on Windows 10. When you first are doing changes and introducing new HW (and SW?), maybe it's time to update the OS as well. Or only upgrade to newer HW/SW on the machines you have that run Windows 10.

[dhla]

Its a major task since its a test equipment where we then need to update all instrument drivers and test sequences and so on. It always gives a lot of issues. Isn't there any other way to trouble shoot on this? I wonder why the dongle can be seen from windows and not from Nrf Connect

[Sigurd]

Hi,

dhla said:

If I try to install older version of nrfConnect i get this error message

Try uninstalling the version you have now, before installing an older version. Try e.g. v3.5.0 or older.

[dhla]

Hi 

Thank you for your suggestion. I tried th following

- uninstalling3 Bluetooth Low Energy and Programmer from nRF Connect.

- Then I uninstalled Nrf Connect from control panel

- Then Install 3.5.0

- Then install Bluetooth Low Energy and Programmer from nRF connect 3.5.0 and i get this message  

If I say launch anyway then this one comes up

The same happens if I install version 3.0.0 and 2.7.0