DFU bootloader not identified correctly in nRF Connect for Desktop > Programmer

[masterLee]

Hi,

I want to use the DFU open bootloader with my nRF52840 device.

When I send the bootloader hex file to the microcontroller and then I open the nRF connect for Windows > Programmer app

the device  is identified as as 2.4G Keyboard Mouse instead of DFU bootloader that I expect so I can send my code to the device.

When I open the manage settings in my PC, the port that is connected to the device is identified as SDFU

So, what am I doing wrong here?

[Vidar Berg]

Hi,

Please try to upgrade the Programmer app to the current version (v3.0.8) and see if you get the same result. Also, is this 52840 device a custom board, or are you using the 52840 Dongle? If it is a custom board, do you have a dongle you can test with?

Best regards,

Vidar

[masterLee]

Yes I have upgraded the programmer to v3.0.8. Still nothing with this specific custom board
Also, I programmed a second custom board  (same to the first one) and the bootloader is identified correctly. It is the same hex file and the same build.  No unfortunately I don't have a dongle at the moment.

In device manager both devices are identified as nRF52 SDFU USB but in the programmer app, the first is identified as 2.4G Keyboard Mouse and the second is identified as open bootloader as expected.  What is going on here :)

[Vidar Berg]

Do you have another PC you can test this on to try narrow down the problem?

[masterLee]

yes I can Install it. Give me a sec please

[masterLee]

Fixed it...
I tried it as you said to another PC and all the custom devices I tested were identified as open bootloader (as expected) once I pressed the reset button. The issue originated from my wireless mouse. Somehow(!!!) it interfered with the custom devices and they were identified as wireless mice. The moment I removed the mouse adapter from the usb hub of the PC and put it to another usb connector, everything was fixed.