USB, BLE and other Middlewares

STM32WB Forth without BLE, USB, Filesystems, RTOS etc. is not complete, to build this 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 STM ecosystem. Mecrisp Forth running as a CMSIS-RTOS thread.

Already done

• Integrated in Cube ecosystem
• Forth as CMSIS-RTOS thread
• Buffered console IO (20 KiB for UART Rx)
• USB-CDC for serial communication. Redirect console IO like usb_emit, usb_key
• Board Support Package BSP
  • LEDs
  • switches
• Using RTOS from Forth

Planned

• BSP
  • Digital port pins D0 to D15
  • Analog port pins A0 to A5
  • PWM
  • I2C
• USB-MSC to make it possible to read and write blocks or include source files. INCLUDE vs BLOCK? Forth source files
• Command line editing like Gforth
• BLE 5.0
  • BLE vSP profile is proprietary, there is no standard serial communication profile. Redirect console IO like ble_emit, ble_key
  • BLE Event driven programming like LAIRD's smartBASIC, WAITEVENT ONEVENT.
  • BLE GATT (Characteristics, Services, Profiles)
• Watchdog
• Low power
• Calling HAL and other C functions
• Calling forth words form C (crawling through the dictionary)
• Support for the floating point unit, CMSIS-DSP
• UML state machine (extended state machine, hierarchically nested states)

• https://stackoverflow.com/questions/8422287/how-to-call-c-functions-from-arm-assembly
• https://static.docs.arm.com/ihi0042/g/aapcs32.pdf