Index of /releases/firmware/v0.1.6/
[ICO]NameLast modifiedSizeDescription
[PARENTDIR]Parent Directory  -  
[ ]iomixer-bluepill-PB2-128kb-20kb-8MHz-0.1.6.bin2026-09-22 12:24 112K 
[ ]iomixer-bluepill-PC13-128kb-20kb-8MHz-0.1.6.bin2026-09-22 12:24 112K 
[ ]iomixer-512kb-64kb-8MHz-0.1.6.bin2026-09-22 12:24 166K 
[ ]iomixer-256kb-48kb-8MHz-0.1.6.bin2026-09-22 12:24 166K 
[ ]iomixer-512kb-64kb-12MHz-0.1.6.bin2026-09-22 12:24 166K 
[ ]iomixer-256kb-48kb-12MHz-0.1.6.bin2026-09-22 12:24 166K 

The naming of files above is:
variant-flashsize-ramsize-clock-version
Variant mainly refers to internal pin usage, eg. some boards use SPI1 instead of SPI2, or simply don't have as many pins as others. Some 'blue pill' boards have the status LED on different pins, which is what the 'PB2' refers to in those names. For variants titled simply 'iomixer', all nodes and features are included. For others (currently only bluepill) there are less features due to flash size constrants - see below for a list.

Flash size is how large the firmware file can be, and limits how many features can be included in a firmware build. You can see the flash size of your board in the 'Devices' panel.

RAM size is how much memory the program has available while running, and limits the size of configuration you can make (ie. the number of nodes, basically). This number is not so simple to confirm, but you can do it like this:
  1. Set up a completely empty configuration and do 'Upload+write'
  2. Power the board off to completely reset it, and then connect to USB again
  3. In the 'Device' panel, click 'Measure loop time' and check the value of 'Untouched RAM'
The full RAM size of a board will be the empty configuration RAM size plus about 8940 bytes. For example a board with 64kb of RAM has 64*1024 = 65536 bytes total, so with an empty configuration you would expect to see around 56596 bytes untouched (65536-8940).

Clock speed refers to the crystal/oscillator on the board. Currently this is not displayed anywhere in the configurator, but a regular iomixer board will be 12MHz, a blue pill will usually be 8MHz. You can actually run firmware with the wrong clock speed, but anything involving timing will not function correctly (eg. UART communication). So you could set up a 'millis' node, and check that the value it shows matches up with real time.

About 'blue pill' setup

Note: The 'bluepill-PB1' target is intended for Maple Mini, for which this also applies.

For 'bluepill', you will need to add your own SPI flash memory. These are a couple dollars, or under $1 each if you buy 10 at a time, eg. on AliExpress (the 16Mbit one is plenty, no need to buy a larger capacity).

SPI flash connections:
Pin for ignoring the stored config on startup is PA8 (currently same for all boards).

For 'bluepill' the pin to use for RGB LED strings is the same MOSI pin as used for the SPI flash. As a side-effect of having the LEDs driven by the same pin as the SPI flash, you will see them light up in random colors when reading or writing a config (usually just the first 2-3 LEDs in the chain).

List of features included in 'bluepill' builds for v0.1.6:
For a full list of which pins on a bluepill correspond to pin number in the iomixer configurator, check the table at the bottom of this page: https://iomixer.com/prototypes/
Note that some pins don't exist on a bluepill (eg. C10,C11 for UART2) so those features cannot be used.