nRF Connect for Desktop - Programmer v3.0.4 support for nRF9160 using other USB chips

[Achim Kraus]

I'm developing currently with the nRF9160 feather , which uses a CP2102 for USB.

That works quite well, especially it enables to add different sensors, which isn't that easy with a Thingy:91. Using a nRF9160-DK for that requires a larger form-factor.

Flashing firmware for the Arm33 works quite well over USB using the zephyr tools. Also using a jlink works.

But using nRF Connect for Desktop and a USB connection seems to be refused (or not considered by Nordic).

According pc-nrfconnect-programmer devices.ts the Programmer App filters on the USB ids.

Would it be possible to add a checkbox to make other USB serials also available?

That would make it easier to update the modem-firmware over USB without jlink.

[Achim Kraus]

Why ever, now the Programmer (both v3.0.4 and v3.0.8) refuses a nRF5340-DK, when a TC2030-CTX debug header is used!

"Unsupported device. The detected device could not be recognized as neither JLink device nor Nordic USB device."

Flashing works with other tools (e.g. "Visual Studio").

For me this smells, that this checks are not a that good idea. It makes it very complicated to use.

Edit:

Really strange!

If I use a nRF5340-DK with the TC2030-CTX debug header, it requires a Nordic device to be connected when starting the nRF5340-DK. Using a nRF9160-DK, this seems to be not required, it works with that debug header.

All in all:

I guess, it's better to NOT use the Programmer as long as Nordic insist in that check. It takes me about 4 hours yesterday and to be frank, I' pretty closed to change the modem manufacturer because of those repeating wastes of time. 

[Jared]

Hi,

Achim Kraus said:

If I use a nRF5340-DK with the TC2030-CTX debug header, it requires a Nordic device to be connected when starting the nRF5340-DK.

I'm not sure I understood you correctly, it requires you to debug a Nordic device when you use a TC2030-CTX debug header? 

Are you still trying to program the nRF9160 feather?

regards

Jared 

[Achim Kraus]

> Are you still trying to program the nRF9160 feather?

I try to use the "nRF Connect Programmer" to update the nRF9160 feather's modem firmware.

Everything else, flashing with nrfjprog or west flash works without any issues.

And for flashing the application on a nRF9160 feather I use your newtmgr, which is much more comfortable.

The main culprit is the "nordic device check" when starting the "nRF Connect Programmer"  and that requires to already connect a nRF9160 feather when switching on the nRF5340-DK with a TC2030-CTX.

[Jared]

Hi,

I've forwarded this to our developers,

Thank you for the feedback!

regards

Jared 

[Achim Kraus]

> I've forwarded this to our developers,

Thanks!

I guess, that are two different topics.

The first was to detect a nRF9160, if it's connected via an other USB chip (CP2102).

The second was to detect a "valid Jlink", if used with that debug header. The usage with that header may be considered as "special", because it's not plugged to the device. For me the handling is to start "Programmer" , select the "firmware" and then stick the header on the feather. But with this check, it requires to stick the header on the feather, start the Programmer, (now you may remove the debug header from the feather), load the firmware into the "Programmer App" and then stick the header on the feather again.