Stm32World Wiki - Recent changes [en]

Colibri WebAssembly Notes

Niclas — Wed, 06 May 2026 08:42:00 GMT

Zephyr Mutexes

Colibri WebAssembly Notes

Niclas — Wed, 06 May 2026 04:54:38 GMT

Created page with "Various notes, investigations and other useful information that might be needed later. = Meory Allocations = This was an investigation into how much RAM is used to instantia..."

New page

Various notes, investigations and other useful information that might be needed later.

= Meory Allocations =
This was an investigation into how much RAM is used to instantiate WebAssembly runtimes. 8 wasm files were deployed, each blinking the LED for the respective slot.

---- Program to be loaded ----

#include "colibri.h"
#define export __attribute__((visibility("default")))

static int next = 0;
static int state = 0;

int tick(long time) {
if (next < time) {
if (state){
set_rgb_error();
next = time + 100;
}
else {
set_rgb_off();
next = time + 500;
}
}
return state;
}

export void event(int id, long value) {
tick(value);
}

export void init() {
set_rgb_ok_color(0x000400);
set_rgb_warning_color(0x040400);
set_rgb_error_color(0x080000);
}

export void loaded() {
set_rgb_off();
}

export void unloading() {
set_rgb_off();
}

Env Heap @ 0x10000000 112 bytes
wasm0 Heap @ 0x10000070 4960 bytes
wasm1 Heap @ 0x100013D0 4368 bytes
wasm2 Heap @ 0x100024E0 4368 bytes
wasm3 Heap @ 0x100035f0 4368 bytes
wasm4 Heap @ 0x10004700 4608 bytes
wasm5 Heap @ 0x10005900 4368 bytes
wasm6 Heap @ 0x10006a10 4368 bytes
wasm7 Heap @ 0x10007b20 5200 bytes
End Heap @ 0x10008F70

----- Once -----
NewEnvironment
M3Environment struct 0x20
AllocFuncType 0x09
AllocFuncType 0x09
AllocFuncType 0x09
AllocFuncType 0x09
AllocFuncType 0x09

----- Per wasm ---

NewRuntime
M3Runtime struct 0x434
runtime->origStack 0x410 (stack + 4 32bit words)

ParseModule
M3Module module 0x78
io_module->functTypes 0x0c
AllocFuncType 0x08
Free
AllocFuncType 0x09
Free
AllocFuncType 0x0A
Free
PreAllocFunctions 0x154 (5 functions * 68 bytes?)
"env" 0x04
"memory" 0x07
Free NULL (freeing import, module name)
Free NULL (freeing import, field name)
"env" 0x04
"set_rgb_off" 0x0C
Free NULL (freeing import, module name)
Free NULL (freeing import, field name)
"env" 0x04
"set_rgb_ok_color" 0x11
Free NULL (freeing import, module name)
Free NULL (freeing import, field name)
"env" 0x04
"set_rgb_warning_color" 0x16
Free NULL (freeing import, module name)
Free NULL (freeing import, field name)
"env" 0x04
"set_rgb_error_color" 0x14
Free NULL (freeing import, module name)
Free NULL (freeing import, field name)
Free NULL (freeing import, module name)
Free NULL (freeing import, field name)
PreAllocFunctions 0x220
AddGlobal 0x20
"event" 0x06 (exports)
Free NULL (exported name)
"init" 0x05
Free NULL (exported name)
"loaded" 0x07
Free NULL (exported name)
"unloading" 0x0A
Free NULL (exported name)
Free NULL (one extra exported name)
M3DataSegments 0x20 (0 data segment)

LoadModule
NewCodePage 0x40
Free NULL
Free NULL
Free NULL
Free NULL
AllocFuncType 0x09
Free
AllocFuncType 0x09
Free
AllocFuncType 0x09
Free
AllocFuncType 0x09
Free
AllocFuncType 0x09
Free
NewCodePage 0x40
NewCodePage 0x40
NewCodePage 0x40
NewCodePage 0x40
CompileFunction 0x08 ("event")
NewCodePage 0x40
NewCodePage 0x40
NewCodePage 0x40
NewCodePage 0x40
CompileFunction 0x12 ("init")
NewCodePage 0x40
NewCodePage 0x40
NewCodePage 0x40
NewCodePage 0x40
NewCodePage 0x40
NewCodePage 0x40
NewCodePage 0x40
NewCodePage 0x40
NewCodePage 0x40
NewCodePage 0x40
NewCodePage 0x40
NewCodePage 0x40
NewCodePage 0x40
NewCodePage 0x40
NewCodePage 0x40
NewCodePage 0x40
CompileFunction 0x14

