• State Verified Answer
  • Replies 4 replies
  • Subscribers 67 subscribers
  • Views 1438 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 233331
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Qspi interrupt hangs caused by power consumption problems

outspace

Hi,Master:

When I use the QSPI library to communicate with flash, everything works fine. After a complete read and write, nrfx_qspi_uninit() is called to reduce power consumption, but there will always be a qspi interrupt pending in the NVIC, which causes the sleep to be unsuccessful, resulting in power consumption. Adding NRFX_IRQ_PENDING_CLEAR(QSPI_IRQn) solves this problem. Why? What are the hidden issues on the nordic platform that need attention? Thank you

Parents
  • 0

    Hi,

    Is nrfx_qspi_uninit() called from an interrupt context that could block a QSPI IRQ from being serviced? Please check if the EVENTS_READY register actually is cleared (read as '0') after you have uninitialized the peripheral.    

  • +1 in reply to Vidar Berg

    Hi,Vidar Berg

    Maybe I didn't express my question clearly: I mean:When I use the QSPI library to communicate with flash, first initialize nrfx_qspi_init(&config, NULL, NULL) (handler parameter is NULL, ie: qspi internal interrupt is not enabled); after reading and writing, call nrfx_qspi_uninit() to reduce power consumption , but there will always be qspi interrupt hangs in NVIC, which will result in main

    for(;;)

    {

    App_sched_execute();

    Ble_idle_state();

    Sys_wdt_feed();

    }

    is always woken up, resulting in an average power consumption that cannot be reduced. This problem can be solved by adding NRFX_IRQ_PENDING_CLEAR(QSPI_IRQn) after calling nrfx_qspi_uninit(). why? Is there any hidden problem that needs attention in other places on the nordic platform? Thank you

Reply
  • +1 in reply to Vidar Berg

    Hi,Vidar Berg

    Maybe I didn't express my question clearly: I mean:When I use the QSPI library to communicate with flash, first initialize nrfx_qspi_init(&config, NULL, NULL) (handler parameter is NULL, ie: qspi internal interrupt is not enabled); after reading and writing, call nrfx_qspi_uninit() to reduce power consumption , but there will always be qspi interrupt hangs in NVIC, which will result in main

    for(;;)

    {

    App_sched_execute();

    Ble_idle_state();

    Sys_wdt_feed();

    }

    is always woken up, resulting in an average power consumption that cannot be reduced. This problem can be solved by adding NRFX_IRQ_PENDING_CLEAR(QSPI_IRQn) after calling nrfx_qspi_uninit(). why? Is there any hidden problem that needs attention in other places on the nordic platform? Thank you

Children
Related