peripheral uart power consumption

RE: peripheral uart power consumption

Hung Bui — Thu, 22 Apr 2021 09:10:54 GMT

According to this CONFIG_HAS_POWER_STATE_DEEP_SLEEP_1 would put the device to deep sleep (system off) after a power down timeout. But I don't see it would reduce current consumption if you just simply use k_sleep() (it retain in Idle mode which is System ON)

3.5uA base current is expected when staying in System ON. When you turn on peripheral (i2C, ADC, GPIO input) it's expected to have power consumption increased. So I don't see any abnormal here after you turn off the logging in the netcore module.

The best way IMO to verify the power consumption is to use a PPK and can visualize the power consumption over time.

RE: peripheral uart power consumption

KentOverton — Wed, 21 Apr 2021 15:36:02 GMT

The advertising interval is set to 2 seconds.

I commented out everything in main() except for the loop

for(;;)

{k_sleep(k_forever);

}

When

CONFIG_HAS_POWER_STATE_DEEP_SLEEP_1=y is set

power consumption is 3.5uA. An nearly as I can tell from my DMM this is unchanging.

When

CONFIG_HAS_POWER_STATE_DEEP_SLEEP_1is not set

power consumption is 53uA.

Uncommenting the balance of main, which enables I2C, ADC, and GPIO, connects to blue tooth and starts advertising, power consumption is 53uA, with a visible spike every two seconds.

RE: peripheral uart power consumption

Hung Bui — Wed, 21 Apr 2021 09:17:58 GMT

Depends on the advertising interval you have you may have different power consumption.

I would suggest to turn off all functionality and only sleep to get to the base sleep current before testing with BLE. Having UART running would also draw current as it keeps the clock running.

RE: peripheral uart power consumption

KentOverton — Tue, 20 Apr 2021 10:42:35 GMT

Hi.

I'm providing power from a regulated power supply at 3.0V through the "External Supply" pins on the DK.

I'm measuring current with a BK Precision Bench DMM on. the NRF Current Measurement pins on the DK (I've cut solder bridge SB40).

In the context of what I'm trying to do, I'm running the simplest possible configuration I can. It's a slimmed down version of peripheral_uart that starts advertising, then does a k_sleep(K_FOREVER).

In fact, it's unrealistic. I want my main loop to idle, waiting for either a GPIO interrupt or a Bluetooth connection. The k_sleep is the only mechanism I could make work on the 52832.

I've attached a zip file of the top of my project (the build directories are empty)devzone.nordicsemi.com/.../peripheral_5F00_uart_2D00_4_2D00_20-_2D00_-Copy.zip

RE: peripheral uart power consumption

Hung Bui — Tue, 20 Apr 2021 09:50:16 GMT

I would suggest to test using very simple application without any peripheral, you can try only toggling an LED for example.
Just so that you make sure you can get to the base current consumption of a few uA.

How did you measure the current consumption ? Please try recording using a PPK it would help showing what may draw the current.

You can have a look at my webinar here at minute 50th that I showed some tips on measuring current consumption on a BLE application on nRF53:
https://webinars.nordicsemi.com/get-started-on-your-advanced-1

RE: peripheral uart power consumption

KentOverton — Mon, 19 Apr 2021 15:36:52 GMT

I downloaded the nrfjprog stuff, did the two nrfjprog steps your documentation suggests, then went back to hci_rpmsg and tried to download it again.

I got the same kind of error as I had before.

I reloaded my app.

Idle power consumption is now in the 100 uA range.

RE: peripheral uart power consumption

KentOverton — Mon, 19 Apr 2021 15:15:03 GMT

I'm in a Windows environment. Neither west nor nrfjprog are in my $PATH. I looked in Progam Files and Program Files x86 and couldn't find them.

RE: peripheral uart power consumption

Hung Bui — Mon, 19 Apr 2021 14:49:59 GMT

