Difference in power profile between blinky and uart example projects?

RE: Difference in power profile between blinky and uart example projects?

Simonr — Mon, 23 Mar 2020 07:01:03 GMT

The UART service (NUS) is advertised by the peripheral I assume, and this needs to be on while advertising. Yes, I assume the extra current consumption you see is due to the UART being active.

Best regards,

Simon

RE: Difference in power profile between blinky and uart example projects?

riceman0 — Fri, 20 Mar 2020 15:37:45 GMT

This is the power profile for blinky. I don't have the image handy for uart, but it was similar in frequency and amplitude except the power only came down about 60-70%, not down to zero.

I'm not sure what you mean by "the central won't be able to recognize that your peripheral supports...". The actual uart hardware doesn't relate to the peripheral. The example connects to the peripheral, and any characters that come in over BLE, are forwarded over the uart peripheral via physical lines to the local controller. It's initialized on power up but not meaningfully used except while connected.

Could idle UART hardware be eating up this power? Or is something else going on?

RE: Difference in power profile between blinky and uart example projects?

Simonr — Fri, 20 Mar 2020 11:04:37 GMT

How big of a difference is it between these examples? I assume this is the peripheral(s) in the UART example drawing this excess current. I don't think you can initialize the UART after connecting, as the central won't be able to recognize that your peripheral supports the peripheral if it isn't initialized upon connection.

Are the SDK examples edited at all?

Best regards,

Simon