i just rebuilt the code in the beacon_advertiser.zip file attach to this issue for the NRF52232....
the code runs as expected, though consumes about 200uA when sleeping....
but contrast, the original nRF54L version consumes about 3uA when sleeping....
what can i do lower my sleep current???
one other note -- when building for nRF52 i received a warning that ASSERT was enabled
Hello,
I wasn't able to reproduce this high floor current. My results are shown below. Could you try using the attached hex file and let me know if you get the same result?
Measurement result nRF52 DK - 0 dBm
Measurement setup - Source meter mode (Measuring current in Source Meter mode)
hex file (tested both with SDK v2.9.1 and v3.0.0-rc2 with the same result)
Best regards,
Vidar
actually, what i saw before might have been a fluke.... here's what i initially captured....
but then i realized that the .hex file you sent was actually the same beacon_advertiser sample.... here's the capture from running your file...
this suggests that (perhaps) something is wrong on my board setup??? the active power numbers seem consistent with your capture; it's the IDLE power that 200uA too high....
could this be a bad solder bridge cut??? is there some else i need to do in setting up the board for power measurement??? is there some other component on the board (eg., SPI flash) that needs to be disabled???
all the more mysterious, in that **some program** (which i believe was mine) produced that initial capture....
missing capture:
bios-bob said:question about nRF52-DK setup.... when in source meter mode, do i have the USB plugged in or not???
It must be plugged in as it supplies power to the interface MCU, LEDs,.. It's also important that the voltage provided by the PPK matches the regulated voltage from the USB (3.3V minus the voltage drop across the protection diode). Otherwise, current leakage may occur. You can measure the voltage on VDD to get the exact voltage from this regulator. I just set it to 2.9v which should be close enough:
bios-bob said:i've also tried ampere meter mode, by supplying my own 3.3V while connecting the PPK Vin and Vout to the current measure jumper.... the USB is now unplugged.... but i continue to see the same results -- 200uA when sleeping....
Are you seeing this with the hex file I provided (built from the beacon sample I uploaded), or only with your project? If it’s the latter, could you upload that project here so I can try to reproduce the issue?
bios-bob said:documentation also talks about soldering/desoldering SB12 -- which i have not done....
This is only to avoid the voltage drop across the diode. It is not required.
bios-bob said:question about nRF52-DK setup.... when in source meter mode, do i have the USB plugged in or not???
It must be plugged in as it supplies power to the interface MCU, LEDs,.. It's also important that the voltage provided by the PPK matches the regulated voltage from the USB (3.3V minus the voltage drop across the protection diode). Otherwise, current leakage may occur. You can measure the voltage on VDD to get the exact voltage from this regulator. I just set it to 2.9v which should be close enough:
bios-bob said:i've also tried ampere meter mode, by supplying my own 3.3V while connecting the PPK Vin and Vout to the current measure jumper.... the USB is now unplugged.... but i continue to see the same results -- 200uA when sleeping....
Are you seeing this with the hex file I provided (built from the beacon sample I uploaded), or only with your project? If it’s the latter, could you upload that project here so I can try to reproduce the issue?
bios-bob said:documentation also talks about soldering/desoldering SB12 -- which i have not done....
This is only to avoid the voltage drop across the diode. It is not required.
tried a different DK, same 200uA result....
but then, i tried a very simple test -- a main() that calls k_busy_wait(2000000) followed by k_sleep(K_FOREVER).... this resulted inj very good results, which i verified with my PPK as well as my multimeter....
somethiing is obviously working here!!!! presumably this means my DK + PPK are working???? i still don't understand why YOUR .hex file shows 200uA of sleep current???
