Difference: MecrispCubeKatydid (11 vs. 12)

Revision 122022-10-11 - PeterSchmid

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
%DASHBOARD{ section="banner"
Line: 7 to 7
  titlestyle="color:#F00000;" }%
Intro
Changed:
<
<		Unfortunately the STM32WB Feather Development Board is no longer available. But there is a very good substitute the Firefly designed by Tlera Corp. The pinout is very similar to Arduino UNO but with the size of an Arduino Nano. The GPIOs are very carefully selected. JTAG SWD is on the pin header too!
>
>		If you want a small BLE board with a QSPI NOR flash memory, a BMA400 low-power accelerometer and an STBC08 LiPo battery charger then this board could be the right board for you.

The Katydid Wearable BLE Sensor Board is designed by Tlera Corp. The GPIOs are very carefully selected. JTAG SWD is on the pin header too!

  Instant real-time programming with Forth.
Line: 20 to 22
 
Contents
Changed:
<
<
>
>
 

Features

Changed:
<
<
  • 61 KiB RAM dictionary
  • 384 KiB Flash dictionary
  • Forth as CMSIS-RTOS thread. CMSIS-RTOS API to use FreeRTOS within Forth.
  • Buffered terminal I/O (5 KiB buffer for UART Rx). Interrupt driven and RTOS aware, key and emit block the calling thread. USART1: D0 RX, D1 TX
  • USB-CDC for serial communication via USB. Redirect console I/O like cdc-emit, cdc-key
  • microSD and internal serial Flash mass storage for blocks and FAT filesystem.
  • Digital and analog pins
    • LEDs: LED1 (blue), Neopixel (D4, optional)
    • Digital port pins: D0 to D5 (some ports are shared)
    • Analog port pins: A0 to A2 (can also be used as digital port pins D16 to D20)
    • PWM: D0 (TIM1CH3), D1 (TIM1CH2), A4 (TIM1CH1)
    • Input capture A1 (TIM2CH2)
    • Output compare D13=13 (TIM2CH1), A2=18 (TIM2CH3), A3=19 (TIM1CH4)
    • EXTI: D2, D4, D7, and D10
  • UART: D0 RX, D1 TX
  • SPI: D11 SCK, D12 MISO, D13 MOSI (e.g. for display, memory, CS for SD-Card is D10)
  • I2C: D14 SDA, D15 SCL (external peripherals e.g. pressure sensor, OLED)
  • vi Editor origin in BusyBox tiny vi. Workflow development: begin Edit EVALUATE while SaveFile repeat
  • Real Time Clock (32 bit UNIX time stamp, valid times are from 1.1.2000 to 31.12.2099 because of the STM32WB RTC peripheral) time!, time@, and .time (YYYY-MM-DDTHH:MM:SS ISO 8601).

>
>		The standard Mecrisp-Cube features like RTOS, Filesystem, USB, etc.
 
Changed:
<
<
>
>
  For more BSP details see BoardSupportPackageKatydid.
Line: 69 to 46
 

Prerequisites

Changed:
<
<
  • STM32WB Feather Development Board Stackable Feather board with STM32WB55 MCU (Cortex ARM M4) runs at a 32 MHz (the Bluetooth stack runs on a Cortex ARM M0+ core). If you want to debug C and assembler programs you need an ST-Link debugger/programmer.
>
>
  • Katydid Wearable BLE Sensor Board with STM32WB55 MCU (Cortex ARM M4) runs at a 32 MHz (the Bluetooth stack runs on a Cortex ARM M0+ core). If you want to debug C and assembler programs you need an ST-Link debugger/programmer.
 
  • Terminal emulator application for PC, e.g.:
Line: 77 to 54
 
    • minicom, microcom, screen - Linux
    • Use the built in Eclipse console (but no LF)

Changed:
<
<		Flash the Mecrisp-Cube binary (MecrispCubeKatydid.bin) or the util-binary (MecrispCubeUtil.bin, everything included e.g. internal flash drive and Forth tools) to the Katydid Board.
>
>		Flash the Mecrisp-Cube binary (MecrispCubeKatydid.bin) or the util-binary (MecrispCubeKatydidUtil.bin, everything included e.g. internal flash drive and Forth tools) to the Katydid Board.
 
  1. Connect the Katydid Board USB to the PC
  2. Hold the BTN button (BOOTP Pin), push the nRST button, release the nRST button
Changed:
<
<
  1. Program the binary (MecrispCubeKatydid.bin or MecrispCubeUtil.bin) with the STMCubeProgrammer (select USB Device)
>
>
  1. Program the binary (MecrispCubeKatydid.bin or MecrispCubeKatydidUtil.bin) with the STMCubeProgrammer (select USB Device)
 
  1. Reset or power cycle the Katydid board

Start the terminal emulator application on the PC.

Line: 98 to 75
 
Mecrisp-Stellaris RA 2.5.4 by Matthias Koch.
Changed:
<
<		Mecrisp-Cube 1.4.5 for STM32WB Nucleo, 63/128 KiB RAM/FLASH dictionary (C) 2022 peter@spyr.ch
>
>		Mecrisp-Cube 1.4.5 for STM32WB Katydid, 63/384 KiB RAM/FLASH dictionary (C) 2022 peter@spyr.ch
  * Firmware Package STM32Cube FW_WB V1.14.1, USB-CDC, BLE Stack 5.3 (C) 2022 STMicroelectronics * CMSIS-RTOS V2 FreeRTOS wrapper, FreeRTOS Kernel V10.3.1 (C) 2020 Amazon.com * FatFs for internal flash and microSD - Generic FAT fs module R0.12c (C) 2017 ChaN
Line: 151 to 128
  ok.
Changed:
<
<		The Mecrisp have some tools bundled in its distribution e.g. assembler, disassembler, dump, float. I put those tools and some more into the folder /fsr. With the "init.fs script" I compile my favorite ones into the flash directory (if you use the util-binary binary, these tools are already compiled in):
>
>		The Mecrisp have some tools bundled in its distribution e.g. assembler, disassembler, dump, float. I put those tools and some more into the folder /fsr. With the "init.fs script" I compile my favorite ones into the flash directory (if you use the util-binary binary, these tools are already compiled in):
 
compiletoflash[CR]  ok.
include /etc/init.fs[CR]
Line: 186 to 163
 
Changed:
<
<

Installing

>
>

Installing Development Environment

  A step by step series of examples that tell you how to get a development env running
Line: 228 to 209
 {list of changed files} $ git restore {files to restore}
Changed:
<
<		or instead of git restore 
$ git stash
$ git stash drop
>
>
  Select the Build Configuration (Debug if you want to debug the project) and Build the project:
View topic | History: r22 < r21 < r20 < r19 | More topic actions...
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback