From 3052f4bb13d42c769baa5fc2f0512566ca60a0a0 Mon Sep 17 00:00:00 2001 From: Uwe Hermann Date: Wed, 9 Jul 2014 17:35:59 +0200 Subject: spi/nrf24l01: Minor cosmetics, fixed typos. --- spi/nrf24l01/README | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) (limited to 'spi') diff --git a/spi/nrf24l01/README b/spi/nrf24l01/README index 0d7667c..97d404b 100644 --- a/spi/nrf24l01/README +++ b/spi/nrf24l01/README @@ -3,7 +3,7 @@ nRF24L01/nRF24L01+ ------------------------------------------------------------------------------- This directory contains a capture of the communication between two nRF24L01+ -tranceivers, one connected to a Raspberry Pi and the other connected to an +transceivers, one connected to a Raspberry Pi and the other connected to an AVR microcontroller, and some generated files to test paths in the protocol decoder that aren't covered in the capture. @@ -23,7 +23,7 @@ The logic analyzer used was a Lcsoft Mini Board (at 12MHz): PB2 (rpi_CLK) clock signal of the receiving chip PB3 (rpi_MOSI) MOSI signal of the receiving chip PB4 (rpi_MISO) MISO signal of the receiving chip - PB5 (rpi_IRQ) interrupt signal fo the receiving chip, active low + PB5 (rpi_IRQ) interrupt signal for the receiving chip, active low PD0 (uc_CSN) chip select signal of the sending chip, active low PD1 (uc_CLK) clock signal of the sending chip PD2 (uc_MOSI) MOSI signal of the sending chip @@ -45,18 +45,18 @@ The sigrok command line used was: The capture starts with the Raspberry Pi initializing its chip as a receiver, followed by the microcontroller initializing the second chip as a transmitter at about 8.8ms - 9ms. 30ms after the start of the capture, the microcontroller -starts sending the strings "message #0" to "message #9" in intervalls of about +starts sending the strings "message #0" to "message #9" in intervals of about 10ms. After sending a message, it uses polling to detect when the message is sent and the acknowledge from the receiver is received. The Raspberry Pi handles the first six messages after the receiving chip asserts the interrupt signal. -Because it doesn't handle the other four messages and the receive fifo in the +Because it doesn't handle the other four messages and the receive FIFO in the receiver runs full after three messages, the last message isn't acknowledged. The sender detects that and reads the lost packet counter from the sender chip, which consequently has a value of one. nrf24l01-communication-[rx|tx].sr ----------------------------- +--------------------------------- These files were generated from the file 'nrf24l01-communication.sr' using the commands @@ -77,7 +77,7 @@ decoder correctly decodes the message payload. nrf24l01-test-... --------------------- +----------------- These files were generated by the 'gen-testfiles.py' script and contain test cases for the decoder that aren't yet covered by the other captures. -- cgit v1.2.3-54-g00ecf