Yes, at the BAT input.
The application is approximately 130µA with my one GPIO interrupt during idle state. I was able to add the interrupt driven GPIO to tell the nRF9160 to turn on the UART. I plan to disable it once I’m done receiving.
So I’ve pretty much isolated the issue. It has to do with the interrupt driven UART.
This balloons the consumption close to 1mA and I’m unable to reduce power using the following code:
/* Initialize the UART module */
printk("Cannot bind UART device\n");
/* Power off UART module */
err = pm_device_action_run(uart_dev2, PM_DEVICE_ACTION_SUSPEND);
printk("Can't power off uart: %d\n", err);
This does disable the UART, as I can’t receive and the the interrupt never fires but the power remains high.
So I’m stuck at this last hurdle, because otherwise the system functions as I want it to.