Stm32World Wiki - Recent changes [en]

Colibri Zephyr

Niclas — Mon, 20 Apr 2026 11:15:27 GMT

Setting up Zephyr

File:Colibri Architecture-1.svg

Niclas — Mon, 20 Apr 2026 04:37:22 GMT

Niclas uploaded a new version of File:Colibri Architecture-1.svg

New page

== Summary ==
One architectural conceptual view of the Colibri system.

File:Colibri Architecture-1.svg

Niclas — Mon, 20 Apr 2026 01:04:38 GMT

Niclas uploaded a new version of File:Colibri Architecture-1.svg

New page

== Summary ==
One architectural conceptual view of the Colibri system.

File:Colibri Architecture-1.svg

Niclas — Sun, 19 Apr 2026 23:53:24 GMT

Niclas uploaded a new version of File:Colibri Architecture-1.svg

New page

== Summary ==
One architectural conceptual view of the Colibri system.

Colibri

Niclas — Sun, 19 Apr 2026 16:00:13 GMT

Architecture Overview

File:Colibri Architecture-1.svg

Niclas — Sun, 19 Apr 2026 15:57:57 GMT

Niclas uploaded a new version of File:Colibri Architecture-1.svg

New page

== Summary ==
One architectural conceptual view of the Colibri system.

File:Colibri Architecture-1.svg

Niclas — Sun, 19 Apr 2026 15:56:43 GMT

Niclas uploaded File:Colibri Architecture-1.svg One architectural conceptual view of the Colibri system.

New page

== Summary ==
One architectural conceptual view of the Colibri system.

Streamline MCU STM32C511

Lth — Sun, 19 Apr 2026 12:14:36 GMT

STM32C511

Lth — Sun, 19 Apr 2026 12:11:32 GMT

Created page with "Category:STM32{{metadesc|STM32C511 MCU}} == Miscellaneous Links == * [https://stm32world.com/images/9/9f/Stm32c551ve.pdf STM32C511 Datasheet]"

New page

[[Category:STM32]]{{metadesc|STM32C511 MCU}}
== Miscellaneous Links ==

