summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDario Nieuwenhuis <dirbaio@dirbaio.net>2022-03-15 22:35:15 +0100
committerDario Nieuwenhuis <dirbaio@dirbaio.net>2022-03-15 22:35:15 +0100
commit6ee09a134d9366029462963650dcd7e3921d6c1d (patch)
treeaba264e82748ef0456db7bc47f7c2deca0c7e77d
parent5f6d67abb3a3f72d55b8eb2ef51bc3c646e4814c (diff)
downloadnrf-softdevice-6ee09a134d9366029462963650dcd7e3921d6c1d.zip
readme: warn about assertion failed errors.
-rw-r--r--README.md3
1 files changed, 3 insertions, 0 deletions
diff --git a/README.md b/README.md
index 034c16f..84e2765 100644
--- a/README.md
+++ b/README.md
@@ -126,6 +126,9 @@ Next you need to find out if your board has an external oscillator (which provid
The SoftDevice does time-critical radio processing at high priorities. If its timing is disrupted, it will raise "assertion failed" errors. There's two common mistakes to avoid: (temporarily) disabling the softdevice's interrupts, and running your interrupts at too high priority.
+These mistakes WILL cause "assertion failed" errors, 100% guaranteed. If you do these only "a little bit", such as disabling all interrupts but for very short periods of time only, things may appear to work, but you will get "assertion failed" errors after hours
+of running. Make sure to follow them to the letter.
+
### Critical sections
Interrupts for certain peripherals and SWI/EGUs are [reserved for the SoftDevice](https://infocenter.nordicsemi.com/topic/sds_s140/SDS/s1xx/sd_resource_reqs/hw_block_interrupt_vector.html?cp=4_7_4_0_6_0). Interrupt handlers for them are reserved by the softdevice, the handlers in your application won't be called.