I've merged USB CDC with Multilink, but it will not work if you disable logging.

RE: I've merged USB CDC with Multilink, but it will not work if you disable logging.

jwcheon — Thu, 21 Jun 2018 01:51:09 GMT

Hi, Hakon.

As you have said, QIAAC0 devices will behave well even if you disable logging.

It seems that USB recognition failed when LOG is disabled only in QIAAAA chip. Thank you.

RE: I've merged USB CDC with Multilink, but it will not work if you disable logging.

Håkon Alseth — Fri, 15 Jun 2018 10:30:29 GMT

Hi,

We always recommend that you develop with and use the production release of the silicon.

QIAAAA is the first engineering revision, and this will not work with newer SDKs.

If you have the QIAAC0 device, please try this one instead and see if it works better.

Best regards,

Håkon

RE: I've merged USB CDC with Multilink, but it will not work if you disable logging.

jwcheon — Fri, 15 Jun 2018 09:19:15 GMT

Additionally,
I also have the nRF52840 QIAAC0 chip.
I have not tested this chip.

RE: I've merged USB CDC with Multilink, but it will not work if you disable logging.

jwcheon — Fri, 15 Jun 2018 09:17:44 GMT

Yes, it is.
Windows driver error message.

The version of the nRF52840 is nRF52840 PDK and the chip type is shown as "Q1AAAA".

RE: I've merged USB CDC with Multilink, but it will not work if you disable logging.

Håkon Alseth — Fri, 15 Jun 2018 07:27:26 GMT

"USB Failure" - is this the windows driver error message that you are referring to?

Which version of the nRF52840 are you using? Note that engineering A device workaround have been removed from SDK 15, and will therefore not work.

Cheers,

Håkon

RE: I've merged USB CDC with Multilink, but it will not work if you disable logging.

jwcheon — Fri, 15 Jun 2018 01:24:04 GMT

Hi,

I have not seen anywhere in debug mode.
The build is working normally, but I have only checked that the "USB Failure" message is displayed on my computer.

RE: I've merged USB CDC with Multilink, but it will not work if you disable logging.

Håkon Alseth — Tue, 12 Jun 2018 14:33:53 GMT

Hi,

Have you tried entering debugging mode to see where it fails? Do you get an assertion or similar in your firmware?

Best regards,

Håkon