Colibri Runtime

Niclas — Wed, 06 May 2026 04:49:46 GMT

Created page with "The Colibri Runtime is the custom firmware that is running on Colibri MCUs, an application in Colibri Zephyr orchestrating the hardware resources, WebAssembly engines with..."

New page

The Colibri Runtime is the custom firmware that is running on Colibri MCUs, an application in [[Colibri Zephyr]] orchestrating the hardware resources, WebAssembly engines with I/O drivers and user programs.

== Development ==

[[Colibri WebAssembly Notes]]

Streamline Neopixel 8x8 Video

Lth — Tue, 05 May 2026 23:30:46 GMT

Created page with "{{Video |series=Streamline Video |number=7 |title=Streamline Neopixel 8x8 Video |youtube-id=JcWQyCiDzPE |description=Streamline Neopixel 8x8 - ws2812 blade. }}"

New page

{{Video
|series=Streamline Video
|number=7
|title=Streamline Neopixel 8x8 Video
|youtube-id=JcWQyCiDzPE
|description=Streamline Neopixel 8x8 - ws2812 blade.
}}

Streamline Connect

Lth — Tue, 05 May 2026 23:27:18 GMT

Schematics

STM32 Official Documentation

Lth — Tue, 05 May 2026 07:45:22 GMT

STM32C51x

Streamline MCU STM32C511

Lth — Mon, 04 May 2026 06:04:05 GMT

STM32C5 First Blink

Lth — Mon, 04 May 2026 05:32:13 GMT

STM32C5 First Blink

Lth — Mon, 04 May 2026 05:29:12 GMT

Created page with "{{Video |series=STM32 Tutorial Video |number=87 |title=HOWTO STM32C5 First Blink |youtube-id=C0ql2WqKzIE |description=First attempt to create a Blink application for the new S..."

New page

{{Video
|series=STM32 Tutorial Video
|number=87
|title=HOWTO STM32C5 First Blink
|youtube-id=C0ql2WqKzIE
|description=First attempt to create a Blink application for the new STM32C551 MCU.
}}

Hardware Interconnect Buses

Lth — Sun, 03 May 2026 00:22:15 GMT

File:Two Serial Ports.jpg

Lth — Sun, 03 May 2026 00:15:19 GMT

Lth uploaded File:Two Serial Ports.jpg File uploaded with MsUpload

New page

File uploaded with MsUpload

Hardware Interconnect Bus

Lth — Sat, 02 May 2026 23:54:48 GMT

Lth moved page Hardware Interconnect Bus to Hardware Interconnect Buses

New page

[[Category:Electronics]]{{metadesc|Documenting various forms of hardware interconnect}}
'''NOTICE!''' This page is a [[Category:Work in progress]] Work in progress

There are literally hundreds - if not thousands - of different specifications for communications between different devices. Most of these are probably proprietary but this page will document the most common on an introductory level.

== Speed ==

When it comes to any kind of communication, the speed is often expressed as "bps" (bits per second) or faster rates in "kbps" (kilobits per second), "Mbps" (Meta-bits per second) or even "Gbps" (Giga-bits per second). Soon we'll probably begin to see "Tbps" but I am not sure that is available as of yet.

It is worth noticing that, since a byte is 8 bits, you can often divide the bit-rate by 8 to get the Bytes per second). Often, however, there are a few extra bits stuffed in the protocol, start, stop, parity, so this calculation really depends on the protocol.