* [https://stm32world.com/images/9/9f/Stm32c551ve.pdf STM32C511 Datasheet]

Streamline MCU STM32C511

Lth — Sun, 19 Apr 2026 12:10:48 GMT

Streamline

Lth — Sun, 19 Apr 2026 12:02:57 GMT

STM32

Streamline MCU STM32C511

Lth — Sun, 19 Apr 2026 11:59:31 GMT

File:Sl mcu stm32c551.svg

Lth — Sun, 19 Apr 2026 11:58:24 GMT

Lth uploaded File:Sl mcu stm32c551.svg File uploaded with MsUpload

New page

File uploaded with MsUpload

File:Sl mcu stm32c551 bot render.png

Lth — Sun, 19 Apr 2026 11:58:18 GMT

Lth uploaded File:Sl mcu stm32c551 bot render.png File uploaded with MsUpload

New page

File uploaded with MsUpload

File:Sl mcu stm32c551 top left render.png

Lth — Sun, 19 Apr 2026 11:58:17 GMT

Lth uploaded File:Sl mcu stm32c551 top left render.png File uploaded with MsUpload

New page

File uploaded with MsUpload

File:Sl mcu stm32c551 top render.png

Lth — Sun, 19 Apr 2026 11:58:16 GMT

Lth uploaded File:Sl mcu stm32c551 top render.png File uploaded with MsUpload

New page

File uploaded with MsUpload

File:Sl mcu stm32c551 top right render.png

Lth — Sun, 19 Apr 2026 11:58:14 GMT

Lth uploaded File:Sl mcu stm32c551 top right render.png File uploaded with MsUpload

New page

File uploaded with MsUpload

Streamline MCU STM32C511

Lth — Sun, 19 Apr 2026 11:57:01 GMT

Created page with "Category:STM32 Category:Streamline Category:Streamline Blade{{metadesc|STM32C511 Streamline MCU board documentation}} File:Sl mcu stm32f407 top right.jpg|350px|thu..."

New page

[[Category:STM32]][[Category:Streamline]][[Category:Streamline Blade]]{{metadesc|STM32C511 Streamline MCU board documentation}}
[[File:Sl mcu stm32f407 top right.jpg|350px|thumb|Streamline MCU STM32F407]]
The [[Streamline MCU STM32C511]] is a basic [[Streamline]] [[STM32]] [[MCU]] board build around a [[STM32C511]].
{{clear}}

The Journey starts towards Free and Open PLCs

Lth — Sat, 18 Apr 2026 05:46:53 GMT

Created page with "{{Video |series=Colibri Video |number=3 |title=The Journey starts towards Free and Open PLCs |youtube-id=5KDnvAnH8x8 |description=In this episode, we start programming the Col..."

New page

{{Video
|series=Colibri Video
|number=3
|title=The Journey starts towards Free and Open PLCs
|youtube-id=5KDnvAnH8x8
|description=In this episode, we start programming the Colibri at firmware level. We will look at the I2C multiplexor and the MCU3, which contains a STM32F405RG, with a dual-color LED.
}}

Colibri MCU3

Niclas — Fri, 17 Apr 2026 04:55:00 GMT

Colibri

Niclas — Fri, 17 Apr 2026 01:44:36 GMT

Programming

Colibri MCU5

Niclas — Fri, 17 Apr 2026 01:20:33 GMT

Programming

Colibri MCU2

Niclas — Fri, 17 Apr 2026 01:19:55 GMT

Programming

Colibri MCU4

Niclas — Fri, 17 Apr 2026 01:19:37 GMT

Programming

Colibri MCU2

Niclas — Fri, 17 Apr 2026 01:19:04 GMT

Programming

Colibri MCU3

Niclas — Fri, 17 Apr 2026 01:16:42 GMT

C/C++

Colibri 3a

Niclas — Fri, 17 Apr 2026 01:13:14 GMT

MCU slot

Colibri 8

Niclas — Fri, 17 Apr 2026 01:11:08 GMT

MCU slot

File:Colibri 8-IO Expansion-X1.svg

Niclas — Fri, 17 Apr 2026 00:52:45 GMT

Niclas uploaded File:Colibri 8-IO Expansion-X1.svg Schematics of the I/O slot on Colibri 8. This is repeated 7 times.

New page

== Summary ==
Schematics of the I/O slot on Colibri 8. This is repeated 7 times.

File:Colibri 8-IO Expansion.svg

Niclas — Fri, 17 Apr 2026 00:51:35 GMT

Niclas uploaded File:Colibri 8-IO Expansion.svg Schematics of the I/O subsystem on Colibri 8

New page

== Summary ==
Schematics of the I/O subsystem on Colibri 8

← Older revision		Revision as of 11:15, 20 April 2026
(3 intermediate revisions by the same user not shown)
Line 26:		Line 26:

	Additionally to task scheduling, we also get '''cross-platform APIs for SPI and I2C peripherals''', as well as access to many Zephyr libraries, such as '''Modbus/RTU, TCP/IP, MQTT''' and much more.		Additionally to task scheduling, we also get '''cross-platform APIs for SPI and I2C peripherals''', as well as access to many Zephyr libraries, such as '''Modbus/RTU, TCP/IP, MQTT''' and much more.
		+
		+	= Supported Boards =
		+	* [[Streamline MCU STM32F407]]
		+	* [[Colibri MCU3]]
		+	* [[Colibri 3a]]
		+	* [[Colibri 8]]
		+
		+	= Colibri Integration =
		+	Colibri carrier boards and Colibri MCU modules are being integrated with Zephyr.
		+
		+
		+	= Setting up Zephyr =
		+	Follow the installation instructions on [https://docs.zephyrproject.org/latest/develop/getting_started/index.html Zephyr's Getting Started documentation].
		+
		+	You will end up with a <code>${HOME}/zephyrproject</code> directory. If you chose to place that elsewhere, the instructions below must be adjusted.
		+
		+	Check out [https://github.com/currentmakers/zephyr-cm https://github.com/currentmakers/zephyr-cm]
		+
		+	Create a <code>${HOME}/.zephyrrc</code> with the following content;
		+	export ZEPHYR_BASE=${HOME}/zephyrproject/zephyr/ # Maybe change this
		+	export ZEPHYR_EXTRA_MODULES=${HOME}/dev/currentmakers/zephyr-cm # <--- CHANGE THIS
		+
		+	Create a file <code>init-zephyr</code> and place somewhere you easily remember how to access it. Let's assume it is in <code>${HOME}</code>. Following content;
		+	export ZEPHYR_BASE=${HOME}/zephyrproject/zephyr
		+	source ${ZEPHYR_BASE}/../.venv/bin/activate
		+	source ${ZEPHYR_BASE}/zephyr-env.sh
		+
		+	= Developing with Zephyr =
		+
		+	After opening the terminal to compile, remember to run
		+	. ${HOME}/init-zephyr
		+	to enable the Python environment and set up the paths.
		+
		+	For any given Zephyr project, for instance the ones in [https://github.com/currentmakers/zephyr-examples] you build like this
		+
		+	west build -b colibri_mcu3 -- -DSHIELD=colibri_8
		+
		+	and the <code>.elf</code> and <code>.bin</code> output files are in <code>build/zephyr</code> and can be flashed as usual with
		+
		+	st-flash --connect-under-reset write build/zephyr/zephyr.bin 0x8000000
		+
		+	(I have seen the <code>st-flash</code> failed to access without the <code>connect-under-reset</code>.)

@@ Line 25: / Line 25: @@
 * Each I/O module has an 1Mbit EEPROM with calibration parameters and a WebAssembly program for the MCU module to execute.
 * Some I/O modules have on-board secondary processors for time-critical or other reasons, for instance RS-485 communication, digital inputs (pulse counting) and PID regulator.
 == Programming ==

@@ Line 3: / Line 3: @@
 The [[Streamline MCU STM32C511]] is a basic [[Streamline]] [[STM32]] [[MCU]] board build around a [[STM32C511]].
 {{clear}}
 == Schematics ==
@@ Line 18: / Line 39: @@
 File:sl_mcu_stm32c551_bot_render.png
 </gallery>

@@ Line 94: / Line 94: @@
 | Streamline MCU board including a [[STM32L475]]
 | [https://currentmakers.com/products/streamline/streamline_mcu_stm32l475/ Available]
 |}

← Older revision		Revision as of 11:59, 19 April 2026
Line 3:		Line 3:
	The [[Streamline MCU STM32C511]] is a basic [[Streamline]] [[STM32]] [[MCU]] board build around a [[STM32C511]].		The [[Streamline MCU STM32C511]] is a basic [[Streamline]] [[STM32]] [[MCU]] board build around a [[STM32C511]].
	{{clear}}		{{clear}}
		+
		+	== Schematics ==
		+
		+	<div class="res-img">
		+	[[File:sl_mcu_stm32c551.svg\|2400px]]
		+	</div>
		+
		+	== Gallery ==
		+
		+	<gallery>
		+	File:sl_mcu_stm32c551_top_right_render.png
		+	File:sl_mcu_stm32c551_top_render.png
		+	File:sl_mcu_stm32c551_top_left_render.png
		+	File:sl_mcu_stm32c551_bot_render.png
		+	</gallery>

@@ Line 1: / Line 1: @@
 [[Category:STM32]][[Category:Streamline]][[Category:Streamline Blade]]{{metadesc|STM32C511 Streamline MCU board documentation}}
-[[File:Sl mcu stm32f407 top right.jpg|350px|thumb|Streamline MCU STM32F407]]
+[[File:sl_mcu_stm32c551_top_right_render.png|350px|thumb|Streamline MCU STM32C511 (render)]]
 The [[Streamline MCU STM32C511]] is a basic [[Streamline]] [[STM32]] [[MCU]] board build around a [[STM32C511]].
 {{clear}}

@@ Line 10: / Line 10: @@
 The MCU3 is a relatively simple MCU module, on an M.2 board with the size 22x42mm and the Key E configuration.
-Besides the [[STM32F405|STM32F405RE]] MCU there are also
+Besides the [[STM32F405|STM32F405RG]] MCU there are also
 * 128 Mbits (16MB) flash memory for application use.
 * a dual-colored (Green/Red) LED

@@ Line 23: / Line 23: @@
 * Each I/O slot is addressable individually.
 * MCU communicates with each I/O slot via I2C and/or SPI. The I2C bus is multiplexed to avoid address collision. SPI uses one Chip Select per I/O slot and 2 additional Chip Select if multi SPI devices are on a single I/O module.
-* Each I/O module has an 1Mbit EEPROM with calibration parameters and a Forth program for the MCU module.
+* Each I/O module has an 1Mbit EEPROM with calibration parameters and a WebAssembly program for the MCU module to execute.
 * Some I/O modules have on-board secondary processors for time-critical or other reasons, for instance RS-485 communication, digital inputs (pulse counting) and PID regulator.
 == Carrier Boards ==
@@ Line 39: / Line 52: @@
 * ''[[Colibri MCU3]]'' - MCU module with a STM32F405RG, 1MB Flash, 192kB+4kB RAM and a 16MB external flash memory.
 * ''[[Colibri MCU4]]'' - MCU module with a STM32L475RG, 1MB Flash, 128kB RAM and a 16MB external flash memory.
-* ''[[Colibri MCU5]]'' - MCU module with a RP2354B, 2MB Flash, 192kB+4kB RAM and a 16MB external flash memory.
+* ''[[Colibri MCU5]]'' - (deprecated) MCU module with a STM32F103RE, 512kB Flash and 64kB RAM. No external flash memory.
 == I/O Modules ==
-The Colibri system is based around the M.2 connector and a non-standard bus for I2C and SPI communications. Each I/O module has an EEPROM memory available to identify which module is present in each I/O slot. Furthermore, there is a ''[[zeptoforth]]'' program located in the EEPROM that contains the functionality of the module, executed in the MCU module. This allows for future I/O modules without requiring the upgrade of the MCU module. You might want to use other [[Colibri Programming Languages]], if Forth does not suit your needs.
+The Colibri system is based around the M.2 connector and a non-standard bus for I2C and SPI communications. Each I/O module has an [[Colibri_EEPROM_Layout|EEPROM memory]] available to identify which module is present in each I/O slot, links to documentation, calibration parameters, testing results and (up to) 16kB of WebAssembly for the MCU module to execute.
 == [[Colibri Form Factor|Form Factor]] ==
@@ Line 97: / Line 109: @@
 | Prototyping
 |-
-| ''[[Colibri MCU5]]''
+| ''[[Colibri MCU6]]''
 | Host MCU
 | MCU module with a Raspberry Pi RP2354B and a 16MB flash memory.

@@ Line 6: / Line 6: @@
 = Programming =
 == C/C++ ==
 == Zephyr ==

@@ Line 3: / Line 3: @@
 = Programming =
-STM32CubeMX file [[Media:Mcu2.ioc|MCU2.ioc template file]] for Colibri carrier boards. (Right-click, "Save link as..." on the link)
+STM32CubeMX file [[Media:Mcu2.ioc|mcu2.ioc template file]] for Colibri carrier boards. (Right-click, "Save link as..." on the link)
 == Low Level ==

← Older revision		Revision as of 01:19, 17 April 2026
Line 4:		Line 4:

	= Programming =		= Programming =
		+	STM32CubeMX file [[Media:Mcu4.ioc\|mcu4.ioc template file]] for Colibri carrier boards. (Right-click, "Save link as..." on the link)

	== Low Level ==		== Low Level ==

← Older revision		Revision as of 01:19, 17 April 2026
(One intermediate revision by the same user not shown)
Line 3:		Line 3:

	= Programming =		= Programming =
		+	STM32CubeMX file [[Media:Mcu2.ioc\|MCU2.ioc template file]] for Colibri carrier boards. (Right-click, "Save link as..." on the link)

	== Low Level ==		== Low Level ==

@@ Line 17: / Line 17: @@
 * I2C bus and I2C Mux
 * 16MB flash memory
-* 128kB EEPROM memory on carrier board
+* 128kB EEPROM memory
 == I/O module slots ==
@@ Line 30: / Line 30: @@
 that I/O slot's I2C bus. I2C bus 0 is the ''Colibri 3a'' carrier board itself, i.e. to the EEPROM. It is important that only one I2C
 bus is enable at a time.
 == SPI communications ==

@@ Line 17: / Line 17: @@
 * Galvanically Isolated RS-485 port, for SCADA and other supervisory systems.
 * 16MB flash memory
-* 128kB EEPROM memory on carrier board
+* 128kB EEPROM memory
 * Temperature and Humidity sensor
 == I/O module slots ==
 There are seven I/O module slots on this carrier board. Most I/O modules can be used, but there are I/O modules that
-will depend on the power supply, for instance [[Colibri Triac1]] will only work if the ''Colibri 3a'' are powered by an AC source.
+will depend on the power supply, for instance [[Colibri Triac1]] will only work if the ''Colibri 8'' are powered by an AC source.
-Also [[Colibri DIO1]] must NOT be used on systems with AC power supply.
+Also [[Colibri DIO1]] must '''NOT''' be used on systems with AC power supply.
 == I2C communications ==
@@ Line 29: / Line 29: @@
 The multiplexer is a TCA9548APWR on address 0x70 (0b1110000x), and each bit in the "data byte" written to the multiplexer will enable
-that I/O slot's I2C bus. I2C bus 0 is the ''Colibri 3a'' carrier board itself, i.e. to the EEPROM. It is important that only one I2C
+that I/O slot's I2C bus. I2C bus 0 is the ''Colibri 8'' carrier board itself, i.e. to the EEPROM. It is important that only one I2C
 bus is enable at a time.
@@ Line 39: / Line 39: @@
 == I/O slot power ==
-Each I/O slot has +3.3V, +5V and +12V available on the connector. On the ''Colibri 3a'' the power for +3.3V and +5V can be turned on/off
+Each I/O slot has +3.3V, +5V and +12V available on the connector. On the ''Colibri 8'' the power for +3.3V and +5V can be turned on/off
 individually by the MCU, meaning the MCU can for instance turn off the +5V on X2, for instance to re-initialize some circuit.
-Additionally, the external power that is used to power the ''Colibri 3a'' device is also available on the I/O slot header. This is how some
+Additionally, the external power that is used to power the ''Colibri 8'' device is also available on the I/O slot header. This is how some
-I/O modules become dependent on the type of power that drives the ''Colibri 3a'', for instance the [[Colibri DIO1]] that will malfunction and
+I/O modules become dependent on the type of power that drives the ''Colibri 8'', for instance the [[Colibri DIO1]] that will malfunction and
 possibly break if AC voltage is used.
@@ Line 60: / Line 60: @@
 = I2C Addresses =
    TCA9548 = 0x70    ; Selects which I/O slot the I2C should be connected to.
 = Architecture =
@@ Line 67: / Line 71: @@
 <div class="res-img">
 [[File:Colibri_8-rev_A-schematics1.svg|2400px]]
 [[File:Colibri_8-Power Supply.svg|2400px]]
 [[File:Colibri 8-IO Expansion-LEDs.svg|2400px]]