USBD starting up lowers board's overall current draw

RE: USBD starting up lowers board's overall current draw

user71763 — Tue, 14 Jun 2022 19:05:05 GMT

Sorry for the delay in my response. There could very well be another reason unrelated to the USBD. It is because I can repeatably get a difference in the current draw depending if I let the USBD start up or not that I was focusing on it.

Unfortunately because the code base runs on our custom board with different pin assignments and chips than what is on the DK board, it would be a significant amount of modifications to make it run on the DK. I don't think the code would be anywhere near representative, so I don't think it would be worth the effort at the moment.

RE: USBD starting up lowers board's overall current draw

user93767 — Wed, 08 Jun 2022 16:06:19 GMT

Something else about this high current draw problem: Reflashing the processor with the same code resolves the problem.

I was troubleshooting a unit that had the same problem Kraig described. I saved the image using the nRF Connect programmer, than loaded an image onto it which resolved the issue. I then reloaded the saved image onto it expecting the problem to reappear but it didn't reappear.

Is there any non-volatile state in the nRF52840 that would not get saved in the image file when using nRF Connect Programmer. To narrow it down any state that could affect GPIO configuration?

Also, loading firmware via the DFU bootloader does not resolve the problem. Only flashing it seems to resolve the problem.

RE: USBD starting up lowers board's overall current draw

user73165 — Tue, 07 Jun 2022 13:57:21 GMT

Hi,

I can't say that I've seen this before. Maybe something else in your code is effected when you comment out the USBD part. Have you tried flashing a development kit with your project? Do you measure the same with the dk?

regards

Jared