Difference: BoardSupportPackageKatydid (41 vs. 42)

Revision 422022-10-11 - PeterSchmid

Line: 1 to 1

META TOPICPARENT	name="WebHome"

%DASHBOARD{ section="banner"

Changed:

<
<

image="/twiki/pub/MecrispCube/MecrispCubeFirefly/header.jpg"

>
>

image="/twiki/pub/MecrispCube/MecrispCubeKatydid/header.jpg"

title="Board Support Package for the Katydid Wearable BLE Sensor Board" titlestyle="color:#F00000;" }%

Intro

Changed:

<
<

The board support package for the STM32WB Firefly Development Board is restricted to the Arduino UNO R3 pin header and the onboard LED and switch (button). The STM32 has much more capabilities then 16 digital I/O pins, 5 analog input pins, UART, SPI, and I2C interfaces. But if you want to use the more advanced features you can use the CubeMX to create source code for the internal peripherals. This project wants to show how to use the Cube Ecosystem for a Forth system (or vice versa) and can't implement all features and possibilities the STM32WB has. It is a good starting point for your project.

>
>

The board support package for the STM32WB Katydid Wearable BLE Sensor Board is restricted to the xx pins, the QSPI flash and the onboard LED and switch (button). The STM32 has much more capabilities then ?? digital I/O pins, ?? analog input pins, UART, SPI, and I2C interfaces. But if you want to use the more advanced features you can use the CubeMX to create source code for the internal peripherals. This project wants to show how to use the Cube Ecosystem for a Forth system (or vice versa) and can't implement all features and possibilities the STM32WB has. It is a good starting point for your project.

Contents

View topic | History: r46 < r45 < r44 < r43 | More topic actions...