Skip to content

NRF52832 (PCA10040) hangs in BLE event handler routine or timer callback when printing #13520

Closed Answered by tb4450
tb4450 asked this question in nRF
Discussion options

You must be logged in to vote

I have set config.interrupt_priority = 5 in ports/nrf/modules/machine/uart.c and printing in that event handler seems to work.

Here is the description of the use of interrupts by the softdevice:

  • Level 0 is used for the SoftDevice's timing critical processing.
  • Level 1 is used for handling the memory isolation and run time protection, see Memory isolation and runtime protection.
  • Level 4 is used by higher-level deferrable tasks and the API functions executed as SVC interrupts.

Also the diagram https://infocenter.nordicsemi.com/topic/sds_s132/SDS/s1xx/Images/exception_model_s132.svg suggests that priorities 2, 3, 5, 6 and 7 are available for the application.

I just checked timer.c to see wh…

Replies: 5 comments 1 reply

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
1 reply
@tb4450
Comment options

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by tb4450
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
nRF
Labels
None yet
3 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy