boards/blues/cygnet/doc/index.rst
.. zephyr:board:: cygnet
Overview
The Blues Cygnet board features an ARM Cortex-M4 based STM32L433CC MCU with a wide range of connectivity support and configurations. Here are some highlights of the Cygnet board:
More information about the board can be found at the Blues Cygnet website_.
Hardware
The STM32L433CC SoC provides the following hardware IPs:
Ultra-low-power with FlexPowerControl (down to 28 nA Standby mode and 84 µA/MHz run mode)
Core: ARM® 32-bit Cortex®-M4 CPU with FPU, frequency up to 80 MHz, 100DMIPS/1.25DMIPS/MHz (Dhrystone 2.1)
Clock Sources:
RTC with HW calendar, alarms and calibration
11x timers:
Up to 21 fast I/Os, most 5 V-tolerant
Memories
Rich analog peripherals (independent supply)
17x communication interfaces
14-channel DMA controller
True random number generator
CRC calculation unit, 96-bit unique ID
Development support: serial wire debug (SWD), JTAG, Embedded Trace Macrocell*
More information about STM32L433CC can be found here:
STM32L433CC on www.st.com_STM32L432 reference manual_.. zephyr:board-supported-hw::
.. note:: CAN feature requires a CAN transceiver.
The Cygnet board has 6 GPIO controllers. These controllers are responsible for pin muxing, input/output, pull-up, etc.
.. image:: img/cygnet-pinout.webp :align: center :alt: Cygnet Pinout
For more details please refer to Blues Cygnet User Manual_.
The Cygnet board System Clock could be driven by internal or external oscillator, as well as main PLL clock. By default System clock is driven by PLL clock at 80MHz, driven by 16MHz high speed internal oscillator.
The Cygnet board has 4 U(S)ARTs and 1 LPUART. The Zephyr console output is assigned to LPUART1. Default settings are 115200 8N1.
Programming and Debugging
The Cygnet board requires an ST-LINK embedded debug tool in order to be programmed and debugged.
Applications for the cygnet board configuration can be built and
flashed in the usual way (see :ref:build_an_application and
:ref:application_run for more details).
The board is configured to be flashed using west STM32CubeProgrammer_ runner,
so its :ref:installation <stm32cubeprog-flash-host-tools> is required.
Alternatively, OpenOCD or JLink can also be used to flash the board using
the --runner (or -r) option:
.. code-block:: console
$ west flash --runner openocd $ west flash --runner jlink
Connect the Cygnet to the ST-LINK debugger, then run a serial host program to connect with your Cygnet board.
.. code-block:: console
$ picocom /dev/ttyACM0 -b 115200
Now build and flash an application. Here is an example for
:zephyr:code-sample:hello_world.
.. zephyr-app-commands:: :zephyr-app: samples/hello_world :board: cygnet :goals: build flash
You should see the following message on the console:
.. code-block:: console
$ Hello World! cygnet
You can debug an application in the usual way. Here is an example for the
:zephyr:code-sample:hello_world application.
.. zephyr-app-commands:: :zephyr-app: samples/hello_world :board: cygnet :maybe-skip-config: :goals: debug
References
.. target-notes::
.. _Blues Cygnet website: https://www.blues.dev/
.. _Blues Cygnet User Manual: https://dev.blues.io/feather-mcus/cygnet/cygnet-introduction/
.. _STM32L433CC on www.st.com: https://www.st.com/en/microcontrollers-microprocessors/stm32l433cc.html
.. _STM32L432 reference manual: https://www.st.com/resource/en/reference_manual/dm00151940.pdf
.. _STM32CubeProgrammer: https://www.st.com/en/development-tools/stm32cubeprog.html