|
| 1 | +.. _intro_soft_peripherals: |
| 2 | + |
| 3 | +Introduction |
| 4 | +############ |
| 5 | + |
| 6 | +.. contents:: |
| 7 | + :local: |
| 8 | + :depth: 2 |
| 9 | + |
| 10 | +Soft peripherals enable the emulation of a digital hardware peripheral (IP) by executing it on the Fast Lightweight Peripheral Processor (FLPR) through an application-controlled user interface. |
| 11 | +This functionality allows the soft peripheral to be used in a system where the hardware of a peripheral is not available. |
| 12 | +It also allows to include additional instances of a peripheral in case the platform lacks sufficient hardware peripherals. |
| 13 | + |
| 14 | +In most cases, the features and performance of a soft peripheral are equivalent to those of a hardware peripheral. |
| 15 | +However, there may be some limitations. For more information, see the :ref:`sqspi_limitations` page. |
| 16 | + |
| 17 | +The operation of a soft peripheral is abstracted, and its control is facilitated through a user interface managed through the nrfx driver API. |
| 18 | +This user interface is a set of functions that the application can call to interact with the peripheral. |
| 19 | + |
| 20 | +The following image shows the software stack of an application: |
| 21 | + |
| 22 | +.. image:: images/SP_concept.svg |
| 23 | + :alt: Soft Peripheral concept |
| 24 | + |
| 25 | +.. note:: |
| 26 | + |
| 27 | + Note that in both the documentation and source files, soft peripherals are referred to by prefixing the letter *s* before the name of the peripheral. |
| 28 | + For example, ``sQSPI``. |
| 29 | + |
| 30 | + |
| 31 | +Comparison between QSPI and sQSPI support |
| 32 | +***************************************** |
| 33 | + |
| 34 | +You should be aware of the differences between sQSPI and QSPI features: |
| 35 | + |
| 36 | +.. list-table:: |
| 37 | + :header-rows: 1 |
| 38 | + |
| 39 | + * - Feature |
| 40 | + - QSPI support |
| 41 | + - sQSPI support |
| 42 | + * - DDR Clocking |
| 43 | + - yes |
| 44 | + - no |
| 45 | + * - XIP (Execute in Place) |
| 46 | + - yes |
| 47 | + - no |
| 48 | + * - SSP (Synchronous Serial Protocol) |
| 49 | + - yes |
| 50 | + - no |
| 51 | + * - MICROWIRE |
| 52 | + - yes |
| 53 | + - no |
| 54 | + * - JEDEC xSPI |
| 55 | + - yes |
| 56 | + - no |
| 57 | + * - HyperBus |
| 58 | + - yes |
| 59 | + - no |
| 60 | + * - Data Masking |
| 61 | + - yes |
| 62 | + - no |
| 63 | + * - SPI Dynamic Wait State |
| 64 | + - yes |
| 65 | + - no |
| 66 | + * - Multi-Master Bus Topologies (Arbitration) |
| 67 | + - yes |
| 68 | + - no |
| 69 | + * - Clock Stretching |
| 70 | + - yes |
| 71 | + - no |
| 72 | + * - Toggling CS High Between Data Frames (SSTE: Target Select Toggle Enable) |
| 73 | + - yes |
| 74 | + - no |
| 75 | + * - QSPI Address/Command Lengths Using 4-Bit Increments |
| 76 | + - yes |
| 77 | + - no |
| 78 | + |
| 79 | +Platform support |
| 80 | +**************** |
| 81 | + |
| 82 | +The following table shows which soft peripherals and their versions are supported by each platform: |
| 83 | + |
| 84 | +.. list-table:: Soft peripheral device support |
| 85 | + :widths: auto |
| 86 | + :header-rows: 1 |
| 87 | + |
| 88 | + * - Soft Peripheral |
| 89 | + - Hardware platform |
| 90 | + - Version(s) |
| 91 | + * - sQSPI |
| 92 | + - nRF54L15 SoC |
| 93 | + - v0.1.0 |
| 94 | + * - sQSPI |
| 95 | + - nRF54H20 SoC |
| 96 | + - v0.1.0 |
0 commit comments