BlaatSchaap Wiki - User contributions [en]

MCU32F1

2026-05-17T15:42:14Z

Andre: Add links to STM31F2 and HK32

This page discusses [[STM32F1]] compatible microcontrollers, sometimes referred to as clones.

While most of the xxx32F103 MCUs are drop-in replacements, there are exceptions to this rule.

Data needs to be copies from the old wiki ( https://pmwiki.blaatschaap.be/pmwiki.php/Microcontrollers/MCU32F1 ) and updated.

* [[STM32F1|STM32F1xx]]

* APM32F103
* BLM32F103 (marked not compatible in the past, needs more investigation)
* CH32F103
* CKS32F103
* CS32F103
* FCM32F103
* GD32F103
* [[MH32|HK32F103]]
* MG32F103 (not drop-in compatible, completely different peripheral memory map)
* MH32F103
* MM32F103 (not drop-in compatible, minor changes in the RCC, other peripherals not investigated)
* MS32F103
* RX32F103 (marked not compatible in the past, needs more investigation)

==== Memory Map ====

===== System Memory =====
The system memory is located at 0x1FFFF000 to 0x1FFFF7FF.

It contains the boot rom, this is the internal bootloader which can be entered using the BOOT pins.

At location 0x1FFFF7E0 the flash size is stored.

At location 0x1FFFF7E8 the serial number is stored.

This memory is programmed during production and cannot be altered by the user.

The content of this memory area is one way to identify the MCU we are running on, as it contains the internal bootloader, a different manufacturer puts their own code in there, however, some of them have copied ST's bootloader.

Furthermore, there may be some more identifying bytes in there. It seems for [[MH32F103|MegaHunt's MCUs]] the Serial Number contains some identifying information. Also on the APM32, there is a value at location 0x1FFFF7D0. While Geehy has their own bootloader, older ApexMic versions has ST's.

===== Option Bytes =====
The option bytes are located at 0x1FFFF800

MH32

2026-05-17T14:53:25Z

Andre: Add link to MH2103 reseller

This page discusses a number of MCUs that are expected to share the same or a closely related die.

Disclaimer: the following is speculation:

These microcontrollers are manufacturer by MegaHunt https://megahuntmicro.com/

MegaHunt is the OEM for a number of companies

=== Beijing Hongli Kunpeng International Trade Co., LTD. ===
Website: https://www.hlkpint.com

The site mentions they replace ST parts. The following parts are mentioned:

* HL2030A
* HL2103A
* MH2103C
* HL32F103A (in an image 'table')
* HL32F103C (in an image 'table')

It is assumed the F103A and 2103A are equivalent, as well as the F103C and 2103C.
It is assumed the 2103 is a replacement for F1 series (Cortex M3).
and the 2030 a replacement for F0 series, as it has a Cortex M0 core.
So far the 2103 has been observed.

The datasheets provided for these parts contain a disclaimer mentioning MegaHunt, therefore it has been established MegaHunt is related to these parts.

No official distributor known.

There appear to be little resellers on AliExpress in 2026. Only one found: [https://nl.aliexpress.com/item/1005009501159380.html? https://nl.aliexpress.com/item/1005009501159380.html?]

=== LuatOS ===
Website: https://wiki.luatos.org/

LuatOS offers a series of AIR32F103 microcontrollers, variants with different amounts of flash and pins are available. Mentions of the following variants are made:
* AIR32F103CBT6
* AIR32F103CCT6
* AIR32F103RPT6
* AIR32F103VET6
* AIR32F103VGT6
* AIR32F103ZET6

Availability:

No official distributors known.

There appear to be little resellers on AliExpress in 2026. Only one found: https://nl.aliexpress.com/item/1005009166472987.html

On an LuatOS Air32F103 board:

These boards were available for a while, but appear to be no longer available.

On a Blue Pill:

https://nl.aliexpress.com/item/32719680030.html
Select option "STM32F103C8T6 china"
In February 2023 the board received contained what appears to be a relabelled AIR32F103,
which likely is an MH2103A.

WIZNet https://wiznet.io

WIZNet, the creator of the W5500 Ethernet controller, has created a microcontroller with an integrated ethernet controller. Amongst others, there is the WH55MH32 ( https://wiznet.io/products/mcu-chips/w55mh32 ) which appears to be a MegaHunt core. The part name containing MH32 also suggest this.

No known distributors.

WIZNet Evaluation Board: W55MH32Q-EVB https://nl.aliexpress.com/item/1005010531068787.html

===== TODO: rewrite below =====

There are various git repositories floating around on github for the air32f103, mh32f103 and mh2103c, mentioning the parts are equivalent.

These chips are reported to have additional RAM (96 KiB) that can be unlocked by some magic bytes. Additionally they can run much faster (up to 218 MHz). Furthermore they offer a random number generator and a dac.

In a migration guide it discusses a way to identify the MCU. It seems their serial number starts with a fixed value. The migration guide discusses

MH2103C CBT6 0x1C5A5BBX
MH2103C CCT6 0x1C5A5CCX

The LuatOS wiki mentions the following values

AIR32F103CBT6 0x1A5A5BBX
AIR32F103CCT6 0x1A5A5CCX
AIR32F103RPT6 0x1A6A5CDX
AIR32F103VET6 0x1A8A6DDX
AIR32F103VGT6 0x1A8A6EDX
AIR32F103ZET6 0x1A9A6DDX

Observed values are

AIR32F103 0x1a5a5bb5
MH32F103 0x1a5a5cca

The fist byte in the migration guide is 1C. Observed on the tested MCU it is 1A. This suggests these are equivalent to HL2103A in stead, furthermore we see the BB and CC near the end, suggesting a 128 KiB flash and a 256 KiB flash variant.

There have some issues as discussed in a previous blog post (TODO link)

MH32

2026-05-17T14:46:16Z

Andre: Rewrite in progress

This page discusses a number of MCUs that are expected to share the same or a closely related die.

Disclaimer: the following is speculation:

These microcontrollers are manufacturer by MegaHunt https://megahuntmicro.com/

MegaHunt is the OEM for a number of companies

=== Beijing Hongli Kunpeng International Trade Co., LTD. ===
Website: https://www.hlkpint.com

The site mentions they replace ST parts. The following parts are mentioned:

* HL2030A
* HL2103A
* MH2103C
* HL32F103A (in an image 'table')
* HL32F103C (in an image 'table')

It is assumed the F103A and 2103A are equivalent, as well as the F103C and 2103C.
It is assumed the 2103 is a replacement for F1 series (Cortex M3).
and the 2030 a replacement for F0 series, as it has a Cortex M0 core.
So far the 2103 has been observed.

The datasheets provided for these parts contain a disclaimer mentioning MegaHunt, therefore it has been established MegaHunt is related to these parts.

=== LuatOS ===
Website: https://wiki.luatos.org/

LuatOS offers a series of AIR32F103 microcontrollers, variants with different amounts of flash and pins are available. Mentions of the following variants are made:
* AIR32F103CBT6
* AIR32F103CCT6
* AIR32F103RPT6
* AIR32F103VET6
* AIR32F103VGT6
* AIR32F103ZET6

Availability:

No official distributors known.

There appear to be little resellers on AliExpress in 2026. I have located one: https://nl.aliexpress.com/item/1005009166472987.html

On an LuatOS Air32F103 board:

These boards were available for a while, but appear to be no longer available.

On a Blue Pill:

https://nl.aliexpress.com/item/32719680030.html
Select option "STM32F103C8T6 china"
In February 2023 the board received contained what appears to be a relabelled AIR32F103,
which likely is an MH2103A.

WIZNet https://wiznet.io

WIZNet, the creator of the W5500 Ethernet controller, has created a microcontroller with an integrated ethernet controller. Amongst others, there is the WH55MH32 ( https://wiznet.io/products/mcu-chips/w55mh32 ) which appears to be a MegaHunt core. The part name containing MH32 also suggest this.

No known distributors.

WIZNet Evaluation Board: W55MH32Q-EVB https://nl.aliexpress.com/item/1005010531068787.html

===== TODO: rewrite below =====

There are various git repositories floating around on github for the air32f103, mh32f103 and mh2103c, mentioning the parts are equivalent.

These chips are reported to have additional RAM (96 KiB) that can be unlocked by some magic bytes. Additionally they can run much faster (up to 218 MHz). Furthermore they offer a random number generator and a dac.

In a migration guide it discusses a way to identify the MCU. It seems their serial number starts with a fixed value. The migration guide discusses

MH2103C CBT6 0x1C5A5BBX
MH2103C CCT6 0x1C5A5CCX

The LuatOS wiki mentions the following values

AIR32F103CBT6 0x1A5A5BBX
AIR32F103CCT6 0x1A5A5CCX
AIR32F103RPT6 0x1A6A5CDX
AIR32F103VET6 0x1A8A6DDX
AIR32F103VGT6 0x1A8A6EDX
AIR32F103ZET6 0x1A9A6DDX

Observed values are

AIR32F103 0x1a5a5bb5
MH32F103 0x1a5a5cca

The fist byte in the migration guide is 1C. Observed on the tested MCU it is 1A. This suggests these are equivalent to HL2103A in stead, furthermore we see the BB and CC near the end, suggesting a 128 KiB flash and a 256 KiB flash variant.

There have some issues as discussed in a previous blog post (TODO link)

MH32F103

2026-05-17T13:50:18Z

Andre: Andre moved page MH32F103 to MH32: More variants known, cover them in one article

#REDIRECT [[MH32]]

MH32

2026-05-17T13:50:18Z

Andre: Andre moved page MH32F103 to MH32: More variants known, cover them in one article

This page discusses a number of MCUs that are expected to share the same or a closely related die.

* AIR32F103
* HL2030A
* HL2103A
* MH2103C
* MH32F103A
* MH32F103C

Companies:
* Beijing Hongli Kunpeng International Trade Co., LTD. https://www.hlkpint.com
* Mega Hunt https://megahuntmicro.com/
* LuatOS https://wiki.luatos.org/

On https://www.hlkpint.com it currently lists the HL2030 and HL2103. There are mentions of HL32F103C and HL32F103A. The website shows replacement part numbers for ST, GD and Geehy part numbers.
There are English datasheets for HL2030A, HL2103A and MH2103C, but there are no reference manuals. The datasheets are mention Megahunt as the company.

There are various git repositories floating around on github for the air32f103, mh32f103 and mh2103c, mentioning the parts are equivalent.

These chips are reported to have additional RAM (96 KiB) that can be unlocked by some magic bytes. Additionally they can run much faster (up to 218 MHz). Furthermore they offer a random number generator and a dac.

In a migration guide it discusses a way to identify the MCU. It seems their serial number starts with a fixed value. The migration guide discusses

MH2103C CBT6 0x1C5A5BBX
MH2103C CCT6 0x1C5A5CCX

The LuatOS wiki mentions the following values

AIR32F103CBT6 0x1A5A5BBX
AIR32F103CCT6 0x1A5A5CCX
AIR32F103RPT6 0x1A6A5CDX
AIR32F103VET6 0x1A8A6DDX
AIR32F103VGT6 0x1A8A6EDX
AIR32F103ZET6 0x1A9A6DDX

Observed values are

AIR32F103 0x1a5a5bb5
MH32F103 0x1a5a5cca

The fist byte in the migration guide is 1C. Observed on the tested MCU it is 1A. This suggests these are equivalent to HL2103A in stead, furthermore we see the BB and CC near the end, suggesting a 128 KiB flash and a 256 KiB flash variant.

There have some issues as discussed in a previous blog post (TODO link)

Blue Pill

2026-05-16T06:48:15Z

Andre: Add links to stm32-base.org

The Blue Pill is a popular Core Board containing an [[MCU32F1|STM32F103C8T6 or equivalent MCU]].

The board is believed to have originated from [http://www.vcc-gnd.com/ VCC-GND].

== Blue Pill ==
Blue Pill on [https://stm32-base.org/boards/STM32F103C8T6-Blue-Pill stm32-base.org]

The most common variants are one with a Micro USB connector with 4 mounting tabs, and a variant with a Micro USB connector with 2 mounting tabs. For mechanical stability, the variant with 4 mounting tabs is recommended.

Recently another variant with a USB-C connector has been observed.

{| class="wikitable"
|+ Standard Blue Pill Variants
|-
| [[File:BluePill variant 1.jpg|alt=Blue Pill variant 1|Blue Pill variant, Micro USB with 4 mounting tabs|none|thumb|300x300px]] || [[File:BluePill variant 2.jpg|alt=Blue Pill variant 2|Blue Pill variant, Micro USB with 2 mounting tabs|none|thumb|300x300px]]
|[[File:Blue Pill USB-C.jpg|alt=Blue Pill variant, USB-C|none|thumb|300x300px|Blue Pill variant, USB-C]]
|}

For mechanical stability it is recommended to solder the mounting tabs to the board.
{| class="wikitable"
|+ Solder the USB connector
|-
| [[File:Blue Pill Solder USB 1.jpg|alt=Solder USB connector|Solder USB connector|none|thumb|250x250px]] ||

[[File:BluePill SolderUSB Bijg 02.jpg|alt=Solder USB connector|Solder USB connector|none|thumb|250x250px]]
|}
Boards sold before 2019 are likely to have an incorrect value for resistor R10. The correct value is 1k5.
{|
![[File:R10 is 103 (10K).jpg|alt=R10 is 103 (10K) Incorrect Value|none|thumb|300x300px|R10 is 103 (10K) Incorrect Value]]
![[File:R10 is 152 (1K5) Correct Value.jpg|alt=R10 is 152 (1K5) Correct Value|none|thumb|300x300px|R10 is 152 (1K5) Correct Value]]
|}

== Blue Pill Plus ==
Blue Pill Plus on [https://stm32-base.org/boards/STM32F103C8T6-WeAct-Blue-Pill-Plus-Clone stm32-base.org]

The Blue Pill Plus is a variant made by WeAct.

Be aware of a variation in pinout, where on the original Blue Pill, there is a GND and on the Blue Pill Plus it is a 5V. It is recommended to leave this pin disconnected so both variants will work.

Most notable differences are the Blue Pill Plus got rid of the jumpers, and uses a boot button in stead. Furthermore, the Micro USB connector has been replaced with a USB Type C connector.[[File:Blue Pill Plus.jpg|thumb|300x300px|none|WeAct Blue Pill Plus]]
The schematics are available at github: https://github.com/WeActStudio/BluePill-Plus WeAct sells the following variants:

* APM32F103CBT6
* GD32F103CBT6
* GD32F303CCT6
* CH32F103C8T6
* CH32V203C8T6
* STM32F103C8T6
* STM32F103CBT6

The GD32F303CCT6 is available at the following link https://nl.aliexpress.com/item/1005001986456057.html

The other variants are available at the following link https://nl.aliexpress.com/item/1005001474741936.html

== RobotDyn STM32 MINI ==
RobotDyn STM32 MINI page on [https://stm32-base.org/boards/STM32F103C8T6-RobotDyn-Black-Pill stm32-base.org]

Product page: https://robotdyn.com/stm32-arm-arduino-mini-system-dev-board-blue-pill-with-arduino-bootloader.html

The RobotDyn STM32 MINI, sometimes called RobotDyn Black Pill, should not be confused with a Black Pill. The pinout is the standard BluePill layout.[[File:RobotDyn STM32 MINI.jpg|alt=RobotDyn STM32 MINI|none|thumb|300x300px|RobotDyn STM32 MINI]]

The RobotDyn STM32 MINI seems to be no longer in production.

Blue Pill

2026-05-13T18:38:58Z

Andre: Update Blue Pill Plus

The Blue Pill is a popular Core Board containing an [[MCU32F1|STM32F103C8T6 or equivalent MCU]].

The board is believed to have originated from [http://www.vcc-gnd.com/ VCC-GND].

== Standard Blue Pill ==
The most common variants are one with a Micro USB connector with 4 mounting tabs, and a variant with a Micro USB connector with 2 mounting tabs. For mechanical stability, the variant with 4 mounting tabs is recommended.

Recently another variant with a USB-C connector has been observed.

{| class="wikitable"
|+ Standard Blue Pill Variants
|-
| [[File:BluePill variant 1.jpg|alt=Blue Pill variant 1|Blue Pill variant, Micro USB with 4 mounting tabs|none|thumb|300x300px]] || [[File:BluePill variant 2.jpg|alt=Blue Pill variant 2|Blue Pill variant, Micro USB with 2 mounting tabs|none|thumb|300x300px]]
|[[File:Blue Pill USB-C.jpg|alt=Blue Pill variant, USB-C|none|thumb|300x300px|Blue Pill variant, USB-C]]
|}

For mechanical stability it is recommended to solder the mounting tabs to the board.
{| class="wikitable"
|+ Solder the USB connector
|-
| [[File:Blue Pill Solder USB 1.jpg|alt=Solder USB connector|Solder USB connector|none|thumb|250x250px]] ||

[[File:BluePill SolderUSB Bijg 02.jpg|alt=Solder USB connector|Solder USB connector|none|thumb|250x250px]]
|}
Boards sold before 2019 are likely to have an incorrect value for resistor R10. The correct value is 1k5.
{|
![[File:R10 is 103 (10K).jpg|alt=R10 is 103 (10K) Incorrect Value|none|thumb|300x300px|R10 is 103 (10K) Incorrect Value]]
![[File:R10 is 152 (1K5) Correct Value.jpg|alt=R10 is 152 (1K5) Correct Value|none|thumb|300x300px|R10 is 152 (1K5) Correct Value]]
|}

== Blue Pill Plus ==
[[File:Blue Pill Plus.jpg|thumb|300x300px|none|WeAct Blue Pill Plus]]
The Blue Pill Plus is a variant made by WeAct.

Be aware of a variation in pinout, where on the original Blue Pill, there is a GND and on the Blue Pill Plus it is a 5V. It is recommended to leave this pin disconnected so both variants will work.

Most notable differences are the Blue Pill Plus got rid of the jumpers, and uses a boot button in stead. Furthermore, the Micro USB connector has been replaced with a USB Type C connector.

The schematics are available at github: https://github.com/WeActStudio/BluePill-Plus WeAct sells the following variants:

* APM32F103CBT6
* GD32F103CBT6
* GD32F303CCT6
* CH32F103C8T6
* CH32V203C8T6
* STM32F103C8T6
* STM32F103CBT6

The GD32F303CCT6 is available at the following link https://nl.aliexpress.com/item/1005001986456057.html

The other variants are available at the following link https://nl.aliexpress.com/item/1005001474741936.html

== RobotDyn STM32 MINI ==
[[File:RobotDyn STM32 MINI.jpg|alt=RobotDyn STM32 MINI|none|thumb|300x300px|RobotDyn STM32 MINI]]
Product page: https://robotdyn.com/stm32-arm-arduino-mini-system-dev-board-blue-pill-with-arduino-bootloader.html

The RobotDyn STM32 MINI seems to be no longer in production.

Blue Pill

2026-05-13T18:11:37Z

Andre: Link to VCC-GND

The Blue Pill is a popular Core Board containing an [[MCU32F1|STM32F103C8T6 or equivalent MCU]].

The board is believed to have originated from [http://www.vcc-gnd.com/ VCC-GND].

== Standard Blue Pill ==
The most common variants are one with a Micro USB connector with 4 mounting tabs, and a variant with a Micro USB connector with 2 mounting tabs. For mechanical stability, the variant with 4 mounting tabs is recommended.

Recently another variant with a USB-C connector has been observed.

{| class="wikitable"
|+ Standard Blue Pill Variants
|-
| [[File:BluePill variant 1.jpg|alt=Blue Pill variant 1|Blue Pill variant, Micro USB with 4 mounting tabs|none|thumb|300x300px]] || [[File:BluePill variant 2.jpg|alt=Blue Pill variant 2|Blue Pill variant, Micro USB with 2 mounting tabs|none|thumb|300x300px]]
|[[File:Blue Pill USB-C.jpg|alt=Blue Pill variant, USB-C|none|thumb|300x300px|Blue Pill variant, USB-C]]
|}

For mechanical stability it is recommended to solder the mounting tabs to the board.
{| class="wikitable"
|+ Solder the USB connector
|-
| [[File:Blue Pill Solder USB 1.jpg|alt=Solder USB connector|Solder USB connector|none|thumb|250x250px]] ||

[[File:BluePill SolderUSB Bijg 02.jpg|alt=Solder USB connector|Solder USB connector|none|thumb|250x250px]]
|}
Boards sold before 2019 are likely to have an incorrect value for resistor R10. The correct value is 1k5.
{|
![[File:R10 is 103 (10K).jpg|alt=R10 is 103 (10K) Incorrect Value|none|thumb|300x300px|R10 is 103 (10K) Incorrect Value]]
![[File:R10 is 152 (1K5) Correct Value.jpg|alt=R10 is 152 (1K5) Correct Value|none|thumb|300x300px|R10 is 152 (1K5) Correct Value]]
|}

== Blue Pill Plus ==
[[File:Blue Pill Plus.jpg|thumb|300x300px|none|WeAct Blue Pill Plus]]
The Blue Pill Plus is a variant made by WeAct.

Be aware of a variation in pinout, where on the original Blue Pill, there is a GND and on the Blue Pill Plus it is a 5V. It is recommended to leave this pin disconnected so both variants will work.

Most notable differences are the Blue Pill Plus got rid of the jumpers, and uses a boot button in stead. Furthermore, the Micro USB connector has been replaced with a USB Type C connector.

WeAct sells the following variants:

TODO

== RobotDyn STM32 MINI ==
[[File:RobotDyn STM32 MINI.jpg|alt=RobotDyn STM32 MINI|none|thumb|300x300px|RobotDyn STM32 MINI]]
Product page: https://robotdyn.com/stm32-arm-arduino-mini-system-dev-board-blue-pill-with-arduino-bootloader.html

The RobotDyn STM32 MINI seems to be no longer in production.

Blue Pill

2026-05-13T17:40:36Z

Andre: Add RobotDyn

The Blue Pill is a popular Core Board containing an STM32F103C8T6 or equivalent MCU.

The board is believed to have originated from VCC-GND. However, there are many sellers around selling various variants

== Standard Blue Pill ==
The most common variants are one with a Micro USB connector with 4 mounting tabs, and a variant with a Micro USB connector with 2 mounting tabs. For mechanical stability, the variant with 4 mounting tabs is recommended.

Recently another variant with a USB-C connector has been observed.

{| class="wikitable"
|+ Standard Blue Pill Variants
|-
| [[File:BluePill variant 1.jpg|alt=Blue Pill variant 1|Blue Pill variant, Micro USB with 4 mounting tabs|none|thumb|300x300px]] || [[File:BluePill variant 2.jpg|alt=Blue Pill variant 2|Blue Pill variant, Micro USB with 2 mounting tabs|none|thumb|300x300px]]
|[[File:Blue Pill USB-C.jpg|alt=Blue Pill variant, USB-C|none|thumb|300x300px|Blue Pill variant, USB-C]]
|}

For mechanical stability it is recommended to solder the mounting tabs to the board.
{| class="wikitable"
|+ Solder the USB connector
|-
| [[File:Blue Pill Solder USB 1.jpg|alt=Solder USB connector|Solder USB connector|none|thumb|250x250px]] ||

[[File:BluePill SolderUSB Bijg 02.jpg|alt=Solder USB connector|Solder USB connector|none|thumb|250x250px]]
|}
Boards sold before 2019 are likely to have an incorrect value for resistor R10. The correct value is 1k5.
{|
![[File:R10 is 103 (10K).jpg|alt=R10 is 103 (10K) Incorrect Value|none|thumb|300x300px|R10 is 103 (10K) Incorrect Value]]
![[File:R10 is 152 (1K5) Correct Value.jpg|alt=R10 is 152 (1K5) Correct Value|none|thumb|300x300px|R10 is 152 (1K5) Correct Value]]
|}

== Blue Pill Plus ==
[[File:Blue Pill Plus.jpg|thumb|300x300px|none|WeAct Blue Pill Plus]]
The Blue Pill Plus is a variant made by WeAct.

Be aware of a variation in pinout, where on the original Blue Pill, there is a GND and on the Blue Pill Plus it is a 5V. It is recommended to leave this pin disconnected so both variants will work.

Most notable differences are the Blue Pill Plus got rid of the jumpers, and uses a boot button in stead. Furthermore, the Micro USB connector has been replaced with a USB Type C connector.

WeAct sells the following variants:

TODO

== RobotDyn STM32 MINI ==
[[File:RobotDyn STM32 MINI.jpg|alt=RobotDyn STM32 MINI|none|thumb|300x300px|RobotDyn STM32 MINI]]
Product page: https://robotdyn.com/stm32-arm-arduino-mini-system-dev-board-blue-pill-with-arduino-bootloader.html

The RobotDyn STM32 MINI seems to be no longer in production.

File:RobotDyn STM32 MINI.jpg

2026-05-13T17:35:12Z

Andre:

RobotDyn STM32 MINI

Blue Pill

2026-05-13T17:24:20Z

Andre: Initial page creation

The Blue Pill is a popular Core Board containing an STM32F103C8T6 or equivalent MCU.

The board is believed to have originated from VCC-GND. However, there are many sellers around selling various variants

== Standard Blue Pill ==
The most common variants are one with a Micro USB connector with 4 mounting tabs, and a variant with a Micro USB connector with 2 mounting tabs. For mechanical stability, the variant with 4 mounting tabs is recommended.

Recently another variant with a USB-C connector has been observed.

{| class="wikitable"
|+ Standard Blue Pill Variants
|-
| [[File:BluePill variant 1.jpg|alt=Blue Pill variant 1|Blue Pill variant, Micro USB with 4 mounting tabs|none|thumb|300x300px]] || [[File:BluePill variant 2.jpg|alt=Blue Pill variant 2|Blue Pill variant, Micro USB with 2 mounting tabs|none|thumb|300x300px]]
|[[File:Blue Pill USB-C.jpg|alt=Blue Pill variant, USB-C|none|thumb|300x300px|Blue Pill variant, USB-C]]
|}

For mechanical stability it is recommended to solder the mounting tabs to the board.
{| class="wikitable"
|+ Solder the USB connector
|-
| [[File:Blue Pill Solder USB 1.jpg|alt=Solder USB connector|Solder USB connector|none|thumb|250x250px]] ||

[[File:BluePill SolderUSB Bijg 02.jpg|alt=Solder USB connector|Solder USB connector|none|thumb|250x250px]]
|}
Boards sold before 2019 are likely to have an incorrect value for resistor R10. The correct value is 1k5.
{|
![[File:R10 is 103 (10K).jpg|alt=R10 is 103 (10K) Incorrect Value|none|thumb|300x300px|R10 is 103 (10K) Incorrect Value]]
![[File:R10 is 152 (1K5) Correct Value.jpg|alt=R10 is 152 (1K5) Correct Value|none|thumb|300x300px|R10 is 152 (1K5) Correct Value]]
|}

== Blue Pill Plus ==
[[File:Blue Pill Plus.jpg|thumb|300x300px]]
The Blue Pill Plus is a variant made by WeAct.

Be aware of a variation in pinout, where on the original Blue Pill, there is a GND and on the Blue Pill Plus it is a 5V. It is recommended to leave this pin disconnected so both variants will work.

Most notable differences are the Blue Pill Plus got rid of the jumpers, and uses a boot button in stead. Furthermore, the Micro USB connector has been replaced with a USB Type C connector.

File:Blue Pill USB-C.jpg

2026-05-13T17:22:00Z

Andre:

Blue Pill with USB-C

File:R10 is 152 (1K5) Correct Value.jpg

2026-05-13T17:13:08Z

Andre:

R10 is 152 (1K5) Correct Value

File:R10 is 103 (10K).jpg

2026-05-13T17:12:00Z

Andre:

R10 is 103 (10K)
Incorrect value

File:Blue Pill Plus.jpg

2026-05-13T17:00:10Z

Andre:

Blue Pill Plus

File:BluePill SolderUSB Bijg 02.jpg

2026-05-13T16:39:56Z

Andre:

Solder USB connector

File:Blue Pill Solder USB 1.jpg

2026-05-13T16:39:02Z

Andre:

Blue Pill (variant 1) solder the USB connector.

File:BluePill variant 2.jpg

2026-05-13T16:32:23Z

Andre:

BluePill variant 2

File:BluePill variant 1.jpg

2026-05-13T16:31:24Z

Andre:

Blue Pill, variant 1

STM32F1

2026-04-27T15:49:00Z

Andre: Add die 428, high density value line

This page discusses the STM32F1 series by ST Microcontrollers.

The F1 series were introduced in 2007. This was one of the first Cortex-M based microcontrollers available.

{| class="wikitable"
|+ Variants of the STM32F1 series
|-
! Line !! Part number !! Flash || DIE
|-
| Low- and Medium-density value || STM32F100x{4,6,8,B} || between 16 and 128 KiB|| DIE420
|-
|High-density Value
|STM32F100x{C,D,E}
|between 256 and 512 KiB
|DIE428
|-
| Low-density || STM32F10{1,2,3}x{4,6} || between 16 and 32 KiB || DIE412
|-
| Medium-density || STM32F10{1,2,3}x{8,B} || between 64 and 128 KiB || DIE410
|-
| High-density || STM32F10{1,2,3}x{C.D.E} || between 256 and 512 KiB || DIE414
|-
| XL-density || STM32F10{1,2,3}x{F,G} || between 768 KiB and 1 MiB || DIE430
|-
| Connectivity line || STM32F10{5,7} || || DIE418
|}

MCU32F1

2026-04-19T09:18:47Z

Andre: Updates notes about incompatible parts

This page discusses [[STM32F1]] compatible microcontrollers, sometimes referred to as clones.

While most of the xxx32F103 MCUs are drop-in replacements, there are exceptions to this rule.

Data needs to be copies from the old wiki ( https://pmwiki.blaatschaap.be/pmwiki.php/Microcontrollers/MCU32F1 ) and updated.

* STM32F103

* APM32F103
* BLM32F103 (marked not compatible in the past, needs more investigation)
* CH32F103
* CKS32F103
* CS32F103
* FCM32F103
* GD32F103
* HK32F103
* MG32F103 (not drop-in compatible, completely different peripheral memory map)
* MH32F103
* MM32F103 (not drop-in compatible, minor changes in the RCC, other peripherals not investigated)
* MS32F103
* RX32F103 (marked not compatible in the past, needs more investigation)

==== Memory Map ====

===== System Memory =====
The system memory is located at 0x1FFFF000 to 0x1FFFF7FF.

It contains the boot rom, this is the internal bootloader which can be entered using the BOOT pins.

At location 0x1FFFF7E0 the flash size is stored.

At location 0x1FFFF7E8 the serial number is stored.

This memory is programmed during production and cannot be altered by the user.

The content of this memory area is one way to identify the MCU we are running on, as it contains the internal bootloader, a different manufacturer puts their own code in there, however, some of them have copied ST's bootloader.

Furthermore, there may be some more identifying bytes in there. It seems for [[MH32F103|MegaHunt's MCUs]] the Serial Number contains some identifying information. Also on the APM32, there is a value at location 0x1FFFF7D0. While Geehy has their own bootloader, older ApexMic versions has ST's.

===== Option Bytes =====
The option bytes are located at 0x1FFFF800

MCU32F1

2026-04-18T09:32:33Z

Andre: Adding notes about not-dropin-compatible xx32F103 parts

This page discusses [[STM32F1]] compatible microcontrollers, sometimes referred to as clones.

While most of the xxx32F103 MCUs are drop-in replacements, there are exceptions to this rule.

Data needs to be copies from the old wiki ( https://pmwiki.blaatschaap.be/pmwiki.php/Microcontrollers/MCU32F1 ) and updated.

* STM32F103

* APM32F103
* BLM32F103 (not drop-in compatible)
* CH32F103
* CKS32F103
* CS32F103
* FCM32F103
* GD32F103
* HK32F103
* MG32F103 (not drop-in compatible)
* MH32F103
* MM32F103 (not drop-in compatible)
* MS32F103
* RX32F103 (not drop-in compatible)

==== Memory Map ====

===== System Memory =====
The system memory is located at 0x1FFFF000 to 0x1FFFF7FF.

It contains the boot rom, this is the internal bootloader which can be entered using the BOOT pins.

At location 0x1FFFF7E0 the flash size is stored.

At location 0x1FFFF7E8 the serial number is stored.

This memory is programmed during production and cannot be altered by the user.

The content of this memory area is one way to identify the MCU we are running on, as it contains the internal bootloader, a different manufacturer puts their own code in there, however, some of them have copied ST's bootloader.

Furthermore, there may be some more identifying bytes in there. It seems for [[MH32F103|MegaHunt's MCUs]] the Serial Number contains some identifying information. Also on the APM32, there is a value at location 0x1FFFF7D0. While Geehy has their own bootloader, older ApexMic versions has ST's.

===== Option Bytes =====
The option bytes are located at 0x1FFFF800

MCU32F1

2026-04-18T08:54:02Z

Andre: Adding System Memory

This page discusses [[STM32F1]] compatible microcontrollers, sometimes referred to as clones.

Data needs to be copies from the old wiki ( https://pmwiki.blaatschaap.be/pmwiki.php/Microcontrollers/MCU32F1 ) and updated.

* STM32F103

* APM32F103
* CH32F103
* CKS32F103
* CS32F103
* FCM32F103
* GD32F103
* HK32F103
* MG32F103
* MH32F103
* MM32F103
* MS32F103
* RX32F103

==== Memory Map ====

===== System Memory =====
The system memory is located at 0x1FFFF000 to 0x1FFFF7FF.

It contains the boot rom, this is the internal bootloader which can be entered using the BOOT pins.

At location 0x1FFFF7E0 the flash size is stored.

At location 0x1FFFF7E8 the serial number is stored.

This memory is programmed during production and cannot be altered by the user.

The content of this memory area is one way to identify the MCU we are running on, as it contains the internal bootloader, a different manufacturer puts their own code in there, however, some of them have copied ST's bootloader.

Furthermore, there may be some more identifying bytes in there. It seems for [[MH32F103|MegaHunt's MCUs]] the Serial Number contains some identifying information. Also on the APM32, there is a value at location 0x1FFFF7D0. While Geehy has their own bootloader, older ApexMic versions has ST's.

===== Option Bytes =====
The option bytes are located at 0x1FFFF800

MH32

2026-04-17T15:42:01Z

Andre: Initial page creation

MCU32F1

2026-04-15T13:39:11Z

Andre: Created page with "This page discusses STM32F1 compatible microcontrollers, sometimes referred to as clones. Data needs to be copies from the old wiki ( https://pmwiki.blaatschaap.be/pmwiki.php/Microcontrollers/MCU32F1 ) and updated. * STM32F103 * APM32F103 * CH32F103 * CKS32F103 * CS32F103 * FCM32F103 * GD32F103 * HK32F103 * MG32F103 * MH32F103 * MM32F103 * MS32F103 * RX32F103"

STM32F1

2026-04-15T13:31:44Z

Andre: Initial page creation

This page discusses the STM32F1 series by ST Microcontrollers.

The F1 series were introduced in 2007. This was one of the first Cortex-M based microcontrollers available.

{| class="wikitable"
|+ Variants of the STM32F1 series
|-
! Line !! Part number !! Flash || DIE
|-
| Value Line || STM32F100 || || DIE420
|-
| Low-density || STM32F10{1,2,3}x{4,6} || between 16 and 32 KiB || DIE412
|-
| Medium-density || STM32F10{1,2,3}x{8,B} || between 64 and 128 KiB || DIE410
|-
| High-density || STM32F10{1,2,3}x{C.D.E} || between 256 and 512 KiB || DIE414
|-
| XL-density || STM32F10{1,2,3}x{F,G} || between 768 KiB and 1 MiB || DIE430
|-
| Connectivity line || STM32F10{5,7} || || DIE418
|}

MediaWiki:Sidebar

2025-03-31T17:44:08Z

Andre: Undo revision 49 by Andre (talk)

* navigation
** mainpage|mainpage-description
** recentchanges-url|recentchanges
** randompage-url|randompage
** helppage|help-mediawiki
* SEARCH
* BlaatSchaap
** [https://www.blaatschaap.be Main]
** [https://forum.blaatschaap.be Forum]
** [https://irc.blaatschaap.be IRC]
** [https://radio.blaatschaap.be Radio]
* TOOLBOX
* LANGUAGES

MediaWiki:Sidebar

2025-03-30T11:42:45Z

Andre:

* navigation
** mainpage|mainpage-description
** recentchanges-url|recentchanges
** randompage-url|randompage
** helppage|help-mediawiki
** [https://www.blaatschaap.be Home]
** [https://forum.blaatschaap.be Forum]
** [https://irc.blaatschaap.be IRC]
** [https://radio.blaatschaap.be Radio]
* SEARCH
* TOOLBOX
* LANGUAGES

MediaWiki:Sidebar

2025-03-30T11:41:21Z

Andre: Created page with " * navigation ** mainpage|mainpage-description ** recentchanges-url|recentchanges ** randompage-url|randompage ** helppage|help-mediawiki * SEARCH * BlaatSchaap ** [https://www.blaatschaap.be Main] ** [https://forum.blaatschaap.be Forum] ** [https://irc.blaatschaap.be IRC] ** [https://radio.blaatschaap.be Radio] * TOOLBOX * LANGUAGES"

MoonEdit

2025-03-30T11:18:45Z

Andre: moony runs fine in wine

[[File:MoonEdit.png|alt=MoonEdit|thumb|MoonEdit]]
MoonEdit (WikiPedia: https://en.wikipedia.org/wiki/MoonEdit), commonly referred to as Moony in the BlaatSchaap community,

was a multi-user notepad.
It was popular in the BlaatSchaap community during its early days. The software, however, is no longer

being maintained, and due the closed source nature cannot be forked.

While the author of the software offered downloads for Windows, Linux and FreeBSD, only the Windows version offered the client.

The *NIX versions were server versions only. However, it runs fine in wine, but there are some issues with multi-monitor setups.

Furthermore, there are some limitations to the Windows editor. This was written in an era when unicode was still not commonly used.

Therefore, the tool uses an 8-bit character set. Due the developer being Polish, it uses the Windows-1250 character set,

while in Western Europe, the Windows-1252 character set was the default. This resulted in wrong characters

being displayed beyond ASCII characters.

After the MoonEdit project shut down, alternatives have been considered. One of such alternatives is Gobby, which is an open source project.

While Gobby offers similar functionality, and does not suffer from the character set issues mentioned above, it never gained the popularity Moony had.

Moony

2025-03-30T10:44:05Z

Andre: Redirected page to MoonEdit

#REDIRECT [[MoonEdit]]

MoonEdit

2025-03-30T08:58:04Z

Andre: Screenshot

[[File:MoonEdit.png|alt=MoonEdit|thumb|MoonEdit]]
MoonEdit (WikiPedia: https://en.wikipedia.org/wiki/MoonEdit), commonly referred to as Moony in the BlaatSchaap community,

was a multi-user notepad.
It was popular in the BlaatSchaap community during its early days. The software, however, is no longer

being maintained, and due the closed source nature cannot be forked.

While the author of the software offered downloads for Windows, Linux and FreeBSD, only the Windows version offered the client.

The *NIX versions were server versions only. Furthermore, there are some limitations to the Windows editor. This was written in an

era when unicode was still not commonly used. Therefore, the tool uses an 8-bit character set. Due the developer being Polish, it uses the

Windows-1250 character set, while in Western Europe, the Windows-1252 character set was the default. This resulted in wrong characters

being displayed beyond ASCII characters.

After the MoonEdit project shut down, alternatives have been considered. One of such alternatives is Gobby, which is an open source project.

While Gobby offers similar functionality, and does not suffer from the character set issues mentioned above, it never gained the popularity Moony had.

File:MoonEdit.png

2025-03-30T08:57:48Z

Andre:

MoonEdit

2025-03-30T08:51:05Z

Andre:

MoonEdit (WikiPedia: https://en.wikipedia.org/wiki/MoonEdit), commonly referred to as Moony in the BlaatSchaap community,

was a multi-user notepad.
It was popular in the BlaatSchaap community during its early days. The software, however, is no longer

being maintained, and due the closed source nature cannot be forked.

While the author of the software offered downloads for Windows, Linux and FreeBSD, only the Windows version offered the client.

The *NIX versions were server versions only. Furthermore, there are some limitations to the Windows editor. This was written in an

era when unicode was still not commonly used. Therefore, the tool uses an 8-bit character set. Due the developer being Polish, it uses the

Windows-1250 character set, while in Western Europe, the Windows-1252 character set was the default. This resulted in wrong characters

being displayed beyond ASCII characters.

After the MoonEdit project shut down, alternatives have been considered. One of such alternatives is Gobby, which is an open source project.

While Gobby offers similar functionality, and does not suffer from the character set issues mentioned above, it never gained the popularity Moony had.

MoonEdit

2025-03-30T08:43:00Z

Andre: Created page with "MoonEdit (WikiPedia: https://en.wikipedia.org/wiki/MoonEdit), commonly referred to as Moony in the BlaatSchaap community, was a multi-user notepad. It was popular in the BlaatSchaap community during its early days. The software, however, is no longer being maintained, and due the closed source nature cannot be forked. While the author of the software offered downloads for Windows, Linux and FreeBSD, only the Windows version offered the client. The *NIX versions were ser..."

MoonEdit (WikiPedia: https://en.wikipedia.org/wiki/MoonEdit), commonly referred to as Moony in the BlaatSchaap community, was a multi-user notepad.
It was popular in the BlaatSchaap community during its early days. The software, however, is no longer being maintained, and due the closed source
nature cannot be forked.

While the author of the software offered downloads for Windows, Linux and FreeBSD, only the Windows version offered the client. The *NIX versions
were server versions only. Furthermore, there are some limitations to the Windows editor. This was written in an era when unicode was still not
commonly used. Therefore, the tool uses an 8-bit character set. Due the developer being Polish, it uses the Windows-1250 character set, while in
Western Europe, the Windows-1252 character set was the default. This resulted in wrong characters being displayed beyond ASCII characters.

After the MoonEdit project shut down, alternatives have been considered. One of such alternatives is Gobby, which is an open source project.
While Gobby offers similar functionality, and does not suffer from the character set issues mentioned above, it never gained the popularity
Moony had.

IRC/Services

2025-03-30T07:24:05Z

Andre: add password to RECOVER

On BlaatIRC we offer Anope Services to register nicknames and channels.

To register your nickname, type (replace password and emailaddress with your desired password and your email address)<syntaxhighlight lang="irc">
/MSG NickServ REGISTER password emailaddress
</syntaxhighlight>Then after connecting to IRC, you can identify yourself with<syntaxhighlight lang="irc">
/MSG NickServ IDENTIFY password
</syntaxhighlight>Most IRC clients can do this automatically. Furthermore if your IRC clients supports SASL, that can be used instead, and doing so is preferred.

To register additional nicknames, change to the desired nickname and type<syntaxhighlight lang="irc">
/MSG NickServ GROUP
</syntaxhighlight>To remove a nick from a group, change to that nick and type:<syntaxhighlight lang="irc">
/MSG NickServ UNGROUP
</syntaxhighlight>If your connection got a PING timeout, and you connect with a different nickname, you can regain your nickname with (replacing nickname with the nick you with to recover)<syntaxhighlight lang="irc">
/MSG NickServ RECOVER nickname password
</syntaxhighlight>

IRC/Clients

2025-03-29T11:06:09Z

Andre: KVIrc screenshot now with I/O Dark theme.

=== Clients ===

==== Desktop ====

===== HexChat =====
[[File:HexChat Screenshot (dark theme).png|alt=HexChat Screenshot (dark theme)|none|thumb|HexChat Screenshot (dark theme)]]
Hexchat was the continuation of the X-Chat, when X-Chat was discontinued. Unfortunately, Hexchat itself got discontinued in February 2024.

Website: https://hexchat.github.io/

Source: https://github.com/hexchat

Windows download: https://hexchat.github.io/downloads.html

Linux: In your distro's repository ;)

===== KVIrc =====
[[File:KVIrc with i-o dark theme.png|alt=KVIrc with i/o dark theme|none|thumb|KVIrc with i/o dark theme]]
Website: https://www.kvirc.net/

Downloads (Windows, macOS) https://www.kvirc.net/?id=releases&lang=nl

Linux: In your distro's repository ;)

===== Quassel =====
[[File:Quassel Screenshot.png|alt=Quassel Screenshot|none|thumb|Quassel Screenshot]]
Website: https://quassel-irc.org/

Downloads (Windows, macOS) : https://quassel-irc.org/downloads

Linux: In your distro's repository ;)

==== Mobile ====

===== Goguma =====

[[File:Screenshot 20250328-125022.png|alt=Goguma Screenshot|thumb|Goguma Screenshot|none]]
Website: https://sr.ht/~emersion/goguma/

Source: https://codeberg.org/emersion/goguma

Available on F-Droid: https://f-droid.org/packages/fr.emersion.goguma/

Google Play: https://play.google.com/store/apps/details?id=fr.emersion.goguma.play

Apple App Store: https://apps.apple.com/us/app/goguma-irc/id6470394620

===== Revolution IRC =====
[[File:Revolution IRC Screenshot.png|thumb|none]]
Revolution IRC is an IRC client for Android.

Source: https://github.com/MCMrARM/revolution-irc

Available on F-Droid: https://f-droid.org/packages/io.mrarm.irc/

File:KVIrc with i-o dark theme.png

2025-03-29T11:05:16Z

Andre:

KVIrc with i/o dark theme

IRC/Clients

2025-03-29T10:57:43Z

Andre: Add screenshots

=== Clients ===

==== Desktop ====

===== HexChat =====
[[File:HexChat Screenshot (dark theme).png|alt=HexChat Screenshot (dark theme)|none|thumb|HexChat Screenshot (dark theme)]]
Hexchat was the continuation of the X-Chat, when X-Chat was discontinued. Unfortunately, Hexchat itself got discontinued in February 2024.

Website: https://hexchat.github.io/

Source: https://github.com/hexchat

Windows download: https://hexchat.github.io/downloads.html

Linux: In your distro's repository ;)

===== KVIrc =====
[[File:KVIrc Screenshot.png|alt=KVIrc Screenshot|none|thumb|KVIrc Screenshot]]
Website: https://www.kvirc.net/

Downloads (Windows, macOS) https://www.kvirc.net/?id=releases&lang=nl

Linux: In your distro's repository ;)

===== Quassel =====
[[File:Quassel Screenshot.png|alt=Quassel Screenshot|none|thumb|Quassel Screenshot]]
Website: https://quassel-irc.org/

Downloads (Windows, macOS) : https://quassel-irc.org/downloads

Linux: In your distro's repository ;)

==== Mobile ====

===== Goguma =====

[[File:Screenshot 20250328-125022.png|alt=Goguma Screenshot|thumb|Goguma Screenshot|none]]
Website: https://sr.ht/~emersion/goguma/

Source: https://codeberg.org/emersion/goguma

Available on F-Droid: https://f-droid.org/packages/fr.emersion.goguma/

Google Play: https://play.google.com/store/apps/details?id=fr.emersion.goguma.play

Apple App Store: https://apps.apple.com/us/app/goguma-irc/id6470394620

===== Revolution IRC =====
[[File:Revolution IRC Screenshot.png|thumb|none]]
Revolution IRC is an IRC client for Android.

Source: https://github.com/MCMrARM/revolution-irc

Available on F-Droid: https://f-droid.org/packages/io.mrarm.irc/

File:Quassel Screenshot.png

2025-03-29T10:57:12Z

Andre:

Quassel Screenshot

File:KVIrc Screenshot.png

2025-03-29T10:56:36Z

Andre:

KVIrc Screenshot

File:HexChat Screenshot (dark theme).png

2025-03-29T10:35:00Z

Andre:

HexChat Screenshot (dark theme)

IRC

2025-03-29T10:24:50Z

Andre: Initial page

The BlaatSchaap IRC Server is at

{| class="wikitable"
|+
!
!
|-
|Hostname
|irc.blaatschaap.be
|-
|IPv4
|77.174.203.200
|-
|IPv6
|2a02:a46a:fc8f:1:ba:23ff:fec7:eb03
|-
|Plain Text Ports
|6667 and 8067
|-
|SSL Ports
|6697 and 9999
|-
|IRCd
|UnrealIRCd-6
|-
|Services
|Anope-2
|}

See [[IRC/Services]] for information about how to use the services.

See [[IRC/Clients]] for information about IRC clients

BlaatBot2025

2025-03-29T09:19:39Z

Andre: Initial page

BlaatBot2025 is the fifth generation on BlaatBots.

It is currently under development. It is written in C++ (--std=gnu++26)

In its current phase, the IRC protocol is being implemented. The IRC implementation will include [https://ircv3.net/ IRCv3] and [https://modern.ircdocs.horse/ Modern IRC] features, as well as [https://datatracker.ietf.org/doc/html/draft-pfenning-irc-extensions-04 IRCX] features.

Currently the project is a single binary, but the planning includes making it modular akin [[BlaatBot2009]]. Initially there will be another IRC bot, but using the IRC implementation for an IRC client is considered.

== Compiler Support ==
BlaatBot2025 is developed to compile with the gcc compiler and tested to build with clang as well. Being developed on ArchLinux, the compiler version will get updated during the development. At the time of writing, the g++ version is 14.2.1 and the clang++ version is 19.1.7.

== Operating System Support ==
BlaatBot2025 is developed on ArchLinux, and primary testing happens on Arch. Thus the primary target OS is GNU/Linux.

However, the code is expected to be able to run on any operatering system that implements POSIX APIs. When the project matures, it is planned to test on OpenBSD, NetBSD, DragonFlyBSD as well as HaikuOS.

It is also planned to perform testing on musl/Linux, thus a Linux kernel with a musl C library in stead of the GNU C library. A Linux distro using the musl C library is for example Alpine Linux.

As for non-POSIX operating systems, Microsoft Windows (and ReactOS) might be supported, but is no priority.

musl/Linux support is investigating what the impact of the fact musl does not implement unloading libraries (https://wiki.musl-libc.org/functional-differences-from-glibc.html#Unloading-libraries). One thing we know, it won't call destructors. We can detect that and call them manually, so big deal. But when loading an updated version of the same library, will the remains of the previous version in memory cause issues. Will it re-use the previous symbols? Eg. when the same symbol name was used, but a struct got additional members.

For the BSD family, it's mostly that their socket structs include a length field. Just some #ifdef in the TCPConnection class. Trivial, no problems expected here. Perhaps an issue could be older compiler versions. I'm not really using C++26 features so switching back to an older version should not be an issue.

For Windows support, the main difference is expected to be library loading, and some trivial things such as initialising WinSock. Some features only interesting during debugging, such as setting a thread name, require Windows 10 version 1607 or later. Removing that feature should drop the minimum required version. The challenge for Windows, how low can we go? What's the earliest version we can support?

== Planned Features ==
The initial planned feature set includes: IRC bot functionality, with loadable bot modules. The commands the bot supports will be loaded as a library.

For these libraries, it is planned they'll include two API. A C++ API and a C API. For the C++ API/ABI it will have to turn out if crossing library borders causes issues. It will have to be sure they're linked to the exact same version of the classes. Might have to implement some checking there.

For the C API, when calling from/to the library, some wrapper code will have to run, but otherwise, less strict checking is required when crossing library borders. the C API will allow for language bindings to other languages. It is planned to at least include Pascal bindings, as this was the language BlaatBot2005 was written in.

=== Language Bindings ===
The support of language bindings will be a research project. The last required is as follows: Load a library written in another language from C++, call into that library and register callbacks, have the library call back into the C++ code.

Calling into another language is one thing, but also being able to call back makes it not all languages can be supported easily (there may be a workaround running in a separate process and communicating over sockets, but that ain't the goal here)

The C++ code will offer a C and a C++ API/ABI.

It should be rather easy to get [https://dlang.org/ D] language bindings, as D can directly bind to C++, and D is also supported by the GNU Compiler Collection. So, language bindings to D are expected to be trivial. https://dlang.org/spec/cpp_interface.html

Another language supported by the GNU Compiler Collection is go. As my compiler already supports it, I might give it a try. https://go.dev/doc/install/gccgo#C_Interoperability

Since Rust is getting popular, I might have a look at that language as well. https://docs.rust-embedded.org/book/interoperability/rust-with-c.html

So far, these languages produce libraries native to the operating system they're built for. Next we consider some languages that do not compile to native code:

Take for example Python, as it is a scripting language, once cannot simply create an .so file and load that. It seems the solution Python gives to this is called Embedding. See https://docs.python.org/3/extending/embedding.html

For JavaScript, or formally, ECMAScript, it is also possible to embed an engine https://duktape.org/guide.html#introduction

As for Java, it compiled to byte code, runs in a VM. However, it offers an interoperability layer called JNI. It seems to support calling into, as well as being called, across language barriers. See https://nachtimwald.com/2017/06/17/calling-java-from-c/

As for C#, when running on Windows, calling managed code from unmanaged code can be done easily. https://www.codeproject.com/Tips/695387/Calling-Csharp-NET-methods-from-unmanaged-C-Cplusp However, it won't be trivial to do the same on other operating systems.

Other languages have been proposed include [https://www.lua.org/ Lua] and [https://www.angelcode.com/angelscript/ AngelScript].

BlaatBot2007

2025-03-29T07:08:38Z

Andre: /* User Commandstest */

[[File:BlaatBot2007 Screenshot.png|alt=BlaatBot2007 Screenshot|thumb|BlaatBot2007 Screenshot]]
BlaatBot2007, the third generation of BlaatBots, is the first BlaatBot written in C++.

It's source code is available at https://github.com/BlaatSchaapArchive/blaatbot2007

The bot does not support a configuration file. All settings, such as the server and channel are determined compile time. (This was left as a TODO)

The bot has no static restrains on the number of channels or users it supports, as opposed to earlier BlaatBots.

== Supported Commands ==
BlaatBot2007 has a number of built-in commands, listed below. Additionally, it could parse a text file with simple text substitution commands, originating from a mIRC bot, supplied by Eileen a.k.a. Violet

=== User Commands ===
<nowiki>:</nowiki>test

<nowiki>:</nowiki>os

<nowiki>:</nowiki>lines

<nowiki>:</nowiki>seen

<nowiki>:</nowiki>ul

<nowiki>:</nowiki>isclone

=== Admin Commands ===
<nowiki>:</nowiki>nick

<nowiki>:</nowiki>join

<nowiki>:</nowiki>part

<nowiki>:</nowiki>quit

<nowiki>:</nowiki>refresh

BlaatBot2007

2025-03-28T16:32:05Z

Andre: Change the prefix from ! to :

[[File:BlaatBot2007 Screenshot.png|alt=BlaatBot2007 Screenshot|thumb|BlaatBot2007 Screenshot]]
BlaatBot2007, the third generation of BlaatBots, is the first BlaatBot written in C++.

It's source code is available at https://github.com/BlaatSchaapArchive/blaatbot2007

The bot does not support a configuration file. All settings, such as the server and channel are determined compile time. (This was left as a TODO)

The bot has no static restrains on the number of channels or users it supports, as opposed to earlier BlaatBots.

== Supported Commands ==
BlaatBot2007 has a number of built-in commands, listed below. Additionally, it could parse a text file with simple text substitution commands, originating from a mIRC bot, supplied by Eileen a.k.a. Violet

=== User Commandstest ===
<nowiki>:</nowiki>os

<nowiki>:</nowiki>lines

<nowiki>:</nowiki>seen

<nowiki>:</nowiki>ul

<nowiki>:</nowiki>isclone

=== Admin Commands ===
<nowiki>:</nowiki>nick

<nowiki>:</nowiki>join

<nowiki>:</nowiki>part

<nowiki>:</nowiki>quit

<nowiki>:</nowiki>refresh

BlaatBot2009

2025-03-28T16:23:43Z

Andre: Adding Screenshot

[[File:BlaatBot2009 Screenshot.png|alt=BlaatBot2009 Screenshot|thumb|BlaatBot2009 Screenshot]]
BlaatBot2009 was the fourth generation of BlaatBots. BlaatBot2009 was written in C++.

It's source code is available at https://github.com/BlaatSchaapArchive/blaatbot2009

BlaatBot2009 got a modular design approach,

* Protocol (only IRC was implemented)
* Clients (only BOT was implemented)

The BOT client supported modules itself, implementing the bot commands, however only a test module was implemented.

This project never left its proof-of-concept phase. Mainly due graduating and being too busy with a full-time job afterwards.

While all components were written in C++, the API between these modules was a C API. The reason for this was twofold. At the time André read about potential issues when passing C++ objects between library boundaries, especially on Windows. Furthermore, such design will allow for modules written in other languages.

File:BlaatBot2009 Screenshot.png

2025-03-28T16:23:30Z

Andre:

BlaatBot2009 Screenshot

BlaatBot2007

2025-03-28T16:18:23Z

Andre: Adding Screenshot

[[File:BlaatBot2007 Screenshot.png|alt=BlaatBot2007 Screenshot|thumb|BlaatBot2007 Screenshot]]
BlaatBot2007, the third generation of BlaatBots, is the first BlaatBot written in C++.

It's source code is available at https://github.com/BlaatSchaapArchive/blaatbot2007

The bot does not support a configuration file. All settings, such as the server and channel are determined compile time. (This was left as a TODO)

The bot has no static restrains on the number of channels or users it supports, as opposed to earlier BlaatBots.

== Supported Commands ==
BlaatBot2007 has a number of built-in commands, listed below. Additionally, it could parse a text file with simple text substitution commands, originating from a mIRC bot, supplied by Eileen a.k.a. Violet

=== User Commands ===
!test

!os

!lines

!seen

!ul

!isclone

=== Admin Commands ===
!nick

!join

!part

!quit

!refresh

File:BlaatBot2007 Screenshot.png

2025-03-28T16:18:08Z

Andre:

BlaatBot2007 Screenshot