13.1.28. PN7160TokenProvider¶
+For a detailed handwritten documentation see here
+diff --git a/docs/latest/_generated/modules/PN532TokenProvider.html b/docs/latest/_generated/modules/PN532TokenProvider.html index eef38c616..a4758b040 100644 --- a/docs/latest/_generated/modules/PN532TokenProvider.html +++ b/docs/latest/_generated/modules/PN532TokenProvider.html @@ -19,7 +19,7 @@ - +
For a detailed handwritten documentation see here
+For a detailed handwritten documentation see here
For a detailed handwritten documentation see here
For a detailed handwritten documentation see here
This module provides authentication tokens obtained from RFID cards via the NXP PN7160 NFC chip.
+It uses a modified libnfc-nci as external dependency to interface the chip via I²C or SPI, either from user space or via a kernel module.
+Configuration of the hardware interface is possible at runtime. +The module installs two configuration files:
+libnfc-nci_config/libnfc-nci.conf
: define NFC options
libnfc-nci_config/libnfc-nxp.conf
: choose the hardware interface (kernel module vs. userspace; I²C vs. SPI, …)
The EVerest module can be adjusted in its behaviour as follows:
+token_debounce_interval_ms
: Publish tokens in minimum intervall of this timespan in order not to flood subscribers.
disable_nfc_rfid
: Allows to load the module without actually initializing the hardware.
See also module’s auto-generated reference.
The module YetiDriver
is a board support driver for Pionix Yeti Power
Board.
The hardware connection between Yeti and Yak (the board running EVerest and this module) is 3.3V TTL UART plus 2 GPIOs (one to reset the microcontroller from Linux and one to wakeup Linux from the microcontroller, which is @@ -59,7 +59,7 @@
The default configuration is 115200 bps 8N1.
EVerest can send commands to Yeti and Yeti publishes data and events back to EVerest. The packets are defined with protobuf to serialize the C structs into a binary representation that is transferred over the serial wire in a @@ -69,7 +69,7 @@
https://en.wikipedia.org/wiki/Consistent_Overhead_Byte_Stuffing
COBS is implemented in yeti_comms/evSerial.cpp
. Whenever a new packet
was extracted from the stream handlePacket()
is called to decode protobuf
and generate the corresponding signals.
@@ -78,7 +78,7 @@
linkWrite
encodes the packet with COBS and outputs it to the UART.
The actual packet definitions are located under yeti_comms/protobuf
.
hi2lo.proto
contains all messages that can be sent from EVerest to Yeti
while lo2hi.proto
defines all messages that Yeti sends to EVerest.
The most important commands that EVerest sends to Yeti are the following:
SetControlMode(mode)
: Yeti firmware can operate in different modes:
Mode NONE = 0
: In this mode Yeti does not allow control over UART. It will
@@ -108,7 +108,7 @@
The following commands describe the Low level control mode only:
AllowPowerOn(bool)
: Inform yeti that it is allowed to switch on the power
relais/contactors to the car on (true) or must switch off now (false). The
@@ -121,7 +121,7 @@
FirmwareUpdate(bool)
: Send true to reboot Yeti into ROM boot loader.
After that stm32flash tool can be used to flash any firmware binary to it.
Note that this is a dev kit and for a real product this needs to be implemented
@@ -149,7 +149,7 @@
The following messages are relevant for LOW control mode:
Event
: This is the most important message from Yeti. It will send an event
on CP transitions:
Addtionally, you can have a look at the documentation regarding interfaces diff --git a/docs/latest/general/06_handling_bank_cards.html b/docs/latest/general/06_handling_bank_cards.html index af1406129..6192be181 100644 --- a/docs/latest/general/06_handling_bank_cards.html +++ b/docs/latest/general/06_handling_bank_cards.html @@ -20,7 +20,7 @@ - +
For a detailed handwritten documentation see here
+For a detailed handwritten documentation see here