This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

CONFIG_POWER_OPTIMIZATION_ENABLE=y and asset_tracker application on master branch

I cannot set CONFIG_POWER_OPTIMIZATION_ENABLE to yes in the master branch. It leads to deadlock in at_cmd_write() because that ends up getting executed in the socket_thread. Actually it triggers the ASSERT 

__ASSERT(k_current_get() != socket_tid,
"at_cmd deadlock: socket thread blocking self\n");

to prevent deadlock.

Will the lte_link_control code be updated to match those changes on master branch in at_cmd? Is there a time frame? My colleague Timothy received the suggestion to use the master branch due to problems getting modem_info, and I am following along that path.

Thanks,

Burt

Parents
  • Hi Burt,

    Thank you for the feedback. 
    The R&D team are looking into it, hopefully there will come a fix a soon as possible.
    I will let you know when it's ready.

  • Thanks, Martin, looking forward to hearing more when it's ready.

  • There is now a Pull Request that should fix this issue: https://github.com/nrfconnect/sdk-nrf/pull/2679
    It will be merged into the master branch as soon as it has been approved by the reviewers.

    Either you wait for it to get in master and then update NCS:

    Fullscreen
    1
    2
    3
    4
    cd ncs/nrf
    git checkout master
    git pull
    west update
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    or test out the PR:

    Fullscreen
    1
    2
    3
    4
    cd ncs/nrf
    git fetch ncs pull/2679/head:pr-2679
    git checkout pr-2679
    west update
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    (change out "ncs" with origin based on what you have called your remote)

    e.g.

Reply
  • There is now a Pull Request that should fix this issue: https://github.com/nrfconnect/sdk-nrf/pull/2679
    It will be merged into the master branch as soon as it has been approved by the reviewers.

    Either you wait for it to get in master and then update NCS:

    Fullscreen
    1
    2
    3
    4
    cd ncs/nrf
    git checkout master
    git pull
    west update
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    or test out the PR:

    Fullscreen
    1
    2
    3
    4
    cd ncs/nrf
    git fetch ncs pull/2679/head:pr-2679
    git checkout pr-2679
    west update
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    (change out "ncs" with origin based on what you have called your remote)

    e.g.

Children
No Data