• State Suggested Answer
  • +1 person also asked this people also asked this
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 70 subscribers
  • Views 791 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 232211
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

NRF9160 low power current consumption back up again with production SDK V1.0.0

GJSea

Hi,

Since migrating to V1 of modem firmware and tag v1.0.0 the low power mode of the SIP is back up to about 700uA again instead of the 7uA we were seeing before upgrading to the production SDK and firmware. Below is code in its simplest for with CONFIG_SERIAL=n, nrf9160_pca10090ns.

Any ideas? Thx!

void main(void)
{
  while (true) 
  {
     k_sleep(5000);
  }
}

Here's the prj.conf

# General config
CONFIG_NEWLIB_LIBC=y
CONFIG_TEST_RANDOM_GENERATOR=y
CONFIG_ASSERT=y
CONFIG_REBOOT=y
CONFIG_NO_OPTIMIZATIONS=y

# Network
CONFIG_NETWORKING=y
CONFIG_NET_SOCKETS=y
CONFIG_NET_SOCKETS_OFFLOAD=y

# MQTT
CONFIG_MQTT_SOCKET_LIB=y
CONFIG_MQTT_LIB_TLS=y
CONFIG_MQTT_MAX_PACKET_LENGTH=2048

# GPIO
CONFIG_GPIO=y

# LTE link control
CONFIG_POWER_OPTIMIZATION_ENABLE=y
CONFIG_LTE_LINK_CONTROL=y
CONFIG_LTE_AUTO_INIT_AND_CONNECT=n
CONFIG_LTE_PSM_REQ_RPTAU="10101010"
CONFIG_LTE_PSM_REQ_RAT="00100001"

# Time
CONFIG_SNTP=y

# BSD library
CONFIG_BSD_LIBRARY=y

# nRF Cloud
CONFIG_NRF_CLOUD=y

# MQTT
# CONFIG_MQTT_LIB=y
CONFIG_MQTT_LIB_TLS=y

# Sensors
CONFIG_GPS_USE_SIM=y
CONFIG_ACCEL_USE_SIM=y

# Enable I2C
CONFIG_I2C=y
CONFIG_I2C_2=y
CONFIG_I2C_2_NRF_TWIM=y
CONFIG_I2C_NRFX=y
CONFIG_I2C_INIT_PRIORITY=60

# Console
CONFIG_BSD_LIBRARY_TRACE_ENABLED=n
CONFIG_SERIAL=n

# Main thread
CONFIG_MAIN_THREAD_PRIORITY=7

# Heap and stacks
CONFIG_HEAP_MEM_POOL_SIZE=16384
CONFIG_MAIN_STACK_SIZE=8192
CONFIG_GPS_SIM_THREAD_STACK_SIZE=1024
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=1500
CONFIG_HW_STACK_PROTECTION=y

Parents Reply Children
  • 0 in reply to AndreasF

    Hi Andreas,

    Aaaargh it was this that tripped me up again and I'm back to proper low current levels again. I assumed the newly integrated projects from V0.4.0 forward dealt with the SPM autonomously rather than as a separately configured example project in another location.

    I'm sure many others are going to stumble over this time over time again, perhaps the *default* for SPM is to have CONFIG_SERIAL=n, and only those that need to get logs out of SPM can turn it back on?

    Thanks!!

  • 0 in reply to GJSea

    Hi again.

    Glad to hear you have it working now.

    GJSea said:
    I'm sure many others are going to stumble over this time over time again, perhaps the *default* for SPM is to have CONFIG_SERIAL=n, and only those that need to get logs out of SPM can turn it back on?

     Thanks for the suggestion, I will forward this to the developers :-)

    Best regards,

    Andreas

Related