GitLab

The documentation says:
"In cases where default mutex attributes are appropriate, the macro
PTHREAD_MUTEX_INITIALIZER can be used to initialize mutexes that are
statically allocated. The effect shall be equivalent to dynamic
initialization by a call to pthread_mutex_init() with parameter attr
specified as NULL, except that no error checks are performed."

Signed-off-by: mz-fuzzy <mzfuzzy800@gmail.com>

Clean-up/fix of RF24 configuration examples in RPi/Python example.
Signed-off-by: mz-fuzzy <mzfuzzy800@gmail.com>

Ooops.. thanks to marceloaqno for spotting this.

- Update scanner examples to use channels 0-125
- Update documentation indicating channels 0-125 only
- Per datasheet radio only has 126 channels

RPI2 autodetection

- SPI_HAS_TRANSACTION define was not being picked up properly: add
define to RF24_arch_config.h
- Fix beginTransaction call using RF_SPI_SPEED instead of RF24_SPI_SPEED
- Change beginTransaction to use SPISettings object
-

- Bring beginTransaction inline with Arduino API
- #define SPI_HAS_TRANSACTION in SPI.h
- #define the spi speed on both Arduino and RPi/Linux using
RF24_SPI_SPEED instead of different vars
- Chg beginTransaction to use bitOrder & mode instead of CSN
- Add delay directly to chipSelect function (helps ensure pin is active
before beginning SPI transactions)

#173

- Fix blank response detect & remove wait

- Create interrupts folder for RPi examples
- Add new examples
- Update Makefile

- SPI transfern function calls transfernb function so a deadlock was
occurring when a lock was attempted prior to the call
- Thread should be unlocked before returning if bcm2835_init() fails

- Create separate mutex for SPI vs User data handling
Problems:
A: Memory/Data conflicts became apparent after time without thread-safe
queues
B: Without implementing locking at the SPI level, even simple code
examples (rx_transfer.cpp) would hang if a write was done out of sync
with reads

Solutions:
A: Keep initial locking mechanism for users
B: Implement separate automatic mutex and locking mechanism for SPI

#172 #173

per #172 #173

- Add mutex locking to SPI for RPi interrupt usage
- Leave rfInterrupts() rfNoInterrupts() functions for testing purposes

Using interrupts on RPi

Updated bcm library via http://www.airspayce.com/mikem/bcm2835/

http://www.airspayce.com/mikem/bcm2835/bcm2835-1.48.tar.gz

- #include <unistd.h>