GitLab

- Fix for compatibility with SoftSPI and SPI_UART
- I seemed to be running two different versions, fixed for compatibility
between RPi and Arduino

Update scanner.ino

Update Transfer.ino

Update GettingStarted.ino

Changed baudrate to match other examples.

Serial baudrates should be the same in all examples.

Serial connection baudrates should be same in all examples.

Per https://github.com/TMRh20/RF24/issues/101#issuecomment-94163382
initialize pipe0_reading_address[0] to address "Weird and unstable
behavior of python wrapper" identified by @kormitigrov   Resolution/Root
Cause identified by mz-fuzzy

Fix over reading a buffer by 1 byte

https://github.com/TMRh20/RF24/issues/101

https://github.com/TMRh20/RF24/commit/28c363f4965ad4059e108a0a4921a64e4e737cac

- Per suggestion by @nerdralph use SPI_HAS_TRANSACTION instead of
Arduino version for detection of transaction support

- Remove most Due specific code
- Update remaining SPI code using transaction functions

- Use SPI transactions for 1.6.0 and up

- Temporarily comment changes to begin() pending further testing/dev
- Maintain backwards compatibility by detecting Arduino IDE version

- tmp fix - remove virtual destructor for Arduino etc
- Replace bell with null per #91

Conflicts:
	RF24.cpp

- Push fix to updates branch

https://github.com/TMRh20/RF24/pull/83

Fix operator precedence for isAckPayloadAvailable.

- Found the prev. method of RPi detection was not working on rasbpmc
- Updated to check for BCM via /proc/cpuinfo  - idea taken from MRAA lib

- Define SPI config vars for non-Arduino systems:
RF24_BIT_ORDER, RF24_DATA_MODE, RF24_CLOCK_DIVIDER
- Allow use of standard RF24 constructor on RPi with default of 8Mhz SPI
clock speed
- Cleanup #ifdefs in RF24::csn();
- Fix compile on ATTiny

- Add BBB pin config to examples per @desertgourd #69
- BBB tested and working well with SPIDEV and MRAA: Thanks to
@desertgourd for all the testing, troubleshooting, etc
- Sync pin config info between all *.cpp examples
- Add links to related documentation in examples

Added ```busNo``` passing to mraa::Spi()... per @prophet-roshak suggestion to SPI.begin chagnes

Added ```busNo``` passing to mraa::Spi() object creation call so that SPI bus number now can be defined by user when instatiating RF24 object

- Add Template folder with example class declarations etc
- Add template info to modules section in doxygen
- Update related links etc for doxygen in RF24.h

- Change SPI API for Linux devices to specify bus number in
SPI.begin(0);
- Enable kernel to handle cs toggling with SPIDEV
- Comment out GPIO for CS pin with MRAA
- Prevent linux devices from toggling CSN in RF24.cpp
- Ensure all linux devices default to 0 or 1 for csn_pin
- Remove some #ifdefs from RF24.cpp via above changes

- Note: When using SPIDEV, if the pin used for CSN has been toggled via
GPIO, users may need to do the following, to enable the kernel to toggle
CSN:
``` sudo modprobe -r spi_bcm2708 ```
``` sudo modprobe spi_bcm2708  ```

- Code needs cleanup/review

#69 #74

- Add Portability section to docs
- Add source file browser to docs
- Filter out GPIO and SPI classes from docs, but include in file lists
- Update doxyfile

- Modify spidev writes for bbb/linux - Something seems to have changed
with spidev with the spi_ioc_transfer struct on my machine. This seems
closer to the spidevtest.c example, so hopefully keeps working???
- Prevent warnings via compatibility.c/.h
- Add spi.begin to align with RF24 spi functions

Inadequate testing appeared to indicate the CRC checking was at fault,
this was incorrect.

Seemed to be 2 separate bugs in transfer example:
Symptoms: Arduino would start reading 150+ KB/s and about 5000
payloads/second received after a period of time with transfers ongoing
continuously.
Fixes:
1. Remove the printf of Payload Count (same issue with %lu )
2. Prevent division into 0