It should also be mentioned that in the early days the term "baud" was often used ([https://en.wikipedia.org/wiki/Baud Wikipedia article on baud]). Baud is defined as a symbol rate and is typically equivalent of the bit-rate. However, later generation modems could use various forms of encoding to transfer multiple bits in one symbol which is why the term is rarely seen today.

== Asynchronous vs. Synchronous ==

Serial communication exist in two different types. In synchronous communication, the data line(s) are combined with a clock signal that synchronize the devices together. In asynchronous communication there is no clock signal and the transmission speeds are "agreed upon". This require a fairly precise timing for both transmitters and receivers.

== Asynchronous ==

=== RS-232 ===
[[File:PDP-11-70.jpeg|thumb|300px|PDP-11 with a serial terminal in the center]]
RS-232 can be considered the granddad of [[Hardware Interconnect Bus]]es. It is a point-to-point bus which will connect exactly two devices with each other. RS-232 would operate at speeds from around 150 bps, through 300, 4800, 9600 and 19200 bps.

RS-232 was first introduced in 1960 and up through the 70s and even 80s it was widely used. Early computers (see image on the right) were monstrous and were often operated through multiple serial terminals. The communication between the central computer and those terminals were almost always (if not always) RS-232.

Early PC's always had at least one RS-232 port which was often used to attach a modem. Modems were common up until the late 90s and again - exclusively used RS-232.

[[File:RS-232_POTS_DTE_DCE.svg|450px]]

[[File:uart-tx-rx-cross-768x466.png|thumb|300px]]
Today, [[#RS-232|RS-232]] have all but vanished in consumer and professional equipment and is almost exclusively replaced by [[#USB|USB]]. The basic signalling are still commonly used for short distance communication.

These connections will typically operate and a voltage level depending on the actual equipment - typically either 3.3V or 5V.

[https://en.wikipedia.org/wiki/RS-232 Wikipedia article on RS-232]

{{clear}}

=== RS-422 / RS 423 ===
RS-422 and RS-423 are serial communication standards that work with differential voltages, rather than absolute voltage levels like RS-232, and using 2 twisted pairs. This means that much longer cables can be used and the data will not get corrupted on the way. These are rarely used nowadays, and have essentially been superseded by more modern communication systems, such as CAN and Ethernet. The RS-485 sibling has survived until present day, see below.

RS-422 is (i.e. was) the point-to-point variant, with full duplex in both directions. RS-423 is (i.e. was) the multi-drop variant, with one master that "owned" one pair and all the slaves shared the other pair, and higher level protocols would ensure that only one slave would respond at any given time.

[[File:RS-422_Network.svg|600px]]

[https://en.wikipedia.org/wiki/RS-422 Wikipedia article on RS-422]

=== RS-485 ===
Wikipedia claims that RS-485 was introduced in 1983. I think that is when it formalized as a standard (TIA-485/EIA-485), because I worked with RS-485 in 1984 with equipment that was way older than just 1 year. Modicon introduce Modbus in 1979, which was a serial protocol on top of RS-485. Nevertheless, RS-485 quickly became a favorite in industrial automation, and is still very popular, especially thanks to Modbus.

RS-485 was originally a single twisted pair, differential voltage interface with maximum 30 devices on one segment, something like ~1000 feet (~300 meters) and 1 Mbit/s maximum communication speed. This has been revised over the years, as silicon vendors have improved performance, and the current standard (1998 & 2012) has been updated to reflect this. Faster speeds, more devices and longer cables. Only in-the-field tests can determine the maximum cable lengths at a given speed.

Connecting an MCU to a RS-485 transceiver is very simple. The UART/USART Tx and Rx are connected to "D" (drive) and "R" (receive) pins on the transceiver chip. There are dozens (or more) RS-485 transceivers on the market, and most of the SOIC-8 variants, which are the majority, are pin compatible. Additionally, there are "RE" (receive enable) and "DE" (drive enable) on the transceivers, which the MCU needs to control. They are electrically inverted, so in most cases, we only need a single MCU pin for (direction) and it gos to both RE and DE.

[[File:RS-485_Network.png|800px]]

[https://en.wikipedia.org/wiki/RS-485 Wikipedia article on RS-485]

== {{I2C}} (Inter-Integrated Circuit) ==
[[File:I²C_bus_logo.svg|thumb|250px]]
{{I2C}} is a communication bus originally invented by Philips Semiconductors (now NXP) in 1980. Today, it is widely used for communication between [[MCU]]s and various peripheral devices.

Originally the speed was defined as 100 Kbps or 400 Kbps but faster options were possible and today a newer I3C option is emerging.

[[File:i2c_bus.svg|800px]]

An [[{{I2C}}]] bus typically consist of one master and multiple slaves. It ''is'' possible to have multiple masters but this is rarely seen "in the wild".

The two lines - CLK and SDA both operate in "open drain" mode so they need to be pulled up. The strength of the pull-up resistor depends on the distance. Typical values are less than 10 kOhm.

Due to the modern day sensitivities, some people frown on the use of master/slave and come up with modern "acceptable" terms, but this only ads confusion, so we will stick with the original terms.

[https://en.wikipedia.org/wiki/I2C Wikipedia article on {{I2C}}]
{{clear}}

== SPI (Serial Peripheral Interface) ==

An option, which is '''much''' faster, is SPI. SPI is a single master controlling the communication with one slave using one clock and two data lines:

[[File:SPI_8-bit_circular_transfer.svg|thumb|300px]]

[[File:SPI_single_slave.svg|600px]]

There is also a SS (slave select) line so the same bus can be shared with multiple slaves, but under normal circumstances only a single master.

[[File:SPI_three_slaves.svg|600px]]

A final option is to daisy chain multiple slaves using the same SS.

[[File:SPI_three_slaves_daisy_chained.svg|600px]]

There is no "upper limit" on speed - it depends on the capabilities of the master and slaves. Speeds in the Mbit range is common, even 10s of Mbit.

[https://en.wikipedia.org/wiki/Serial_Peripheral_Interface Wikipedia article on SPI]

{{clear}}

== CAN ==

The CAN bus was developed by Bosch in the early 1980s. It was designed to provide reliable communication in noisy environments and it is typically used in vehicles (cars, ships). It is a package oriented bus and do away with the concept of master and slave. Every device on the bus can transmit packages and every device will receive all those packages and individually must decide what to do with them.

Multiple CAN standards exist with different speed.

[[File:CAN_ISO11898-3_Network.png|600px]]

[https://en.wikipedia.org/wiki/CAN_bus Wikipedia article on CAN]

== USB ==
[[File:USB_icon.svg|thumb|200px]]
USB have today almost completely replaced the original RS-232 for device to device communication.

[https://en.wikipedia.org/wiki/USB Wikipedia article on USB]

{{clear}}

== Ethernet ==
[[File:PC_Network.svg|thumb|200px]]
To be added!

[https://en.wikipedia.org/wiki/Ethernet Wikipedia article on Ethernet]
{{clear}}

== Miscellaneous Links ==

* [https://en.wikipedia.org/wiki/Serial_communication Wikipedia article on Serial Communications]

Streamline Zephyr

Niclas — Sat, 02 May 2026 02:54:23 GMT

Category:RP2350

Lth — Fri, 01 May 2026 12:04:55 GMT

Created page with "RP2350 related pages"

New page

RP2350 related pages

Streamline MCU RP2354 First Test

Lth — Fri, 01 May 2026 12:04:03 GMT

Created page with "Category:Work in progress Category:Streamline Category:RP2350{{metadesc|First test on Streamline MCU RP2354}} To be added"

New page

[[Category:Work in progress]][[Category:Streamline]][[Category:RP2350]]{{metadesc|First test on Streamline MCU RP2354}}
To be added

Streamline Zephyr

Niclas — Fri, 01 May 2026 09:26:21 GMT

Installation

Streamline Zephyr

Lth — Fri, 01 May 2026 00:18:54 GMT

Streamline Zephyr

Niclas — Thu, 30 Apr 2026 11:57:19 GMT

Streamline Zephyr

Niclas — Thu, 30 Apr 2026 11:41:13 GMT

Created page with "Category:STM32 Category:Streamline Category:Streamline Software{{metadesc|Zephyr on Streamline boards}} = Installation = Let's see how we can easily setup a Zephyr..."

New page

[[Category:STM32]][[Category:Streamline]][[Category:Streamline Software]]{{metadesc|Zephyr on Streamline boards}}

= Installation =
Let's see how we can easily setup a Zephyr development environment for some Streamline demos.

sudo apt update
sudo apt upgrade
sudo apt install --no-install-recommends git cmake ninja-build gperf \
ccache dfu-util device-tree-compiler wget python3-dev python3-venv python3-tk \
xz-utils file make gcc gcc-multilib g++-multilib libsdl2-dev libmagic1 curl

mkdir streamline_demos
cd streamline_demos
python3 -m venv .venv
echo "export ZEPHYR_BASE=`pwd`/zephyr" >>.venv/bin/activate
echo "export ZEPHYR_TOOLCHAIN_VARIANT=zephyr" >>.venv/bin/activate
echo "export ZEPHYR_SDK_INSTALL_DIR=$HOME/zephyr-sdk-1.0.1" >>.venv/bin/activate
source .venv/bin/activate
pip install west
echo "
# @copyright Copyright (c) 2026, CurrentMakers.com and the individuals that has contributed to this project.
#
# SPDX-License-Identifier: Apache-2.0

manifest:
projects:
- name: zephyr
revision: v4.4.0
url: https://github.com/zephyrproject-rtos/zephyr
west-commands: scripts/west-commands.yml
import:
name-allowlist:
- littlefs
- picolibc
- hal_stm32
- hal_st
- hal_nordic
- hal_rpi_pico
- cmsis_6
- name: zephyr-cm
url: https://github.com/currentmakers/zephyr-cm
revision: master
path: zephyr-cm
- name: zephyr-ws2812b-pwm
url: https://github.com/currentmakers/zephyr-ws2812b-pwm
revision: master
path: modules/lib/zephyr-ws2812b-pwm
self:
path: .
">west.yml
west init --local
west update
west zephyr-export
west packages pip --install
west sdk install -t arm-zephyr-eabi
west config zephyr.toolchain-variant zephyr
west config zephyr.sdk-install-dir $HOME/zephyr-sdk-1.0.1

Zephyr as base for open PLC platform

Lth — Thu, 30 Apr 2026 06:51:20 GMT

Zephyr as base for open PLC platform

Lth — Thu, 30 Apr 2026 06:48:34 GMT

Created page with "{{Video |series=Colibri Video |number=4 |title=Zephyr as base for open PLC platform |youtube-id=08TAfotF3ok |description=CurrentMakers is a small team of makers and creators,..."

New page

{{Video
|series=Colibri Video
|number=4
|title=Zephyr as base for open PLC platform
|youtube-id=08TAfotF3ok
|description=CurrentMakers is a small team of makers and creators, with decades of experience in electronics, low-level programming, networking and real-time systems.
}}

Hardware Interconnect Bus

Lth — Thu, 30 Apr 2026 00:39:35 GMT

Hardware Interconnect Bus

Niclas — Wed, 29 Apr 2026 02:40:14 GMT

RS-485

Hardware Interconnect Bus

Lth — Wed, 29 Apr 2026 02:00:08 GMT

{{I2C}} (Inter-Integrated Circuit)

File:I2c bus.svg

Lth — Wed, 29 Apr 2026 01:59:40 GMT

Lth uploaded File:I2c bus.svg File uploaded with MsUpload

New page

File uploaded with MsUpload

@@ Line 9: / Line 9: @@
 <div class="res-img">
-[[File:Sl prog schematics rev a.svg|2400px]]
+[[File:Sl prog schematics rev a.svg|1800px]]
 </div>

@@ Line 11: / Line 11: @@
 * [https://stm32world.com/images/6/67/Rm0522-stm32c5-series-armbased-32bit-mcus-stmicroelectronics.pdf STM32C5 Series Reference manual]
-=== STM32C51x ===
+=== STM32C55x ===
-* [https://stm32world.com/images/9/9f/Stm32c551ve.pdf STM32C511 Datasheet]
+* [https://stm32world.com/images/9/9f/Stm32c551ve.pdf STM32C551 Datasheet]
 == STM32F1xx ==

@@ Line 3: / Line 3: @@
 The [[Streamline MCU STM32C511]] is a basic [[Streamline]] [[STM32]] [[MCU]] board build around a [[STM32C511]].
 {{clear}}
 == Specifications ==

← Older revision		Revision as of 00:22, 3 May 2026
(3 intermediate revisions by the same user not shown)
Line 22:		Line 22:
	RS-232 can be considered the granddad of [[Hardware Interconnect Bus]]es. It is a point-to-point bus which will connect exactly two devices with each other. RS-232 would operate at speeds from around 150 bps, through 300, 4800, 9600 and 19200 bps.		RS-232 can be considered the granddad of [[Hardware Interconnect Bus]]es. It is a point-to-point bus which will connect exactly two devices with each other. RS-232 would operate at speeds from around 150 bps, through 300, 4800, 9600 and 19200 bps.

		+	[[File:Two Serial Ports.jpg\|thumb\|300px]]
	RS-232 was first introduced in 1960 and up through the 70s and even 80s it was widely used. Early computers (see image on the right) were monstrous and were often operated through multiple serial terminals. The communication between the central computer and those terminals were almost always (if not always) RS-232.		RS-232 was first introduced in 1960 and up through the 70s and even 80s it was widely used. Early computers (see image on the right) were monstrous and were often operated through multiple serial terminals. The communication between the central computer and those terminals were almost always (if not always) RS-232.

@@ Line 61: / Line 61: @@
 We also need to redirect the <code>st-flash</code> to use the STM32CubeIDE TCL scripts, to support the newer STM32 families, like STM32H5 and STM32C5. So
-   cd streamline-demos/demo1
+== Flashing ==
-   echo "set ST_SCRIPTS ${HOME}/st/stm32cubeide_2.1.1/plugins/com.st.stm32cube.ide.mcu.debug.openocd_2.3.300.202602021527/resources/openocd/st_scripts" >openocd_paths.cfg  # or wherever your stm32cubeide directory is.
+It is really difficult to get flashing to work reliably with new STM32 families, so I suggest the following;
-Unfortunately, I have not gotten the <code>west</code> build system to do the right thing with that.
+# Download the [https://www.st.com/en/development-tools/stm32cubeprog.html STM32CubeProgrammer].
 == Demo 1 ==
     west build --pristine always --board streamline_mcu_stm32f407 ../zephyr/samples/basic/blinky
-    st-flash --connect-under-reset write build/zephyr/zephyr.bin 0x8000000
+    west flash --runner stm32cubeprogrammer
 And any of the following boards can be substituted;

@@ Line 1: / Line 1: @@
 Various notes, investigations and other useful information that might be needed later.
-= Meory Allocations =
+    k_mutex_lock(&data->lock, K_FOREVER);
 This was an investigation into how much RAM is used to instantiate WebAssembly runtimes. 8 wasm files were deployed, each blinking the LED for the respective slot.

@@ Line 2: / Line 2: @@
 |series=STM32 Tutorial Video
 |number=87
-|title=HOWTO STM32C5 First Blink
+|title=STM32C5 First Blink
 |youtube-id=C0ql2WqKzIE
 |description=First attempt to create a Blink application for the new STM32C551 MCU.
 }}

← Older revision		Revision as of 09:26, 1 May 2026
(3 intermediate revisions by the same user not shown)
Line 58:		Line 58:
	west config zephyr.toolchain-variant zephyr		west config zephyr.toolchain-variant zephyr
	west config zephyr.sdk-install-dir $HOME/zephyr-sdk-1.0.1		west config zephyr.sdk-install-dir $HOME/zephyr-sdk-1.0.1
		+
		+	We also need to redirect the <code>st-flash</code> to use the STM32CubeIDE TCL scripts, to support the newer STM32 families, like STM32H5 and STM32C5. So
		+
		+	cd streamline-demos/demo1
		+	echo "set ST_SCRIPTS ${HOME}/st/stm32cubeide_2.1.1/plugins/com.st.stm32cube.ide.mcu.debug.openocd_2.3.300.202602021527/resources/openocd/st_scripts" >openocd_paths.cfg # or wherever your stm32cubeide directory is.
		+
		+	Unfortunately, I have not gotten the <code>west</code> build system to do the right thing with that.
		+
		+	== Demo 1 ==
		+
		+	west build --pristine always --board streamline_mcu_stm32f407 ../zephyr/samples/basic/blinky
		+	st-flash --connect-under-reset write build/zephyr/zephyr.bin 0x8000000
		+
		+	And any of the following boards can be substituted;
		+
		+	streamline_mcu_stm32f407
		+	streamline_mcu_stm32h562
		+	streamline_mcu_stm32c551
		+	streamline_mcu_stm32l475

← Older revision		Revision as of 00:18, 1 May 2026
Line 1:		Line 1:
−	[[Category:STM32]][[Category:Streamline]][[Category:Streamline Software]]{{metadesc\|Zephyr on Streamline boards}}	+	[[Category:STM32]][[Category:Streamline]][[Category:Streamline Software]][[Category:Zephyr]][[Category:Work in progress]]{{metadesc\|Zephyr on Streamline boards}}

	= Installation =		= Installation =

@@ Line 10: / Line 10: @@
       xz-utils file make gcc gcc-multilib g++-multilib libsdl2-dev libmagic1 curl
-    mkdir streamline_demos
+    mkdir streamline-demos
-    cd streamline_demos
+    cd streamline-demos
     python3 -m venv .venv
     echo "export ZEPHYR_BASE=`pwd`/zephyr" >>.venv/bin/activate
@@ Line 18: / Line 18: @@
     source .venv/bin/activate
     pip install west
     echo "
     # @copyright Copyright (c) 2026, CurrentMakers.com and the individuals that has contributed to this project.
@@ Line 47: / Line 48: @@
           path: modules/lib/zephyr-ws2812b-pwm
       self:
-        path: .
+        path: demo1
-    ">west.yml
+    ">demo1/west.yml
-    west init --local
+   cd demo1
     west update
     west zephyr-export

@@ Line 4: / Line 4: @@
 |title=Zephyr as base for open PLC platform
 |youtube-id=08TAfotF3ok
-|description=CurrentMakers is a small team of makers and creators, with decades of experience in electronics, low-level programming, networking and real-time systems.
+|description=In this episode, we introduce the Zephyr Project, a very popular Real-Time Operating System (RTOS) and showcase that the Colibri hardware has (for the most part) been successfully adapted for Zephyr. This is done with "drivers" (zephyr-ws2812b-pwm) and "device trees" (colibri_mcu3, colibri_carrier).
 }}

@@ Line 10: / Line 10: @@
 It is worth noticing that, since a byte is 8 bits, you can often divide the bit-rate by 8 to get the Bytes per second).  Often, however, there are a few extra bits stuffed in the protocol, start, stop, parity, so this calculation really depends on the protocol.
-It should also be mentioned that in the early days the term "baud" was often used ([https://en.wikipedia.org/wiki/Baud Wikipedia article on baud).  Baud is defined as a symbol rate and is typically equivalent of the bit-rate.  However, later generation modems could use various forms of encoding to transfer multiple bits in one symbol which is why the term is rarely seen today.
+It should also be mentioned that in the early days the term "baud" was often used ([https://en.wikipedia.org/wiki/Baud Wikipedia article on baud]).  Baud is defined as a symbol rate and is typically equivalent of the bit-rate.  However, later generation modems could use various forms of encoding to transfer multiple bits in one symbol which is why the term is rarely seen today.
 == Asynchronous ==
@@ Line 59: / Line 63: @@
 Originally the speed was defined as 100 Kbps or 400 Kbps but faster options were possible and today a newer I3C option is emerging.
-[[File:i2c_bus.svg|600px]]
+[[File:i2c_bus.svg|800px]]
 [https://en.wikipedia.org/wiki/I2C Wikipedia article on {{I2C}}]
@@ Line 66: / Line 76: @@
 == SPI (Serial Peripheral Interface) ==
-[[File:SPI_8-bit_circular_transfer.svg|thumb|400px]]
+An option, which is '''much''' faster, is SPI.  SPI is a single master controlling the communication with one slave using one clock and two data lines:
-[[File:SPI_single_slave.svg|400px]]
+[[File:SPI_single_slave.svg|600px]]
-[[File:SPI_three_slaves.svg|400px]]
+There is also a SS (slave select) line so the same bus can be shared with multiple slaves, but under normal circumstances only a single master.
-[[File:SPI_three_slaves_daisy_chained.svg|400px]]
+[[File:SPI_three_slaves.svg|600px]]
 [https://en.wikipedia.org/wiki/Serial_Peripheral_Interface Wikipedia article on SPI]
@@ Line 80: / Line 98: @@
 == CAN ==
-The CAN bus was developed by Bosch in the early 1980s.
+The CAN bus was developed by Bosch in the early 1980s.  It was designed to provide reliable communication in noisy environments and it is typically used in vehicles (cars, ships).  It is a package oriented bus and do away with the concept of master and slave.  Every device on the bus can transmit packages and every device will receive all those packages and individually must decide what to do with them.
 [[File:CAN_ISO11898-3_Network.png|600px]]
@@ Line 96: / Line 116: @@
 == Ethernet ==
 [[File:PC_Network.svg|thumb|200px]]
 [https://en.wikipedia.org/wiki/Ethernet Wikipedia article on Ethernet]

@@ Line 34: / Line 34: @@
 === RS-422 / RS 423 ===
 [[File:RS-422_Network.svg|600px]]
@@ Line 40: / Line 43: @@
 === RS-485 ===
 [[File:RS-485_Network.png|800px]]