Difference: WebHome (158 vs. 159)

Revision 1592022-06-19 - PeterSchmid

 %DASHBOARD{ section="banner"
 image="/twiki/pub/Cosmac/ForthSTM32WB/nucleo-header.jpg"
 C & Forth in the 21st Century. C and Forth are both about 50 years old. To combine the strength of this two worlds results in a powerful system that outperforms other much newer systems like Python. Good design withstands the test of time.
-<
<
+The goal of Mecrisp-Cube is to be a complete Forth programming environment for STM32 MCUs.
->
>
+The goal of Mecrisp-Cube is to be a complete Forth programming environment for STM32 MCUs. There are three flavors available:
-<
<
+Sources on GitHub.
 

 MecrispCubeWB for the STM's STM32WB55 Nucleo Board and dongle and a variant for the ST32WB Feather Dev Board.
->
>
+ MecrispCubeWB (BLE) for the STM32WB55 Nucleo Board and dongle and a variant for the ST32WB Feather Dev Board.
  MecrispCubeF405 for Adafruit's Feather STM32F405.
-<
<
+ MecrispCubeH74x for STM NUCLEO-H743ZI and Arduino Portenta H7 Development Board.
->
>
+ MecrispCubeH74x for STM NUCLEO-H743ZI and Arduino Portenta H7 Development Board.
->
>
+Sources on GitHub.
 See ForthSTM32WB for standard Mecrisp-Stellaris for the STM32WB.
   Features 
  Already done  
  Integration in STM32 Cube Ecosystem
   RTOS
   USB Device
   Filesystem
   Board Support Package (BSP)
   BLE
   Floating-Point Unit
   External Peripherals (e.g. Feather Wings)
   Documentation
 
   Planned 
 
   Built With
   21st Century Forth 
  What's good about Forth
   What's bad about Forth
   What 21st Century Forth should be
   What Forth needs
   21st Century Forth desires and vision
   Forth 2012
 
   Copyright 
  Authors
   License
   Acknowledgments
-<
<
+ USB, BLE (for STM32WB55) and other Middlewares
->
>
+ Features 

USB, BLE (for STM32WB55) and other Middlewares
-<
<
+STM32 Forth without BLE, USB, Filesystems, RTOS etc. is not complete, to build this in Forth by myself from the scratch overwhelms me. I would like to go the reverse way and use the STM tools like CubeIDE, HAL, CubeMX and integrate the Mecrips Forth into it. Forth as an interactive extension for the STM32 ecosystem. Mecrisp Forth running as a CMSIS-RTOS thread.
->
>
+STM32 Forth without BLE, USB, Filesystems, RTOS etc. is not complete, to build this in Forth by myself from the scratch overwhelms me. I would like to go the reverse way and use the STM tools like CubeIDE, HAL, CubeMX and integrate the Mecrisp-Cube Forth into it. Forth as an interactive extension for the STM32 ecosystem. Mecrisp-Cube Forth is running as a CMSIS-RTOS thread.
-<
<
+Already done  
 Integrated in STM32 Cube ecosystem. Create C code from CubeMX for internal peripherals and use it in Forth.
  Forth as CMSIS-RTOS thread. CMSIS-RTOS API to use FreeRTOS from Forth.
->
>
+ Already done  

 Integration in STM32 Cube Ecosystem 
 
 Integrated in STM32 Cube ecosystem. 
  Create C code from CubeMX for internal peripherals and use it in Forth.
  Calling C Functions from Forth and vice versa 
 

 RTOS 
 
 Forth as CMSIS-RTOS thread. 
  CMSIS-RTOS API to use FreeRTOS from Forth.
  Buffered terminal I/O (5 KiB buffer for UART Rx). Interrupt driven and RTOS aware, key and emit block the calling thread.
->
>
+ USB
  USB-CDC for serial communication via USB. Redirect console I/O like cdc-emit, cdc-key
->
>
+ Filesystem
  microSD and internal Flash mass storage for blocks and FAT filesystem. 
 Filesystem API
  UNIX like Shell commands
-<
<
+ Calling C Functions from Forth and vice versa
  vi Editor origin in BusyBox tiny vi. Workflow development: begin Edit EVALUATE while SaveFile repeat
-<
<
+ Board Support Packages (BSPs): Nucleo STM32WB55, STM32WB5MM Discovery Kit, STM32WB Feather development board, Adafruit Feather STM32F405, NUCLEO-H743ZI, and Arduino Portenta H7
->
>
+ Board Support Package (BSP)
  Onboard LEDs: LED1 (blue), LED2 (green), LED3 (red)
  Switches: SW1, SW2, SW3 
  Digital port pins: D0 to D15
  Watchdog
  Assertation and Logging
->
>
+ BSPs 
 Nucleo STM32WB55
  STM32WB5MM Discovery Kit
  STM32WB Feather development board
  Adafruit Feather STM32F405
  NUCLEO-H743ZI
  Arduino Portenta H7
 
 

 BLE
  BLE 5.0 GAP Peripheral Role (STM32WB) 
 DIS Device Information Service
  HRS Heart Rate Service (heart rate depends on A0 for Nucleo and A2 for Dongle)
  CRS Cable Replacement Server service (proprietary service from STM, similar to Classic Bluetooth SPP). Redirect console I/O like crs-emit, crs-key.
->
>
+ External Peripherals (e.g. Feather Wings)
  OLED Display 128x32, 128x64, I2C
  NeoPixel
->
>
+ Documentation
  Markdown manual pages
-<
<
+Planned
->
>
+ Planned
  USB-MSC to read and write blocks or files from a host computer UsbCompositeMscCdc. 
  Command line editing like Gforth  no longer needed, see EditorVi
  Support for the floating point unit, CMSIS-DSP

View topic | History: r178 < r177 < r176 < r175 | More topic actions...