High power consumption delta with new and old hci_lpuart on thingy91

RE: High power consumption delta with new and old hci_lpuart on thingy91

Charlie — Tue, 16 Jan 2024 16:00:50 GMT

Hi 0x35c,

Thanks for sharing the fix and sorry for the late reply. Unfortunately, we did not do any optimization like you did for the lte_ble_gateway sample before.

From the default samples of hci_lpuart+lte_ble_gatway running on Thingy91, I can see nRF52840+nRF9160 consumes around 1.3mA with NCS v1.9.1 and around 63mA with NCS v2.5.0. The difference is mainly caused by GNSS usage. Neither of them is close to your measurement.

I wonder if you have done some optimization for your lte_ble_gatway application running on nRF9160 since it consumes much less current than the original sample. Without achieving this on my side, I am not able to investigate the relatively small difference caused by hci_lpuart.

Best regards,

Charlie

RE: High power consumption delta with new and old hci_lpuart on thingy91

0x35c — Thu, 11 Jan 2024 14:26:57 GMT

Hi, you probably need to change a few things in your sdk in order to make the sample work.
Please, see this pull request with all the details

github.com/.../files

RE: High power consumption delta with new and old hci_lpuart on thingy91

Charlie — Thu, 11 Jan 2024 14:24:17 GMT

Hi 0x35c,

I encountered some errors when running NCS 2.5.0 late ble gateway sample on Thingy91, but NCS 1.9.1 has no problem.

I am not sure if this issue is related to your measurements. I will continue to work on debugging this issue.

SEGGER J-Link V7.92q - Real time terminal output
SEGGER J-Link (unknown) V1.0, SN=960035261
Process: JLink.exe
*** Booting nRF Connect SDK v2.5.0 ***
[00:00:00.256,164] <inf> lte_ble_gw: LTE Sensor Gateway sample started
[00:00:00.256,317] <inf> lte_ble_gw: Initializing Bluetooth..
[00:00:00.269,958] <wrn> lpuart: req pin low when expected high
[00:00:00.270,050] <err> lpuart: Empty receiver state:4
[00:00:00.502,868] <inf> lte_ble_gw: Establishing LTE link (this may take some time) ...
[00:00:01.346,008] <err> lpuart: Empty receiver state:4
[00:00:01.348,175] <wrn> lpuart: req pin low when expected high
[00:00:01.348,297] <err> lpuart: Empty receiver state:4
[00:00:01.350,433] <wrn> lpuart: req pin low when expected high
[00:00:01.350,555] <err> lpuart: Empty receiver state:4
ASSERTION FAIL [err == 0] @ WEST_TOPDIR/zephyr/subsys/bluetooth/host/hci_core.c:338
        command opcode 0x0c03 timeout with err -11
[00:00:10.266,845] <err> os: r0/a1:  0x00000003  r1/a2:  0x00000000  r2/a3:  0x00000002
[00:00:10.266,845] <err> os: r3/a4:  0x2000d298 r12/ip:  0x00000010 r14/lr:  0x0002049d
[00:00:10.266,876] <err> os:  xpsr:  0x41000000
[00:00:10.266,876] <err> os: Faulting instruction address (r15/pc): 0x000204a8
[00:00:10.266,937] <err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
[00:00:10.266,967] <err> os: Current thread: 0x2000f7b8 (unknown)
[00:00:10.492,584] <err> fatal_error: Resetting system

Best regards,

Charlie

RE: High power consumption delta with new and old hci_lpuart on thingy91

0x35c — Wed, 10 Jan 2024 10:42:30 GMT

Hi, this is the measurement for the whole system.

Here is my setup, and I connect this to my computer on the PPK app with 4000mV.

Our app on nfr91 is very similar to LTE Sensor Gateway so you should have a similar result.

RE: High power consumption delta with new and old hci_lpuart on thingy91

Charlie — Wed, 10 Jan 2024 10:38:13 GMT

Hi 0x35c,

Is this only current consumption of nRF52840 or the whole system?

Can you share a picture of your measurement setup? I will try to repeat your measurement with the following samples.

Bluetooth: HCI low power UART — nRF Connect SDK 2.5.0 documentation (nordicsemi.com)

Cellular: LTE Sensor Gateway — nRF Connect SDK 2.5.0 documentation (nordicsemi.com)

Best regards,

Charlie