My nrf52840 dongle firmware seems to be corrupted

[hafsa]

My laptop does not detect my dongle after I program it through nrfConnect. I am thinking that maybe I have to reflash the pca 10059 firmware, but I do not have any nrf development kit. Is there a way to revert the dongle to its original configuration?

[runsiv]

Hi

Are you able to find the dongle if you press down the button on the dongle when you insert into the computer? 

This will put the device into bootloader mode and allow you to flash a new application using nrf connect for desktop's programmer app. If not you need to use a programmer or a development kit to flash the bootloader again

Regards

Runar

[hafsa]

I am using NrfConnect for Desktop. I was testing different programs on my dongle, and I clicked write in nrf connect without resetting the dongle first. I got a pop up that now mcu bootloader will be used to program it, and I realized my mistake, so I clicked cancel, instead of Ok, and reset the dongle with the sideway button. Now my laptop is not detecting the dongle due to some error in dongle, and each time I connect it to laptop, it shows green light and then the error is shown by laptop and the light stops. Then I have to reset it, and reprogram through nrf connect, which is done successfully. After that, the error again emerges, and dongle is not detected. If I reset it and remove it, upon attaching back to laptop, it is not in programmable state, and error emerges.

[runsiv]

Normally I would suggest a Jlink-lite or similar. However I'm still not sure what you have done with the dongle. I have had my dongle for some years without seeing any issue nor have I heard.  

You are saying that you can program it, but after you take it out of bootloader mode it fails? That sounds to me like thare is something wrong with the cdc sample you flashed to the device. Do you see this if you for example but it in bootloader mode and try a non usb-cdc sample? 

Regards

Runar

[hafsa]

Yes, the problem remains with any kind of program I flash. After I reset the dongle and eject it, upon inserting it again, the red light does  not flash, it is in the previous programmed state, and I have to reset again. After programming any kind of program, the usb is no longer detected. This all happened suddenly, even though I have done nothing out of the ordinary.

[PaKa]

So when you push the button and this make the USB start up and you can program the device? If so then the bootloader should be working as designed.

The USB missing when you start the program you have downloaded is normally due to the code not using the USB interface or the USB code being faulty.

What samples have you programmed into the part that should have USB that doesn't work?

[hafsa]

Yes, I can program all kinds of programs. I have tried to look deeper in the issue, and the main issue since the mcu boot pop up message in nrf connect desktop is that when I reset it, and replug it, it is reverted back to the programmed state and not the reset state(for any program). The burned applications seem to be working, but as I intend to use usb cdc(which had worked perfectly before), it does not work, and the programmer goes to mcu boot mode. I get the error:

22:26:18.844

Error: Failed with exit code 1. One or more set mcu state tasks failed: * D8AB43AFAAC5: [mcuBoot] Non supported device for setting mcu state, code: Argument. Message: Failed to set mcu state on D8AB43AFAAC5, [mcuBoot] Non supported device for setting mcu state.

22:26:18.844

Error when fetching device versions: Error: Failed with exit code 1. One or more set mcu state tasks failed: * D8AB43AFAAC5: [mcuBoot] Non supported device for setting mcu state, code: Argument. Message: Failed to set mcu state on D8AB43AFAAC5, [mcuBoot] Non supported device for setting mcu state.

ps: this is where the problem started:

(I am using NrfConnect for Desktop. I was testing different programs on my dongle, and I clicked write in nrf connect without resetting the dongle first. I got a pop up that now mcu bootloader will be used to program it, and I realized my mistake, so I clicked cancel, instead of Ok, and reset the dongle with the sideway button.)

In any other normal application it does not enable mcu boot, so works application wise, but the reset problem persists:

[PaKa]

The error message is normal and comes when the device has been programmed and exits the bootloader and starts running the program, all as normal.

Based on what you are saying there is nothing wrong with the bootloader, the issues are with the programs you are uploading so you should check those and not the bootloader.

[hafsa]

I am saying that the same program was running normally before. The reset issue is new. The mcu boot being enabled only in usb_cdc_acm program is new.