Please make sure you recover the chip as erasing is not possible after programming (because of readback protection)

Please have a look here: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_nrf5340.html#readback-protection

RE: peripheral uart power consumption

KentOverton — Mon, 19 Apr 2021 14:08:58 GMT

I did as you suggested, turning off CONFIG_LOG and CONFIG_SERIAL via the Segger SES "Configure nRF Connect SDK Project."

There was an error reported on downloading - the transcript is

Preparing target for download
Executing Reset script TargetInterface.resetAndStop()
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.SYSRESETREQ.
Downloading ‘merged.hex’ to J-Link
Programming 159.9 KB of addresses 00000000 — 00027fef
J-Link: Flash download: Bank 1 @ 0x00000000: 1 range affected (131072 bytes)
J-Link: Flash download: Total: 4.181s (Prepare: 0.107s, Compare: 0.103s, Erase: 2.793s, Program & Verify: 1.168s, Restore: 0.008s)
J-Link: Flash download: Program & Verify speed: 109 KB/s
Connecting ‘J-Link’ using ‘USB’
Connecting to target using SWD
Loaded C:/Users/kover/ncs/v1.5.1/toolchain/segger_embedded_studio/bin/JLink_x64.dll
Firmware Version: J-Link OB-K22-NordicSemi compiled Jan 21 2020 17:33:01
DLL Version: 6.94a
Hardware Version: V1.00
Target Voltage: 3.300
Device "NRF5340_XXAA_NET" selected.
ConfigTargetSettings() start
ConfigTargetSettings() end
InitTarget() start
InitTarget() end
Found SW-DP with ID 0x6BA02477
DPIDR: 0x6BA02477
AP map detection skipped. Manually configured AP map found.
AP[0]: AHB-AP (IDR: Not set)
AP[1]: AHB-AP (IDR: Not set)
AP[2]: MEM-AP (IDR: Not set)
AP[3]: MEM-AP (IDR: Not set)
AP[1]: Core found
AP[1]: AHB-AP ROM base: 0xE00FE000
CPUID register: 0x410FD214. Implementer code: 0x41 (ARM)
Found Cortex-M33 r0p4, Little endian.
FPUnit: 8 code (BP) slots and 0 literal slots
Security extension: not implemented
CoreSight components:
ROMTbl[0] @ E00FE000
ROMTbl[0][0]: E00FF000, CID: B105100D, PID: 000BB4C9 ROM Table
ROMTbl[1] @ E00FF000
ROMTbl[1][0]: E000E000, CID: B105900D, PID: 000BBD21 Cortex-M33
ROMTbl[1][1]: E0001000, CID: B105900D, PID: 000BBD21 DWT
ROMTbl[1][2]: E0002000, CID: B105900D, PID: 000BBD21 FPB
ROMTbl[1][6]: E0042000, CID: B105900D, PID: 000BBD21 CSS600-CTI
Preparing target for download
Executing Reset script TargetInterface.resetAndStop()
ResetTarget() start
ResetTarget() end
Downloading ‘zephyr.elf’ to J-Link
Programming 167.0 KB of addresses 01000000 — 01029c4b
Programming 1.3 KB of addresses 01029c4c — 0102a1bb
T-bit of XPSR is 0 but should be 1. Changed to 1.
Timeout while preparing target, RAMCode did not respond in time. (PC = 0x00000000, CPSR = 0x00000000, LR = 0x61000003)!
Failed to prepare RAMCode using RAM
Failed to download application.
Generic error.
Please check J-Link and target connection.
Illegal value 0x21009F28 written to register 67 (PSP_NS) ignored

The current draw after the download is uncganged.

RE: peripheral uart power consumption

Hung Bui — Mon, 19 Apr 2021 13:46:03 GMT

Hei Martin,
When you configure the hci_rpmsg, please make sure you set CONFIG_LOG=n and CONFIG_SERIAL=n . Logging enabled on the netcore could be the reason you have higher current consumption.