Hi nordic team,
I have tried enabling SQSPI on the system off sample, but the power consumption jumped to 6.3mA in system off mode; I tried to disable the cpulfpr core but couldn't find anything, so I have attached my sample code with system off and sqspi enabled to help identify why the current remains so high.
Regards,
Hi,
In system off mode, the cores are switched off, and the system should be in sleep mode.
If you see excessive current draw at this point, I would recommend that you look into your gpio states, specifically the CSN pin in this case. This should be high in idle state.
Are you testing on a custom board or a nRF54L15-DK?
Kind regards,
Håkon
Could you clarify if you are referring to the CSN (Chip Select) pin? If so, yes, it remains HIGH during System OFF mode.
I am currently building for the nrf54l15 target, and my custom board uses the same flash IC and the same configuration as the DK.
For context, this is a custom board. The baseline consumption is 2.6 µA when the flash is not in use, so the 6.3 mA draw appears specifically linked to the SQSPI being enabled.
USER_BTN 3.3 v
LOAD_SWITCH 1.67v
AFE_OUT 2.5v
BAT_LEVEL 0v
I measured these corresponding to battery ground.
for the sample given I was just using nrf54l15dk dts with given overlay and flashing on my board. I am getting same consumption as when building on custom board dts
if the issue is schematic related. shouldn't be also there when flash flag is disabled?
Hi,
Ghazi-Faisal said:if the issue is schematic related. shouldn't be also there when flash flag is disabled?
Floating GPIOs will change based on how the system behaves.
Please set the corresponding GPIOs to their idle level and test.
If you still see issues, please start isolating each part of your design, and see what draws current.
Ghazi-Faisal said:LOAD_SWITCH 1.67v
Should this signal be ~1.7V?
Kind regards,
Håkon
Should this signal be ~1.7V?
This is digital signal and it should be low. so I think it should be close to zero
Floating GPIOs will change based on how the system behaves.
Aside from rgb led and LOAD_SWITCH, which are already set to their idle state before going to system_off, all other used gpios are inputs.
Hi,
Please read my former answers.
I strongly advice that you enable pull inside the GPIO pad on all your connected GPIOs, by setting this for each of your connected signals:
https://docs.nordicsemi.com/bundle/ps_nrf54L15/page/gpio.html#ariaid-title22
You can also search around for "floating inputs" - this will cause excessive current consumption in your custom board unless properly addressed.
Given that LOAD_SWITCH is 1.7V, and you state this:
Ghazi-Faisal said:This is digital signal and it should be low.
This is clearly something you should address.
Kind regards,
Håkon
Hi,
Please read my former answers.
I strongly advice that you enable pull inside the GPIO pad on all your connected GPIOs, by setting this for each of your connected signals:
https://docs.nordicsemi.com/bundle/ps_nrf54L15/page/gpio.html#ariaid-title22
You can also search around for "floating inputs" - this will cause excessive current consumption in your custom board unless properly addressed.
Given that LOAD_SWITCH is 1.7V, and you state this:
Ghazi-Faisal said:This is digital signal and it should be low.
This is clearly something you should address.
Kind regards,
Håkon
I strongly advice that you enable pull inside the GPIO pad on all your connected GPIOs, by setting this for each of your connected signals:
I tried pulling all GPIOs but that didn't help.
This is clearly something you should address.
do you have any thorughts of how to debug this?
Hi,
You are not sharing any in-depth information, other that "did not help" - if you want help, please be verbose.
Can you please test on a DK, and try to replicate it there?
Kind regards,
Håkon
I’m not entirely sure what information would help you diagnose this issue. Please let me know what details would be useful (for example logs, configuration files, DTS, power measurements, etc.), and I’ll provide whatever I can.
Also, I don’t currently have the DK with me to run additional tests. If there’s another way we can work around this or gather useful information without the DK, please let me know.
Given that LOAD_SWITCH is 1.7V, and you state this
excuse me this was GND1 relative to GND when both GNDs are disconnected. I was measuring the wrong pin
Regards,
You can also search around for "floating inputs" - this will cause excessive current consumption in your custom board unless properly addressed.
I had a thought that the higher current might be caused by GND1 floating during System OFF.
To test this, I performed the following:
Removed the external flash, after which the current dropped to ~0.6 mA.
After that, I removed all 3.3 V components that could potentially create a path to GND to simulate the System OFF condition without the possibility of GND1 floating. The current consumption remained ~0.6 mA.
Note: in both cases I shorted both GND planes (GND and GND1)
