Ultra Low Power on B523

When putting B523 to ultra low power sleep on the B SOM eval board v1.1, I get 108.5uA on both 2.0.2 and 4.0.2 instead of the 55uA mentioned in the reference:


Tested with this sketch (ultra low power sleeps 60 secs after connecting):


Testing on the B SOM eval board v1.1. All J12, J13, J5, J31 jumpers removed to isolate B523. Then powering both 3.3V and VCC directly at J5 and J31 with 3.59V from a power profiler (PPK2).

Same if I connect to Particle cloud before sleeping.

Going over the eval board schematic and board (loaded into Eagle), I can’t find a culprit for the extra consumption. So I wonder what OS version the reference numbers are from?

It’s almost certainly the Wiznet W5500 Ethernet chip on the B Series SoM eval board. Device OS does not put it into sleep mode, and the jumpers only isolate the data lines, not the power lines.

The power numbers weren’t done on the eval board, they were done on a different board with no extra peripherals.

Hello @thrmttnw

I had a similar problem when I also tested the eval board with a PowerProfiler Kit 2, have a look at my thread here:

It was primarily the Ethernet component that has a high power consumption during my testing, after desoldering It lowered the power consumption a lot, then you still have the PMIC and fuel gauge using power typically.

Thank you for the hints.

There should be no power to anything on the right side of the board Wiznet, PMIC, regulators etc. I am powering B523 via the left pins in J5 and J31, with all jumpers removed (except charge status). :

I have highlighted the 3.3V rail that does get power.

Looking at B523 connections apart from reset and LED’s and SWD/JTAG pads. And I am left with ADC7 connected to Wiznet RESET pin.

I have also set all digital and analog pins to input in case of a leakage issue, and still get the same result.

It would be great if I could try the same OS as for the reference numbers, as I would still need this for testing my own board?

The Device OS version for the original B523 testing wasn’t recorded in the internal document, but it would have been old. However, The B404X was recently tested with Device OS 5, and the numbers with cellular off were identical to the B523 numbers, so I don’t think the Device OS version should matter too much.

What LTS/OS version are you guys on?

What version of OS 5?

As I am not able to verify the 55uA and it is paramount for the project I had in mind, I have decided not to go ahead with it.

It is great to see the increased focus on low power applications. It is cool that ultra low power mode retains the date and time. I hope in the future sleeping modes will become part of release/regression tests for LTS releases.

If you want to work with real low-power applications, I suggest to look at the Nordic Semi NRF9160 (down to 5 microampere in sleep!) and it has LTE-M and NB-IoT connectivity for low-power data transmission. It can be found in a prototype kit called Nordic Thingy:91 - I’m testing it out as well, as we cannot develop low-power variants with the current Particle hardware.

1 Like

I believe it was 3.3.0 at the time

1 Like

Sleeping on it, I found the leaking culprit by measuring consumption w.o. B523 mounted, to be the 47Kohm R9 SD card detect pull-up.

Disabling the card detect with a plastic insert, and with B523 mounted, consumption during ultra low power sleep was 37.9uA on average over a minute for both the 3.3V and VCC rails combined powered by 3.6V.

This dropped down during the first minutes, and settled around 36.4uA average.


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.