|
| 1 | +.. zephyr:board:: mikroe_quail |
| 2 | +
|
| 3 | +Overview |
| 4 | +******** |
| 5 | +MikroE Quail for STM32 is a development board containing an `STM32F427`_ |
| 6 | +microcontroller. It is equipped with four mikrobus sockets. |
| 7 | +The edges of the board are lined with screw terminals and USB ports for |
| 8 | +additional connectivity. |
| 9 | + |
| 10 | +Hardware |
| 11 | +******** |
| 12 | +The Quail board contains the following connections: |
| 13 | + |
| 14 | + - Four MikroBUS connectors |
| 15 | + - lined with 32 screw terminals and USB ports for |
| 16 | + |
| 17 | +Furthermore the board contains three LEDs that are connected |
| 18 | +to the microcontroller. |
| 19 | + |
| 20 | +Supported Features |
| 21 | +================== |
| 22 | + |
| 23 | +.. zephyr:board-supported-hw:: |
| 24 | +
|
| 25 | +Connections and IOs |
| 26 | +=================== |
| 27 | + |
| 28 | +The four mikroBUS interfaces are aliased in the device tree so that their |
| 29 | +peripherals can be accessed using ``mikrobus_N_INTERFACE`` so e.g. the spi on |
| 30 | +bus 2 can be found by the alias ``mikrobus_2_spi``. The counting corresponds |
| 31 | +with the marking on the board. |
| 32 | + |
| 33 | +For connections on the edge connectors, please refer to `Quail for STM32 User Manual`_. |
| 34 | + |
| 35 | +Programming and Debugging |
| 36 | +************************* |
| 37 | + |
| 38 | +.. zephyr:board-supported-runners:: |
| 39 | +
|
| 40 | +Applications for the ``mikroe_quail`` board can be built and flashed in the usual way |
| 41 | +(see :ref:`build_an_application` and :ref:`application_run` for more details). |
| 42 | + |
| 43 | + |
| 44 | +Flashing |
| 45 | +======== |
| 46 | +The initial state of the board is set to lock. |
| 47 | +When you flash, it will fail with the message: |
| 48 | + |
| 49 | +.. code-block:: console |
| 50 | +
|
| 51 | + Error: stm32x device protected |
| 52 | +
|
| 53 | +Unlocking with openocd makes it possible to flash. |
| 54 | + |
| 55 | +.. code-block:: console |
| 56 | +
|
| 57 | + $ openocd -f /usr/share/openocd/scripts/interface/stlink-v2.cfg \ |
| 58 | + -f /usr/share/openocd/scripts/target/stm32f4x.cfg -c init\ |
| 59 | + -c "reset halt" -c "stm32f4x unlock 0" -c "reset run" -c shutdown |
| 60 | +
|
| 61 | +Here is an example for the :zephyr:code-sample:`hello_world` application. |
| 62 | + |
| 63 | +.. zephyr-app-commands:: |
| 64 | + :zephyr-app: samples/hello_world |
| 65 | + :board: mikroe_quail |
| 66 | + :goals: build flash |
| 67 | + |
| 68 | +You should see the following message on the console: |
| 69 | + |
| 70 | +.. code-block:: console |
| 71 | +
|
| 72 | + Hello World! mikroe_quail |
| 73 | +
|
| 74 | +
|
| 75 | +Debugging |
| 76 | +========= |
| 77 | + |
| 78 | +You can debug an application in the usual way. Here is an example for the |
| 79 | +:zephyr:code-sample:`hello_world` application. |
| 80 | + |
| 81 | +.. zephyr-app-commands:: |
| 82 | + :zephyr-app: samples/hello_world |
| 83 | + :board: mikroe_quail |
| 84 | + :maybe-skip-config: |
| 85 | + :goals: debug |
| 86 | + |
| 87 | +References |
| 88 | +********** |
| 89 | + |
| 90 | +.. target-notes:: |
| 91 | + |
| 92 | +.. _Quail website: |
| 93 | + https://www.mikroe.com/quail |
| 94 | +.. _Quail for STM32 User Manual: |
| 95 | + https://download.mikroe.com/documents/starter-boards/other/quail/quail-board-manual-v100.pdf |
| 96 | +.. _STM32F427VIT6 Website: |
| 97 | + https://www.st.com/en/microcontrollers-microprocessors/stm32f427vi.html |
| 98 | +.. _STM32F427: |
| 99 | + https://www.st.com/resource/en/datasheet/stm32f427vg.pdf |
0 commit comments