This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SPI long handler and crach

Hello, Platform nRF52 with SDK 11 (S132)

I use nrf_drv_spi_init to register a Handler (used for screen and SD card so it can be long)

I have sometimes crashes when i have activity on SPI and BLE at the same time. My Handler is maybe too long for execution.

Is there any way to check that ? Change SPI priority to low and to not perturbate SD timings ?

Thank you.

Parents
  • In the nrf_drv_spi_config_t struct used to initialize the SPI, you can set the irq_priority field to APP_IRQ_PRIORITY_LOW

  • Hi, I had a quick question on this:

    From where does the conflict arise if the SPI IRQ priority is APP_IRQ_PRIORITY_HIGH? My understanding of the IRQ priorities is all BLE and SD related priorities run at level APP_IRQ_PRIORITY_HIGHEST, so even if SPI is running at APP_IRQ_PRIORITY_HIGH, shouldn't the SD still be able to take control of the system as needed?

    Thanks!

Reply
  • Hi, I had a quick question on this:

    From where does the conflict arise if the SPI IRQ priority is APP_IRQ_PRIORITY_HIGH? My understanding of the IRQ priorities is all BLE and SD related priorities run at level APP_IRQ_PRIORITY_HIGHEST, so even if SPI is running at APP_IRQ_PRIORITY_HIGH, shouldn't the SD still be able to take control of the system as needed?

    Thanks!

Children
No Data
Related